From: George Shuklin <shuklin@selectel.ru>
To: xen-devel@lists.xensource.com
Subject: pvgrub --> kexec
Date: Sat, 19 Nov 2011 07:38:50 +0400 [thread overview]
Message-ID: <4EC724CA.7040609@selectel.ru> (raw)
Good day.
Right now we have pvgrub and pygrub as loaders. Pygrub is more mature,
pvgrub is safer and more 'right' stuff to have.
But even the pvgrub is still have one real problem: we need to write our
own domU operating system with support of bunch of filesystems, hardly
to create interactivity, limited network capabilities (...yep, I can be
nice to have networking at boot time).
How about different approach? If we run linux with specially crafted
initrd, which will look around, see correct partition, mount it (in
domU!), get kernel, show menu, do networking and prepare the coffee for
admin. After that it will to kexec to found kernel with found initrd
with required argument.
No any dangerous dom0 manipulation with VDI, no more modules
synchronization problem (in case 'external' kernel loading). Easy to
create menus (just any ncurses application), ideal pre-boot
configuration environment for appliances (I ask user about settings and
boot real kernel with asked parameters).
The single problem: kexec is not supporting xen.
next reply other threads:[~2011-11-19 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 3:38 George Shuklin [this message]
2011-11-23 8:11 ` pvgrub --> kexec Daniel Kiper
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=4EC724CA.7040609@selectel.ru \
--to=shuklin@selectel.ru \
--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 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).