Skip to contentSkip to conversation

Native KVM: can't boot existing Fedora 14 image

DISCUSSION David Ahern 2 participants 3 messages Apr 5, 2011

lore
Share & tools
lore
#0 lore raw

I was trying out the new kvm tool with an existing KVM image, and it is failing to boot because the hard drive cannot be found.

The qemu-kvm command is:

/usr/bin/qemu-kvm \
-kernel /tmp/vmlinuz-2.6.38 \
-initrd /tmp/initramfs-2.6.38.img \
-append "ro root=/dev/mapper/vg_f14vm-lv_root LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us selinux=0 console=ttyS0" \
-drive file=/home/dsa/vm/images/f14/disk-1.img,if=virtio,cache=none \
-m 1024 -nographic -serial stdio -monitor unix:/tmp/f14,server,nowait

The console output during disk discovery is:

[   10.794727] dracut: dracut-006-6.fc14
[   10.849603] udev[53]: starting version 161
[   10.949862] dracut: Starting plymouth daemon
[   11.500216] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
[   11.501581] virtio-pci 0000:00:04.0: PCI INT A -> Link[LNKD] -> GSI
11 (level, high) -> IRQ 11
[   11.518211]  vda: vda1 vda2

And of course it boots nicely.

The corresponding (native) kvm command I tried is:

./kvm --kernel=/tmp/vmlinuz-2.6.38 \
      --initrd=/tmp/initramfs-2.6.38.img \
      --image=/home/dsa/vm/images/f14/disk-1.img  \
      --params="ro root=/dev/mapper/vg_f14vm-lv_root LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYTABLE=us selinux=0" \
      --mem=1024

And the relevant discovery output is:

[   11.492079] dracut: dracut-006-6.fc14
[   11.550571] udev[50]: starting version 161
[   11.649098] dracut: Starting plymouth daemon
putfont: PIO_FONT trying ...
.[   11.977699] virtio-pci 0000:00:01.0: enabling device (0000 -> 0001)
[   11.991637]  vda: vda1 vda2
  Warning: request type 8
  Warning: request type 8
  Warning: request type 8
[   12.086194] EXT3-fs (vda): error: can't find ext3 filesystem on dev vda.
[   12.087358] EXT4-fs (vda): VFS: Can't find ext4 filesystem
[   12.141795] ISOFS: Unable to identify CD-ROM format.

mount: you must specify the filesystem type

At that point it loops over a few iterations of the last few lines and I kill it. Any ideas why?

David

#1 lore raw
Quoted 2 lines · David Ahern

At that point it loops over a few iterations of the last few lines and I kill it. Any ideas why?

What happens if you remove the (hardcoded) "root=vda" kernel parameter from the commandline (in tools/kvm/main.c)?

PUal Bolle

#2 lore raw
Quoted 6 lines · Paul Bolle
Quoted 2 lines · David Ahern

At that point it loops over a few iterations of the last few lines and I kill it. Any ideas why?

What happens if you remove the (hardcoded) "root=vda" kernel parameter from the commandline (in tools/kvm/main.c)?

It boots. :-)

Thanks,

David

Quoted 4 lines

PUal Bolle