xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* pvgrub --> kexec
@ 2011-11-19  3:38 George Shuklin
  2011-11-23  8:11 ` Daniel Kiper
  0 siblings, 1 reply; 2+ messages in thread
From: George Shuklin @ 2011-11-19  3:38 UTC (permalink / raw)
  To: xen-devel

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: pvgrub --> kexec
  2011-11-19  3:38 pvgrub --> kexec George Shuklin
@ 2011-11-23  8:11 ` Daniel Kiper
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Kiper @ 2011-11-23  8:11 UTC (permalink / raw)
  To: George Shuklin; +Cc: xen-devel

On Sat, Nov 19, 2011 at 07:38:50AM +0400, George Shuklin wrote:
> 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.

kexec/kdump is partialy supported by Xen. Xenlinux Ver. 2.6.18
supports kexec/kdump in dom0. As I know Olaf Hering works (still ???)
on support for kexec/kdump for PV-on-HVM domains. Currently my work
focuses on kexec/kdump support for domU for Xenlinux Ver. 2.6.18.
Later it will be ported to mainline kernel. I am going to publish
this about Feb 2012. Additionally, I am going to prepare kexec/kdump
support for dom0 for mainline kernel.

Daniel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-11-23  8:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-19  3:38 pvgrub --> kexec George Shuklin
2011-11-23  8:11 ` Daniel Kiper

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).