From owner-freebsd-virtualization@freebsd.org  Tue Apr 26 11:29:29 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 AC982B1B34F
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue, 26 Apr 2016 11:29:29 +0000 (UTC)
 (envelope-from prvs=917dd492e=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 5479A1DD4
 for <freebsd-virtualization@freebsd.org>; Tue, 26 Apr 2016 11:29:28 +0000 (UTC)
 (envelope-from prvs=917dd492e=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="356459031"
Date: Tue, 26 Apr 2016 13:29:25 +0200
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Marcin Cieslak <saper@saper.info>
CC: <freebsd-virtualization@freebsd.org>
Subject: Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may
 break ZFS pool?)
Message-ID: <20160426112925.hmijqrxt52kyswfg@mac>
References: <alpine.BSF.2.11.1604251906400.1768@z.fncre.vasb>
 <alpine.BSF.2.11.1604252000401.1768@z.fncre.vasb>
 <alpine.BSF.2.11.1604252048220.1768@z.fncre.vasb>
 <20160426071151.ctzdaehgfhzij6q3@mac>
 <alpine.BSF.2.11.1604260715130.1768@z.fncre.vasb>
 <20160426074302.4i3rv7wd5ogg7ful@mac>
 <alpine.BSF.2.11.1604260811450.1768@z.fncre.vasb>
 <alpine.BSF.2.11.1604260842200.1768@z.fncre.vasb>
 <20160426093556.oxeh5qyafe3ro6xy@mac>
 <alpine.BSF.2.11.1604261036070.1768@z.fncre.vasb>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.11.1604261036070.1768@z.fncre.vasb>
User-Agent: Mutt/1.6.0-neo (2016-04-07)
X-DLP: MIA1
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2016 11:29:29 -0000

On Tue, Apr 26, 2016 at 10:39:06AM +0000, Marcin Cieslak wrote:
> Yes, should be easy. Will try to plug a binary port in.

Thanks :).
 
> By the way, I just managed to crash a whole machine by trying to
> boot Solaris 11.3:
> 
> # builder = "hvm"
> memory = 2048
> vcpus = 1
> name = "Solaris0"
> disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', '/dev/zvol/zroot/solaris0,raw,hda,w' ]
> kernel = "/root/xen/solaris/unix"
> ramdisk = "/root/xen/solaris/boot_archive"
> extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya,livemode=text"
> #boot = "c"
> usbdevice = 'tablet'
> vnc = 1
> vnclisten = '0.0.0.0'
> vif = [ 'bridge=bridge0' ]
> 
> /root/xen/solaris/unix and /root/xen/solaris/boot_archive where extracted from sol-11_3-text-x86.iso
> ("Intel text-only image").

I don't think you can boot Solaris as a PV guest anymore, you should instead 
boot it as a HVM guest. You will have to remove the kernel and ramdisk 
options and instead add builder="hvm" (that you have left commented out).

Roger.