Jozef Uhliarik napsal(a):
Hello,
On Friday 26 June 2009 16:49:13 PGNet Dev wrote:
hi joseph,
On Fri, Jun 26, 2009 at 1:19 AM, josef reidinger
wrote: (1) correctly use/write,
root (hd0)
instead of
root (hd0,0) Because it is not correct, root set device to which is write relative path in section. it must be partition not disc. i'm not clear as to what's "not correct".
Grub's fine with partionless disks ... and, in my scenario,
title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen
root = (hd0), NOT (hd0,0) is required.
There _is_ an issue with it recognizing filesystems when on a pv-grub'd DomU (cref: Bug 516677 - grub fails to recognize filesystem on partitionless hd, in DomU booted on pv-grub Dom0).
Please look at your bugreport bnc#516677 again. The error message about wrong filesystem is generated because you used disk intead of partition:
from your bugreport:
grub> root (hd0) root (hd0) Filesystem type unknown, using whole disk grub>
If you enter root (hd0,0) instead of root (hd0) what happend?
(2) write the kernel/initrd entries as
kernel /boot/vmlinuz... initrd /boot/initrd...
not,
kernel /vmlinuz... initrd /initrd... Because you have separated boot partition and perl-Bootloader detect it and correctly write section. It cannot be modified...only option is change fstab to not include separate /boot then that's a problem, isn't it?
again, for my situation:
title PVGRUB root (hd0) kernel /boot/vmlinuz-2.6.27.25-9-xen root=/dev/xvdc resume=/dev/xvdb kbdtype=us text nofb selinux=0 edd=off splash=silent noshell showopts initrd /boot/initrd-2.6.27.25-9-xen
/boot/vmlinuz... is required ...
if just /vmlinuz is used, the system -- not finding the kernel/initrd -- simply fails to boot.
If you use root (hd0,0) instead of root (hd0) you probably not need /boot in front of /vmlinuz-....
Have a lot of fun.
Jozef
If I good understand question, then problem is that is used in this case some partition-less technology, so grub should act on whole disc and problem is that perl-bootloader doesn't support this case and don't expect it. So if I good understand it, could you provide some resource about this technology? Also as that it is not supported It should not be reported as bug but as enhancement and new feature to features.opensuse.org. But if you use just one kernel then you can set sections to symlink /boot/vmlinux and disable perl-Bootloader to modify menu.lst during upgrade ( set BOOTLOADER_TYPE to NONE in /etc/sysconfig/bootloader ). JR -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org