Hi Didi. On 25 Aug 2020, at 04:52, Yedidyah Bar David <didi@redhat.com<mailto:didi@redhat.com>> wrote: On Sun, Aug 23, 2020 at 7:45 AM Vinícius Ferrão via Users <users@ovirt.org<mailto:users@ovirt.org>> wrote: Hello, I’ve an strange issue with oVirt 4.4.1 The hosted engine is stuck in the UEFI firmware trying to “never” boot. I think this happened when I changed the default VM mode for the cluster inside the datacenter. If you think this indeed is the root cause, then perhaps: I double checked. By default the Hosted Engine does not set’s the BIOS type, it inherited from the Cluster: [cid:67300FB7-511F-41BB-8510-2A9E105B347D] I tried to manually set it up, but edits on Hosted Engine are locked. So may the default HE template should set this to avoid this mess? There’s a way to fix this without redeploying the engine? If you happen to have backup copies of /var/run/ovirt-hosted-engine-ha/vm.conf , you can try: hosted-engine --vm-start --vm-conf=somefile If this works, update the VM/cluster/whatever back to a good state from the engine (after it's up), and wait to make sure it updated vm.conf on /var before you try to shutdown/start the engine vm again. I ended up redeploying from the ground and reimporting back the VMs. I even tested again to confirm my first assumptions. So I think we may have a bug right? Thank you. Best regards, -- Didi
