@gskger huh, well then this is particularly odd because the VM came from the same destination! Literally it was migrate A->B (which went fine). Immediately try to migrate B->A with the no host available error. Host B here is the non-VT machine. Not to mention these were stopped VMs. They aren’t taking any resources - just disk.

Hello!

This will sound a bit weird, but I purposely installed XCP-ng onto a non-Intel VT-d/AMD-V machine just to see how it would work. Not very well, as to be expected: I could not start any VMs because all the default templates are HVM templates and not e.g. pure (old school) PV — at least with XOA. I'm sure with enough xe shenanigans I could create a PV VM if I wanted. However I wanted to ask about migrations to and from these hosts.

I was able to migrate a stopped VM over to this older machine fine. Of course I couldn't start the VM. That was to be expected. However my challenge came when I wanted to migrate it back. It gave me the same errors as if I was starting the machine (no hosts available). So my question is: when you migrate a VM off a host does it "start" the VM — even in some preliminary way? I'm not sure why I was getting the 'no hosts available' message when trying to migrate a stopped VM.

Thanks!

@parallax Were you able to get this working?

If not I might open a new thread for to ask for a way to expose what's needed for Ignition. My ask is for Fedora CoreOS, which has QEMU instructions (as you noted): https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/ (basically, using the -fw_cfg switch).