The emulator required to run this VM failed to start..?
-
Hello,
So we tried to do a rolling update on our servers, and for some reason, this seemed to have failed.
I've manually completed the updates, but now I'm trying to re-start several VMs, and I'm running into the same problem. I get an error:
"An emulator required to run this VM failed to start"
Anybody know how to resolve this?
-
Restart the toolstack on each server.
-
@Danp Yeah, that didn't work. I restarted the tool stack on all of the pool's hosts, and no go still.
-
@TheNorthernLight I'm also getting that the VM failed to pass secure boot verification. I've never had that problem and have no idea how to resolve it.
-
@Danp Turns out, I was missing the UEFI Secure boot certificates on my hosts. Odd how this never came up as an issue prior, but now it seems "required". At least its an easy fix:
-
Previously, enabling Secure Boot on a VM would do nothing at all. Starting with update 8.2.1, we now support it and as you found out you need to bootstrap it on the pool.
-
@stormi So from what I understand, at the moment the XCP-NG client drivers cannot be used for secure boot, and we must use the Citrix drivers.
We have ALL of our VMs using the XCP-NG Client drivers. How do we successfully switch to the Citrix drivers?
I tried on a test VM to uninstall the XCP-NG client drivers, reboot and enable the Citrix drivers install, but the OS refuses to boot after removing the XCP-NG Client drivers. How do I "install" the Citrix drivers without having the xcp-ng client driver conflict?
-
I think the steps would be similar to what we do in the opposite situation: https://xcp-ng.org/docs/guests.html#upgrade-from-citrix-xenserver-client-tools
-
@Danp said in The emulator required to run this VM failed to start..?:
Restart the toolstack on each server.
This worked for me.
-
J jrubenc referenced this topic on
-
Please check this: https://xcp-ng.org/forum/post/78137
-
Check your disk space on the server. in my case no diskspace left...
