Julian Pelizäus

> LGTM! > > One thing I would like you to check separately is what happens in a failure scenario where some of the snapshots have been synced but then...

> @roosterfish also do we have tests in lxd-ci that check for VM and block custom volume refresh ? Looks like there aren't any, I'll add some.

**Update:** Edited to reflect the right release numbers. We have added support for explicitly specifying trust tokens with https://github.com/canonical/lxd/pull/13589. This way we can backport this addition into the 5.21.X releases....

> You mean 5.21.x releases? We dont do backports for 6.x releases. Yes thanks for catching this! I have updated the comment.

Looks like Ceph backed VM's don't get frozen too during copy. Just tested this on `edge`.

Not particularly, I have just ran across it since I have added https://github.com/canonical/lxd-ci/pull/41 which copies a running instance and I was wondering what happens for VMs.

Hi @benoitjpnet, it looks like live migration isn't yet enabled on your cluster. You can confirm by checking the LXD daemons error logs using `journalctl -u snap.lxd.daemon`.

Can you check the logs on both ends (source and target host)? One of them should tell that the migration has to be enabled in the config.

I was able to reproduce the warnings including the hanging migration. I guess you have added a new CephFS storage pool to the MicroCloud cluster and attached one of its...

Hi @dmitry-lyfar it looks like if you have a file with the same name as `path=XYZ` inside the container, it gets removed too: ``` lxc launch ubuntu:22.04 c1 lxc exec...