4:22 p.m.
--Apple-Mail=_B2BF5B68-E5BD-4998-9F5D-5188B3CB9653
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
On 13 Jul 2017, at 11:51, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> =
wrote:
=20
On Thu, Jul 13, 2017 at 11:08 AM, Michal Skrivanek =
<mskrivan(a)redhat.com
<mailto:mskrivan@redhat.com>> wrote:
> On 12 Jul 2017, at 16:30, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com =
<mailto:gianluca.cecchi@gmail.com>> wrote:
>
> In the mean time I have verified that the problem is with
>
> emulatedMachine=3Dpc-i440fx-rhel7.3.0
=20
Might be. The fact that it works with 7.2 in esxi nested environment
is nice, but definitely not supported.
Use lower-than-broadwell CPU - that might help. Instead of qemu64
which is emulated...but if if works fast enough and reliably for you
then it's fine
=20
=20
The qemu64 is not a problem actually, because if I set cpu Broadwell =
and machine
type pc-i440fx-rhel7.2.0 things go well.
Also, on an older physical hw with Westmere CPUs where I have oVirt =
4.1 too, the VMs start with emulatedMachine=3Dpc-i440fx-rhel7.3.0, so =
this parameter doesn't depend on cpu itself.
=20
I think emulatedMachine is comparable to vSphere Virtual HW instead, =
correct?
yes
And that this functionality is provided actually by qemu-kvm-ev (and
=
perhaps in junction with seabios?).
yes. By using -7.2.0 type you=E2=80=99re basically just using the =
backward compatibility code. Likely there was some change in how the =
hardware looks like in the guest which affected ESXi nesting for some =
CPUs
If I run=20
=20
rpm -q --changelog qemu-kvm-ev I see in fact
=20
...
* Mon Jun 06 2016 Miroslav Rezanina <mrezanin(a)redhat.com =
<mailto:mrezanin@redhat.com>> - rhev-2.6.0-5.el7
...
- kvm-pc-New-default-pc-i440fx-rhel7.3.0-machine-type.patch =
[bz#1305121]
...
=20
So it means that at a certain point, the default machine type used by =
qemu-kvm-ev
has become 7.3 and this generates problems in my specific =
lab environment now (not searching "official" support for it.. ;-).
For the other ordinary L2 VMs definedinside this oVirt nested =
environment, I can set in System --> Advanced Parameters --> Custom =
Emulated Machine the value pc-i440fx-rhel7.2.0 and I'm ok and they are =
able to start.
The problem still remains for the engine vm itself, where I cannot =
manually set it.
Possibly is there a qemu-kvm-ev overall system configuration where I
=
can tell to force emulated machine type to pc-i440fx-rhel7.2.0 (without =
downgrading qemu-kvm-ev)?
I suppose you can define it in HE OVF? Didi? That would be cleaner.
You can also use a vdsm hook just for that...
=20
Otherwise I know that when I have to poweroff/restart the engine vm I =
have to
manually start it in 7.2 mode, as I'm testing right now.
=20
Hope I have clarified better...
=20
Gianluca
--Apple-Mail=_B2BF5B68-E5BD-4998-9F5D-5188B3CB9653
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote
type=3D"cite" class=3D""><div =
class=3D"">On 13 Jul 2017, at 11:51, Gianluca Cecchi <<a =
href=3D"mailto:gianluca.cecchi@gmail.com" =
class=3D"">gianluca.cecchi(a)gmail.com</a>&gt;
wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div
dir=3D"ltr" =
class=3D""><div class=3D"gmail_extra"><div
class=3D"gmail_quote">On Thu, =
Jul 13, 2017 at 11:08 AM, Michal Skrivanek <span dir=3D"ltr" =
class=3D""><<a href=3D"mailto:mskrivan@redhat.com"
target=3D"_blank" =
class=3D"">mskrivan(a)redhat.com</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote"
style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span =
class=3D"gmail-">> On 12 Jul 2017, at 16:30, Gianluca Cecchi
<<a =
href=3D"mailto:gianluca.cecchi@gmail.com" =
class=3D"">gianluca.cecchi(a)gmail.com</a>&gt; wrote:<br
class=3D"">
><br class=3D"">
> In the mean time I have verified that the problem is with<br =
class=3D"">
><br class=3D"">
> emulatedMachine=3Dpc-i440fx-<wbr class=3D"">rhel7.3.0<br
class=3D"">
<br class=3D"">
</span>Might be. The fact that it works with 7.2 in esxi nested =
environment<br class=3D"">
is nice, but definitely not supported.<br class=3D"">
Use lower-than-broadwell CPU - that might help. Instead of qemu64<br =
class=3D"">
which is emulated...but if if works fast enough and reliably for you<br =
class=3D"">
then it's fine<br class=3D"">
<div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"><br
=
class=3D""></div></div></blockquote><div
class=3D""><br =
class=3D""></div><div class=3D"">The qemu64 is not a
problem actually, =
because if I set cpu Broadwell and machine type pc-i440fx-rhel7.2.0 =
things go well.</div><div class=3D"">Also, on an older physical hw
with =
Westmere CPUs where I have oVirt 4.1 too, the VMs start =
with emulatedMachine=3Dpc-i440fx-rhel7.3.0, so this parameter =
doesn't depend on cpu itself.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I
think emulatedMachine is =
comparable to vSphere Virtual HW instead, =
correct?</div></div></div></div></div></blockquote><div><br
=
class=3D""></div>yes</div><div><br
class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr"
class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div
class=3D"">And =
that this functionality is provided actually by qemu-kvm-ev (and perhaps =
in junction with =
seabios?).</div></div></div></div></div></blockquote><div><br
=
class=3D""></div>yes. By using -7.2.0 type you=E2=80=99re basically
just =
using the backward compatibility code. Likely there was some change in =
how the hardware looks like in the guest which affected ESXi nesting for =
some CPUs</div><div><br class=3D""><blockquote
type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr"
class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div
class=3D"">If I =
run </div><div class=3D""><br
class=3D""></div><div class=3D"">rpm =
-q --changelog qemu-kvm-ev I see in fact</div><div class=3D""><br
=
class=3D""></div><div class=3D"">...</div><div
class=3D""><div =
class=3D"">* Mon Jun 06 2016 Miroslav Rezanina <<a =
href=3D"mailto:mrezanin@redhat.com"
class=3D"">mrezanin(a)redhat.com</a>&gt;=
- rhev-2.6.0-5.el7</div></div><div
class=3D"">...</div><div =
class=3D""><div class=3D"">- =
kvm-pc-New-default-pc-i440fx-rhel7.3.0-machine-type.patch =
[bz#1305121]</div></div><div class=3D"">...</div><div
class=3D""><br =
class=3D""></div><div class=3D"">So it means that at a
certain point, =
the default machine type used by qemu-kvm-ev has become 7.3 and this =
generates problems in my specific lab environment now (not searching =
"official" support for it.. ;-).</div><div class=3D"">For
the other =
ordinary L2 VMs definedinside this oVirt nested environment, I can set =
in System --> Advanced Parameters --> Custom Emulated Machine the =
value pc-i440fx-rhel7.2.0 and I'm ok and they are able to =
start.</div><div class=3D"">The problem still remains for the engine
vm =
itself, where I cannot manually set =
it.</div></div></div></div></div></blockquote><blockquote
type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr"
class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div
class=3D"">Possibly =
is there a qemu-kvm-ev overall system configuration where I can tell to =
force emulated machine type to pc-i440fx-rhel7.2.0 (without =
downgrading =
qemu-kvm-ev)?</div></div></div></div></div></blockquote><div><br
=
class=3D""></div>I suppose you can define it in HE OVF? Didi? That
would =
be cleaner.</div><div>You can also use a vdsm hook just for =
that...</div><div><br class=3D""><blockquote
type=3D"cite" class=3D""><div=
class=3D""><div dir=3D"ltr" class=3D""><div
class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div class=3D""><br
class=3D""></div><div =
class=3D"">Otherwise I know that when I have to poweroff/restart the =
engine vm I have to manually start it in 7.2 mode, as I'm testing right =
now.</div><div class=3D""><br
class=3D""></div><div class=3D"">Hope I =
have clarified better...</div><div class=3D""><br
class=3D""></div><div =
class=3D"">Gianluca</div></div></div></div>
</div></blockquote></div><br
class=3D""></body></html>=
--Apple-Mail=_B2BF5B68-E5BD-4998-9F5D-5188B3CB9653--