Hi, Just to be sure I understand, you can see the device with lspci (as the CX23887/8 Broadcast thing) but it's not listen in XO web UI, right?

Hi, Small side note: lately I’ve noticed that some posts look like they were generated by LLMs. This can actually make it harder for the community to help, because the text is often long, unclear, or missing the basic details we really need to assist. I’d really encourage everyone to write posts in their own words and share as much relevant information as possible. The real value of this community is people helping each other directly

Hmm are you sure it's correctly ignored before trying to pass it trough? The success of PCI passthrough is only possible because it's hidden from the Dom0

Adding @florent in the loop

@AlbertK said in XCP-ng - XOA vs. XOCE: @Danp , Is it possible to add the comparison of the XOCE together wit XO in this page?. https://vates.tech/pricing-and-support/#features-matrix XOCE is a term that I came up with when I originally started writing the deployment script that exists today. It's stuck around. Vates uses the terms XOA and "XO from Sources" as their unique products. XOCE would be "you used a github script to deploy" (my github) XO. XO from Sources is a completely manual process where you're following the documentation to deploy XO. This approach gets you the same thing that XOCE does, but takes longer to complete since you're finishing each step over SSH rather than running a single bash command on a Ubuntu/Debian VM.

Hello, thank you for your reply @bogikornel @TrapoSAMA . Here are my processor specifications: Intel Xeon E5-1620 v2 (8) @ 3.691GHz. Unfortunately @Andrew , I have to use RHEL 10 on my server ^^ but thank you for providing the link. I will change my processor/server.

@Danp UEFI

Thanks for engaging! In this thread I would say: Storage I need it to get ISO files uploaded without going native (CLI). Or in other words, the basic stuff you would expect of a web-interface to be able to launch working VM's.

I worked with ChatGPT on this for a bit. We have narrowed it down to an issue with the NFS Storage that I ship the backups to. "When you recreated storage and moved data back, OMV is technically exporting a different underlying filesystem object than before. NFS clients that had an old handle cached (your XCP-ng host) try to access it and get ESTALE. That explains the initial backup errors and why deleting/re-adding the SR is failing now." I had to remove the NFS storage from XCP-ng, then delete the NFS share from OMV, then add the NFS share back to OMV, and then add it back to XCP-ng. I probably could have resolved this with a reboot, but I didn't wanna. This issue is resolved now.

@acebmxer Hello, We’re aware of the Backblaze rate limits and this isn’t the first time it’s been raised. We’ll be looking into this on the XO side, studying different options such as caching restore points to reduce API calls. Longer-term improvements, possibly tied to advanced XO6 dashboards, are more of a 2026 horizon. Thanks for bringing this up!

@bryonadams said in Trouble Creating VM via API: Is there a place I can submit a feature request to allow setting a description and other settings from the UI to get feature parity when creating a VM? Otherwise, there's not much point since I have to go in and touch the new VM anyway. Unless I'm going about this wrong to begin with? You can create a feature request on Xen Orchestra github repository (https://github.com/vatesfr/xen-orchestra/issues), and if you have subscribed to support via XOA you can send a request through Zammad.

@Bastien-Nollet Thanks for the suggestion, though I think I am going to avoid doing that in a production setup. I'll look forward to it being included in a newer version. Our backups run nightly and it's random which VMs fail with this error, but so far it's almost never been the same one each night, so at worst we are 24hrs behind on a single VM backup which isn't a huge deal. Our other nightly backup job to S3 works just fine too so we're covered. Thanks!

@olivierlambert While VDI is maybe not as vital as it once was...I'm experimenting with multimedia work in XCP-ng. Having a VM with GPU off-loading of CODEC encoding would be nice. It's a pretty big CPU hit to make that go.

This info may also shed light: [08:39 xandria /]# dmesg | grep i40e [ 24.513039] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.25.11 [ 24.513042] i40e: Copyright (C) 2013-2024 Intel Corporation [ 24.530151] i40e 0000:04:00.0: fw 6.0.48442 api 1.7 nvm 6.01 0x80003484 1.1747.0 [ 24.600704] i40e 0000:04:00.0: MAC source pruning enabled on all VFs [ 24.600844] i40e 0000:04:00.0: MAC address: 40:a6:b7:b8:45:e8 [ 24.601304] i40e 0000:04:00.0: FW LLDP is disabled [ 24.601361] i40e 0000:04:00.0: FW LLDP is disabled, attempting SW DCB [ 24.609522] i40e 0000:04:00.0: SW DCB initialization succeeded. [ 24.612187] i40e 0000:04:00.0: MAC source pruning enabled on all VFs [ 24.626574] i40e 0000:04:00.0 eth1: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: RX/TX [ 24.628624] i40e 0000:04:00.0: PCI-Express: Speed 8.0GT/s Width x8 [ 24.637352] i40e 0000:04:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 16 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA [ 24.654350] i40e 0000:04:00.1: fw 6.0.48442 api 1.7 nvm 6.01 0x80003484 1.1747.0 [ 24.823713] i40e 0000:04:00.1: MAC source pruning enabled on all VFs [ 24.823850] i40e 0000:04:00.1: MAC address: 40:a6:b7:b8:45:e9 [ 24.824318] i40e 0000:04:00.1: FW LLDP is disabled [ 24.824375] i40e 0000:04:00.1: FW LLDP is disabled, attempting SW DCB [ 24.832392] i40e 0000:04:00.1: SW DCB initialization succeeded. [ 24.834904] i40e 0000:04:00.1: MAC source pruning enabled on all VFs [ 24.848482] i40e 0000:04:00.1 eth3: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: RX/TX [ 24.850610] i40e 0000:04:00.1: PCI-Express: Speed 8.0GT/s Width x8 [ 24.859297] i40e 0000:04:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 16 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA [ 24.876551] i40e 0000:04:00.2: fw 6.0.48442 api 1.7 nvm 6.01 0x80003484 1.1747.0 [ 24.941234] i40e 0000:04:00.2: MAC source pruning enabled on all VFs [ 24.941368] i40e 0000:04:00.2: MAC address: 40:a6:b7:b8:45:ea [ 24.941827] i40e 0000:04:00.2: FW LLDP is disabled [ 24.941883] i40e 0000:04:00.2: FW LLDP is disabled, attempting SW DCB [ 24.949994] i40e 0000:04:00.2: SW DCB initialization succeeded. [ 24.952571] i40e 0000:04:00.2: MAC source pruning enabled on all VFs [ 24.966298] i40e 0000:04:00.2 eth5: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: RX/TX [ 24.968447] i40e 0000:04:00.2: PCI-Express: Speed 8.0GT/s Width x8 [ 24.977158] i40e 0000:04:00.2: Features: PF-id[2] VFs: 32 VSIs: 34 QP: 16 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA [ 24.994453] i40e 0000:04:00.3: fw 6.0.48442 api 1.7 nvm 6.01 0x80003484 1.1747.0 [ 25.063546] i40e 0000:04:00.3: MAC source pruning enabled on all VFs [ 25.063681] i40e 0000:04:00.3: MAC address: 40:a6:b7:b8:45:eb [ 25.064149] i40e 0000:04:00.3: FW LLDP is disabled [ 25.064205] i40e 0000:04:00.3: FW LLDP is disabled, attempting SW DCB [ 25.072278] i40e 0000:04:00.3: SW DCB initialization succeeded. [ 25.075960] i40e 0000:04:00.3: MAC source pruning enabled on all VFs [ 25.089578] i40e 0000:04:00.3 eth7: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: RX/TX [ 25.091713] i40e 0000:04:00.3: PCI-Express: Speed 8.0GT/s Width x8 [ 25.100391] i40e 0000:04:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 16 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA [ 25.117883] i40e 0000:41:00.0: fw 9.154.78653 api 1.15 nvm 9.54 0x8000fb5f 1.3800.0 [ 25.306399] i40e 0000:41:00.0: MAC source pruning enabled on all VFs [ 25.306607] i40e 0000:41:00.0: MAC address: 68:05:ca:df:3b:26 [ 25.307055] i40e 0000:41:00.0: FW LLDP is disabled [ 25.307111] i40e 0000:41:00.0: FW LLDP is disabled, attempting SW DCB [ 25.313620] i40e 0000:41:00.0: SW DCB initialization succeeded. [ 25.316748] i40e 0000:41:00.0: MAC source pruning enabled on all VFs [ 25.322371] i40e 0000:41:00.0: PCI-Express: Speed 8.0GT/s Width x8 [ 25.324617] i40e 0000:41:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 16 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA [ 25.342061] i40e 0000:41:00.1: fw 9.154.78653 api 1.15 nvm 9.54 0x8000fb5f 1.3800.0 [ 25.402254] i40e 0000:41:00.1: MAC source pruning enabled on all VFs [ 25.402406] i40e 0000:41:00.1: MAC address: 68:05:ca:df:3b:27 [ 25.402924] i40e 0000:41:00.1: FW LLDP is disabled [ 25.402981] i40e 0000:41:00.1: FW LLDP is disabled, attempting SW DCB [ 25.409497] i40e 0000:41:00.1: SW DCB initialization succeeded. [ 25.412550] i40e 0000:41:00.1: MAC source pruning enabled on all VFs [ 25.418165] i40e 0000:41:00.1: PCI-Express: Speed 8.0GT/s Width x8 [ 25.420417] i40e 0000:41:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 16 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE P

Partly, I will see when back from vacation Anyway, unrelated to XO

Before the end of this month.

On DOM0 (host xcp-ng) traffic is filtered by iptables. So iptables -L will show which ports are open. Everything else will be rejected by default. For testing, you can stop iptables. If that helps, add rules. Keep in mind that XCP-NG is based on CentOS. So you can easily find an answer on Google for any question.

@DustinB Guest tools simply don't support the system I'm running.