<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jul 10, 2017 at 4:38 PM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@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"><div><div class="gmail-h5"><br>
><br>
> Currently I have set the environment in global maintenance.<br>
> Does it make sense to try to start the HostedEngine with an alternate<br>
> vm.conf to crosscheck it it is then able to start ok?<br>
<br>
</div></div>Not sure. Depends on why you think it currently fails. Sorry but I didn't<br>
check your logs yet.<br></blockquote><div><br></div><div>Because in 4.1.2 it started. During update to 4.1.3 I moved the engine vm without problems to the already updated hosts.</div><div>But I suppose during migration the qemu-kvm command line is preserverd, isn't it?</div><div>And only when I planned to update kernel of the engine vm so I had to power off it, I began to have problems....</div><div> </div><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-"><br>
> I see that there is the file /var/run/ovirt-hosted-engine-<wbr>ha/vm.conf that<br>
> seems refreshed every minute<br>
<br>
</span>Indeed. In recent versions it's possible to change some of the HE VM<br>
configuration from the engine itself, just like any other VM, so HA<br>
has to update this file.<br>
<span class="gmail-"><br>
><br>
> It seems that apparently I can copy it into another place, modify it and try<br>
> to start engine with the modified file using<br>
><br>
> hosted-engine --vm-start --vm-conf=/alternate/path_vm.<wbr>conf<br>
><br>
> is it correct?<br>
<br>
</span>Yes, as also written here:<br>
<br>
<a href="https://www.ovirt.org/documentation/how-to/hosted-engine/#handle-engine-vm-boot-problems" rel="noreferrer" target="_blank">https://www.ovirt.org/<wbr>documentation/how-to/hosted-<wbr>engine/#handle-engine-vm-boot-<wbr>problems</a><br>
<span class="gmail-"><br>
><br>
> the modified file would be such that:<br>
><br>
> [root@ovirt02 images]# diff /var/run/ovirt-hosted-engine-<wbr>ha/vm.conf<br>
> /root/alternate_vm.conf<br>
> 1,2c1,2<br>
> < cpuType=Broadwell<br>
> < emulatedMachine=pc-i440fx-<wbr>rhel7.3.0<br>
> ---<br>
>> cpuType=qemu64<br>
>> emulatedMachine=pc-i440fx-<wbr>rhel7.2.0<br>
> [root@ovirt02 images]#<br>
<br>
</span>No idea about your specific issue or whether this can fix it, but you can try.<br>
Especially if you can test on a test env...<br>
<br>
Best,<br>
<span class="gmail-HOEnZb"><font color="#888888">--<br>
Didi<br></font></span></blockquote><div><br></div><div>And in fact the engine vm is now up again with the customized parameters</div><div>How can I have it permanent? Frome where on shared storage are they read?</div><div> <br></div><div>Possibly the problems is generated by my nested environment:</div><div><br></div><div>L0 = ESXi 6.0 U2 on NUC6i5syh</div><div>L1 are my oVirt hosts on this L0</div><div>L2 is my engine VM that doesn't start in 4.1.3</div><div><br></div><div>it seems that </div></div>cpuType=Broadwell and/or emulatedMachine=pc-i440fx-rhel7.3.0 <br></div><div class="gmail_extra">generates problems....</div><div class="gmail_extra"><br></div><div class="gmail_extra">And I think I would have same problems with ordinary VMs, correct?</div><div class="gmail_extra">Gianluca</div></div>