@olivierlambert @stormi Restarting toolstack solved the problem. But after migration, VMs are performing very slow. We are on bios.

@rfx77 said in Problems doing live/warm migrations from vSphere/ESXi 7 to XCP-ng:

@Carello

Thanks. The problem is taht we dont have a NFS datastore to use. So we had to do export/import.

you can migrate without a NFS datastore, but on esxi 6.5+ , you'll need to shutdown the VM before starting the migration
and with vsan there is an additionnal , slower steps : extractig the vmdk to a Remote (in XO )

Done: https://docs.xcp-ng.org/guides/shrink_virtual_drive/#pre-requisites

I figured, for the purpose of completion, I'd document what I did to solve this problem.

Create a new VM on the target XCP-ng host Attach 6 virtual drives to the VM in the sizes of the VM I need to migrate Install Windows Server 2022 in the target VM Format the additional 5 drives Share the 5 drives over the network From source VM on ESXi Map network drives to each of the 5 drives in the target VM Copy files and folders to each drive Originally tried using RichCopyUI which uses Robocopy but it kept crashing Finally used FreeFileSync over the course of several days and nights to do an initial copy of the data Performed one final mirror of the data from the source to the target Shut down the source VM In vCenter, detach all but the boot drive from the source VM Migrate the VM from ESXi to XCP-ng using XO Attach drive files from target VM to migrated VM Boot migrated VM, it had no network access and the CD wasn't working but a couple reboots fixed it. Only 2 of the 5 extra drives appeared. Two attached automatically but 3 weren't even visible in Disk Manager. Install XCP-ng guest tools and reboot Extra drives now working inside the VM Had to fight a little with network settings and my DHCP server to get the same IP address assigned Did some testing, had to tweak a few things in some software but everything seems to be working normally again without too much work Shut down the old host running ESXi - one step closer to severing ties with VMware and also made my server room quieter and cooler

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.

@manilx Created a VM using this template on our business xcpng 8.2 and exported it.
Attached disk from the last VM but doesn't work. Lots of drivers missing, scsi, vga etc.

VM created with Other Install media works fine.

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