12:44 a.m.
---1504104896-299338706-1384321468=:29063
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
I have just set up an Ovirt 3.3.0 install and have done a test install of C=
entos 6.4 in a VM.=A0 The VM was configured with an IDE drive and a virtio-=
scsi drive.=A0 The Centos 6.4 install sees both drives OK.=0AI'm wanting to=
do some testing on a product that is based on EL5, but I'm finding that it=
cannot see the virtio-scsi drive.=A0 It does show up in the output of 'lsp=
ci', but I don't see a corresponding 'sd' device.=0A=0AI've just tried
inst=
alling Centos 5.10 and the support is not there.=0A=0ADoes anyone know of a=
ny tricks to allow EL5 to see the virtio-scsi device?
---1504104896-299338706-1384321468=:29063
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"><div>I have just set
=
up an Ovirt 3.3.0 install and have done a test install of Centos 6.4 in a V=
M. The VM was configured with an IDE drive and a virtio-scsi drive.&n=
bsp; The Centos 6.4 install sees both drives OK.</div><div>I'm wanting to
d=
o some testing on a product that is based on EL5, but I'm finding that it c=
annot see the virtio-scsi drive. It does show up in the output of 'ls=
pci', but I don't see a corresponding 'sd'
device.<br></div><div>I've just =
tried installing Centos 5.10 and the support is not
there.</div><div><br></=
div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: times =
new roman,new york,times,serif; background-color: transparent; font-style: =
normal;">Does anyone know of any tricks to allow EL5 to see the virtio-scsi=
device?<br></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px;
font-family: times new roman,new york,times,serif; background-color: trans=
parent; font-style:
normal;"><span><br></span></div></div></body></html>
---1504104896-299338706-1384321468=:29063--
3:32 a.m.
Hi,
afaik the rhel 5 kernel series just has not the necessary drivers for
all virtio stuff, so it's not supported and does not work, unless
you want to patch your own kernel.
Am 13.11.2013 06:44, schrieb Paul Jansen:
I have just set up an Ovirt 3.3.0 install and have done a test
install of Centos 6.4 in a VM. The VM was configured with an IDE drive and a virtio-scsi
drive. The Centos 6.4 install sees both drives OK.
I'm wanting to do some testing on a product that is based on EL5, but I'm finding
that it cannot see the virtio-scsi drive. It does show up in the output of
'lspci', but I don't see a corresponding 'sd' device.
I've just tried installing Centos 5.10 and the support is not there.
Does anyone know of any tricks to allow EL5 to see the virtio-scsi device?
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
3:41 a.m.
According to https://access.redhat.com/site/solutions/20511 virtio
work on > rhel5.3.
You have to edit /etc/modprobe.conf and generate a new initrd.
On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <S.Kieske(a)mittwald.de> wrote:
Hi,
afaik the rhel 5 kernel series just has not the necessary drivers for
all virtio stuff, so it's not supported and does not work, unless
you want to patch your own kernel.
Am 13.11.2013 06:44, schrieb Paul Jansen:
> I have just set up an Ovirt 3.3.0 install and have done a test install of Centos 6.4
in a VM. The VM was configured with an IDE drive and a virtio-scsi drive. The Centos 6.4
install sees both drives OK.
> I'm wanting to do some testing on a product that is based on EL5, but I'm
finding that it cannot see the virtio-scsi drive. It does show up in the output of
'lspci', but I don't see a corresponding 'sd' device.
>
> I've just tried installing Centos 5.10 and the support is not there.
>
> Does anyone know of any tricks to allow EL5 to see the virtio-scsi device?
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:53 a.m.
On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:
According to https://access.redhat.com/site/solutions/20511 virtio
work on > rhel5.3.
You have to edit /etc/modprobe.conf and generate a new initrd.
If you're installing the OS on a VirtIO disk this is done automatically
by anaconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and
everything worked out of the box.
On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <S.Kieske(a)mittwald.de> wrote:
> Hi,
>
> afaik the rhel 5 kernel series just has not the necessary drivers for
> all virtio stuff, so it's not supported and does not work, unless
> you want to patch your own kernel.
>
> Am 13.11.2013 06:44, schrieb Paul Jansen:
>> I have just set up an Ovirt 3.3.0 install and have done a test install of Centos
6.4 in a VM. The VM was configured with an IDE drive and a virtio-scsi drive. The Centos
6.4 install sees both drives OK.
>> I'm wanting to do some testing on a product that is based on EL5, but
I'm finding that it cannot see the virtio-scsi drive. It does show up in the output
of 'lspci', but I don't see a corresponding 'sd' device.
>>
There's no /dev/sd* device - the devices are named /dev/vd*...
>> I've just tried installing Centos 5.10 and the support
is not there.
Didn't test CentOS but RHEL 5 is working fine.
Regards,
René
>>
>> Does anyone know of any tricks to allow EL5 to see the virtio-scsi device?
>
>
> --
> Mit freundlichen Grüßen / Regards
>
> Sven Kieske
>
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +49-5772-293-100
> F: +49-5772-293-333
> https://www.mittwald.de
> Geschäftsführer: Robert Meyer
> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:58 a.m.
--708812334-1801761447-1384333128=:57910
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Rene.=0AI specifically need the scsi support (virtio-scsi).=0AI do know =
about the virtio-block support, which results in /dev/vd* devices as you sa=
y.=0AFrom what I read even EL6 earlier than 6.3 does not support virtio-scs=
i=0A=0AAlternatively, does oVirt support an emulated scsi adapter of a diff=
erent type that would allow me to see scsi disks?=0A=0ARegards,=0APaul=0A=
=0A=0A=0A=0AOn Wednesday, 13 November 2013 7:23 PM, Ren=E9 Koch (ovido) <r.=
koch(a)ovido.at> wrote:=0A =0AOn Wed, 2013-11-13 at 09:41 +0100, Sander Grend=
elman wrote:=0A> According to https://access.redhat.com/site/solutions/2051=
1 virtio=0A> work on > rhel5.3.=0A> =0A> You have to edit /etc/modprobe.con=
f and generate a new initrd.=0A=0A=0AIf you're installing the OS on a VirtI=
O disk this is done automatically=0Aby anaconda. I just installed RHEL 5 on=
oVirt 3.3 with VirtIO disk and=0Aeverything worked out of the box.=0A=0A=
=0A> =0A> On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <S.Kieske(a)mittwald.d=
e> wrote:=0A> > Hi,=0A> >=0A> > afaik the rhel 5 kernel series just
has not=
the necessary drivers for=0A> > all virtio stuff, so it's not supported an=
d does not work, unless=0A> > you want to patch your own kernel.=0A> >=0A>
=
Am 13.11.2013 06:44, schrieb Paul Jansen:=0A> >> I have just
set up an Ov=
irt 3.3.0 install and have done a test install of Centos 6.4 in a
VM.=A0 Th=
e VM was configured with an IDE drive and a virtio-scsi drive.=A0 The Cento=
s 6.4 install sees both drives OK.=0A> >> I'm wanting to do some testing on=
a product that is based on EL5, but I'm finding that it cannot see the vir=
tio-scsi drive.=A0 It does show up in the output of 'lspci', but I don't se=
e a corresponding 'sd' device.=0A> >>=0A=0A=0AThere's no /dev/sd*
device - =
the devices are named /dev/vd*...=0A=0A=0A> >> I've just tried installing C=
entos 5.10 and the support is not there.=0A=0A=0ADidn't test CentOS but RHE=
L 5 is working fine.=0A=0A=0ARegards,=0ARen=E9=0A=0A=0A=0A> >>=0A> >>
Does =
anyone know of any tricks to allow EL5 to see the virtio-scsi device?=0A> >=
=0A> >=0A> > --=0A> > Mit freundlichen Gr=FC=DFen / Regards=0A>
>=0A> > Sve=
n Kieske=0A> >=0A> > Systemadministrator=0A> > Mittwald CM Service GmbH
& C=
o. KG=0A> > K=F6nigsberger Stra=DFe 6=0A> > 32339 Espelkamp=0A> > T:
+49-57=
72-293-100=0A> > F: +49-5772-293-333=0A> > https://www.mittwald.de=0A> >
Ge=
sch=E4ftsf=FChrer: Robert Meyer=0A> > St.Nr.: 331/5721/1033, USt-IdNr.: DE8=
14773217, HRA 6640, AG Bad Oeynhausen=0A> > Komplement=E4rin: Robert Meyer =
Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen=0A> > ______________________=
_________________________=0A> > Users mailing list=0A> > Users(a)ovirt.org=0A=
> http://lists.ovirt.org/mailman/listinfo/users=0A>
_____________________=
__________________________=0A> Users mailing list=0A>
Users(a)ovirt.org=0A> h=
ttp://lists.ovirt.org/mailman/listinfo/users
--708812334-1801761447-1384333128=:57910
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 Rene.<br>I
specifi=
cally need the scsi support (virtio-scsi).<br>I do know about the virtio-bl=
ock support, which results in /dev/vd* devices as you say.<br>From what I r=
ead even EL6 earlier than 6.3 does not support virtio-scsi<br><br>Alternati=
vely, does oVirt support an emulated scsi adapter of a different type that =
would allow me to see scsi
disks?<br><br>Regards,<br>Paul<br><div style=3D"=
display: block;" class=3D"yahoo_quoted"> <br> <br> <div
style=3D"font-famil=
y: times new roman, new york, times, serif; font-size: 12pt;"> <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 Wednesday, 13 Novem=
ber 2013 7:23 PM, Ren=E9 Koch
(ovido) &lt;r.koch(a)ovido.at&gt; wrote:<br> </=
font> </div> <div class=3D"y_msg_container">On Wed, 2013-11-13
at 09:41 +0=
100, Sander
Grendelman wrote:<br>> According to <a
href=3D"https://access.redhat.co=
m/site/solutions/20511"
target=3D"_blank">https://access.redhat.com/site/so=
lutions/20511 </a>virtio<br>> work on >
rhel5.3.<br>> <br>> You=
have to edit /etc/modprobe.conf and generate a new
initrd.<br><br><br>If y=
ou're installing the OS on a VirtIO disk this is done automatically<br>by a=
naconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and<br>every=
thing worked out of the box.<br><br><br>> <br>> On
Wed, Nov 13, 2013 =
at 9:32 AM, Sven Kieske <<a ymailto=3D"mailto:S.Kieske@mittwald.de"
href=
=3D"mailto:S.Kieske@mittwald.de">S.Kieske@mittwald.de</a>>
wrote:<br>>=
; > Hi,<br>> ><br>> > afaik the rhel 5
kernel series just ha=
s not the necessary drivers for<br>> > all virtio stuff, so it's
not =
supported and does not work, unless<br>> > you want to patch your
own=
kernel.<br>> ><br>> > Am 13.11.2013 06:44,
schrieb Paul
Jansen:<br>> >> I have just set up an Ovirt 3.3.0 install and
hav=
e done a test install of Centos 6.4 in a VM. The VM was configured wi=
th an IDE drive and a virtio-scsi drive. The Centos 6.4 install sees =
both drives OK.<br>> >> I'm wanting to do some testing on a
produc=
t that is based on EL5, but I'm finding that it cannot see the virtio-scsi =
drive. It does show up in the output of 'lspci', but I don't see a
co=
rresponding 'sd' device.<br>>
>><br><br><br>There's no /dev/sd* de=
vice - the devices are named /dev/vd*...<br><br><br>>
>> I've just=
tried installing Centos 5.10 and the support is not
there.<br><br><br>Didn=
't test CentOS but RHEL 5 is working
fine.<br><br><br>Regards,<br>Ren=E9<br=
<br><br><br>>
>><br>> >> Does anyone know of any tricks =
to allow EL5 to see the virtio-scsi device?<br>>
><br>> ><br>&g=
t; > --<br>> > Mit freundlichen Gr=FC=DFen /
Regards<br>>
><br>> > Sven Kieske<br>>
><br>> > Systemadministrato=
r<br>> > Mittwald CM Service GmbH & Co. KG<br>>
> K=F6nigsb=
erger Stra=DFe 6<br>> > 32339 Espelkamp<br>> > T:
+49-5772-293-=
100<br>> > F: +49-5772-293-333<br>> > <a
href=3D"https://www.mi=
ttwald.de/"
target=3D"_blank">https://www.mittwald.de</a><br>>
> Gesc=
h=E4ftsf=FChrer: Robert Meyer<br>> > St.Nr.: 331/5721/1033,
USt-IdNr.=
: DE814773217, HRA 6640, AG Bad Oeynhausen<br>> > Komplement=E4rin:
R=
obert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen<br>> >
___=
____________________________________________<br>> > Users mailing
lis=
t<br>> > <a ymailto=3D"mailto:Users@ovirt.org"
href=3D"mailto:Users@o=
virt.org">Users(a)ovirt.org</a><br>&gt; > <a
href=3D"http://lists.ovirt.or=
g/mailman/listinfo/users"
target=3D"_blank">http://lists.ovirt.org/mailman/=
listinfo/users</a><br>>
_______________________________________________<=
br>>
Users mailing list<br>> <a ymailto=3D"mailto:Users@ovirt.org"
href=3D"m=
ailto:Users@ovirt.org">Users@ovirt.org</a><br>> <a
href=3D"http://lists.=
ovirt.org/mailman/listinfo/users"
target=3D"_blank">http://lists.ovirt.org/=
mailman/listinfo/users</a><br><br><br><br></div>
</div> </div> </div> </d=
iv></body></html>
--708812334-1801761447-1384333128=:57910--
4:07 a.m.
I specifically need the scsi support (virtio-scsi).
I do know about the virtio-block support, which results in /dev/vd*
devices as you say.
From what I read even EL6 earlier than 6.3 does not support
virtio-scsi
Sorry, I did read your email to fast as it seems.
You're right you need at least RHEL 6.3 for virtio-scsi support.
Alternatively, does oVirt support an emulated scsi adapter of a
different type that would allow me to see scsi disks?
Regards,
Paul
On Wednesday, 13 November 2013 7:23 PM, René Koch (ovido)
<r.koch(a)ovido.at> wrote:
On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:
> According to https://access.redhat.com/site/solutions/20511 virtio
> work on > rhel5.3.
>
> You have to edit /etc/modprobe.conf and generate a new initrd.
If you're installing the OS on a VirtIO disk this is done
automatically
by anaconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and
everything worked out of the box.
>
> On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <S.Kieske(a)mittwald.de>
wrote:
> > Hi,
> >
> > afaik the rhel 5 kernel series just has not the necessary drivers
for
> > all virtio stuff, so it's not supported and does not work, unless
> > you want to patch your own kernel.
> >
> > Am 13.11.2013 06:44, schrieb Paul Jansen:
> >> I have just set up an Ovirt 3.3.0 install and have done a test
install of Centos 6.4 in a VM. The VM was configured with an IDE
drive and a virtio-scsi drive. The Centos 6.4 install sees both
drives OK.
> >> I'm wanting to do some testing on a product that is based on EL5,
but I'm finding that it cannot see the virtio-scsi drive. It does
show up in the output of 'lspci', but I don't see a corresponding
'sd'
device.
> >>
There's no /dev/sd* device - the devices are named /dev/vd*...
> >> I've just tried installing Centos 5.10 and the support is not
there.
Didn't test CentOS but RHEL 5 is working fine.
Regards,
René
> >>
> >> Does anyone know of any tricks to allow EL5 to see the
virtio-scsi device?
> >
> >
> > --
> > Mit freundlichen Grüßen / Regards
> >
> > Sven Kieske
> >
> > Systemadministrator
> > Mittwald CM Service GmbH & Co. KG
> > Königsberger Straße 6
> > 32339 Espelkamp
> > T: +49-5772-293-100
> > F: +49-5772-293-333
> > https://www.mittwald.de
> > Geschäftsführer: Robert Meyer
> > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad
Oeynhausen
> > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
Oeynhausen
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
4:19 a.m.
On Wed, Nov 13, 2013 at 9:58 AM, Paul Jansen wrote:
Hi Rene.
I specifically need the scsi support (virtio-scsi).
I do know about the virtio-block support, which results in /dev/vd* devices
as you say.
From what I read even EL6 earlier than 6.3 does not support virtio-scsi
Alternatively, does oVirt support an emulated scsi adapter of a different
type that would allow me to see scsi disks?
Regards,
Paul
Hello Paul,
in 6.3 virtio-scsi was only a TechPreview.
From 6.4 it is fully supported.
I found also support in Win
guests (> WinXP) with RHEV and updated
virtio-win drivers, but nothing abut rhel 5.x guests, neither 5.10...
If you have RH EL subscription you can find more details here:
https://access.redhat.com/site/solutions/300563
(I took the time to put a note asking about support in RH EL 5.x)
It could be a good idea to create an rfe entry in bugzilla if you have
entitlements.
I don't know if there is any particular limitation or special
backporting effort to gain virtio-scsi support in RHEL 5.x, but
through my quick search I didn't find any reference in special repos
such as CentOS extra er plus or elrepo....
I think you already saw here, but just for other ones eventually:
http://www.ovirt.org/Features/Virtio-SCSI
5:27 a.m.
On 11/13/2013 03:58 AM, Paul Jansen wrote:
Hi Rene.
I specifically need the scsi support (virtio-scsi).
I do know about the virtio-block support, which results in /dev/vd*
devices as you say.
From what I read even EL6 earlier than 6.3 does not support virtio-scsi
Alternatively, does oVirt support an emulated scsi adapter of a
different type that would allow me to see scsi disks?
may i ask why do you need the virtual disks to specifically be scsi?
Regards,
Paul
On Wednesday, 13 November 2013 7:23 PM, René Koch (ovido)
<r.koch(a)ovido.at> wrote:
On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:
> According to https://access.redhat.com/site/solutions/20511
<https://access.redhat.com/site/solutions/20511>virtio
> work on > rhel5.3.
>
> You have to edit /etc/modprobe.conf and generate a new initrd.
If you're installing the OS on a VirtIO disk this is done automatically
by anaconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and
everything worked out of the box.
>
> On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske <S.Kieske(a)mittwald.de
<mailto:S.Kieske@mittwald.de>> wrote:
> > Hi,
> >
> > afaik the rhel 5 kernel series just has not the necessary drivers for
> > all virtio stuff, so it's not supported and does not work, unless
> > you want to patch your own kernel.
> >
> > Am 13.11.2013 06:44, schrieb Paul Jansen:
> >> I have just set up an Ovirt 3.3.0 install and have done a test
install of Centos 6.4 in a VM. The VM was configured with an IDE drive
and a virtio-scsi drive. The Centos 6.4 install sees both drives OK.
> >> I'm wanting to do some testing on a product that is based on EL5,
but I'm finding that it cannot see the virtio-scsi drive. It does show
up in the output of 'lspci', but I don't see a corresponding 'sd'
device.
> >>
There's no /dev/sd* device - the devices are named /dev/vd*...
> >> I've just tried installing Centos 5.10 and the support is not there.
Didn't test CentOS but RHEL 5 is working fine.
Regards,
René
> >>
> >> Does anyone know of any tricks to allow EL5 to see the virtio-scsi
device?
> >
> >
> > --
> > Mit freundlichen Grüßen / Regards
> >
> > Sven Kieske
> >
> > Systemadministrator
> > Mittwald CM Service GmbH & Co. KG
> > Königsberger Straße 6
> > 32339 Espelkamp
> > T: +49-5772-293-100
> > F: +49-5772-293-333
> > https://www.mittwald.de <https://www.mittwald.de/>
> > Geschäftsführer: Robert Meyer
> > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad
Oeynhausen
> > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
Oeynhausen
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org <mailto:Users@ovirt.org>
> > http://lists.ovirt.org/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:20 a.m.
---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(a)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(a)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=
=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=
lichen Gr=FC=DFen / Regards=0A>=A0 > >=0A>=A0 > > Sven Kieske=0A>=A0
> >=0A=
=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/=
listinfo/users=0A>=A0 > _______________________________________________=0A>=
=A0 > Users mailing list=0A>=A0 > Users(a)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(a)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;"=
<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 &lt;iheim(a)redhat.com&gt; 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=
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(a)ovido.at</a>&gt; 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/2...
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"=
><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"
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(a)ovirt.org</a>&gt;<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/us...
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(a)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/use...
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--
2:04 a.m.
Hi Paul,
First of all, thanks for the detailed answer, it really helps.
See comments inline.
----- Original Message -----
Hello Itamar.
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.
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.
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.
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.
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.
virtio-scsi support was just recently added to oVirt to allow for scsi passthrough and
improved performance over virtio-blk.
I believe the emulated scsi device in qemu never matured enough but possibly Stefan
(cc'd) can correct me here.
For simplicity sake we kept choosing the controller type out but there is nothing in the
design preventing one from adding it. This is however the first time I've actually
heard any requests for it.
Note that using hooks you can still enable any functionality that qemu-kvm supports but is
not exposed in the GUI. It's not the most elegant way, but it works.
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.
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.
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.
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.
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'.
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.
Cheers,
Paul
On Wednesday, 13 November 2013 8:57 PM, Itamar Heim <iheim(a)redhat.com> wrote:
On 11/13/2013 03:58 AM, Paul Jansen wrote:
> Hi Rene.
> I specifically need the scsi support (virtio-scsi).
> I do know about the virtio-block support, which results in /dev/vd*
> devices as you say.
> From what I read even EL6 earlier than 6.3 does not support virtio-scsi
>
> Alternatively, does oVirt support an emulated scsi adapter of a
> different type that would allow me to see scsi disks?
may i ask why do you need the virtual disks to specifically be scsi?
>
> Regards,
> Paul
>
>
> On Wednesday, 13 November 2013 7:23 PM, René Koch (ovido)
> < r.koch(a)ovido.at > wrote:
> On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:
> > According to https://access.redhat.com/site/solutions/20511
> < https://access.redhat.com/site/solutions/20511 >virtio
> > work on > rhel5.3.
> >
> > You have to edit /etc/modprobe.conf and generate a new initrd.
>
>
> If you're installing the OS on a VirtIO disk this is done automatically
> by anaconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and
> everything worked out of the box.
>
>
> >
> > On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske < S.Kieske(a)mittwald.de
> <mailto: S.Kieske(a)mittwald.de >> wrote:
> > > Hi,
> > >
> > > afaik the rhel 5 kernel series just has not the necessary drivers for
> > > all virtio stuff, so it's not supported and does not work, unless
> > > you want to patch your own kernel.
> > >
> > > Am 13.11.2013 06:44, schrieb Paul Jansen:
> > >> I have just set up an Ovirt 3.3.0 install and have done a test
> install of Centos 6.4 in a VM. The VM was configured with an IDE drive
> and a virtio-scsi drive. The Centos 6.4 install sees both drives OK.
> > >> I'm wanting to do some testing on a product that is based on EL5,
> but I'm finding that it cannot see the virtio-scsi drive. It does show
> up in the output of 'lspci', but I don't see a corresponding
'sd' device.
> > >>
>
>
> There's no /dev/sd* device - the devices are named /dev/vd*...
>
>
> > >> I've just tried installing Centos 5.10 and the support is not
there.
>
>
> Didn't test CentOS but RHEL 5 is working fine.
>
>
> Regards,
> René
>
>
>
> > >>
> > >> Does anyone know of any tricks to allow EL5 to see the virtio-scsi
> device?
> > >
> > >
> > > --
> > > Mit freundlichen Grüßen / Regards
> > >
> > > Sven Kieske
> > >
> > > Systemadministrator
> > > Mittwald CM Service GmbH & Co. KG
> > > Königsberger Straße 6
> > > 32339 Espelkamp
> > > T: +49-5772-293-100
> > > F: +49-5772-293-333
> > > https://www.mittwald.de < https://www.mittwald.de/ >
> > > Geschäftsführer: Robert Meyer
> > > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad
> Oeynhausen
> > > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
> Oeynhausen
> > > _______________________________________________
> > > Users mailing list
> > > Users(a)ovirt.org <mailto: Users(a)ovirt.org >
> > > http://lists.ovirt.org/mailman/listinfo/users
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org <mailto: Users(a)ovirt.org >
> > http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2:39 a.m.
Adding Stefan with the correct email this time.
----- Original Message -----
Hi Paul,
First of all, thanks for the detailed answer, it really helps.
See comments inline.
----- Original Message -----
> Hello Itamar.
> 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.
> 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.
>
> 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.
> 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.
> 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.
virtio-scsi support was just recently added to oVirt to allow for scsi
passthrough and improved performance over virtio-blk.
I believe the emulated scsi device in qemu never matured enough but possibly
Stefan (cc'd) can correct me here.
For simplicity sake we kept choosing the controller type out but there is
nothing in the design preventing one from adding it. This is however the
first time I've actually heard any requests for it.
Note that using hooks you can still enable any functionality that qemu-kvm
supports but is not exposed in the GUI. It's not the most elegant way, but
it works.
> 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.
> 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.
> 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.
> 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.
>
> 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'.
>
> 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.
>
> Cheers,
> Paul
>
>
> On Wednesday, 13 November 2013 8:57 PM, Itamar Heim <iheim(a)redhat.com>
> wrote:
> On 11/13/2013 03:58 AM, Paul Jansen wrote:
> > Hi Rene.
> > I specifically need the scsi support (virtio-scsi).
> > I do know about the virtio-block support, which results in /dev/vd*
> > devices as you say.
> > From what I read even EL6 earlier than 6.3 does not support virtio-scsi
> >
> > Alternatively, does oVirt support an emulated scsi adapter of a
> > different type that would allow me to see scsi disks?
>
> may i ask why do you need the virtual disks to specifically be scsi?
>
> >
> > Regards,
> > Paul
> >
> >
> > On Wednesday, 13 November 2013 7:23 PM, René Koch (ovido)
> > < r.koch(a)ovido.at > wrote:
> > On Wed, 2013-11-13 at 09:41 +0100, Sander Grendelman wrote:
> > > According to https://access.redhat.com/site/solutions/20511
> > < https://access.redhat.com/site/solutions/20511 >virtio
> > > work on > rhel5.3.
> > >
> > > You have to edit /etc/modprobe.conf and generate a new initrd.
> >
> >
> > If you're installing the OS on a VirtIO disk this is done automatically
> > by anaconda. I just installed RHEL 5 on oVirt 3.3 with VirtIO disk and
> > everything worked out of the box.
> >
> >
> > >
> > > On Wed, Nov 13, 2013 at 9:32 AM, Sven Kieske < S.Kieske(a)mittwald.de
> > <mailto: S.Kieske(a)mittwald.de >> wrote:
> > > > Hi,
> > > >
> > > > afaik the rhel 5 kernel series just has not the necessary drivers
for
> > > > all virtio stuff, so it's not supported and does not work,
unless
> > > > you want to patch your own kernel.
> > > >
> > > > Am 13.11.2013 06:44, schrieb Paul Jansen:
> > > >> I have just set up an Ovirt 3.3.0 install and have done a test
> > install of Centos 6.4 in a VM. The VM was configured with an IDE drive
> > and a virtio-scsi drive. The Centos 6.4 install sees both drives OK.
> > > >> I'm wanting to do some testing on a product that is based on
EL5,
> > but I'm finding that it cannot see the virtio-scsi drive. It does show
> > up in the output of 'lspci', but I don't see a corresponding
'sd' device.
> > > >>
> >
> >
> > There's no /dev/sd* device - the devices are named /dev/vd*...
> >
> >
> > > >> I've just tried installing Centos 5.10 and the support is not
there.
> >
> >
> > Didn't test CentOS but RHEL 5 is working fine.
> >
> >
> > Regards,
> > René
> >
> >
> >
> > > >>
> > > >> Does anyone know of any tricks to allow EL5 to see the
virtio-scsi
> > device?
> > > >
> > > >
> > > > --
> > > > Mit freundlichen Grüßen / Regards
> > > >
> > > > Sven Kieske
> > > >
> > > > Systemadministrator
> > > > Mittwald CM Service GmbH & Co. KG
> > > > Königsberger Straße 6
> > > > 32339 Espelkamp
> > > > T: +49-5772-293-100
> > > > F: +49-5772-293-333
> > > > https://www.mittwald.de < https://www.mittwald.de/ >
> > > > Geschäftsführer: Robert Meyer
> > > > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad
> > Oeynhausen
> > > > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
> > Oeynhausen
> > > > _______________________________________________
> > > > Users mailing list
> > > > Users(a)ovirt.org <mailto: Users(a)ovirt.org >
> > > > http://lists.ovirt.org/mailman/listinfo/users
> > > _______________________________________________
> > > Users mailing list
> > > Users(a)ovirt.org <mailto: Users(a)ovirt.org >
>
> > > http://lists.ovirt.org/mailman/listinfo/users
> >
> >
> >
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
7:51 a.m.
On Thu, Nov 14, 2013 at 02:39:33AM -0500, Ayal Baron wrote:
> ----- Original Message -----
> > Hello Itamar.
> > 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.
> > 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.
> >
> > 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.
> > 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.
> > 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.
>
> virtio-scsi support was just recently added to oVirt to allow for scsi
> passthrough and improved performance over virtio-blk.
> I believe the emulated scsi device in qemu never matured enough but possibly
> Stefan (cc'd) can correct me here.
The only supported emulated SCSI HBA device is virtio-scsi. It was Tech
Preview in RHEL 6.3 and became fully supported in RHEL 6.4. virtio-scsi
is not available in RHEL 5.
Stefan
9:09 a.m.
--1060583355-139603096-1384438153=:20660
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hello Stefan.=0AThanks.=A0 I understand qemu supports other scsi adapters h=
owever.=A0 See this post from earlier this year.=0AThat post makes referenc=
e to the following hbas: auto, buslogic, ibmvscsi. lsilogic, lsisas1068, ls=
isas1078, virtio-scsi, vmpvscsi.=0AThe post is referring to libvirt, so the=
number of adapters may be related to the various virtualization backends t=
hat libvirt can interface with.=0A=0AThere are numerous references to qemu/=
qemu-kvm supporting other scsi adapters as well as AHCI SATA.=A0 I installe=
d the Centos 6.4 based node, so perhaps the Fedora 19 based node has a newe=
r qemu that supports more of these features?=A0 I might see if I can do an =
install of the Fedora 19 based node tomorrow.=0A=0AAyal mentioned using 'ho=
oks' to interface with qemu to possibly create a VM outside of the definiti=
ons that Ovirt allows.=A0 If I am understanding this correctly - how do I d=
o this?=A0 Am I to expect some interface inconsistencies in the ovirt porta=
l I I view a 'custom' VM like this?=0A=0ASo, in short - is there the potent=
ial 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)?=0A=0A=0A=0A=0AOn Thursday, 14 November 2013 11:22 PM, Stefan Hajnoczi=
<stefanha(a)redhat.com> wrote:=0A =0AOn Thu, Nov 14, 2013 at 02:39:33AM -050=
0, Ayal Baron wrote:=0A> > ----- Original Message -----=0A> > > Hello
Itama=
r.=0A> > > The specific use case is a particular propriety filesystem that =
needs to=0A> > > see=0A> > > a scsi device. It will do scsi inquiry
conmman=
ds to verify suitability.=0A> > > In talking to the devs - of the filesyste=
m - there is no way around it. I'd=0A> > > previously tried virtio-block - =
resulting in the /dev/vd* device - and the=0A> > > filesystem would not wor=
k.=0A> > > =0A> > > From doing a bit of web searching it appears the
kvm/qe=
mu supports (or did=0A> > > support) an emulated LSI scsi controller. My un=
derstanding is that the=0A> > > various virtualization platforms will emula=
te a well supported device (by=0A> > > the guest OSes) so that drivers are =
not an issue. For example this should=0A> > > allow a VM on Vmware vsphere/=
vcenter to be exported to Ovirt and have it=0A> > > boot up. The potential =
for further optimising the guest is there by=0A> > > installing ovirt/qemu/=
kvm guest utils that then allow the guest OS to=0A> > > understand the virt=
io nic and scsi devices. The guest could then be shut=0A> > > down, the nic=
and scsi controller changed and the guest booted up again.=0A> > > You can=
do the same thing in the Vmware world by installing their guest=0A> > > to=
ols, shutting down the guest VM, then reconfiguring it with a vmxnet3 nic=
=0A> > > and pvscsi scsi adapter, then booting up again.=0A> > > It does
se=
em somewhat inconsistent in Ovirt that we allow a choice of Intel=0A> > > e=
1000 or virtio nics, but do not offer any choice with the scsi adapter.=0A>=
=0A> > virtio-scsi support was just recently added to oVirt to
allow for=
scsi=0A> > passthrough and improved performance over
virtio-blk.=0A> > I b=
elieve the emulated scsi device in qemu never matured enough but possibly=
=0A> > Stefan (cc'd) can correct me here.=0A=0AThe only supported emulated =
SCSI HBA device is virtio-scsi.=A0 It was Tech=0APreview in RHEL 6.3 and be=
came fully supported in RHEL 6.4.=A0 virtio-scsi=0Ais not available in RHEL=
5.=0A=0A=0AStefan
--1060583355-139603096-1384438153=:20660
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
Stefan.<br>Than=
ks. I understand qemu supports other scsi adapters however. See=
<a href=3D"https://www.redhat.com/archives/libvir-list/2013-March/msg01...
.html"><span>this</span></a> post from earlier this
year.<br>That post make=
s reference to the following hbas: auto, buslogic, ibmvscsi. lsilogic, lsis=
as1068, lsisas1078, virtio-scsi, vmpvscsi.<br>The post is referring to libv=
irt, so the number of adapters may be related to the various virtualization=
backends that libvirt can interface with.<br><br>There are numerous refere=
nces to qemu/qemu-kvm supporting other scsi adapters as well as AHCI SATA.&=
nbsp; 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 po=
ssibly 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 s=
ome interface inconsistencies in the ovirt portal I I view a 'custom' VM li=
ke 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=3D"di=
splay: block;" class=3D"yahoo_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 roman, new york, times, serif; font-size: 12pt;"> <d=
iv dir=3D"ltr"> <font size=3D"2" face=3D"Arial"> On
Thursday, 14 November 2=
013 11:22 PM, Stefan Hajnoczi &lt;stefanha(a)redhat.com&gt; wrote:<br>
</font=
</div> <div class=3D"y_msg_container">On Thu,
Nov 14, 2013 at 02:39:33AM=
-0500,
Ayal Baron wrote:<br clear=3D"none">> > ----- Original
Message -----=
<br clear=3D"none">> > > Hello Itamar.<br
clear=3D"none">> >=
> The specific use case is a particular propriety filesystem that needs=
to<br clear=3D"none">> > > see<br
clear=3D"none">> > > a=
scsi device. It will do scsi inquiry conmmands to verify suitability.<br c=
lear=3D"none">> > > In talking to the devs - of the
filesystem - t=
here is no way around it. I'd<br clear=3D"none">> >
> previously t=
ried virtio-block - resulting in the /dev/vd* device - and the<br clear=3D"=
none">> > > filesystem would not work.<br
clear=3D"none">> >=
> <br clear=3D"none">> > > From doing a bit
of web searching i=
t appears the kvm/qemu supports (or did<br clear=3D"none">>
> > su=
pport) an emulated LSI scsi controller. My understanding is that the<br cle=
ar=3D"none">> > > various virtualization platforms will
emulate a =
well supported
device (by<br clear=3D"none">> > > the guest OSes)
so that driver=
s are not an issue. For example this should<br clear=3D"none">>
> >=
; allow a VM on Vmware vsphere/vcenter to be exported to Ovirt and have it<=
br clear=3D"none">> > > boot up. The potential for
further optimis=
ing the guest is there by<br clear=3D"none">> > >
installing ovirt=
/qemu/kvm guest utils that then allow the guest OS to<br
clear=3D"none">>=
; > > understand the virtio nic and scsi devices. The guest could the=
n be shut<br clear=3D"none">> > > down, the nic and
scsi controlle=
r changed and the guest booted up again.<br clear=3D"none">>
> > Y=
ou can do the same thing in the Vmware world by installing their guest<br c=
lear=3D"none">> > > tools, shutting down the guest VM,
then reconf=
iguring it with a vmxnet3 nic<br clear=3D"none">> > >
and pvscsi s=
csi adapter, then booting up again.<br clear=3D"none">> >
> It doe=
s seem
somewhat inconsistent in Ovirt that we allow a choice of Intel<br clear=3D=
"none">> > > e1000 or virtio nics, but do not offer any
choice wit=
h the scsi adapter.<br clear=3D"none">> > <br
clear=3D"none">> >=
; virtio-scsi support was just recently added to oVirt to allow for scsi<br=
clear=3D"none">> > passthrough and improved performance over
virtio-=
blk.<br clear=3D"none">> > I believe the emulated scsi
device in qemu=
never matured enough but possibly<br clear=3D"none">> >
Stefan (cc'd=
) can correct me here.<br clear=3D"none"><br
clear=3D"none">The only suppor=
ted emulated SCSI HBA device is virtio-scsi. It was Tech<br clear=3D"=
none">Preview in RHEL 6.3 and became fully supported in RHEL 6.4. vir=
tio-scsi<br clear=3D"none">is not available in RHEL 5.<div
class=3D"yqt2796=
650658" id=3D"yqtfd21253"><br clear=3D"none"><br
clear=3D"none">Stefan<br c=
lear=3D"none"></div><br><br></div> </div>
</div> </div> </div></body></ht=
ml>
--1060583355-139603096-1384438153=:20660--
10:33 a.m.
On 11/14/2013 09:09 AM, Paul Jansen wrote:
Hello Stefan.
Thanks. I understand qemu supports other scsi adapters however. See
this
<https://www.redhat.com/archives/libvir-list/2013-March/msg01254.html>
post from earlier this year.
That post makes reference to the following hbas: auto, buslogic,
ibmvscsi. lsilogic, lsisas1068, lsisas1078, virtio-scsi, vmpvscsi.
The post is referring to libvirt, so the number of adapters may be
related to the various virtualization backends that libvirt can
interface with.
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.
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?
hooks are compatible with the ui. you'd define a custom property with
scsi=xxx or something like that.
see for more detials:
http://www.ovirt.org/VDSM-Hooks
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)?
On Thursday, 14 November 2013 11:22 PM, Stefan Hajnoczi
<stefanha(a)redhat.com> wrote:
On Thu, Nov 14, 2013 at 02:39:33AM -0500, Ayal Baron wrote:
> > ----- Original Message -----
> > > Hello Itamar.
> > > 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.
> > > 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.
> > >
> > > 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.
> > > 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.
> > > 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.
> >
> > virtio-scsi support was just recently added to oVirt to allow for scsi
> > passthrough and improved performance over virtio-blk.
> > I believe the emulated scsi device in qemu never matured enough but
possibly
> > Stefan (cc'd) can correct me here.
The only supported emulated SCSI HBA device is virtio-scsi. It was Tech
Preview in RHEL 6.3 and became fully supported in RHEL 6.4. virtio-scsi
is not available in RHEL 5.
Stefan
3:30 a.m.
On Thu, Nov 14, 2013 at 06:09:13AM -0800, Paul Jansen wrote:
Thanks. I understand qemu supports other scsi adapters however. See
this post from earlier this year.
That post makes reference to the following hbas: auto, buslogic, ibmvscsi. lsilogic,
lsisas1068, lsisas1078, virtio-scsi, vmpvscsi.
From an upstream QEMU perspective, the HBAs that ought to work on
x86_64
guests are virtio-scsi, lsisas1078, and vmpvscsi.
The lsilogic adapter is known to be buggy/incomplete. ibmvscsi is for
POWER, not x86_64.
That said, I'd still only rely on virtio-scsi for production systems.
I am confident there is development effort behind virtio-scsi to fix
bugs and so on. With the other adapters it's more of a best-effort
scenario.
Stefan
5:20 a.m.
Il 15/11/2013 09:30, Stefan Hajnoczi ha scritto:
> > Thanks. I understand qemu supports other scsi adapters
however. See this post from earlier this year.
> > That post makes reference to the following hbas: auto, buslogic, ibmvscsi.
lsilogic, lsisas1068, lsisas1078, virtio-scsi, vmpvscsi.
From an upstream QEMU perspective, the HBAs that ought to work on x86_64
guests are virtio-scsi, lsisas1078, and vmpvscsi.
I think vmpvscsi is not supported for QEMU in libvirt. It would be a
very simple patch, I may get round to it before Christmas...
Paolo
10:40 p.m.
---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(a)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(a)redhat.com&gt; 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--
4055
days inactive
4058
days old
16 comments
9 participants
participants (9)
-
Ayal Baron -
Gianluca Cecchi -
Itamar Heim -
Paolo Bonzini -
Paul Jansen -
René Koch (ovido) -
Sander Grendelman -
Stefan Hajnoczi -
Sven Kieske