From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Jan Beulich" <JBeulich@suse.com>,
"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] Uniform commands for booting xen
Date: Thu, 12 Nov 2015 16:46:56 +0000 [thread overview]
Message-ID: <5644C280.9080606@citrix.com> (raw)
In-Reply-To: <5644C1F502000078000B455F@prv-mh.provo.novell.com>
On 12/11/15 15:44, Jan Beulich wrote:
>>>> On 12.11.15 at 14:41, <phcoder@gmail.com> 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
next prev parent reply other threads:[~2015-11-12 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 13:41 Uniform commands for booting xen Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-12 15:44 ` [Xen-devel] " Jan Beulich
2015-11-12 16:46 ` Andrew Cooper [this message]
2015-11-12 16:58 ` Andrei Borzenkov
2015-11-12 17:08 ` Jan Beulich
2015-11-12 17:11 ` Andrei Borzenkov
2015-11-12 17:09 ` Ian Campbell
2015-11-13 7:48 ` Jan Beulich
2015-11-13 9:04 ` Andrei Borzenkov
2015-11-13 9:50 ` Ian Campbell
2016-01-11 14:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-11 14:32 ` Jan Beulich
2016-01-11 14:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-11 15:36 ` Jan Beulich
2016-01-18 10:28 ` Ian Campbell
2016-01-22 9:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-13 9:48 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5644C280.9080606@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).