Tauren Mills wrote:
...
root=/dev/VolGroup00/lvdom0. I did this because after the yum update,
AFAIK, the init process runs scripts/tools like "vgscan" *after* the
kernel has mounted it's rootdev, etc. ....
and i believe *exactly afterwards*
/dev/mapper/VolGroup00-lvdom0 is the same then
/dev/VolGroup00/lvdom0
but i'm no lvm expert !
the new kernel used the mapper syntax while the original kernel
didn't. At the moment I have it like this:
title Fedora Core (2.6.20-1.2948.fc6xen)
root (hd0,0)
kernel /xen.gz-2.6.20-1.2948.fc6
module /vmlinuz-2.6.20-1.2948.fc6xen ro
shouldn't it read kernel /boot/...
module /boot/... ???
keying error ?
root=/dev/VolGroup00/lvdom0 ide=nodma
module /initrd-2.6.20-1.2948.fc6xen.img
title Fedora Core (2.6.18-1.2798.fc6xen)
root (hd0,0)
kernel /xen.gz-2.6.18-1.2798.fc6
module /vmlinuz-2.6.18-1.2798.fc6xen ro
root=/dev/VolGroup00/lvdom0 ide=nodma
module /initrd-2.6.18-1.2798.fc6xen.img
did the non-xen 2.6.20.x.y kernels talk to your hd-controller/hd's ?
with that hand keyed lvm-lines ?
you could compare the initrd's of the non-xen-kernel and a xen-kernel
(both version 2.6.20.x.y), also. - they shouldn't be very different -
something prevents your xen-kernel talking to/seeing your hd-controller/hd !
and
weeks ago i read something on one of the fedora-{test,devel}-list
about initrd's and the module raid456...
--
ronald
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
