<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Hello Itamar.<br>The specific use case is a particular propriety filesystem that needs to see a scsi device. It will do scsi inquiry conmmands to verify suitability.<br>In talking to the devs - of the filesystem - there is no way around it. I'd previously tried virtio-block - resulting in the /dev/vd* device - and the filesystem would not work.<br><br>From doing a bit of web searching it appears the kvm/qemu supports (or did support) an emulated LSI scsi controller. My understanding is that the various virtualization platforms will emulate a well supported device (by the guest OSes) so that drivers are not an issue. For example this should allow a VM on Vmware vsphere/vcenter to be exported to Ovirt and have it boot up. The potential for further optimising the guest is there by installing
ovirt/qemu/kvm guest utils that then allow the guest OS to understand the virtio nic and scsi devices. The guest could then be shut down, the nic and scsi controller changed and the guest booted up again.<br>You can do the same thing in the Vmware world by installing their guest tools, shutting down the guest VM, then reconfiguring it with a vmxnet3 nic and pvscsi scsi adapter, then booting up again.<br>It does seem somewhat inconsistent in Ovirt that we allow a choice of Intel e1000 or virtio nics, but do not offer any choice with the scsi adapter.<br>Again, in Vmware land you can choose to have a scsi disk, but you choose which controller type it is attached to. In the current Ovirt 3.3.0 release you just chose a virtio-scsi disk, rather than there being a separation of the scsi disk and scsi controller.<br>The messy situation with importing VMs from other platforms could be eased by allowing an emulated scsi controller as well as the
preferred virtio controller.<br>As mentioned previously, the support for this seems to be present in kvm/qemu. I wonder if there was a specific design decision (ie: some particular reason) to not support the approach I've just described? I can understand that in some cases simplicity is something to aim for though.<br>I think this would make migration away from the dominant market leader - Vmware - easier and is something that would make ovirt/RHEV that more compelling.<br><br>Getting back to my original query - 'open-vm-tools' support the vmware paravirtual scsi adapter and I am able to install these on EL5 and then see that adapter. It would be great if there was a similar initiative for the various virtio devices where you could install a packge/kmod and then allow some of the older OSes (of which there are still lots of VMs around for various reasons). There are obviously drivers for the various Windows flavours that take this
approach. I'm surprised that for Linux it is just a case of 'if it's in the kernel you are running then it is supported'.<br><br>I'm really pleased with the progress the ovirt has been making. I'm like to see it continue to knock down the various reasons out there as to why people with Vmware vcenter shops can't migrate over to it.<br><br>Cheers,<br>Paul<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 Wednesday, 13 November 2013 8:57 PM, Itamar Heim <iheim@redhat.com> wrote:<br> </font> </div> <div class="y_msg_container">On 11/13/2013 03:58 AM, Paul Jansen wrote:<br clear="none">> Hi Rene.<br clear="none">> I specifically need the scsi support (virtio-scsi).<br clear="none">> I do know about the
virtio-block support, which results in /dev/vd*<br clear="none">> devices as you say.<br clear="none">> From what I read even EL6 earlier than 6.3 does not support virtio-scsi<br clear="none">><br clear="none">> Alternatively, does oVirt support an emulated scsi adapter of a<br clear="none">> different type that would allow me to see scsi disks?<br clear="none"><br clear="none">may i ask why do you need the virtual disks to specifically be scsi?<br clear="none"><br clear="none">><br clear="none">> Regards,<br clear="none">> Paul<br clear="none">><br clear="none">><br clear="none">> On Wednesday, 13 November 2013 7:23 PM, René Koch (ovido)<br clear="none">> <<a shape="rect" ymailto="mailto:r.koch@ovido.at" href="mailto:r.koch@ovido.at">r.koch@ovido.at</a>> wrote:<br clear="none">> On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:<br clear="none">> > According to <a shape="rect"
href="https://access.redhat.com/site/solutions/20511" target="_blank">https://access.redhat.com/site/solutions/20511</a><br clear="none">> <<a shape="rect" href="https://access.redhat.com/site/solutions/20511" target="_blank">https://access.redhat.com/site/solutions/20511</a>>virtio<br clear="none">> > work on > rhel5.3.<br clear="none">> ><br clear="none">> > You have to edit /etc/modprobe.conf and generate a new initrd.<br clear="none">><br clear="none">><br clear="none">> If you're installing the OS on a VirtIO disk this is done automatically<br clear="none">> by anaconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and<br clear="none">> everything worked out of the box.<br clear="none">><br clear="none">><br clear="none">> ><br clear="none">> > On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <<a shape="rect" ymailto="mailto:S.Kieske@mittwald.de"
href="mailto:S.Kieske@mittwald.de">S.Kieske@mittwald.de</a><br clear="none">> <mailto:<a shape="rect" ymailto="mailto:S.Kieske@mittwald.de" href="mailto:S.Kieske@mittwald.de">S.Kieske@mittwald.de</a>>> wrote:<br clear="none">> > > Hi,<br clear="none">> > ><br clear="none">> > > afaik the rhel 5 kernel series just has not the necessary drivers for<br clear="none">> > > all virtio stuff, so it's not supported and does not work, unless<br clear="none">> > > you want to patch your own kernel.<br clear="none">> > ><br clear="none">> > > Am 13.11.2013 06:44, schrieb Paul Jansen:<br clear="none">> > >> I have just set up an Ovirt 3.3.0 install and have done a test<br clear="none">> install of Centos 6.4 in a VM. The VM was configured with an IDE drive<br clear="none">> and a virtio-scsi drive. The Centos 6.4
install sees both drives OK.<br clear="none">> > >> I'm wanting to do some testing on a product that is based on EL5,<br clear="none">> but I'm finding that it cannot see the virtio-scsi drive. It does show<br clear="none">> up in the output of 'lspci', but I don't see a corresponding 'sd' device.<br clear="none">> > >><br clear="none">><br clear="none">><br clear="none">> There's no /dev/sd* device - the devices are named /dev/vd*...<br clear="none">><br clear="none">><br clear="none">> > >> I've just tried installing Centos 5.10 and the support is not there.<br clear="none">><br clear="none">><br clear="none">> Didn't test CentOS but RHEL 5 is working fine.<br clear="none">><br clear="none">><br clear="none">> Regards,<br clear="none">> René<br clear="none">><br clear="none">><br clear="none">><br clear="none">> > >><br
clear="none">> > >> Does anyone know of any tricks to allow EL5 to see the virtio-scsi<br clear="none">> device?<br clear="none">> > ><br clear="none">> > ><br clear="none">> > > --<br clear="none">> > > Mit freundlichen Grüßen / Regards<br clear="none">> > ><br clear="none">> > > Sven Kieske<br clear="none">> > ><br clear="none">> > > Systemadministrator<br clear="none">> > > Mittwald CM Service GmbH & Co. KG<br clear="none">> > > Königsberger Straße 6<br clear="none">> > > 32339 Espelkamp<br clear="none">> > > T: +49-5772-293-100<br clear="none">> > > F: +49-5772-293-333<br clear="none">> > > <a shape="rect" href="https://www.mittwald.de/" target="_blank">https://www.mittwald.de </a><<a shape="rect"
href="https://www.mittwald.de/" target="_blank">https://www.mittwald.de/</a>><br clear="none">> > > Geschäftsführer: Robert Meyer<br clear="none">> > > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad<br clear="none">> Oeynhausen<br clear="none">> > > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad<br clear="none">> Oeynhausen<br clear="none">> > > _______________________________________________<br clear="none">> > > Users mailing list<br clear="none">> > > <a shape="rect" ymailto="mailto:Users@ovirt.org" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <mailto:<a shape="rect" ymailto="mailto:Users@ovirt.org" href="mailto:Users@ovirt.org">Users@ovirt.org</a>><br clear="none">> > > <a shape="rect" href="http://lists.ovirt.org/mailman/listinfo/users"
target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br clear="none">> > _______________________________________________<br clear="none">> > Users mailing list<br clear="none">> > <a shape="rect" ymailto="mailto:Users@ovirt.org" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <mailto:<a shape="rect" ymailto="mailto:Users@ovirt.org" href="mailto:Users@ovirt.org">Users@ovirt.org</a>><div class="yqt6536836530" id="yqtfd61729"><br clear="none">> > <a shape="rect" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br clear="none">><br clear="none">><br clear="none">><br clear="none">><br clear="none">><br clear="none">> _______________________________________________<br clear="none">> Users mailing list<br clear="none">> <a shape="rect" ymailto="mailto:Users@ovirt.org"
href="mailto:Users@ovirt.org">Users@ovirt.org</a><br clear="none">> <a shape="rect" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br clear="none">><br clear="none"><br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>