From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 59F9A1A1DEE for ; Thu, 8 Sep 2016 02:38:12 -0700 (PDT) X-IronPort-AV: E=Sophos;i="5.30,298,1470700800"; d="scan'208";a="377019844" Date: Thu, 8 Sep 2016 10:38:09 +0100 From: Anthony PERARD To: , Jordan Justen , Laszlo Ersek CC: Message-ID: <20160908093809.GR1847@perard.uk.xensource.com> MIME-Version: 1.0 User-Agent: Mutt/1.6.2 (2016-07-01) X-DLP: MIA2 Subject: OVMF for Xen PVH X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2016 09:38:12 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Hello, We are introducing a new virtualisation mode in Xen called PVHv2 (also called hvmlite in the past). We would like to have a UEFI firmware running on it to make it easier to start a guest. (Right now, I think it involves supplying the guest kernel to the guest config, like a PV guest.) I'm exploring different possibility of what could be done, and what should be avoided. It would be nice to have only one binary for both PVHv2 guest and HVM guest. Would it be possible to introduce a different entry point in OVMF? The current one cannot be used at the start of the day of a PVHv2 guest. If not, we'll try to use the current entry point or create a new package like it has been done for Xen on ARM. Thanks for any feedback, -- Anthony PERARD