=A0 > >> I have just set up an Ovirt 3.3.0 install and have done a test=0A= install of Centos 6.4 in a VM.=A0 The VM was configured with an IDE drive= =0A> and a virtio-scsi drive.=A0 The Centos 6.4 install sees both drives OK= .=0A>=A0 > >> I'm wanting to do some testing on a product that is based on = EL5,=0A> but I'm finding that it cannot see the virtio-scsi drive.=A0 It do= es show=0A> up in the output of 'lspci', but I don't see a corresponding 's= d' device.=0A>=A0 > >>=0A>=0A>=0A> There's no /dev/sd* device - the devices= are named /dev/vd*...=0A>=0A>=0A>=A0 > >> I've just tried installing Cento= s 5.10 and the support is not there.=0A>=0A>=0A> Didn't test CentOS but RHE= L 5 is working fine.=0A>=0A>=0A> Regards,=0A> Ren=E9=0A>=0A>=0A>=0A>=A0 > >= =0A>=A0 > >> Does anyone know of any tricks to allow EL5 to see the virtio= -scsi=0A> device?=0A>=A0 > >=0A>=A0 > >=0A>=A0 > > --=0A>=A0 > > Mit freund=
=A0 > > Systemadministrator=0A>=A0 > > Mittwald CM Service GmbH & Co. KG= =0A>=A0 > > K=F6nigsberger Stra=DFe 6=0A>=A0 > > 32339 Espelkamp=0A>=A0 > >= T: +49-5772-293-100=0A>=A0 > > F: +49-5772-293-333=0A>=A0 > > https://www.= mittwald.de <https://www.mittwald.de/>=0A>=A0 > > Gesch=E4ftsf=FChrer: Robe= rt Meyer=0A>=A0 > > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640= , AG Bad=0A> Oeynhausen=0A>=A0 > > Komplement=E4rin: Robert Meyer Verwaltun= gs GmbH, HRB 13260, AG Bad=0A> Oeynhausen=0A>=A0 > > ______________________= _________________________=0A>=A0 > > Users mailing list=0A>=A0 > > Users@ov= irt.org <mailto:Users@ovirt.org>=0A>=A0 > > http://lists.ovirt.org/mailman/=
<div style=3D"font-family: times new roman, new york, times, serif; font-= size: 12pt;"> <div dir=3D"ltr"> <font size=3D"2" face=3D"Arial"> On Wednesd= ay, 13 November 2013 8:57 PM, Itamar Heim <iheim@redhat.com> wrote:<b= r> </font> </div> <div class=3D"y_msg_container">On 11/13/2013 03:58 AM, P= aul Jansen wrote:<br clear=3D"none">> Hi Rene.<br clear=3D"none">> I = specifically need the scsi support (virtio-scsi).<br clear=3D"none">> I = do know about the virtio-block support, which results in /dev/vd*<br clear=3D"none">> dev= ices as you say.<br clear=3D"none">> From what I read even EL6 ear=
><br clear=3D"none">> Regards,<br clear=3D"none">> Ren=E9<br clea= r=3D"none">><br clear=3D"none">><br clear=3D"none">><br clear=3D"n= one">> > >><br clear=3D"none">> > >> Does anyone know of any tricks to = allow EL5 to see the virtio-scsi<br clear=3D"none">> device?<br clear=3D= "none">> > ><br clear=3D"none">> > ><br clear= =3D"none">> > > --<br clear=3D"none">> > > Mi= t freundlichen Gr=FC=DFen / Regards<br clear=3D"none">> > ><= br clear=3D"none">> > > Sven Kieske<br clear=3D"none">>&n= bsp; > ><br clear=3D"none">> > > Systemadministrator<b= r clear=3D"none">> > > Mittwald CM Service GmbH & Co. KG= <br clear=3D"none">> > > K=F6nigsberger Stra=DFe 6<br clear= =3D"none">> > > 32339 Espelkamp<br clear=3D"none">> = > > T: +49-5772-293-100<br clear=3D"none">> > > F: +4= 9-5772-293-333<br clear=3D"none">> > > <a shape=3D"rect" hre= f=3D"https://www.mittwald.de/" target=3D"_blank">https://www.mittwald.de </= a><<a shape=3D"rect"
---1504104896-943642325-1384345221=:44659 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello Itamar.=0AThe specific use case is a particular propriety filesystem = that needs to see a scsi device.=A0 It will do scsi inquiry conmmands to ve= rify suitability.=0AIn talking to the devs - of the filesystem - there is n= o way around it.=A0 I'd previously tried virtio-block - resulting in the /d= ev/vd* device - and the filesystem would not work.=0A=0AFrom doing a bit of= web searching it appears the kvm/qemu supports (or did support) an emulate= d LSI scsi controller.=A0 My understanding is that the various virtualizati= on platforms will emulate a well supported device (by the guest OSes) so th= at drivers are not an issue.=A0 For example this should allow a VM on Vmwar= e vsphere/vcenter to be exported to Ovirt and have it boot up.=A0 The poten= tial 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.=A0 The guest could then be shut down, the nic and scsi contro= ller changed and the guest booted up again.=0AYou can do the same thing in = the Vmware world by installing their guest tools, shutting down the guest V= M, then reconfiguring it with a vmxnet3 nic and pvscsi scsi adapter, then b= ooting up again.=0AIt does seem somewhat inconsistent in Ovirt that we allo= w a choice of Intel e1000 or virtio nics, but do not offer any choice with = the scsi adapter.=0AAgain, in Vmware land you can choose to have a scsi dis= k, but you choose which controller type it is attached to.=A0 In the curren= t 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.=0AThe messy situat= ion with importing VMs from other platforms could be eased by allowing an e= mulated scsi controller as well as the preferred virtio controller.=0AAs me= ntioned previously, the support for this seems to be present in kvm/qemu.= =A0 I wonder if there was a specific design decision (ie: some particular r= eason) to not support the approach I've just described? I can understand th= at in some cases simplicity is something to aim for though.=0AI think this = would make migration away from the dominant market leader - Vmware - easier= and is something that would make ovirt/RHEV that more compelling.=0A=0AGet= ting back to my original query - 'open-vm-tools' support the vmware paravir= tual scsi adapter and I am able to install these on EL5 and then see that a= dapter.=A0 It would be great if there was a similar initiative for the vari= ous virtio devices where you could install a packge/kmod and then allow som= e of the older OSes (of which there are still lots of VMs around for variou= s reasons).=A0 There are obviously drivers for the various Windows flavours= that take this approach.=A0 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'.=0A=0AI'm = really pleased with the progress the ovirt has been making.=A0 I'm like to = see it continue to knock down the various reasons out there as to why peopl= e with Vmware vcenter shops can't migrate over to it.=0A=0ACheers,=0APaul= =0A=0A=0A=0A=0AOn Wednesday, 13 November 2013 8:57 PM, Itamar Heim <iheim@r= edhat.com> wrote:=0A =0AOn 11/13/2013 03:58 AM, Paul Jansen wrote:=0A> Hi R= ene.=0A> I specifically need the scsi support (virtio-scsi).=0A> I do know = about the virtio-block support, which results in /dev/vd*=0A> devices as yo= u say.=0A>=A0 From what I read even EL6 earlier than 6.3 does not support v= irtio-scsi=0A>=0A> Alternatively, does oVirt support an emulated scsi adapt= er of a=0A> different type that would allow me to see scsi disks?=0A=0Amay = i ask why do you need the virtual disks to specifically be scsi?=0A=0A>=0A>= Regards,=0A> Paul=0A>=0A>=0A> On Wednesday, 13 November 2013 7:23 PM, Ren= =E9 Koch (ovido)=0A> <r.koch@ovido.at> wrote:=0A> On Wed, 2013-11-13 at 09:= 41 +0100, Sander Grendelman wrote:=0A>=A0 > According to https://access.red= hat.com/site/solutions/20511=0A> <https://access.redhat.com/site/solutions/= 20511>virtio=0A>=A0 > work on > rhel5.3.=0A>=A0 >=0A>=A0 > You have to edit= /etc/modprobe.conf and generate a new initrd.=0A>=0A>=0A> If you're instal= ling the OS on a VirtIO disk this is done automatically=0A> by anaconda. I = just installed RHEL 5 on oVirt 3.3 with VirtIO disk and=0A> everything work= ed out of the box.=0A>=0A>=0A>=A0 >=0A>=A0 > On Wed, Nov 13, 2013 at 9:32 A= M, Sven Kieske <S.Kieske@mittwald.de=0A> <mailto:S.Kieske@mittwald.de>> wro= te:=0A>=A0 > > Hi,=0A>=A0 > >=0A>=A0 > > afaik the rhel 5 kernel series jus= t has not the necessary drivers for=0A>=A0 > > all virtio stuff, so it's no= t supported and does not work, unless=0A>=A0 > > you want to patch your own= kernel.=0A>=A0 > >=0A>=A0 > > Am 13.11.2013 06:44, schrieb Paul Jansen:=0A= lichen Gr=FC=DFen / Regards=0A>=A0 > >=0A>=A0 > > Sven Kieske=0A>=A0 > >=0A= listinfo/users=0A>=A0 > _______________________________________________=0A>= =A0 > Users mailing list=0A>=A0 > Users@ovirt.org <mailto:Users@ovirt.org>= =0A=0A>=A0 > http://lists.ovirt.org/mailman/listinfo/users=0A>=0A>=0A>=0A>= =0A>=0A> _______________________________________________=0A> Users mailing = list=0A> Users@ovirt.org=0A> http://lists.ovirt.org/mailman/listinfo/users= =0A> ---1504104896-943642325-1384345221=:44659 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">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 search= ing it appears the kvm/qemu supports (or did support) an emulated LSI scsi = controller. My understanding is that the various virtualization platf= orms will emulate a well supported device (by the guest OSes) so that drive= rs are not an issue. For example this should allow a VM on Vmware vsp= here/vcenter to be exported to Ovirt and have it boot up. The potenti= al 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 n= ic 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, shutti= ng down the guest VM, then reconfiguring it with a vmxnet3 nic and pvscsi s= csi adapter, then booting up again.<br>It does seem somewhat inconsistent i= n Ovirt that we allow a choice of Intel e1000 or virtio nics, but do not of= fer any choice with the scsi adapter.<br>Again, in Vmware land you can choo= se 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 contro= ller.<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 t= his 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 somet= hing 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 o= virt/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 t= o install these on EL5 and then see that adapter. It would be great i= f there was a similar initiative for the various virtio devices where you c= ould 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 ob= viously 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 ple= ased 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><d= iv style=3D"display: block;" class=3D"yahoo_quoted"> <br> <br> <div style= =3D"font-family: times new roman, new york, times, serif; font-size: 12pt;"= lier than 6.3 does not support virtio-scsi<br clear=3D"none">><br clear= =3D"none">> Alternatively, does oVirt support an emulated scsi adapter o= f a<br clear=3D"none">> different type that would allow me to see scsi d= isks?<br clear=3D"none"><br clear=3D"none">may i ask why do you need the vi= rtual disks to specifically be scsi?<br clear=3D"none"><br clear=3D"none">&= gt;<br clear=3D"none">> Regards,<br clear=3D"none">> Paul<br clear=3D= "none">><br clear=3D"none">><br clear=3D"none">> On Wednesday, 13 = November 2013 7:23 PM, Ren=E9 Koch (ovido)<br clear=3D"none">> <<a sh= ape=3D"rect" ymailto=3D"mailto:r.koch@ovido.at" href=3D"mailto:r.koch@ovido= .at">r.koch@ovido.at</a>> wrote:<br clear=3D"none">> On Wed, 2013-11-= 13 at 09:41 +0100, Sander Grendelman wrote:<br clear=3D"none">> &g= t; According to <a shape=3D"rect" href=3D"https://access.redhat.com/site/solutions/20511" target=3D"_blank">= https://access.redhat.com/site/solutions/20511</a><br clear=3D"none">> &= lt;<a shape=3D"rect" href=3D"https://access.redhat.com/site/solutions/20511= " target=3D"_blank">https://access.redhat.com/site/solutions/20511</a>>v= irtio<br clear=3D"none">> > work on > rhel5.3.<br clear=3D"n= one">> ><br clear=3D"none">> > You have to edit /et= c/modprobe.conf and generate a new initrd.<br clear=3D"none">><br clear= =3D"none">><br clear=3D"none">> If you're installing the OS on a Virt= IO disk this is done automatically<br clear=3D"none">> by anaconda. I ju= st installed RHEL 5 on oVirt 3.3 with VirtIO disk and<br clear=3D"none">>= ; everything worked out of the box.<br clear=3D"none">><br clear=3D"none= ">><br clear=3D"none">> ><br clear=3D"none">> > = On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <<a shape=3D"rect" ymailto= =3D"mailto:S.Kieske@mittwald.de" href=3D"mailto:S.Kieske@mittwald.de">S.Kieske@mittwald.de</a><br clear=3D"= none">> <mailto:<a shape=3D"rect" ymailto=3D"mailto:S.Kieske@mittwald= .de" href=3D"mailto:S.Kieske@mittwald.de">S.Kieske@mittwald.de</a>>> = wrote:<br clear=3D"none">> > > Hi,<br clear=3D"none">>&nb= sp; > ><br clear=3D"none">> > > afaik the rhel 5 kerne= l series just has not the necessary drivers for<br clear=3D"none">> = ; > > all virtio stuff, so it's not supported and does not work, unle= ss<br clear=3D"none">> > > you want to patch your own kernel= .<br clear=3D"none">> > ><br clear=3D"none">> > = > Am 13.11.2013 06:44, schrieb Paul Jansen:<br clear=3D"none">> = > >> I have just set up an Ovirt 3.3.0 install and have done a te= st<br clear=3D"none">> install of Centos 6.4 in a VM. The VM was c= onfigured with an IDE drive<br clear=3D"none">> and a virtio-scsi drive.= The Centos 6.4 install sees both drives OK.<br clear=3D"none">> > >> I'= m wanting to do some testing on a product that is based on EL5,<br clear=3D= "none">> but I'm finding that it cannot see the virtio-scsi drive. = It does show<br clear=3D"none">> up in the output of 'lspci', but I don= 't see a corresponding 'sd' device.<br clear=3D"none">> > >&= gt;<br clear=3D"none">><br clear=3D"none">><br clear=3D"none">> Th= ere's no /dev/sd* device - the devices are named /dev/vd*...<br clear=3D"no= ne">><br clear=3D"none">><br clear=3D"none">> > >> = I've just tried installing Centos 5.10 and the support is not there.<br cle= ar=3D"none">><br clear=3D"none">><br clear=3D"none">> Didn't test = CentOS but RHEL 5 is working fine.<br clear=3D"none">><br clear=3D"none"= href=3D"https://www.mittwald.de/" target=3D"_blank">https://www.mittwald.d= e/</a>><br clear=3D"none">> > > Gesch=E4ftsf=FChrer: Robe= rt Meyer<br clear=3D"none">> > > St.Nr.: 331/5721/1033, USt-= IdNr.: DE814773217, HRA 6640, AG Bad<br clear=3D"none">> Oeynhausen<br c= lear=3D"none">> > > Komplement=E4rin: Robert Meyer Verwaltun= gs GmbH, HRB 13260, AG Bad<br clear=3D"none">> Oeynhausen<br clear=3D"no= ne">> > > _______________________________________________<br= clear=3D"none">> > > Users mailing list<br clear=3D"none">&= gt; > > <a shape=3D"rect" ymailto=3D"mailto:Users@ovirt.org" hr= ef=3D"mailto:Users@ovirt.org">Users@ovirt.org</a> <mailto:<a shape=3D"re= ct" ymailto=3D"mailto:Users@ovirt.org" href=3D"mailto:Users@ovirt.org">User= s@ovirt.org</a>><br clear=3D"none">> > > <a shape=3D"rect= " href=3D"http://lists.ovirt.org/mailman/listinfo/users" target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br cle= ar=3D"none">> > _______________________________________________= <br clear=3D"none">> > Users mailing list<br clear=3D"none">>= ; > <a shape=3D"rect" ymailto=3D"mailto:Users@ovirt.org" href=3D"m= ailto:Users@ovirt.org">Users@ovirt.org</a> <mailto:<a shape=3D"rect" yma= ilto=3D"mailto:Users@ovirt.org" href=3D"mailto:Users@ovirt.org">Users@ovirt= .org</a>><div class=3D"yqt6536836530" id=3D"yqtfd61729"><br clear=3D"non= e">> > <a shape=3D"rect" href=3D"http://lists.ovirt.org/mailman= /listinfo/users" target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/= users</a><br clear=3D"none">><br clear=3D"none">><br clear=3D"none">&= gt;<br clear=3D"none">><br clear=3D"none">><br clear=3D"none">> __= _____________________________________________<br clear=3D"none">> Users = mailing list<br clear=3D"none">> <a shape=3D"rect" ymailto=3D"mailto:Use= rs@ovirt.org" href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a><br clear=3D"none">>= <a shape=3D"rect" href=3D"http://lists.ovirt.org/mailman/listinfo/users" t= arget=3D"_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br clear= =3D"none">><br clear=3D"none"><br clear=3D"none"></div><br><br></div> <= /div> </div> </div> </div></body></html> ---1504104896-943642325-1384345221=:44659--