Can confirm successful Migration from VSphere 6.7

Had to remove all snapshots on VMWare before migrating.
Then change the network adapter name in /etc/netplan/...
and install recent drivers with
mount /dev/cdrom /media
cd /media
./install.sh

Ok. Thank you for the advise.
Will follow as recommended.
Best regards

To be able to start with dynamic memory at 4GB (min max) for the Windows Guest.
And then if needed, to be able, to expand to 8GB (min max) on the fly.
However, it seems, that the Windows Guest (2022 Server) always sees static max correct?

Hello Olivier

Min value is deactivated and not changeable via GUI.

However, I found out, that the static max value can be changed below the currently set static min value. (looks a bit strange to me?)

Example:
before change
=> min 8GB max 8GB
change max value via GUI to 4GB
after change
=> min 4GB max 4GB
Then change the max value to 8GB again.
=> min 4GB max 8GB

Best regards
Thomas

When migrating VMs from ESXi, the CPU count and Memory allocation is taken over to XCP-ng.
That's all fine for me.
However, after import, the static min memory allocation cannot be reduced.
Is there a workaround?

[02:56 xcp01 ~]# xe vm-param-get uuid=... param-name=memory-static-min
8589934592
[02:57 xcp01 ~]# xe vm-memory-static-range-set uuid=... min=4294967296 max=8589934592
The dynamic memory range violates constraint static_min <= dynamic_min <= dynamic_max <= static_max.

Can confirm successful Migration from VSphere 6.7

Had to remove all snapshots on VMWare before migrating.
Then change the network adapter name in /etc/netplan/...
and install recent drivers with
mount /dev/cdrom /media
cd /media
./install.sh

Dear XCP-ng Team

Are the XCP-ng Windows PV Tools 8.2.2.200-RC1 the latest client tools for windows and are they recommended?