@florent As it turns out, the job completed the next time it ran and this task went away, not sure why that first one failed but it seems to be OK for now. I will update this if I see this error again and be sure to include as many logs as I can. Thanks as always!

@dinhngtu said in XCP-ng Windows PV tools announcements: Hello all, The XCP-ng Standard VGA Display Driver for Windows v0.1.29.2216 has been released https://github.com/xcp-ng/win-xstdvga This driver provides high-resolution consoles and resolution switching for Windows VMs running on the XCP-ng hypervisor. This is a beta release. This driver will eventually be integrated into the main Windows PV tools package. Driver pulled for bug fixes. Will come back soon Test on windows 11 vm no issues to report.

@markxc I don't think this is possible yet with the REST API. However, you should be able to do it using xo-cli: xo-cli vm.setBootOrder vm=<string> order=<string>

Hello Hope this help here is how I manage to configure GPU Passthrough. In my case I have follow the documentation on XCP-ng website : https://docs.xcp-ng.org/compute/ To sum up with XOA 8.3 here is what I did: ssh to XCP host, to identify the GPU PCI and run lspci to find my GPU. [root@xen ~]# lspci ... 0f:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1) Then disable the GPU for being used by XCP-ng itself( Dom0) using the XCP-ng uuid [root@xen ~]# xe pci-list uuid ( RO) : 7970825f-dd1c-c270-93a3-6761f00e1362 vendor-name ( RO): NVIDIA Corporation device-name ( RO): GA102 [GeForce RTX 3090] pci-id ( RO): 0000:0f:00.0 xe pci-disable-dom0-access uuid=<pci uuid> 3 reboot the XCP-ng host 4 Then from XOA attached the PCI related to my GPU to my guest VM. [image: 1770098359041-4dcb36ff-b29c-4d0b-b113-127243928dd6-image-resized.png] [image: 1770098407490-3f29792e-154f-40fc-b554-323d8ef87e52-image.png] [image: 1770098436148-7208a3ff-68e2-4c50-9dc8-2edde9ac8d76-image-resized.png] 5 install official Nvidia drivers ( closed source ) and have then the card available in the guest. [image: 1770098585851-9bcbea25-b83b-4a26-a085-b58236c83f84-image.png] [image: 1770098624052-88f35aba-bd75-4da6-9cbf-d62bb8994ef7-image.png] What I didn't do is adding a vGPU in the guest configuration: [image: 1770098900399-63b2a458-9758-40d1-9515-48b5cd4615ea-image.png] I did it some times ago, also I don't recall having to do any specific configuration in the Bios to make this work. PS: I have an issue, I don't have output to the Display port or HDMI of this video card, which is not a blocker for me as that's not my immediate needs. Best.

@wilsonqanda Make sure to turn off "Network" in boot order. You might also want to increase the VM's root disk size when creating it. Here's a full cloud config that I used (except the ssh keys): #cloud-config hostname: {name} ssh_authorized_keys: - ssh-rsa ... disable_root: false apt: sources: xen-guest-agent: filename: xen-guest-agent.list source: deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/ append: false packages: - xen-guest-agent

Thanks, we need to update this!

Hi, Thanks for your feedback! Let me ping @bastien-nollet or @pdonias maybe

I made a list of processes with a small bash script that I am attaching here [image: 1769612600385-screenshot-2026-01-28-alle-16.01.53.png]

@florent Yes.

What is the purpose of this discussion? Could this feature integrate XCP-ng? We are looking for a new virtualization solution. Oracle is a bottleneck for backups. We tested the backup with the Veeam agent, which appears to be successful. However, replication is not possible for this Oracle point via Veeam.

I just want to add that I am seeing the same issue with Ubuntu 24.04.3. Creating a VM does work, but it crashes immediately when trying to start it for setup. I have not yet tried the approach of starting with 24.04(.00) and then upgrading to the lastest version due to lack of time. We are still using XCP-NG 8.2.1 on the server in question. If an upgrade to 8.3 solves the issue, please let us know. Reading the thread, it appears to have the same problem, though. Processor is an AMD Ryzen 9 3900X. We have not had any other issues with the system and it's been running for a few years.

My current findings regarding this: https://github.com/xcp-ng-rpms/microsemi-aacraid/issues/2 0nelight created this issue in xcp-ng-rpms/microsemi-aacraid open Microsemi Adaptec Series-8 Card not working in XCP-NG 8.3 #2

Hi @champagnecharly , On the XO side, it seems that this PCI has an empty string ID, which doesn't enable us to delete it. We'll have to do some tests to find out how to prevent that. We might have trouble reproducing the issue, so would you mind helping us with the tests? You would need to add this piece of code on file xo-server/dist/xapi-object-to-xo.mjs before the line that start with if (isHvm) { (that should be near line 475) if ((_vm$attachedPcis = vm.attachedPcis) !== null && _vm$attachedPcis !== void 0 && _vm$attachedPcis.includes('')) { warn('Empty string PCI id:', otherConfig.pci); } then restart xo-server and look at the output of journalctl, there should be some lines looking like: 2026-01-30T09:26:17.763Z xo:server:xapi-objects-to-xo WARN Empty string PCI id:

Hello All, This issue seem to completely go away on a older branch/tag if i build it from below for XO: xo-lite-v0.17.0 So the issue I would think is coming from the newer version of XO. Not sure best way to test this. So I am going back to an older commit. If anyone has any suggestion I can try helping as its an annoying issue.