From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZwvNF-0000n9-KZ for mharc-grub-devel@gnu.org; Thu, 12 Nov 2015 12:09:25 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44091) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwvNC-0000la-Oy for grub-devel@gnu.org; Thu, 12 Nov 2015 12:09:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwvN9-0002ag-GJ for grub-devel@gnu.org; Thu, 12 Nov 2015 12:09:22 -0500 Received: from smtp.citrix.com ([66.165.176.89]:46464) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwvN9-0002aU-BI for grub-devel@gnu.org; Thu, 12 Nov 2015 12:09:19 -0500 X-IronPort-AV: E=Sophos;i="5.20,282,1444694400"; d="scan'208";a="311864320" Message-ID: <1447348140.18450.92.camel@citrix.com> Subject: Re: [Xen-devel] Uniform commands for booting xen From: Ian Campbell To: Jan Beulich , Vladimir =?UTF-8?Q?=27=CF=86-coder/phcoder=27?= Serbinenko Date: Thu, 12 Nov 2015 17:09:00 +0000 In-Reply-To: <5644C1F502000078000B455F@prv-mh.provo.novell.com> References: <56449726.8090707@gmail.com> <5644C1F502000078000B455F@prv-mh.provo.novell.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-DLP: MIA2 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 66.165.176.89 Cc: The development of GRUB 2 , "xen-devel@lists.xen.org" X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 17:09:23 -0000 On Thu, 2015-11-12 at 08:44 -0700, Jan Beulich wrote: > > > > On 12.11.15 at 14:41, wrote: > > Hello, all. I'd like to have set of commands that would boot xen on all > > platforms. I thought of following set: > >=20 > > xen_hypervisor FILE XEN_OPTIONS > > xen_kernel FILE KERNEL_OPTIONS > > xen_initrd INITRD INITRD INITRD > > all initrds are concatenated. > > xen_xsm ??? >=20 > xen_ucode (and we might add more going forward). I don't see > why the multiboot mechanism (kernel plus any number of modules) > can't be used, without adding any Xen-specific directives. You likely aren't aware that on ARM Xen doesn't boot via multiboot, but via a protocol which involves passing modules in an fdt[0]. I had originally hoped that this would use the same command names in the grub cfg, such that things would just work, however the grub maintainers didn't like that (and I appreciate why). Hence on grub/ARM we already have xen_{hypervisor,kernel,initrd,...}. The question then is what grub-mkconfig (or more precisely /etc/grub.d/20_linux_xen) ought to emit so that things just work on all architectures. The author of the grub/ARM/Xen patches initially made it generate the xen_* namas for arm and the multiboot names for x86, here is Vladimir's feedback on that:=C2=A0http://lists.gnu.org/archive/html/grub-devel/2015-10/msg00133= .html Which I think gets us to approximately today and Vladimir's question. Ian. [0]=C2=A0http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Mu= ltiboot >=20 > Jan >=20 > > On arm64 it would use the arm64 xen FDT protocol but on x86 should we > > use multiboot2 if multiboot2 header is present and multiboot otherwise? > > Or do xen devs have other preferences? >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel