[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <526804BC02000078000A56E4@nat28.tlf.novell.com>
Date: Wed, 23 Oct 2013 17:17:48 +0100
From: "Jan Beulich" <jbeulich@...e.com>
To: <ian.campbell@...rix.com>, <konrad.wilk@...cle.com>
Cc: <ross.philipson@...rix.com>, <stefano.stabellini@...citrix.com>,
<grub-devel@....org>, <david.woodhouse@...el.com>,
<richard.l.maliszewski@...el.com>, <xen-devel@...ts.xen.org>,
<boris.ostrovsky@...cle.com>, <daniel.kiper@...cle.com>,
<pjones@...hat.com>, <mjg59@...f.ucam.org>,
<linux-kernel@...r.kernel.org>, <keir@....org>
Subject: Re: [Xen-devel] EFI and multiboot2 devlopment work for Xen
>>> Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> 10/23/13 3:15 PM >>>
>On Wed, Oct 23, 2013 at 09:32:30AM +0100, Ian Campbell wrote:
>> Am I correct that xen.efi today can be loaded from grub today using the
>> chainload command? Whereupon it will parse the xen.cfg and load the dom0
>> kernel and load things from FAT etc and everything just works. IOW
>> UEFI -> chainload(Xen)
>> and
>> UEFI -> chainload(grub) -> chainload(Xen)
>> work equivalently from the POV of Xen?
>
>Yes. However it does require the user to know the magic values in the Xen
>configuration file and setup the chainload stanze correctly. That means
>if a user wishes to modify some of the bootup options they have to modify
>the Xen configuration file. No runtime changes.
Not necessarily - there's no reason for it being impossible to specify options
in the GrUB entry, nor for option added on the GrUB prompt (or its graphical
equivalent) to be passed to the chain loaded binary. If that doesn't already
work, it can't be really hard to implement.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists