Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751898AbcDOQHI (ORCPT ); Fri, 15 Apr 2016 12:07:08 -0400 Received: from smtp.citrix.com ([66.165.176.89]:56510 "EHLO SMTP.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751176AbcDOQHH (ORCPT ); Fri, 15 Apr 2016 12:07:07 -0400 X-IronPort-AV: E=Sophos;i="5.24,487,1454976000"; d="scan'208";a="347374335" Subject: Re: [Xen-devel] HVMLite / PVHv2 - using x86 EFI boot entry To: "Luis R. Rodriguez" References: <20160406024027.GX1990@wotan.suse.de> <20160407185148.GL1990@wotan.suse.de> <20160413195257.GB1990@wotan.suse.de> <570F68AB.2040400@citrix.com> <20160414194408.GP1990@wotan.suse.de> <5710BB74.2060409@citrix.com> <20160415153028.GX1990@wotan.suse.de> CC: Matt Fleming , , Michael Chang , Linux Kernel Mailing List , Jim Fehlig , Jan Beulich , "H. Peter Anvin" , Daniel Kiper , "the arch/x86 maintainers" , Takashi Iwai , =?UTF-8?Q?Vojt=c4=9bch_Pavl=c3=adk?= , Gary Lin , xen-devel , Jeffrey Cheung , Juergen Gross , Stefano Stabellini , joeyli , Borislav Petkov , Boris Ostrovsky , Charles Arndol , Andrew Cooper , Julien Grall , Andy Lutomirski , David Vrabel , Linus Torvalds , =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= From: George Dunlap Message-ID: <571110BB.2000408@citrix.com> Date: Fri, 15 Apr 2016 17:03:07 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160415153028.GX1990@wotan.suse.de> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2162 Lines: 42 On 15/04/16 16:30, Luis R. Rodriguez wrote: > On Fri, Apr 15, 2016 at 10:59:16AM +0100, George Dunlap wrote: >> On 14/04/16 20:44, Luis R. Rodriguez wrote: >>> No, I meant to ask, would it be possible to make booting HVMLite using EFI >>> be optional ? That way if you already support EFI that can be used on >>> your entires with some small modifications. >> >> I wasn't talking about actual non-Linux unikernels; I was talking about using >> Linux in the way that unikernels are used ("unikernel-style"). That is, you >> boot a minimal Linux image with a small ramdisk and have a single process >> running as init. For this use case, even an extra megabyte of guest RAM and >> an extra second of boot time is a significant cost. "Use OVMF for domUs" is >> an excellent solution for traditional VMs where you boot a full distro, but >> would impose a significant cost on using Linux in unikernel-style VMs. > > Understood. > >> Whether a stripped-down EFI support would be sufficiently low memory / >> latency for such workloads is an open question that would take time and >> engineering effort to discover. And in any case, it would certainly >> require the maintenance of Yet Another Bootloader in the Xen source tree. > > OVMF is used by ARM, so using it should be a matter of adaptation, and > some changes other than perhaps DT use. Question still stands though, > would it be possible to have HVMLite be using EFI as an option so that > some users could opt-in if they so wish ? Well we definitely intend go have a mode of PVH* which boots OVMF to EFI-enabled guests, if that's what you mean. For one thing, that should in theory allow us to boot Windows guests without needing to spin up qemu to emulate any devices (since OVMF will be able to access the PV devices until the Windows PV drivers come up). Booting to EFI-enabled distros is certainly something we want as well. But we need an option for dom0, and ideally we'd like an option for lightweight Linux guests. It's using EFI for those purposes that we're pushing back on. -George * I'm saying PVH because I hope when everything is sorted out we can just call HVMLite PVH again.