On Tue, May 25, 2010 at 4:29 PM, Ian Campbell <[email protected]> wrote:
> On Tue, 2010-05-25 at 23:38 +0800, Asias He wrote:
>
> This is a known issue due to the grub2 maintainers arbitrarily changing
> the semantics of the modules lines compared with grub1.
Is it necessary to file a bug to grub2, or there is already one?
And the update-grub allways add the dom0 kernel only entry to grub.cfg
instead of add xen.gz combined with the dom0 kernel.
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-xen-686" --class
debian --class gnu-linux --class gnu --class os {
insmod ext2
set root='(/dev/sda,5)'
search --no-floppy --fs-uuid --set c006ca40-0b79-426e-b8d3-5fa5b3696bea
echo Loading Linux 2.6.32-5-xen-686 ...
linux /boot/vmlinuz-2.6.32-5-xen-686 root=/dev/sda5 ro
quiet vga=0x317
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-5-xen-686
}
>
> Please see the section of http://wiki.xen.org/xenwiki/XenCommonProblems
> titled "Booting Xen with GRUB2 fails?" for a workaround.
thanks for the workaround.
--
Best Regards
Asias He
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
