From owner-freebsd-xen@freebsd.org  Fri Jul 31 13:47:25 2015
Return-Path: <owner-freebsd-xen@freebsd.org>
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 2A1289AE6DD
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Fri, 31 Jul 2015 13:47:25 +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 142A9197F
 for <freebsd-xen@freebsd.org>; Fri, 31 Jul 2015 13:47:25 +0000 (UTC)
 (envelope-from kpielorz_lst@tdx.co.uk)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 112D29AE6DB; Fri, 31 Jul 2015 13:47:25 +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 0F9A99AE6D9
 for <xen@mailman.ysv.freebsd.org>; Fri, 31 Jul 2015 13:47:25 +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 A235B197E
 for <xen@FreeBSD.org>; Fri, 31 Jul 2015 13:47:23 +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 t6VDl8w2071380
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <xen@FreeBSD.org>; Fri, 31 Jul 2015 14:47:09 +0100 (BST)
 (envelope-from kpielorz_lst@tdx.co.uk)
Date: Fri, 31 Jul 2015 14:47:00 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: xen@FreeBSD.org
Subject: Boot FreeBSD 10 in HVM mode under Xen?
Message-ID: <D313A9262AEA2AC29FCC4A1C@[10.12.30.106]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 13:47:25 -0000


Hi,

Is there any way of booting FreeBSD 10.x as HVM under Xen?

I've tried removing,

   options         XENHVM
   device          xenpci

>From the kernel - but this just panics on boot now.

<https://wiki.freebsd.org/FreeBSD/XenNG> seems to suggest you can no longer 
boot 10 under Xen as HVM?

If I can't boot HVM, I can't get HVM network support (i.e. Realtek) - and I 
can't get that, all the VM's I have to run as HVM due to a number of 
xen/freebsd/network oddities can't be 10.x machines :(

This is painting those roles/systems into non-agile HVM 9.x boxes that have 
no upgrade path now :(

Unless there's a workaround to ditch xn and replace it with re and / or 
boot HVM under FreeBSD 10?

-Karl