<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Hello Stefan.<br>Thanks. I understand qemu supports other scsi adapters however. See <a href="https://www.redhat.com/archives/libvir-list/2013-March/msg01254.html"><span>this</span></a> post from earlier this year.<br>That post makes reference to the following hbas: auto, buslogic, ibmvscsi. lsilogic, lsisas1068, lsisas1078, virtio-scsi, vmpvscsi.<br>The post is referring to libvirt, so the number of adapters may be related to the various virtualization backends that libvirt can interface with.<br><br>There are numerous references to qemu/qemu-kvm supporting other scsi adapters as well as AHCI SATA. I installed the Centos 6.4 based node, so perhaps the Fedora 19 based node has a newer qemu that supports more of these features? I might see if I can do an install of the Fedora 19 based node
tomorrow.<br><br>Ayal mentioned using 'hooks' to interface with qemu to possibly create a VM outside of the definitions that Ovirt allows. If I am understanding this correctly - how do I do this? Am I to expect some interface inconsistencies in the ovirt portal I I view a 'custom' VM like this?<br><br>So, in short - is there the potential for me to create a VM in ovirt that has a SCSI/SAS/SATA HBA and attach disk(s) to it (other than the virtio-scsi HBA which is not supported under EL5)?<br><div style="display: block;" class="yahoo_quoted"> <br> <br> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> On Thursday, 14 November 2013 11:22 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:<br> </font> </div> <div class="y_msg_container">On Thu, Nov 14, 2013 at 02:39:33AM -0500,
Ayal Baron wrote:<br clear="none">> > ----- Original Message -----<br clear="none">> > > Hello Itamar.<br clear="none">> > > The specific use case is a particular propriety filesystem that needs to<br clear="none">> > > see<br clear="none">> > > a scsi device. It will do scsi inquiry conmmands to verify suitability.<br clear="none">> > > In talking to the devs - of the filesystem - there is no way around it. I'd<br clear="none">> > > previously tried virtio-block - resulting in the /dev/vd* device - and the<br clear="none">> > > filesystem would not work.<br clear="none">> > > <br clear="none">> > > From doing a bit of web searching it appears the kvm/qemu supports (or did<br clear="none">> > > support) an emulated LSI scsi controller. My understanding is that the<br clear="none">> > > various virtualization platforms will emulate a well supported
device (by<br clear="none">> > > the guest OSes) so that drivers are not an issue. For example this should<br clear="none">> > > allow a VM on Vmware vsphere/vcenter to be exported to Ovirt and have it<br clear="none">> > > boot up. The potential for further optimising the guest is there by<br clear="none">> > > installing ovirt/qemu/kvm guest utils that then allow the guest OS to<br clear="none">> > > understand the virtio nic and scsi devices. The guest could then be shut<br clear="none">> > > down, the nic and scsi controller changed and the guest booted up again.<br clear="none">> > > You can do the same thing in the Vmware world by installing their guest<br clear="none">> > > tools, shutting down the guest VM, then reconfiguring it with a vmxnet3 nic<br clear="none">> > > and pvscsi scsi adapter, then booting up again.<br clear="none">> > > It does seem
somewhat inconsistent in Ovirt that we allow a choice of Intel<br clear="none">> > > e1000 or virtio nics, but do not offer any choice with the scsi adapter.<br clear="none">> > <br clear="none">> > virtio-scsi support was just recently added to oVirt to allow for scsi<br clear="none">> > passthrough and improved performance over virtio-blk.<br clear="none">> > I believe the emulated scsi device in qemu never matured enough but possibly<br clear="none">> > Stefan (cc'd) can correct me here.<br clear="none"><br clear="none">The only supported emulated SCSI HBA device is virtio-scsi. It was Tech<br clear="none">Preview in RHEL 6.3 and became fully supported in RHEL 6.4. virtio-scsi<br clear="none">is not available in RHEL 5.<div class="yqt2796650658" id="yqtfd21253"><br clear="none"><br clear="none">Stefan<br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>