Ok, was able to force shutdown via CLI and now I'm able to start VM on source server:
# xe vm-reset-powerstate vm=<vm name> --force
I'm not going to perform live migrations anytime soon again. I was trying to move VMs so we can do an upgrade which requires wiping out all storage because we used experimental ext4.
@julien-f Thank you! That appears to fix the error. Greatly appreciate your help and @olivierlambert.
@andrewperry I couldn't get the live migration to work on large VMs. To move large VMs, I ended up taking a snapshot of the VM and then creating a new VM from that snapshot. It's not ideal but had to do that as we needed to retire some old servers and I couldn't get the live migration to work w/ large VMs.
@Biggen You can do this via cli...see if this doc is helpful (just make sure to back/move/copy any data before performing these steps): https://support.citrix.com/article/CTX131328
@TS79 It seems something is not stable w/ SR NFS creation. The strange thing is XOCE allowed the creation of the NFS Remote under Settings > Remotes but refused to create the SR NFS until I patched to latest build (I was 3 commits behind) and then rebooted the entire server.
I was hoping to test this via just XO to rule out if it's an issue w/ XOCE or not but I couldn't get the XO deploy script to work. But I'll have to tackle that issue another day.
I was able to install a VM using the SR NFS and will be running som Disk IO tests to see how stable the NFS connection.
Thank you again for your help and testing this on your home lab! Greatly appreciate it!
Best Regards,
SW
Thank you @olivierlambert & @Danp . Greatly appreciate your assistance!
@olivierlambert Thank you, I've changed the settings on b2 to "Keep all versions of the file (default)".
I can confirm it's now working. Thank You! Health page loads fine w/ the latest commit.
When I login to xcp-ng cli, I see this when I run list_domains where the UUID of this VM looks different cli vs what xo shows:
