[fedora-virt] How to use virtio-scsi on F17 host and F17 guest

[Kashyap Chamarthy]

On 06/07/2012 06:55 PM, Cole Robinson wrote:
> On 06/06/2012 12:30 PM, Gianluca Cecchi wrote:
>> Hello,
>> reading here:
>> https://fedoraproject.org/wiki/Features/virtio-scsi
>>
>> it should be possible to use virtio-scsi, even if not completely
>> integrated in libvirt.
>> And installation would require this part for the hard disk:
>>
>> -drive if=none,id=hd,file=/path/to/test.img -device
>> virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd
>>
>> I have now an F17 host (kernel 3.3.7) and F17 guest (3.4.0) configured
>> with a virtio_blk disk
>> guest definition for the disk is this:
>>     <disk type='file' device='disk'>
>>       <driver name='qemu' type='qcow2'/>
>>       <source file='/var/lib/libvirt/images/f17.img'/>
>>       <target dev='vda' bus='virtio'/>
>>       <address type='pci' domain='0x0000' bus='0x00' slot='0x06'
>> function='0x0'/>
>>     </disk>
>>
>> Can I change it with "virsh edit" so that I can use virtio-scsi inside
>> guest and test?
>> What would be the xml snippet for it? Or do I have to use also a
>> wrapper to start qemu-kvm with particular options as during install?
>>
> 
> It looks like you want to add :
> 
> <controller type='scsi' index='0' model='virtio-scsi'/>
> 
> Then in change that <target line to
> 
> <target dev='sda' bus='scsi'/>
> 
> Problem is this will change the disk device node in the guest from vda to sda,
> so could cause mounting problems.

Cole,

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"
#---------------------------------------------------#
kashyap@~$ rpm -q qemu-kvm
qemu-kvm-1.0-17.fc16.x86_64
kashyap@~$
#---------------------------------------------------#


I get this Kernel Panic:
#---------------------------------------------------#
.
.
.

[    2.554591] Kernel panic - not syncing: Attempted to kill init!
[    2.556143] Pid: 1, comm: init Not tainted 3.2.7-1.fc16.x86_64 #1
[    2.557768] Call Trace:
[    2.558408]  [<ffffffff815d7510>] panic+0x91/0x1a7
[    2.559649]  [<ffffffff81072541>] do_exit+0x861/0x8a0
[    2.560925]  [<ffffffff810728d2>] do_group_exit+0x42/0xa0
[    2.562289]  [<ffffffff81072947>] sys_exit_group+0x17/0x20
[    2.563730]  [<ffffffff815e9d82>] system_call_fastpath+0x16/0x1b

#---------------------------------------------------#

Complete boot stdout:
http://kashyapc.fedorapeople.org/stdout-booting-kernel-qemu-kvm-virtio-scsi.txt


Any hints?
Though, I could try the way it was just discussed on this thread on F17. Still,just
curious, as the kernel versions I'm having does have all the required virtio-scsi bits.


> 
> - Cole
> _______________________________________________
> virt mailing list
> virt at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/virt