---847950152-513688593-1384573231=:85913 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi Paolo.=0AI think this would be quite a useful patch.=0AThe two benefits = as far as I can see would be:=0A(1) smoother importing of VMs from Vmware/v= sphere/vcenter into hypervisors that make use of libvirt. The VM definition= would not need to change the scsi adapter property.=0A(2) potentially allo= w using the vmware pvscsi controller in ovirt.=A0 In my particular use case= this should allow EL5 guests to be used (and have a supported scsi control= ler once 'open-vm-tools' is installed) in Ovirt.=A0 Ovviously we'd want to = steer people into using virtio-scsi wherever possible though, as has been d= iscussed previously.=0A=0APlease let us know on list if you do get to this.= =0AThanks for your efforts,=0APaul=0A=0A=0A=0A=0AOn Friday, 15 November 201= 3 8:50 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:=0A =0AIl 15/11/2013 0= 9:30, Stefan Hajnoczi ha scritto:=0A=0A>> > Thanks.=A0 I understand qemu su= pports other scsi adapters however.=A0 See this post from earlier this year= .=0A>> > That post makes reference to the following hbas: auto, buslogic, i= bmvscsi. lsilogic, lsisas1068, lsisas1078, virtio-scsi, vmpvscsi.=0A> From = an upstream QEMU perspective, the HBAs that ought to work on x86_64=0A> gue= sts are virtio-scsi, lsisas1078, and vmpvscsi.=0A=0AI think vmpvscsi is not= supported for QEMU in libvirt.=A0 It would be a=0Avery simple patch, I may= get round to it before Christmas...=0A=0APaolo ---847950152-513688593-1384573231=:85913 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:ti= mes new roman, new york, times, serif;font-size:12pt">Hi Paolo.<br>I think = this would be quite a useful patch.<br>The two benefits as far as I can see= would be:<br>(1) smoother importing of VMs from Vmware/vsphere/vcenter int= o hypervisors that make use of libvirt. The VM definition would not need to= change the scsi adapter property.<br>(2) potentially allow using the vmwar= e pvscsi controller in ovirt. In my particular use case this should a= llow EL5 guests to be used (and have a supported scsi controller once 'open= -vm-tools' is installed) in Ovirt. Ovviously we'd want to steer peopl= e into using virtio-scsi wherever possible though, as has been discussed pr= eviously.<br><br>Please let us know on list if you do get to this.<br>Thank= s for your efforts,<br>Paul<br><div style=3D"display: block;" class=3D"yaho= o_quoted"> <br> <br> <div style=3D"font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style=3D"font-family: times new roma= n, new york, times, serif; font-size: 12pt;"> <div dir=3D"ltr"> <font size= =3D"2" face=3D"Arial"> On Friday, 15 November 2013 8:50 PM, Paolo Bonzini &= lt;pbonzini@redhat.com> wrote:<br> </font> </div> <div class=3D"y_msg_c= ontainer">Il 15/11/2013 09:30, Stefan Hajnoczi ha scritto:<div class=3D"yqt= 6236364660" id=3D"yqtfd51451"><br clear=3D"none">>> > Thanks. = ; I understand qemu supports other scsi adapters however. See this po= st from earlier this year.<br clear=3D"none">>> > That post makes = reference to the following hbas: auto, buslogic, ibmvscsi. lsilogic, lsisas= 1068, lsisas1078, virtio-scsi, vmpvscsi.<br clear=3D"none">> From an ups= tream QEMU perspective, the HBAs that ought to work on x86_64<br clear=3D"n= one">> guests are virtio-scsi, lsisas1078, and vmpvscsi.</div><br clear= =3D"none"><br clear=3D"none">I think vmpvscsi is not supported for QEMU in = libvirt. It would be a<br clear=3D"none">very simple patch, I may get round to it befo= re Christmas...<br clear=3D"none"><br clear=3D"none">Paolo<div class=3D"yqt= 6236364660" id=3D"yqtfd41892"><br clear=3D"none"></div><br><br></div> </di= v> </div> </div> </div></body></html> ---847950152-513688593-1384573231=:85913--