From owner-freebsd-xen@freebsd.org Sat Apr 1 22:30:48 2017 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 E0DABD29870 for ; Sat, 1 Apr 2017 22:30:48 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "saper.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E31D1D6 for ; Sat, 1 Apr 2017 22:30:48 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id v31MUiRA070214 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 1 Apr 2017 22:30:44 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1491085844; bh=+nGtmq4NCOG7K/549dGwbKNVwqvY0OaGTMDqiRq/ZQE=; h=Date:From:To:Subject:In-Reply-To:References; b=KW770qyuzzWVgolhEHR4w0P7JZCL0GNgrODfBAeDhSzmGZvik6WHjKQPUJdWYlWL2 6NnbiFt3wsBNCrOc0ymgrnb+CgGs/j6wZPQ0AOvYlnK+BGTZKSSkY6L4bMESv0eYd8 U0OP/jgtqV5UC666ABQW844nllM2jRF9BLsqpu/g= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id v31MUhDg070211 for ; Sat, 1 Apr 2017 22:30:44 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Sat, 1 Apr 2017 22:30:43 +0000 From: Marcin Cieslak To: freebsd-xen@freebsd.org Subject: Re: UEFI trouble with OVMF under Xen - nothing boots - SOLVED In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2017 22:30:49 -0000 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 noise! Marcin