From: David Ahern <dsahern@gmail.com>
To: Pekka Enberg <penberg@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Native KVM: can't boot existing Fedora 14 image
Date: Mon, 04 Apr 2011 20:27:02 -0600 [thread overview]
Message-ID: <4D9A7DF6.1040101@gmail.com> (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
next reply other threads:[~2011-04-05 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 2:27 David Ahern [this message]
2011-04-05 8:23 ` Native KVM: can't boot existing Fedora 14 image Paul Bolle
2011-04-05 12:58 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D9A7DF6.1040101@gmail.com \
--to=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox