Description of problem: At the end of deploy, when ha-agent tries to start the engine vm, it fails. vdsm.log has: libvirt.libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: monitor This is essentially a duplicate of engine bug 1689362, and both should be fixed by libvirt bug 1798004. Opening on hosted-engine for considering a workaround there for now. I think we can fix/workaround this by patching /usr/libexec/vdsm/hooks/before_vm_start/50_hostedengine .
we may just want to wait for bug 1798004, it's finally moving forward.
Keeping this open, we'll need to ensure a recent enough libvirt is installed by requiring it in spec file once the fix will be available.
*** Bug 1925656 has been marked as a duplicate of this bug. ***
HE is not supported to run on nested virtualization, I don't see it in any official documentation.
(In reply to Nikolai Sednev from comment #4) > HE is not supported to run on nested virtualization, I don't see it in any > official documentation. Not sure what official documentation you refer to, but I still think we want to make sure this bug is fixed, official or not.
Also, please do not post private comments on oVirt bugs. Thanks.
(In reply to Yedidyah Bar David from comment #6) > Also, please do not post private comments on oVirt bugs. Thanks. Official means that Red Hat don't officially support for this functionality and doesn't provide any support for it and doesn't has any documentation regarding it, which means that QA doesn't testing it.
This is an oVirt bug. In oVirt, we fix bugs if we think it's worth it, even if we do not document the relevant flow or declare it official some other way.
Closing for now due to capacity. Please feel free to reopen if you still have this issue reproduced.
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.