@whyberg Normally not 10x...

@Pilow I didn't have this before yesterday, which is when I updated. And I update from source regularly. So the regression has happened since the last few (<1w) days. I'll step backwards and see which commit introduced the bug.

@florent I tried to upload it with the "Upload button" and got this error" [2026-02-05T15_03_26.704Z - backup NG.json](Invalid file type. Allowed types are: .png, .jpg, .bmp, .txt, .diff, .patch, .jpeg) " 2026-02-05T15_03_26.704Z - backup NG_json.txt

Answering myself: [image: 1770314370452-screenshot-2026-02-05-at-17.59.10.png]

@olivierlambert Sure, I absolutely get that XO CE comes with absolutely no warranty and XOA is the supported, enterprise grade product. If the budget was there and if I was to decide on that I would be happy to use it. It might still be a good idea to update your documentation at https://docs.xen-orchestra.com/installation#packages-and-prerequisites to at least align it with the Node JS version that you actually use and test against internally. (The linked part of documentation advises to use Node 24 while you are shipping Node 20 in XOA.) During testing it looked like running XO on Node 20 behaves quite differently compared to running it on Node 24 when it comes to RAM management. It looks like this got also confirmed by other users in this thread. XO CE users actually using and testing the versions that you ship might be of value for finding bugs. I think the documentation should generally advise to use the packages that you target during development in order to make the experience as good as possible for everyone. Just my two cents.

@olivierlambert Thank you, I'm hoping to setup a test server for that out this weekend (or sooner) and will update. Amazing to see this level of support and enjoy any time you join the various YouTube channels, especially @lawrencesystems Vlog Thursday or Live Streams.

It's not a problem with XO backups

@markxc could you tell us what endpoint you used ?

Hi I tried again and failed with the same error message.. xe vm-export vm=c57a4225-3adb-b422-34ec-d2a23c6223c9 filename=/run/sr-mount/a7f6df31-412f-d5e9-4163-8af75b1df8ad/dlt-sin-mducv8.xva The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Unix.Unix_error(Unix.EIO, "read", "") Hum in this last reproduction, I the issue happened 3hours after I triggered the export... I have a feeling this is an hardware issue here... Anyone any other idea ? Advice where to look at? [EDIT] I have manage to export another vm without issue. Best. Matth.

@nvs Hi there, we had a similar issue with on our 5900x boxes. We have about a twenty of these and they have been generally greats hosts for xcp loads. However, one of them was constantly rebooting. While testing the ram the temp jumped to 90/90. They are running in 1U boxes so I expect heat but this seemed silly. We ramped the fans to max but this did not help. We then used bios to drop down various cpu boost profiles and gadgets to lower the heat and re-applied paste to cpu.. so far so good.

I know this is old but I had a similar issue. In the end I told dracut NOT to reassemble my raid array which allowed the system to boot perfectly after. I have no idea why it tries to assemble the same array two but on the second seems to be important

I am running NVIDIA P40s on a DELL R720/R730 and a NVIDIA A2000 12GB on a DELL Optiplex 9010 in my playlab. Getting the GPUs to be accessible for VMs was quite easy: shutdown the XCP-ng host, install the GPUs, start the host again, activate the GPU in the advanced settings of the host in the PCI Devices section (“Passthrough enabled”). The host will restart at this point after displaying a warning. That's it – the GPU can now be assigned to a VM in the VMs advanced settings. I do use the GPUs for AI workloads under Debian though, so your use case might vary.

@Pilow tags can work and the path to them is much more succinct. Thanks!

An intake is created for review with XO team. Thanks for the feedback @puffymob !