From owner-freebsd-xen@freebsd.org Fri Jul 31 14:38:48 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 DA2A19AF13A for ; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BDA4718D0 for ; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id BC8149AF139; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) Delivered-To: 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 BC18A9AF138 for ; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F6D618CF for ; Fri, 31 Jul 2015 14:38:47 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6VEclU0074850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jul 2015 15:38:48 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Fri, 31 Jul 2015 15:38:39 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , xen@FreeBSD.org Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? Message-ID: In-Reply-To: <55BB8392.4050000@citrix.com> References: <55BB8392.4050000@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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: Fri, 31 Jul 2015 14:38:48 -0000 --On 31 July 2015 16:17 +0200 Roger Pau Monn=C3=A9 = wrote: > This is a bug then. You should be able to boot without XENHVM/xenpci, > and get a pure HVM guest with no PV devices at all. I'm just setting up another less critical system to reproduce it. To=20 confirm, I just take GENERIC and remove 'XENHVM' and 'xenpci', and it=20 should boot without PV. I'll post the results / panic & exact versions when I get it (though some=20 goes off the top of the console =3D could be interesting). > Since this seems to be getting quite popular (booting without PV > devices), I think adding a sysctl to disable PV nics and PV hard drives > would be interesting. We could still use some of the PV goodies, like > the timer. Can you technically have a system that has HVM network (i.e. realtek) but=20 still has disk PV, and/or is agile? (i.e. can run xen-tools)? That'd kind of be a 'perfect' workaround for all our network woes (openvpn, = routing etc.) at the moment - even if the performance of HVM re0 isn't as=20 good as a PV xn0 Cheers, -Karl