@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

To add custom ACLs and Groups, you would do this from Settings > Groups and Settings > ACLs [image: 1709732780401-d8339fae-5a66-4caf-9e78-9ad779437c9b-image.png] Settings > Groups allows you to create and name a group (which contains users). Settings > ACLs is where you set permissions, and then apply those permissions to a group (or individual user.

@Chr57 Good job, always nice to have everything sorted out before going live

xe pool-list will give you the UUID of the master host. xe host-list will give you the host name. You can use a combination of xe commands to get the name of the master host -- xe host-param-get param-name=name-label uuid=`xe pool-list | grep master | awk '{print $4}'` Once you bring back up the old server, XO is smart enough to detect that it is no longer the master and will determine the correct host within the pool.

@OskarNTT Put the snapshot's UUID into the filter at the top right. This should show you all activity involving this snapshot, including when it was created. The vm.snapshot record contains the UUID of the target VM. In the latest releases of XO, you can click the UUID to be taken to the associated object.