@MajorP93 Fix has been merged, expect a package in your updates soon. Meanwhile check this notice about upcoming changes regarding remote syslog. https://github.com/xcp-ng-rpms/xcp-ng-release/pull/41#issuecomment-3800419449 rzr opened this pull request in xcp-ng-rpms/xcp-ng-release closed Preserve /etc/rsyslog.d/xenserver.conf if present #41

You can forget them, no issue.

@psafont Freezing/thawing doesn't actually suspend a VM, but it's just a part of the backup process, where I/O operations are quiesced to create a stable view of the on-disk data.

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

@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

I had the same question but the responses here was amazing and the following blogpost nailed it. I hope it helps someone else too: https://techdirectarchive.com/2026/01/25/a-z-of-xcp-ng-and-xen-orchestra-setup-and-vm-creation/

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

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.

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

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

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.

Worth asking @Team-OS-Platform-Release

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

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