[fedora-virt] How to use virtio-scsi on F17 host and F17 guest
Kashyap Chamarthy
kashyapc at fedoraproject.org
Fri Jun 8 12:25:15 UTC 2012
(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.
#--------------------------------------------------#
/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 \
-drive file=/var/lib/libvirt/images/f16t1.qcow2,if=none,id=sda \
-device scsi-disk,bus=scsi.0,drive=sda \
-device sga \
-kernel vmlinuz-3.2.7-1.fc16.x86_64 \
-initrd initramfs-3.2.7-1.fc16.x86_64.img \
-append "console=ttyS0"
#--------------------------------------------------#
kashyap@~$ ps -ef | grep qemu-kvm | grep virtio-scsi
root 12705 12704 99 17:49 pts/11 00:00:04 /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 -drive
file=/var/lib/libvirt/images/f16t1.qcow2,if=none,id=sda -device
scsi-disk,bus=scsi.0,drive=sda -device sga -kernel vmlinuz-3.2.7-1.fc16.x86_64 -initrd
initramfs-3.2.7-1.fc16.x86_64.img -append console=ttyS0
kashyap@~$
#--------------------------------------------------#
Actually, I've stumbled across this bug above w/ virt-install while initially testing
F17(now resolved, though) -- https://bugzilla.redhat.com/show_bug.cgi?id=785815
#--------------------------------------------------#
.
.
.
[ 1.972021] dracut Warning: dracut: FATAL: No or empty root= argument
dracut Warning: dracut: FATAL: No or empty root= argument
[ 1.973816] dracut Warning: dracut: Refusing to continue
dracut Warning: dracut: Refusing to continue
[ 1.975691] Kernel panic - not syncing: Attempted to kill init!
[ 1.976631] Pid: 1, comm: init Not tainted 3.2.7-1.fc16.x86_64 #1
[ 1.977596] Call Trace:
[ 1.977998] [<ffffffff815d7510>] panic+0x91/0x1a7
[ 1.978853] [<ffffffff81072541>] do_exit+0x861/0x8a0
[ 1.979650] [<ffffffff810728d2>] do_group_exit+0x42/0xa0
[ 1.980495] [<ffffffff81072947>] sys_exit_group+0x17/0x20
[ 1.981354] [<ffffffff815e9d82>] system_call_fastpath+0x16/0x1b
#--------------------------------------------------#
>
> Kevin
>
>
More information about the virt
mailing list