From owner-freebsd-virtualization@freebsd.org  Tue Apr 26 09:36:05 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 9503DAACC1D
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue, 26 Apr 2016 09:36:05 +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 545751D22
 for <freebsd-virtualization@freebsd.org>; Tue, 26 Apr 2016 09:36:04 +0000 (UTC)
 (envelope-from prvs=917dd492e=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="356435101"
Date: Tue, 26 Apr 2016 11:35:56 +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: <20160426093556.oxeh5qyafe3ro6xy@mac>
References: <alpine.BSF.2.11.1604232216330.1768@z.fncre.vasb>
 <20160425084714.64ejioyqgquwu4gw@mac>
 <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.11.1604260842200.1768@z.fncre.vasb>
User-Agent: Mutt/1.6.0-neo (2016-04-07)
X-DLP: MIA2
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 09:36:05 -0000

On Tue, Apr 26, 2016 at 09:24:30AM +0000, Marcin Cieslak wrote:
> I got lazy and I have downloaded
> 
> https://sourceforge.net/projects/edk2/files/OVMF/OVMF-X64-r15214.zip/download
> 
> recompiled xen-tools by adding to xen-tools/Makefile
> 
> CONFIGURE_ARGS+=        --enable-ovmf
> CONFIGURE_ARGS+=        --with-system-ovmf=/root/xen/OVMF.fd
> 
> and worked pretty much out of the box.

Oh, thanks for the info, I didn't know OVMF provided pre-compiled binaries. 
This should make adding a OVMF port trivial. Would you like to take a stab 
at adding such a port and wiring it into the xen-tools package?
 
Roger.