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

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

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

@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

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

@ronan-a Thanks

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

From the xe help host-shutdown and xe help host-disable "If no parameters to select hosts are given, the operation will be performed on all hosts." I have a single host pool, so I can't test.

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.

@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

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

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.

Worth asking @Team-OS-Platform-Release

@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

@olivierlambert Because Andriy did quite a bit of work before this merge, xcp-ng depends on xenserver releasing the package to the clients before we can integrate it into xcp-ng. I'd say we can release the package February at the earliest

@Bastien-Nollet many thanks

Ping @pdonias

Hi, Have you followed https://help.vates.tech/kb/en-us/8-technical-support/15-open-a-support-ticket ?

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.

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