@florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.

@dinhngtu it still wouldn't boot with the correct template. That said, I have been testing other VMs which were created on xcp-ng, with the correct templates, and get better performance out of them when they are migrated to a hyper-v host. I believe that this is related to SMAPIv1 limitations - which are known and being actively worked on with SMAPIv3. Unfortunately for us at this point, xcp-ng may not fit our business - hopefully one day soon it will be, but until then, it is what it is.

1: Yes, I have seen some of @AtaxyaNetwork Proxmox posts. I'll go back and read them again. 2: No big deal, I only have like 5 vm's on Proxmox, V2V is my choice of tools!

Since you're changing all of the underlying hardware that the guest has, Microsoft is going to force you to reactive. You could look at setting up a licensing server to manage these systems and then feed them that information so they can validate and then license. This isn't an issue presented by XCP-ng (or literally any other hypervisor), its a Microsoft restriction to ensure you aren't stealing their software.

Thanks for the info and the faster than light answer ️

Great! @jkissane please open a new thread if you want to continue discussing your issue