Sorry to revive this topic... I was just wondering: which force flag are you using? Per the docs I couldn't find it for xe host-shutdown command. FYI (in case it could help), my idea is to implement UPS shutdown order via SSH by using force command in /root/.ssh/authorized_keys. command="the_force_shutdown_command_here",no-agent-forwarding,no-port-forwarding,no-pty,no-user-rc,no-X11-forwarding a_dedicated_pub_key_here Then if you ssh in, it will force the command command= (other command will be ignored and you can't open interactive shell). ssh -i /path/to/dedicated_private_key user@xcp-ng-host whatever_command (whatever_command is just there to prevent error message)

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.

Worth asking @Team-OS-Platform-Release

@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.

@tsukraw Your best option is to open a support ticket so that we can assist you on updating the XOA registration.

There's a similar magic we've seen countless time with XO: you have a bug that nobody reports for years and suddenly it pops from various sources (or with many details so it's easy to spot), you think it's recently introduced, you check your diff and then after hours you realize it's there since a while

Nice find! Is there's any plan for Debian to backport that patch?

@florent increasing the timeout value was the solution. Thank you.

@florent said in Problems import vm Vmware to Xcp-ng from import Vmware and OVA: @olivluca skip ssl check in the import form I already did that. In fact it connects and I can get a list of VMs to import.

Does it work as you wanted now? If yes, probably something we can put in our official doc! Ping @thomas-dkmt

Indeed, it's hosted in Lyon, so an issue could happen in many places in the middle ^^

@florent I think you meant it was locking the xoa via .tar.gz but not via .zip which seemed to be the case Yeah I just decompressed the restored .zip and checked number of files and size via ncdu, result: "Total disk usage: 194,5 MiB Apparent size: 193,1 MiB Items: 613" In case I can provide more information for investigating this issue, please let me know. Thanks and best regards

@mpiton thanks for sharing docs, the crucial part was openssl rand -hex 32 my password was too simple and that's why i got :"Query authentication does not match server setting" error after setting 32 characters password i got my metrics, in both http://localhost:9004/metrics and http://<xo-ip>/openmetrics/metrics

I don't think stop will remove it, probably better to yum remove it. For Openmetrics, check: https://docs.xen-orchestra.com/advanced#openmetrics--prometheus-integration I switched our own production to that, so far it looks promising.

@florent I'll send you a link in DM, hope it helps with something. If not, it wasn't too much of an effort, thanks for your time so far

@anthoineb have we found a possible explanation?

I recreate my ZFS pool. But next time or for other stuck with this kind of issue, I think you should start to rename your ZFS POOL. I think the old ZPOOL name stay in XO configuration shadow settings. To rename a ZFS pool, export it with zpool export [poolname] and then import it with the new name using zpool import [poolname] [newpoolname] And then recreate (sr-create) your STORAGE in XO

@ronan-a Thanks