Bug 454989 - mkrootdev not working under Xen
mkrootdev not working under Xen
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: installer (Show other bugs)
i386 Linux
low Severity high
: rc
: ---
Assigned To: Anaconda Maintenance Team
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2008-07-11 06:41 EDT by greg matthews
Modified: 2008-08-25 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-25 12:30:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description greg matthews 2008-07-11 06:41:47 EDT
Description of problem:
mkrootdev does not create correct root device.

Version-Release number of selected component (if applicable):
RHEL4.6 iso images

How reproducible:

Steps to Reproduce:
1. boot iso image from SLES10 using Xen
2. install (works fine)
3. boot installed image - get kernel panic:
Actual results:
SCSI subsystem initialized
Registering block device major 202
Using cfq io scheduler
 xvda: xvda1 xvda2
 xvdb: unknown partition table
device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel@redhat.com
Kernel panic - not syncing: Attempted to kill init!

Expected results:
switchroot should find correct root partition

Additional info:
by editing the init script within the initrd and changing it to read:

     mount -o defaults --ro -t ext3 /dev/VolGroup00/LogVol00 /sysroot
     mount -t tmpfs --bind /dev /sysroot/dev
     sleep 5
     echo Switching to new root
     switchroot /sysroot
     sleep 5
     umount /initrd/dev

results in a clean boot.
Comment 1 greg matthews 2008-07-11 06:43:32 EDT
possibly related to Fedora bug: 212124
Comment 2 greg matthews 2008-07-11 07:24:01 EDT
A workaround in the case of RHEL4 domU on SLES10 is to edit /etc/xen/vm/<name>
and add:

extra=" root=/dev/VolGroup00/LogVol00"

Assuming default LVM naming.
Comment 3 Daniel Riek 2008-08-19 13:53:24 EDT
Product Management does not consider this a bug in RHEL4. RHEL5 virt installations give the correct command line.

SLES is not supported as a host.
Comment 4 RHEL Product and Program Management 2008-08-25 12:30:49 EDT
Product Management has reviewed and declined this request.  You may appeal this
decision by reopening this request.

Note You need to log in before you can comment on or make changes to this bug.