Indeed!

Another win for our awesome community Thanks everyone, I'm really glad to see I'm less and less needed to get threads solved! It's a very good sign edit: fear not, I'll be always around here

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 feedback, I'll discuss the improvement with @florent

@florent It is a very old host. In addition to moving to XCP to get away from VMware, we're upgrading to get off the oldest hosts onto a couple new hosts I just added. It's quite possible that the activity was overwhelming that rather weak old host.

Pinging @florent since I do not remember the best approach in that case.

@Chr57 said in Synology Active Backup for business: Can the backed-up machines in Synology Active Backup for business be imported into XCP-ng and spined up as VMs? They can be started as VMs in Synology Virtual Machine Manager. https://www.synology.com/en-global/dsm/7.2/software_spec/abb "Synology active backup for business" doesn't have any integration with XCP-ng or Xen Orchestra. You could potentially use this to perform backups within a given VM to the Synology, but that isn't your question. You could use Xen Orchestra to backup to an NFS/SMB share on said Synology and then restore from that, but not the inverse.

You can redo the bench with 4 virtual disks in RAID0 and try again, that will represent the more "real" value in the real world (when you have many VMs and disks)

@austinw It stayed at zero forever. I'll see if I can find that post.

@kopeck Sometimes it takes a few reboots for everything to settle down.

@OskarNTT Here's another case of the same issue, from just one day ago. https://xcp-ng.org/forum/topic/8596/issues-with-warm-migration-from-esxi-8-0-2

Adding @florent in the loop

Sure @jasonnix

Thanks for the info and the faster than light answer ️

Created a simple bash script to remove VMware Tools; sudo apt remove open-vm-tools sudo rm -r /etc/vmware-tools sudo rm /etc/systemd/system/open-vm-tools.service sudo rm /etc/systemd/system/vmtoolsd.service sudo rm -r /etc/systemd/system/open-vm-tools.service.requires sudo rm -r /etc/vmware-tools sudo apt autoremove

@elentescaro13 all set?

@stormi said in Importing from Redhat Virtualization: Is there material in this thread for improving the migration documentation? https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/ the qemu-img convert should be the fallback : it needs a lot of space, around twice the disk size (it varies depending on base format efficiency) and a lot of manual action. On the other hand it works as long as qemu know the format : https://docs.openstack.org/image-guide/convert-images.html (for vmdk there is a like a dozen of completely different subformat)

I'm not sure the XVA.py will work with raw files. But Xen Orchestra accepts to import raw drives. So you can create the VM and then import the drives later on (if it doesn't work with the Python script)

haha yes, it feels like a hidden plug for those product (I'm not saying it's the case, but just feeling that way). Also, you can obviously backup your VMs with XO to restore them on a freshly installed (from scratch) XCP-ng 8.2