@delacosta456 said: the pool host maximum limit is 3200% right right

Thank you @olivierlambert !!! I used your Tip, Booted a CD and got it running on XCP-ng Note: chroot + dracut is not an option here, as dracut is not present in the OXE image. Main issue was the disk device naming (sda → xvda). Fix was: Boot via Rocky rescue Mount root partition manually Update root=/dev/sdaX → root=/dev/xvdaX in /boot/grub2/grub.cfg Replace all /dev/sdaX with /dev/xvdaX in /etc/fstab After that the system boots fine. Installation from guest tools via local guest tool iso went thru without any issues. Network config is managed by OXE itself, so changes must be done via OXE CLI (not persistent via Linux/nmcli), but this will be done by the admin of OXE and that's not me. So far it run's. We will do further testing and update this post if issues occur, in case someone else is searching for this. Fingers crossed there will be none. Again many thanks for pointing me in the right direction and the very quick response.

@CyaVMware said: Have a simple question for someone. Looking at migrating a client to XCP. Currently they have a data disk that is exactly 2TB in VMware. My question is the limitation anything OVER 2TB, or is it 2TB AND above? I'd prefer not to use the VMware converter tool to shrink the disk to 1.99TB if I don't have to. VHD format has a strict limit of roughly 2TB (around 2040 GB), so if your client’s VM disks are larger than this then you’re going to have trouble with VHD format. However QCOW2 support is almost here (production ready) about to reach RC2 state, once this reaches stable you’ll be able to safely reach a max of around 16TB. That is if your using ext4 based SR, other Filesystems have different limits. If using a networked file sharing protocol service then, the limit of the host server’s filesystem applies. Though QCOW2 VDI has a limit of 16 TiB.