Good point! Still haven't got my head around grub2 yet. checked one of mine
Ilya and it also has msdos used (must be default). This works for me
(Your device ID's should match yours..)
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64'
--class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 76b3f0ee-34d8-4a13-8a6e-44bd9366cd8c
echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
multiboot /xen-4.0-amd64.gz dom0_mem=2048M
module /vmlinuz-2.6.32-5-xen-amd64 placeholder
root=UUID=25c3ac79-6850-498d-afcf-ea42970e94fd ro quiet
echo 'Loading initial ramdisk ...'
module /initrd.img-2.6.32-5-xen-amd64
}
Regards,
Mark
On Thu, Sep 23, 2010 at 04:49:49PM +0200, Markus Schönhaber wrote:
> 23.09.2010 16:19, Mark Adams:
>
> > your root partition is hd0,0 not hd0,1.
>
> No. Grub2 partition numbers start at 1.
>
> > On Wed, Sep 22, 2010 at 11:35:21PM +0400, Ilya Kozlov wrote:
> >> Hm, the problem is in grub2, with grub1 system boots successfully.
> >>
> >> My currently grub2 menu entry is:
> >> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
> >> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
> >> xen {
> >> insmod ext2
> >> set root=(hd0,1)
> >> multiboot (hd0,1)/boot/xen-4.0-amd64.gz dummy=dummy iommu=off
> >> module (hd0,1)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy root=/dev/sda1
> >> ro
> >> module (hd0,1)/boot/initrd.img-2.6.32-5-xen-amd64
> >>
> >> grub1 menu entry is:
> >> title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
> >> root (hd0,0)
>
> --
> Regards
> mks
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home