From owner-freebsd-xen@freebsd.org Mon Aug 17 09:05:05 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9E2F9BB2AD for ; Mon, 17 Aug 2015 09:05:05 +0000 (UTC) (envelope-from prvs=664592b7d=roger.pau@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48E131951; Mon, 17 Aug 2015 09:05:04 +0000 (UTC) (envelope-from prvs=664592b7d=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,694,1432598400"; d="scan'208";a="295039907" Message-ID: <55D1A377.2000500@citrix.com> Date: Mon, 17 Aug 2015 11:03:51 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Matthew Grooms , Andriy Gapon CC: FreeBSD XEN Subject: Re: dom0: only on intel? References: In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 09:05:05 -0000 El 13/08/15 a les 17.07, Matthew Grooms ha escrit: > On Aug 13, 2015 5:35 AM, Andriy Gapon wrote: >> >> >> My impression from reading documents on FreeBSD Dom0 is that it is >> supported only on Intel systems (VT-x, EPT, etc). >> So, just to be sure, AMD-V is no go at the moment? >> > > That is correct. FreeBSD dom0 support is PVH mode only. The Xen code does not support AMD CPUs with PVH so this is not unique to the FreeBSD port. I saw a couple of patches floated on the Xen list but they never got committed. Roger would know more about their fate. Matthew is right, there's no AMD support at the moment. I'm currently reworking the whole PVH concept inside the hypervisor, because what's currently inside of Xen is not sustainable in the long term: http://lists.xen.org/archives/html/xen-devel/2015-08/msg00512.html This series is going to miss the next Xen version (4.6, which is due in less than a month probably), but I'm very positive it's going to make it into 4.7. Roger. From owner-freebsd-xen@freebsd.org Mon Aug 17 10:52:18 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 758D59BB078; Mon, 17 Aug 2015 10:52:18 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DB8B16E4; Mon, 17 Aug 2015 10:52:18 +0000 (UTC) (envelope-from royger@gmail.com) Received: by wicne3 with SMTP id ne3so67441447wic.0; Mon, 17 Aug 2015 03:52:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dJRDhwwvvSp6IoXMp8MvZ+YpsSXHK18H7HxExA04EMA=; b=p2c2ti33dlaD1jcEBw8tnrlEf4o0A9KCY8W8c10Sv1Ob++TmkuyCXXPR4F73v4cAW8 fQFxPWu29A//ER7RYpIVKlIBiI3Ib0EjW5mdh1V4Uk81nH9pk91ZTvyEB9SDNGbhiEi1 Cth//fBl5JIvv1DNoZLlAVgpfGc0ub/fdw6tND8WlucJxOFVLq45ri68XD0yU/IAHiLy rxZwmYUlqvElMQ4iz4C9wmKgn1wJli9GUDdF34/IA8+PB2nAAFFZeE36CY3LAtjq1Nt9 6SONcvHO78gMx6200sLyeoozjOrI9usea+GQn+oBuukygUD6BAy3eAHPBCXCjrYCuNrs TG/g== X-Received: by 10.194.185.146 with SMTP id fc18mr1468039wjc.46.1439808736462; Mon, 17 Aug 2015 03:52:16 -0700 (PDT) Received: from [172.16.1.30] (5.Red-79-156-191.staticIP.rima-tde.net. [79.156.191.5]) by smtp.gmail.com with ESMTPSA id by17sm16166459wib.18.2015.08.17.03.52.15 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Aug 2015 03:52:15 -0700 (PDT) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Message-ID: <55D1BCDE.9000709@FreeBSD.org> Date: Mon, 17 Aug 2015 12:52:14 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Outback Dingo CC: freebsd-virtualization@freebsd.org, FreeBSD XEN Subject: Re: HEAD UP: notice to FreeBSD/Xen Dom0 users References: <558CFD11.9050807@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 10:52:18 -0000 Hello, El 15/08/15 a les 15.36, Outback Dingo ha escrit: > HEAD UP on 10.2 the instructions found at > http://wiki.xen.org/wiki/FreeBSD_Dom0 > git branch > master > * stable-4.5 > > > > no longer appear to work > > gmake -j8 install-tools HOSTCC=gcc48 CC=gcc48 > > fails with > __________SNIP__________ > gmake[3]: Entering directory > '/usr/home/dingo/xen/tools/qemu-xen-dir-remote' > GEN config-host.h > GEN trace/generated-tracers.h > GEN trace/generated-tracers.c > LINK qemu-nbd > LINK qemu-img > c++ LINK qemu-io > : error: unknown argument: '-fstack-protector-strong' > c++: error: unknown argument: '-fstack-protector-strong' I've tried to reproduce this with a fresh checkout without success. I guess you have some libraries in your system that change the way Qemu is built. In any case, can you try the following rune: gmake -j8 install-tools HOSTCC=gcc48 CC=gcc48 HOSTCXX=g++48 CXX=g++48 Also, did you perform a distclean before building? (If the tree is not a fresh checkout). Roger.