From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Uniform commands for booting xen Date: Thu, 12 Nov 2015 16:46:56 +0000 Message-ID: <5644C280.9080606__26679.5634794564$1447346938$gmane$org@citrix.com> References: <56449726.8090707@gmail.com> <5644C1F502000078000B455F@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5644C1F502000078000B455F@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3A=?= =?UTF-8?B?aGNvZGVyJyBTZXJiaW5lbmtv?= Cc: The development of GRUB 2 , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 12/11/15 15:44, 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: >> >> xen_hypervisor FILE XEN_OPTIONS >> xen_kernel FILE KERNEL_OPTIONS >> xen_initrd INITRD INITRD INITRD >> all initrds are concatenated. >> xen_xsm ??? > 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. I also don't see why multiple directives are necessary or useful. All that matters is that the xen binary gets started at any of its optional entry points, and that there are one or more modules loaded. ~Andrew