2:22 a.m.
---360795340-209196801-1414977774=:40763
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<SNIP>=0A> > > After doing some more searching I came across these two
page=
s:=0A> > > http://www.ovirt.org/Cluster_emulation_modes=0A> > >
http://www.=
ovirt.org/Features/Cluster_parameters_override=0A> > >=0A> > > It sounds
li=
ke this may allow me to achieve what I've described above.=0A> > > From wha=
t I can tell the 'emulated machine type' is tied to the ovirt cluster =0A> =
> level - ie: 3.5.=0A> > >=0A> >=0A> > you
can switch q35 with pc-1.0 in =
ClusterEmulatedMachines config value for =0A>
> version 3.5=0A> Thanks Paul=
for asking and Roy for answering. I thought q35 would be the=0A> default a=
nyway the whole time ;)=0A> >=0A> > engine-config -s ClusterEmulatedMach=
ines=3D"q35,rhel6.5.0"=0A> >=0A> > then create a new cluster and add
that h=
ost to it. once the host is up this =0A> > emulation mode should be set.=0A=
>=0A> > in 3.6 you'd be able to choose an emulation mode
per VM.=0A> Paul=
, since this is really useful would you mind to open an RFE in
BZ=0A> and p=
ost the link here, so we can keep track of this feature?=0A=0AHi Daniel.=0A=
Sorry for the late reply on this.=0AI'm happy that this feature is currentl=
y documented in the wiki pages that I'd referenced above and is on the feat=
ure plan for 3.6.=0AThe workaround that was specified does what I need for =
now.=0AProper support in 3.6 will need to consider some other things, such =
as allowing attaching of disks to the sata interface on the q35 machine.=0A=
3.5s current workflow doesn't provide a way to cater for that. Perhaps all=
owing atachign 'virtio-scsi disks to this interface woudl work fine, but th=
en there's issue with the naming.=0AAdditionally, there have been issues re=
ported with live migration of machines that have the ICH9-AHCI controller e=
nabled.=0AAny RFE should handle these multifaceted issues - and others I'm =
not aware of - so given I don't understand all the ins and outs I'd prefer =
not to raise this.=0AI'd be interested to hear Sandro's take on how this sh=
ould likely proceed though.
---360795340-209196801-1414977774=:40763
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff;
font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;fo=
nt-size:12px"><div style=3D""
class=3D""><SNIP><br style=3D"" class=
=3D"">> > > After doing some more searching I came
across these tw=
o pages:<br style=3D"" class=3D"">> > >
http://www.ovirt.org/Clust=
er_emulation_modes<br style=3D"" class=3D"">> >
> http://www.ovirt=
.org/Features/Cluster_parameters_override<br style=3D""
class=3D"">> >=
; ><br style=3D"" class=3D"">> > >
It sounds like this may allo=
w me to achieve what I've described above.<br style=3D""
class=3D"">> &g=
t; > From what I can tell the 'emulated machine type' is tied to the ovi=
rt cluster <br style=3D"" class=3D"">> > >
level - ie: 3.5.<br sty=
le=3D"" class=3D"">> > ><br
style=3D"" class=3D"">> ><br sty=
le=3D"" class=3D"">> > you can switch q35 with pc-1.0
in ClusterEmula=
tedMachines config value for <br style=3D""
class=3D"">> > version 3.5<br style=3D""
class=3D"">> Thanks Paul=
for asking and Roy for answering. I thought q35 would be the<br style=3D""=
class=3D"">> default anyway the whole time ;)<br
style=3D"" class=3D"">=
> ><br style=3D"" class=3D"">>
> engine-confi=
g -s ClusterEmulatedMachines=3D"q35,rhel6.5.0"<br style=3D""
class=3D"">>=
; ><br style=3D"" class=3D"">> > then
create a new cluster and add=
that host to it. once the host is up this <br style=3D""
class=3D"">> &=
gt; emulation mode should be set.<br style=3D""
class=3D"">> ><br sty=
le=3D"" class=3D"">> > in 3.6 you'd be able to
choose an emulation mo=
de per VM.<br style=3D"" class=3D"">> Paul, since this is
really useful =
would you mind to open an RFE in BZ<br style=3D""
class=3D"">> and post =
the link here, so we can keep track of this feature?<br style=3D"" class=3D=
""><br style=3D"" class=3D"">Hi Daniel.<br
style=3D"" class=3D"">Sorry for =
the late reply on this.<br style=3D"" class=3D"">I'm
happy that this feature is currently documented in the wiki pages that I'd=
referenced above and is on the feature plan for 3.6.<br style=3D"" class=
=3D"">The workaround that was specified does what I need for now.<br
style=
=3D"" class=3D"">Proper support in 3.6 will need to consider some
other thi=
ngs, such as allowing attaching of disks to the sata interface on the q35 m=
achine.<br style=3D"" class=3D"">3.5s current workflow
doesn't provide a wa=
y to cater for that. Perhaps allowing atachign 'virtio-scsi disks to =
this interface woudl work fine, but then there's issue with the naming.<br =
style=3D"" class=3D"">Additionally, there have been issues reported
with li=
ve migration of machines that have the ICH9-AHCI controller enabled.<br sty=
le=3D"" class=3D"">Any RFE should handle these multifaceted issues
- and ot=
hers I'm not aware of - so given I don't understand all the ins and outs I'=
d prefer not to raise this.<br style=3D"" class=3D"">I'd be
interested to h=
ear Sandro's take on
how this should likely proceed though.<br style=3D""
class=3D""><br style=
=3D"" class=3D""></div><div style=3D""
class=3D""><br style=3D"" class=3D""=
</div></div></body></html>
---360795340-209196801-1414977774=:40763--