@stormi Thanks, that sounds great! If there is something I can test / provide please let me know!

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

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

@samuelolavo Yes, I do use NUT, but I don’t want to install any additional packet on XCP-ng. The way I found leverage the SSH authorized keys restrictions, and so you only need to change one file. Thanks for the link anyway

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

@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

I managed to do the migration by splitting over the two storages the remove system has. This made it work and I managed to move that one VM. However I still have a second one It's thick provisioned (LVM - never can remember the terms thin/thick). Offline isn't an option unfortunately since I need the services running, can't take if off for 15 hours. But since two of the services are docker containers, both having a separate disk of 500GB, I can make it work by setting up a two new systems and moving everything from the container there. Which would reduce the size by 1TB and make thing easier to manage. Was hoping I could finally upgrade the main xcp-ng last weekend.

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

@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

@pdonias https://docs.xen-orchestra.com/users [...] Operator An operator can make everyday operations on assigned objects. For example, on a VM: eject a CD insert a CD (if he can view the ISO storage repository) start, restart, shutdown, suspend/resume it All other operations are forbidden. [...] As I understand it (I may be mistaken), changing the "Rate Limit" is already a configuration change and should not be available to an Operator.

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.

You must select a template, you can configure everything after (as @pilow said). It's meant to have some low level specifics you don't want to learn (BIOS/UEFI mode, some virt modes etc.)

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

@LoTus111 Hello, I attempted to reproduce the issue without success. Could you please share the logs with us so we can conduct a deeper investigation? Feel free to send them to me via PM.

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.

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