@MajorTom thanks that could be a solution. In the end I moved my single-machine Homelab to Proxmox, because I have way better control in this specific use-case - I can see IOMMU groupings and figure out which USB controller I can also passthrough. And this works fine, I'm posting this from this VM.
XCPng isn't bad, it´s just not suited to my very specific use case.
Right, if your used is 123.4/128, there seems RAM crunch to migrate anything around 4GB. Can you try migration after freeing up some RAM? Also what version of XCP-NG is being used? There is a known issue related to migration - you can find it on forum.
Can you be more specific? I think you are mixing number of CPU inside the machine and visible CPU inside the dom0. Remember, Xen is type 1, the "host" you are connecting into is not the physical host, but a privileged VM.
Indicates that with not enough grant frames, the guest VM will not be able to use the all the virtual NICs that it expects. Still wonder if increasing max_grant_frames would speed up existing network interfaces even when they have enough working vNICS.
The message was relatively clear (for a XAPI error 😛 😞
This operation cannot be performed because the specified VDI could not be found on the storage substrate
sr: 28a8b360-7b1b-58ca-81b6-f907c164ec38 (XCP-ng Tools)
vdi: b1a7a49a-f17c-42ac-af73-4429eb57b07a (Old version of guest-tools.iso)
This means the VM can't boot with this current CD because it's not there anymore. I suppose you updated your host without ejecting all CDs before. So the old tools CD was removed for the new one, and your VM kept it. So when you tried to boot, it couldn't because it couldn't find the old ISO.