Robert Elz <kre%munnari.OZ.AU@localhost> writes: > I haven't been reading this thread, but why? What's supposed to be > the advantage of pygrub over a normal NetBSD Xen boot (which doesn't > require mangling the image file). Is it just that this way the kernel > booted lives inside the filesystem? Personally I would see that as > a disadvantage - I actually have a 6.1_something kernel in /netbsd > inside my DomU, but I boot 6.99.something (as I need wedge autodiscovery). > > For booting different kernels, just use different Xen configs. That works mostly fine if you control the dom0. In a VPS environment, you have limited access via tools. See linode or prgmr as examples. Further, py-grub lets us run NetBSD on systems where they only think about Linux. Also, having the kernel in the domU makes it behave the same way that a physical system behaves, and the same scripts (assuming they check the kernel name) can be used to upgrade, in the same way. As I understand it, there's also pvgrub, which seems to be a program that runs in the domU as the kernel, and uses PV ops to read the disk. So pvgrub is stored in and run from the dom0, but then lets one configure various kernels and even opperating systems just by manipulating the domU disk image.
Attachment:
pgpLBUCGAIQIj.pgp
Description: PGP signature