<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jul 13, 2017 at 11:08 AM, Michal Skrivanek <span dir="ltr"><<a href="mailto:mskrivan@redhat.com" target="_blank">mskrivan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> On 12 Jul 2017, at 16:30, Gianluca Cecchi <<a href="mailto:gianluca.cecchi@gmail.com">gianluca.cecchi@gmail.com</a>> wrote:<br>
><br>
> In the mean time I have verified that the problem is with<br>
><br>
> emulatedMachine=pc-i440fx-<wbr>rhel7.3.0<br>
<br>
</span>Might be. The fact that it works with 7.2 in esxi nested environment<br>
is nice, but definitely not supported.<br>
Use lower-than-broadwell CPU - that might help. Instead of qemu64<br>
which is emulated...but if if works fast enough and reliably for you<br>
then it's fine<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br></div></div></blockquote><div><br></div><div>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>Also, on an older physical hw with Westmere CPUs where I have oVirt 4.1 too, the VMs start with emulatedMachine=pc-i440fx-rhel7.3.0, so this parameter doesn't depend on cpu itself.</div><div><br></div><div>I think emulatedMachine is comparable to vSphere Virtual HW instead, correct?</div><div>And that this functionality is provided actually by qemu-kvm-ev (and perhaps in junction with seabios?).</div><div>If I run </div><div><br></div><div>rpm -q --changelog qemu-kvm-ev I see in fact</div><div><br></div><div>...</div><div><div>* Mon Jun 06 2016 Miroslav Rezanina <<a href="mailto:mrezanin@redhat.com">mrezanin@redhat.com</a>> - rhev-2.6.0-5.el7</div></div><div>...</div><div><div>- kvm-pc-New-default-pc-i440fx-rhel7.3.0-machine-type.patch [bz#1305121]</div></div><div>...</div><div><br></div><div>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>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>The problem still remains for the engine vm itself, where I cannot manually set it.</div><div>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><br></div><div>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><br></div><div>Hope I have clarified better...</div><div><br></div><div>Gianluca</div></div></div></div>