Ah great news!!

@DonZalmrol good to hear! Another good migration solved!

@chuckb1968 No, your approach sounds fine. Do you see the VDI under the VM's Disks tab? If so, then it should be visible to the installation routine.

Pinging @florent

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!

@BGDev I'm not certain you're encountering a bug or a network issue (or something else). Given that you have a working production workload on ESXi and a Production XCP-ng environment, what I personally would suggest is to replication the data from the old to the new, schedule a final cut over day and perform a final replication. If this was a database drive or something that help system files then I'd dig further into why its not exporting successfully, but since it seems like its just a file share, replicating the individual files would be the simplest approach.

That's interesting, thanks for the feedback @sshughes and keep us posted!

The Xen / XCP-ng equivalent for VMXNET are Xen PV device drivers which either come from Citrix Xenserver, XCP-ng or the Xenserver project itself. Check the Wiki. It describes the installation pretty well: https://xcp-ng.org/docs/guests.html#windows As for 3D acceleration within the VM there is hardly a comparable option unless you do some PCIe pass through of a GPU.

PV is old and made sense when no HVM-supported hardware existed. You can also use PV shim. See https://xcp-ng.org/blog/2022/01/17/removing-support-for-32-bit-pv-guests/ for more details.

In the end it turned out the license was bound to the network card, we needed to recreate it with the original mac and the license server started again! Case closed!

Hi, First, I would test on XOA "Latest" than the sources, since there's already many moving pieces with VMware import, avoiding add another with a non-QA tested version vSAN import is slow but supported.

@irrelevant What's the specification of the hardware of both hosts and also what's the network speed. Especially for the management network interface, as this is the one through which VMs on XCP-ng are imported and also likely exported on VMware vSphere ESXi? The reason being if the hosts and/or network aren't that quick then the migration of the VMs from VMware to XCP-ng will take longer! If you can connect the management network to a faster interface then the migration won't take as long to complete.

@olivierlambert We observed that a VM with higher memory usage on XenServer reacts more slowly compared to VMware. This might be related to the different functioning of XenServer tools. We resized the VMs where customers had complained, and this led to significant improvements. Additionally, we adjusted the VGA switch. While it's unclear if this had a major impact, after increasing the memory and setting the switch, we received positive feedback from the previously dissatisfied customers.

@Tristis-Oris u need to change the boot records for this, on windows we use a specific tool for this that converts the MBR disk to a GPT disk, i am not shure how the proces work in linux but i know that can be done there as well.

Thanks for feedback. No success here. I will move docker instead to a new VM. Johan

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

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!