From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zwv21-0007c5-16 for mharc-grub-devel@gnu.org; Thu, 12 Nov 2015 11:47:29 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36675) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwv1z-0007Yt-0j for grub-devel@gnu.org; Thu, 12 Nov 2015 11:47:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zwv1v-0004KM-0Q for grub-devel@gnu.org; Thu, 12 Nov 2015 11:47:26 -0500 Received: from smtp.citrix.com ([66.165.176.89]:61820) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwv1u-0004JQ-Py for grub-devel@gnu.org; Thu, 12 Nov 2015 11:47:22 -0500 X-IronPort-AV: E=Sophos;i="5.20,282,1444694400"; d="scan'208";a="311856690" Message-ID: <5644C280.9080606@citrix.com> Date: Thu, 12 Nov 2015 16:46:56 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Jan Beulich , =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3A=?= =?UTF-8?B?aGNvZGVyJyBTZXJiaW5lbmtv?= Subject: Re: [Xen-devel] Uniform commands for booting xen References: <56449726.8090707@gmail.com> <5644C1F502000078000B455F@prv-mh.provo.novell.com> In-Reply-To: <5644C1F502000078000B455F@prv-mh.provo.novell.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-DLP: MIA1 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 16:47:28 -0000 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