From: Michael Paesold <mpaesold@gmx.at>
To: Ewan Mellor <ewan@xensource.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: Deficiencies in guest bootloader design
Date: Thu, 13 Apr 2006 21:19:59 +0200 [thread overview]
Message-ID: <443EA45F.4040002@gmx.at> (raw)
In-Reply-To: <20060413151044.GB23641@leeni.uk.xensource.com>
Ewan Mellor wrote:
>> Is there anyone working on bootloader improvements? If not, is a change to
>> move the bootloader stuff from xm to Xend acceptable? In that case I could
>> try to come up with a patch.
>
> Certainly such a patch would be accepted. There was a long thread discussing
> bootloaders recently -- you should dig it out of the archive and see what the
> conclusions were -- there seem to be a few competing ideas for bootloader
> support in Xen (pygrub and domUloader being the two prominent ones). If you
> were going to put some effort into this, it would be appreciated by a number
> of the Xen users, certainly.
I have read through the threads about pygrub/domUloader in the archives,
although I have not found discussion about the initial inclusion of pygrub.
I mostly see discussions about the actual features of the boot loaders
themselves, not really about integration relevant to my question.
I see the most important question is that of interaction with the user,
since that seems to be the main reason for bootloader being invoked from xm
instead of Xend. I will study the code to see what can be done.
I appreciate any input or help!
Best Regards,
Michael
prev parent reply other threads:[~2006-04-13 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 14:29 Deficiencies in guest bootloader design Michael Paesold
2006-04-13 14:34 ` Matt Ayres
2006-04-13 17:28 ` Michael Paesold
2006-04-13 15:10 ` Ewan Mellor
2006-04-13 15:24 ` Anthony Liguori
2006-04-13 15:36 ` Ewan Mellor
2006-04-13 15:40 ` Anthony Liguori
2006-04-13 18:09 ` Michael Paesold
2006-04-13 17:13 ` Michael Paesold
2006-04-13 19:19 ` Michael Paesold [this message]
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=443EA45F.4040002@gmx.at \
--to=mpaesold@gmx.at \
--cc=ewan@xensource.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.