RE: PVM guests and p[yv]grub and the extra= parameter

["Dan Magenheimer" <dan.magenheimer@oracle.com>]

> > Another possibility would be to provide the menu.lst as a 
> ramdisk.  We
> > keep the confinment of grub inside the domain, but still 
> provide full
> > configurability.
> 
> That's a neat solution.  Still not as clean as an extra=
> vm.cfg parameter though.  (Think about instructing a novice
> user over the phone how to construct a grub.conf file from
> scratch!)  But it's much better than the other alternatives.

Thinking about this a bit more, were you thinking about
thh vm config file providing a file name on the dom0
filesystem?  Or providing the entire menu.lst file in
the vm config file.  Or either?

It would be neat if you could put in the vm config file
something like (as a contrived example):

bootconfig="
default=0
timeout=10
title Linux 2.6.25
	kernel /vmlinuz-2.6.25 ro root=xxx
      initrd /initrd-2.6.25.img
title Linux 2.6.25
	kernel /vmlinuz-2.6.25 ro root=xxx debug
      initrd /initrd-2.6.25.img
"

Then you could just tell a customer to change
default=0 to default=1, or change debug to,
for example, clock=pit, or whatever.

Thanks,
Dan