Il 08/06/2012 14:51, Kevin Wolf ha scritto:
Am 08.06.2012 14:25, schrieb Kashyap Chamarthy:
(Sorry for the double email, previously. I thought it didn't went through, and re-sent it.)
On 06/08/2012 03:02 PM, Kevin Wolf wrote:
Am 07.06.2012 19:50, schrieb Kashyap Chamarthy:
A related question:
A while ago, I was using just bare qemu-kvm to invoke an f16 kernel to test virtio-scsi:
qemu-kvm invocation: #---------------------------------------------------# # /usr/bin/qemu-kvm \ -device virtio-scsi-pci,id=scsi \ -enable-kvm \ -nographic -nodefconfig -nodefaults \ -chardev stdio,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -device sga \ -kernel vmlinuz-3.2.7-1.fc16.x86_64 \ -initrd initramfs-3.2.7-1.fc16.x86_64.img \ -append "console=ttyS0" #---------------------------------------------------#
You're only adding the virtio-scsi controller here, but no disks, so your guest can't find its root file system. I think you need to add:
-drive file=disk.img,if=none,id=sda -device scsi-disk,bus=scsi.0,drive=sda
Um, with passing the disk image(which has f16) explicitly, it still complaints can't find the root= argument.
Well, maybe you need to pass the root=... parameter in -append then. :-)
What it needs to be exactly depends on your setup. The GRUB configuration on the guest should tell you the right value.
Or am I missing some additional requirement, Paolo?
No, I think you're right. If the kernel command-line uses UUIDs for the root image, the same image can usually switch transparently among IDE/virtio-scsi/virtio-blk.
Paolo