Red Hat Bugzilla – Bug 216887
xenblk module is not preloaded in initrd on xen slices
Last modified: 2007-11-30 17:11:49 EST
Description of problem:
Updating DomU kernels to kernel-xen, the slice can no longer see the block
device on boot. I managed to get around this by running:
and pointing to the new initrd before booting to the new kernel.
Now, I think it's mkinitrd run by the kernel-xen install script that failes to
notice the need for xenblk but just in case, I've ccd xen-maint in this.
Version-Release number of selected component (if applicable):
Update a DomU kernel to kernel-xen, have a look at the initrd made, you should
notice the lack of xenblk. The slice will not boot up now.
Steps to Reproduce:
1. yum install kernel-xen
Slice does not "see" the block device and hence does not boot.
The slice should boot.
After the slice is back up you still need to --preload=xenblk to create the
right initrd (I've tried mkintrd and lloking at the init script, it does not
load the module) so I beleive the slice should break again on the next kernel
I would imagine it's a trivial patch to mkinitrd to notice it's a xen (none
Dom0/DomU) kernel and preload the xenblk.
Let me know if you need any more info.
To update to kernel-xen, you need to add
alias scsi_hostadapter xenblk
to /etc/modprobe.conf to make this happen by default. Anaconda will set this
automatically on FC-6 or later.
*** This bug has been marked as a duplicate of 204487 ***