linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Native KVM: can't boot existing Fedora 14 image
@ 2011-04-05  2:27 David Ahern
  2011-04-05  8:23 ` Paul Bolle
  0 siblings, 1 reply; 3+ messages in thread
From: David Ahern @ 2011-04-05  2:27 UTC (permalink / raw)
  To: Pekka Enberg, LKML

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Native KVM: can't boot existing Fedora 14 image
  2011-04-05  2:27 Native KVM: can't boot existing Fedora 14 image David Ahern
@ 2011-04-05  8:23 ` Paul Bolle
  2011-04-05 12:58   ` David Ahern
  0 siblings, 1 reply; 3+ messages in thread
From: Paul Bolle @ 2011-04-05  8:23 UTC (permalink / raw)
  To: David Ahern; +Cc: Pekka Enberg, LKML

On Mon, 2011-04-04 at 20:27 -0600, David Ahern wrote:
> 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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Native KVM: can't boot existing Fedora 14 image
  2011-04-05  8:23 ` Paul Bolle
@ 2011-04-05 12:58   ` David Ahern
  0 siblings, 0 replies; 3+ messages in thread
From: David Ahern @ 2011-04-05 12:58 UTC (permalink / raw)
  To: Paul Bolle; +Cc: Pekka Enberg, LKML



On 04/05/11 02:23, Paul Bolle wrote:
> On Mon, 2011-04-04 at 20:27 -0600, David Ahern wrote:
>> 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

> 
> 
> PUal Bolle
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-04-05 12:58 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-05  2:27 Native KVM: can't boot existing Fedora 14 image David Ahern
2011-04-05  8:23 ` Paul Bolle
2011-04-05 12:58   ` David Ahern

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).