virtio_blk fails for rhel5.3 guest with LVM: kernel panic

virtio_blk fails for rhel5.3 guest with LVM: kernel panic

[sudhir kumar]

I see that Rhel5.3 32 and 64 bit guests fail to boot with virtio for
block device. The
guest can not find the root filesystem. The guest is using LVM. As per
the linux-kvm wiki  instructions I did change device.map and booted
with if=virtio.
The wiki link is http://www.linux-kvm.org/page/Boot_from_virtio_block_device

qemu command:
# qemu-system-x86_64 -drive file=rhel5-32.raw,if=virtio,boot=on -m 2048 -smp 4
-net nic,model=rtl8139,macaddr=00:FF:FE:00:00:64 -net
tap,script=/root/qemu-ifup-latest -name 32virtio -vnc :2 -watchdog i6300esb
-watchdog-action reset &
The image was installed using if=ide.

The messages before panic shows that the guest was unable to mount
root file system as below.
"Volume group Volgroup00 not found
mount: could not find filesystem /dev/root
setuproot: moving /dev failed: no such file or directory
setuproot: mounting /proc failed: no such file or directory
setuproot: mounting /sys failed: no such file or directory
switchroot: mount failed: no such file or directory
kernle panic- not syncing: Attempted to kill init "

I see similar messages for 64 bit guest as well.

This is the information from within guest:
[root@ichigo-dom101 ~]# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
[root@ichigo-dom101 ~]# fdisk -l

Disk /dev/hda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   83  Linux
/dev/hda2              14        1305    10377990   8e  Linux LVM
[root@ichigo-dom101 ~]# cat /boot/grub/device.map
# this device map was generated by anaconda
(hd0)     /dev/vda

[root@ichigo-dom101 ~]# cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-128.el5PAE)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-128.el5PAE ro root=/dev/VolGroup00/LogVol00 rhgb
quiet
        initrd /initrd-2.6.18-128.el5PAE.img

I ensured that the guest has the virtio_blk.ko module.

rpm -qa | grep kvm:  qemu-kvm-0.10.5-6

Guest OS: RHEL 5.3 32/64

Host OS: SlES11 64

Guest OS Image storage type: nfs


Is there anything that I am not doing in correct way?
Please let me know any other information is required.

Thanks
Sudhir


-- 
Sudhir Kumar

Re: virtio_blk fails for rhel5.3 guest with LVM: kernel panic

[Avi Kivity]

On 06/23/2009 08:21 PM, sudhir kumar wrote:
> I see that Rhel5.3 32 and 64 bit guests fail to boot with virtio for
> block device. The
> guest can not find the root filesystem. The guest is using LVM. As per
> the linux-kvm wiki  instructions I did change device.map and booted
> with if=virtio.
> The wiki link is http://www.linux-kvm.org/page/Boot_from_virtio_block_device
>
>    

Does your initrd include virtio-pci.ko and virtio-blk.ko?

-- 
error compiling committee.c: too many arguments to function

Re: virtio_blk fails for rhel5.3 guest with LVM: kernel panic

[sudhir kumar]

initrd does not contain these modules. My kernel contains the above modules.
Is it mandatory for the initrd to contain these modules? It does not
contain virtio-net and the guest boots fine with virtio.

On Wed, Jun 24, 2009 at 2:04 PM, Avi Kivity<avi@redhat.com> wrote:
> On 06/23/2009 08:21 PM, sudhir kumar wrote:
>>
>> I see that Rhel5.3 32 and 64 bit guests fail to boot with virtio for
>> block device. The
>> guest can not find the root filesystem. The guest is using LVM. As per
>> the linux-kvm wiki  instructions I did change device.map and booted
>> with if=virtio.
>> The wiki link is
>> http://www.linux-kvm.org/page/Boot_from_virtio_block_device
>>
>>
>
> Does your initrd include virtio-pci.ko and virtio-blk.ko?
>
> --
> error compiling committee.c: too many arguments to function
>
>



-- 
Sudhir Kumar

Re: virtio_blk fails for rhel5.3 guest with LVM: kernel panic

[Avi Kivity]

On 06/24/2009 12:41 PM, sudhir kumar wrote:
> initrd does not contain these modules. My kernel contains the above modules.
> Is it mandatory for the initrd to contain these modules? It does not
> contain virtio-net and the guest boots fine with virtio.
>    

virtio-net isn't used for locating the disks.  If you want your root 
filesystem to use virtio, you must include these modules.

-- 
error compiling committee.c: too many arguments to function