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--