From owner-freebsd-xen@freebsd.org  Mon Apr  3 08:58:27 2017
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 C5B20D27522
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  3 Apr 2017 08:58:27 +0000 (UTC)
 (envelope-from prvs=259eeba07=roger.pau@citrix.com)
Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [185.25.65.24])
 (using TLSv1.2 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "DigiCert SHA2 Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4D92D9C2
 for <freebsd-xen@freebsd.org>; Mon,  3 Apr 2017 08:58:26 +0000 (UTC)
 (envelope-from prvs=259eeba07=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.36,269,1486425600"; d="scan'208";a="43592821"
Date: Mon, 3 Apr 2017 09:58:00 +0100
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Marcin Cieslak <saper@saper.info>
CC: <freebsd-xen@freebsd.org>
Subject: Re: UEFI trouble with OVMF under Xen - nothing boots - SOLVED
Message-ID: <20170403085800.utw7wialhz4e5kl2@dhcp-3-128.uk.xensource.com>
References: <alpine.BSF.2.20.1704011454040.1243@z.fncre.vasb>
 <alpine.BSF.2.20.1704011547270.1243@z.fncre.vasb>
 <alpine.BSF.2.20.1704012227150.1243@z.fncre.vasb>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.20.1704012227150.1243@z.fncre.vasb>
User-Agent: NeoMutt/20170306 (1.8.0)
X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To
 AMSPEX02CL02.citrite.net (10.69.22.126)
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2017 08:58:27 -0000

On Sat, Apr 01, 2017 at 10:30:43PM +0000, Marcin Cieslak wrote:
> On Sat, 1 Apr 2017, Marcin Cieslak wrote:
> 
> > On Sat, 1 Apr 2017, Marcin Cieslak wrote:
> > 
> > > This is a follow up to the UEFI Windows boot problems
> > > reported after 4.7 got imported:
> > > 
> > > https://lists.freebsd.org/pipermail/freebsd-xen/2016-June/002745.html
> > > 
> > > I am using FreeBSD 12.0-CURRENT #6 r314708: Mon Mar  6 13:09:31 UTC 2017     root@o.saper.info:/usr/obj/usr/src/sys/GENERIC  amd64 as dom0
> > > 
> > > In the 4.5 times I could install and boot Windows 2016 Technical Preview 5 without
> > > major problems. In fact, I started using this as my default Windows
> > > environment - it was working very well and very fast.
> > 
> 
> So, for the archives:
> 
> I have compiled the newest OVMF git master in the DEBUG mode and found out
> that under normal qemu both I/O debug port 0x402 logging or serial port logging
> (depending how OVMF got compiled) do work.
> 
> I have never been getting debug output from the OVMF started by Xen.
> What I didn't know is that firmware images are compiled into the hvmloader
> so that just replacing the ovmf.bin DOES NOT work.
> 
> I must have had a 32-bit ovmf.bin on the filesystem when I was compiling
> xen-tools; after replacing it with a 64-bit version and rebuilding
> xen-tools things started to work.

Sorry for not being able to help. Now that you got this working, do you think
you could send a patch(es) to add OVMF support to the xen-tools package? I'm
more than happy to add this functionality (and maintain the OVMF package if
needed).

Thanks, Roger.