<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 6, 2016 at 9:51 PM, Gianluca Cecchi <span dir="ltr">&lt;<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>&gt;</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 dir="ltr"><div class="gmail_extra"><span class="gmail-"><div class="gmail_quote"><div class="gmail_extra"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div><br></span>Here the HostedEngine.log generated under /var/log/libvirt/qemu <br><br><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvZ0V5RTFBZXJfMzA/view?usp=sharing" target="_blank">https://drive.google.com/file/<wbr>d/<wbr>0BwoPbcrMv8mvZ0V5RTFBZXJfMzA/<wbr>view?usp=sharing</a><br><br></div><div class="gmail_extra">I see at the end of it the line<br><br>warning: host doesn&#39;t support requested feature: CPUID.07H:EBX.erms [bit 9]<br><br><br></div></div>
</blockquote></div><br></div><div class="gmail_extra">It seems this second problem was due to qemu-kvm 2.6 too restrictive....<br></div><div class="gmail_extra">So I reverted to 2.3:<br><br>Downgrading:
<br> qemu-img-ev              x86_64       10:2.3.0-31.el7_2.21.1        ovirt-4.1-pre       791 k
<br> qemu-kvm-common-ev       x86_64       10:2.3.0-31.el7_2.21.1        ovirt-4.1-pre       449 k
<br> qemu-kvm-ev              x86_64       10:2.3.0-31.el7_2.21.1        ovirt-4.1-pre       2.1 M
<br> qemu-kvm-tools-ev        x86_64       10:2.3.0-31.el7_2.21.1        ovirt-4.1-pre       250 k
<br> <br><br></div><div class="gmail_extra">clean done with (my env is single host providing nfs export):<br> <br>umount /rhev/data-center/mnt/_var_lib_ovirt-hosted-engine-setup_tmpBrbRge
<br>umount /rhev/data-center/mnt/ovirt41\:_SHE__DOMAIN/
<br></div><div class="gmail_extra">rm -rf /SHE_DOMAIN/* <br>hosted-engine --vm-poweroff (vm was actually already down but the setup claimed it was up...)<br></div><div class="gmail_extra">re-run host-deploy and completed successfully...<br><br>[ INFO  ] Engine is still not reachable, waiting...
<br>[ INFO  ] Engine replied: DB Up!Welcome to Health Status!
<br>[ INFO  ] Acquiring internal CA cert from the engine
<br>[ INFO  ] The following CA certificate is going to be used, please immediately interrupt if not correct:
<br>[ INFO  ] Issuer: C=US, O=localdomain.local, CN=ovirt41she.localdomain.local.40445, Subject: C=US, O=localdomain.local, CN=ovirt41she.localdomain.local.40445, Fingerprint (SHA-1): 744EDCF02EC8AC74E4C5E549AC464B1EC939D7DC
<br>[ INFO  ] Connecting to the Engine
<br>[ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
<br>[ INFO  ] Still waiting for VDSM host to become operational...
<br>[ INFO  ] The VDSM Host is now operational
<br>[ INFO  ] Saving hosted-engine configuration on the shared storage domain
<br>[ INFO  ] Shutting down the engine VM
<br>[ INFO  ] Enabling and starting HA services
<br>[ INFO  ] Stage: Clean up
<br>[ INFO  ] Generating answer file &#39;/var/lib/ovirt-hosted-engine-setup/answers/answers-20161207111416.conf&#39;
<br>[ INFO  ] Generating answer file &#39;/etc/ovirt-hosted-engine/answers.conf&#39;
<br>[ INFO  ] Stage: Pre-termination
<br>[ INFO  ] Stage: Termination
<br>[ INFO  ] Hosted Engine successfully deployed
<br>[root@ovirt41 ~]#
<br><br><br></div><div class="gmail_extra">Now going to test ... ;-)<br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra"><br></div></div>