@Greg_E or just uncheck the "protection"-flag. But that get tedious very quickly. And I only had to do it on 6 VMs.

@dinhngtu tried on a Windows Server 2025 VM, UEFI BIOS working well, no reboot needed

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

It's not a problem with XO backups

@whyberg Normally not 10x...

@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

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.

@markxc could you tell us what endpoint you used ?

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

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

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

@olivierlambert okay, understood. it is small minor cosmetic problem as of now. need to get you an access to our internal developped app, to show you the potential of sub-xoas ^^' almost out of alpha phase

Hi! See https://docs.xcp-ng.org/releases/release-8-3/#4k-native-disks and https://docs.xcp-ng.org/storage/#largeblock-sr Note that qcow2 format is supporting 4k natively, and it's in release candidate stage, maybe the right approach in a near future

Something to document @thomas-dkmt

Hi! ISO-SR over HBA/FC would be very nice, especially when migration form a SAN vmware-System to XCP-NG. One other thing is altering. Errors like "VM cannot be migrated" or similar should not be silent but should be very visible / even mailed to the admin. Another thing (could be cosmetical though) in my opinion is that a failed Rolling upgrade remains visible with a half fulled progress bar in the task-view. this is confusing.

Mentioning also @Team-Hypervisor-Kernel who now manages the drivers. Maybe it's related to https://github.com/xcp-ng-rpms/microsemi-aacraid/issues/2#issuecomment-3837183087 It looks like the switch to the vendor driver instead of the kernel built-in for 8.3 (initiated by XenServer, and that we followed at the time as it was probably made in order to support newer cards) was not without drawbacks. 0nelight created this issue in xcp-ng-rpms/microsemi-aacraid open Microsemi Adaptec Series-8 Card not working in XCP-NG 8.3 #2