Fast solution is to use Clonezilla on a vm template where it works, then move the disk to a Windows 10 vm. The boot mode of the Windows vm is not important, as Clonezilla does copy the disk respecting the source format (UEFI or Bios).

@SpoonyLove @olivierlambert
For usb passthrough we are using USB redirector over network
For anything storage related we use something like this:

mkdir /adm/passSR

passUUID=`xe sr-create name-label="Direct access SR" name-description="Direct acces to hdd with simlink" type=udev content-type=disk device-config:location=/adm/passSR`

ln -s /dev/sdb /adm/passSR/sdb

xe sr-scan uuid=$passUUID
xe vdi-list sr-uuid=$passUUID

Remember to replace /dev/sdb with your device.

The pool master will calculate this when adding new hosts. If you have simillar CPUs all will be ok.

If you enter all hosts in a pool and all servers are up when the vm's are started you'll be able to safely live-migrate.
You can even have more different CPUs but that is not recommended. Also the CPU masking will modify with any host up or down from the pool and will have effect only at the vm start, that's why all XCP hosts should be up when starting vm's.
You'll be able to live-migrate vm's only on hosts with same CPU features as when the vm was started.

Fast solution is to use Clonezilla on a vm template where it works, then move the disk to a Windows 10 vm. The boot mode of the Windows vm is not important, as Clonezilla does copy the disk respecting the source format (UEFI or Bios).

The restart occurs only for the hypervisor, or the whole system (i.e.: starts from post)?

See Citrix documentation, here and here.

or be inspired, use command line or create your own script, like this.

ssh is your best option. That's what we use. Or remote via AnyDesk, Teamviewer or else if you really need GUI.

@vmpr I think the error is because you run out of space when moving. Try to use a larger SR or move one VM at a time, or serialize the operation if you don't have the space for.

P.S.: Every move creates snapshots for every disk. When moving from CLI or XCP-ng Center you move one VM at a time and needs less space. I think XOA starts to move all VM's at once (@olivierlambert correct me if I'm wrong), so the space required is more and soon exhausted. You can check this by starting a move from XOA and checking SR utilization (actual use, total and allocated space).