I recreate my ZFS pool. But next time or for other stuck with this kind of issue, I think you should start to rename your ZFS POOL. I think the old ZPOOL name stay in XO configuration shadow settings. To rename a ZFS pool, export it with zpool export [poolname] and then import it with the new name using zpool import [poolname] [newpoolname] And then recreate (sr-create) your STORAGE in XO

@DaleDibbadel Are you running XOA or XO from the sources? Are you up-to-date?

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

You can forget them, no issue.

Hi, Have you followed https://help.vates.tech/kb/en-us/8-technical-support/15-open-a-support-ticket ?

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

Hi @jacob.becker, We identified the issue last weekend, and we're currently working on a solution. We plan to include a fix in the next XO release.

@myles3 Hello Myles3. This post is over 20 days old. The issue was since been resolved by support. I dont remember the exact solution off the top of my head with out looking it up.

Hi, In those cases, my first bet is a memtest to check the RAM and CPU.

Yes but why it works with some and not others. I suspect the firmware version in the NIC itself.

@irtaza9 it scans all the VDI's on the SR to see if something has changed, if there's a need for coalesce and so on. I dont think it will be a big issue if you increase the auto-scan-interval value to lets say 5 minutes (300 seconds), but do remember, that everything regarding the VDI's on the SR will take up to 5 minutes to update, as well as triggering coalesce after removing snapshots.

@andSmv I definitely think it would be nice with support even though i repurposed my M2 Coral for other uses. But one thing to keep in mind regarding resources is that the product would appear to be heading to https://killedbygoogle.com coral.ai redirects to their new NPU offering and no updates have been made from google to the driver since 2022... Mouser still has plenty of stock though. Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either.

I have no clue, I usually back it up with XO, its the one called "XO config & pool metadata backup" and only had to restore it once.