Are you using EXT or LVM?
I've seen this as well with large VM's and not enough free space on the source host, the only solution is to either free up some space or do an offline copy. Migration wont work, so copy is your only option.
Don't mix XO commands and xe, even if XO is on top of it, the mapping isn't exactly 1:1.
In XO, host force shutdown is preventing XAPI to try moving the VMs around to another host. So in force mode in XO, the host is disabled first, then shutdown command is sent. If you want to do the same thing, you have then 2 xe commands to do: host.disable and finally host.shutdown
Hmm that's interesting. I suppose you can remove it via xe CLI, but XO shouldn't prevent you to remove it.
Let me ping @Team-XAPI-Network for the xe command to remove this parameter, and ping @bastien-nollet to see how we could get rid of this limitation that blocks removing bogus devices.
I just released 0.0.3 https://github.com/benapetr/XenAdminQt/releases/tag/v0.0.3-alpha it brings it even closer to the original client, with packages for macos, debian12, debian13, ubuntu 22, ubuntu 24, Fedora 43, windows
@dinhngtu said in Execute pre-freeze and post-thaw:
There used to be quiescent snapshot capabilities in older versions (mainly for Windows VSS support), but it has since been removed. I'd say @Team-XAPI-Network knows more about the reason.
We have vmware with ppdm backups and the vss part is actually causing some annoying issues such as quite long io stalls. But I do understand the reason for vss, especially for applications that aren't crash safe.
