@Pilow said in Unable to copy template: something preventing you to patch thoses hosts ? yes.

@MajorP93 It's being packaged at the moment. between this and the testing that needs to be done it might take a couple of weeks to be released, but I can't promise anything yet

@olivierlambert New thread is here

It is difficult to know the source of the problem without more details from your logs. Can you run the following commands on your XCP-ng host and then attach the generated files here? grep -A 15 -B 15 -i error /var/log/xensource.log/xensource > xensource.txt grep -A 15 -B 15 -i exception /var/log/SMlog > smlog.txt dmesg -T|grep -Eiv 'guest|capacity|promiscuous' > dmesg.txt

@nathanael-h I have not yet tried the XO CSI driver, if I do I will leave feedback on the relevant thread. (I found the one started in 2025 November)

@MajorP93 Hi, In the demo dashboard it is intended yes but these percentages are obtained by dividing the free memory by total memory so changing the dashboard to show GB/GiB should be quite straight forward. I've forgot to add to the initial post that there is a advanced dot md file that describes all the available metrics located in "xen-orchestra/docs/docs". Thanks.

@Tristis-Oris yes it is likely you're using a newer kernel, we likely need to rebuild the agent using a newer version of the netlink crate.

@florent @fcgo the host that was queried (with host_ip/export_raw_vdi) will do the export from the shared SR, and will redirect the query to the host that can see the SR otherwise. So it's up to the XO/other orchestrators if they want to distribute the load here.

@malemburg Kernel versions: 24.04 - Linux ubuntu-server 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux 24.04.3 - Linux ubuntu-server 6.8.0-71-generic #71-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 16:52:38 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux This is what is running after all the updates: Linux pxe000 6.8.0-100-generic #100-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 13 16:40:06 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux I have this in my autoinstall to install the tools late-commands: - echo 'deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/' > /target/etc/apt/sources.list.d/xen-guest-agent.list - curtin in-target -- apt update - curtin in-target -- apt install -y xen-guest-agent And this to get all the updates: updates: all

Ping @thomas-dkmt for better doc clarity about it.

@Danp damned, i forget about this button) Now it works, thanks.

Not sure If correct but the vhd-tool check seem quite basic. Looks like it only do kind of a "wrapper" check and not a full integrity check $ vhd-tool check 4156d2ea-d39d-436d-b89f-06ad64949c53.vhd 0 START of section 'footer_at_top' 1ff END of section 'footer_at_top' 200 START of section 'header' 5ff END of section 'header' 600 START of section 'BAT' 195ff END of section 'BAT' 67a00 START of section 'locator block 0' 67bff END of section 'locator block 0' 67c00 START of section 'locator block 1' 67dff END of section 'locator block 1' 67e00 START of section 'locator block 2' 67fff END of section 'locator block 2'

@olivierlambert great news, I had a feeling this was in the works! Thanks for the info.

i also have slow speeds. Checked network connections works perfect. Checked disk performance is really good. But on migration speed is around 25mb/s.

@dinhngtu Really appreciate the help finally got it working. In Debian 12 I was able to boot to it without issues even with 3GB (on both UEFI and BIO) but obviously not recommended for logs etc... Testing for Debian 13 now to see if there is something else affecting it and there is definitely weird issue with UEFI. BIOs boots up fine its the UEFI settings. This seem to affect the display as far as I can tell as I can ssh into the terminal without issue. I think part of the issue is to use only generic or genericcloud and avoid nocloud as its doesn't come with cloud-init install... They mention this on the site where we download it. Didn't quite understand until now...: azure: Optimized for the Microsoft Azure environment ec2: Optimized for the Amazon EC2 generic: Should run in any environment using cloud-init, for e.g. OpenStack, DigitalOcean and also on bare metal. genericcloud: Identical to generic but with a reduced set of hardware drivers in the kernel. If it does not work for your use case, you should use the generic images. nocloud: Does not run cloud-init and boots directly to a root prompt. Useful for local VM instantiation with tools like QEMU. (AVOID as it does not work with cloud init but it boot up so that was extremely deceiving...)

@whyberg Nope... that feature is part of the CPU. But is that the actual problem? Maybe... As that machine is too old to do any real work, it's a fine toy. There are better faster cheap test machines available.

@florent Delta backup is also leaving old snapshots on some VMs. It should only have one (current) snapshot for the nightly backup. This is an issue on 1 of 100 VMs. XCP (Jan 2026 update) and XO (91c5d) are current. [image: 1770510564402-30de9803-0b8d-488d-b160-57c623f66e78-image.png]

Edit: For anyone with this issue, stopping and starting the Openmetrics plugin after saving the password in XO fixed it. I keep getting the {"error":"Query authentication does not match server setting"} problem, is there something I'm missing? I run XO proxied through Nginx with HTTPS, is there some additional config required to get it working? I have set the key with openssl rand -hex 32 and have verified that is saved correctly in the plugin, and that I am using the same key for curl. I am able to obtain the /health endpoint as expected, I just cannot obtain the full metrics, only returns that error. Command: curl --insecure -H "Authorization: Bearer mytoken" https://xo.mydomain.local/openmetrics/metrics XO commit: 91c5d I should note that running the command inside my Docker container returns only the error, including the health endpoint. Do I need to expose 9004?

Also.. Thank you for taking a look at it and solving it so quickly, @florent It is a quite nice interaction when reporting bugs that they are looked at and triaged. Not saying everything needs to be a priority 1. But I do appreciate being close to the process. And if I can help make things better by reporting bugs, in a hopefully constructive way. Then I'll continue to contribute my way.