Same answer than the other topic, checking first the basics before investigating further

Have you checked all the pre requisites at https://docs.xcp-ng.org/compute/#-pci-passthrough?

Also be sure to use the complete PCIe address, like:

/opt/xensource/libexec/xen-cmdline --set-dom0 "xen-pciback.hide=(0000:04:01.0)(0000:00:19.0)"

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

Hi,

Sadly, even if Minio is probably better than others (eg BackBlaze), they can suffer from various issues. There's a reason why we only provide official pro support on AWS.

Would it be possible to test another provider to double check it's not XO related?

Hi,

It's not relevant for our most critical users (ie paid customers), because they don't want to have a complex matrix. They all come from VMware and they need something simple to explain.

If you are a home labber, you can just check xcp-ng.org website and https://docs.xen-orchestra.com/installation, that's enough

Can you do a lspci in the Dom0? I'm not sure the audio device is an adressable device (unlike Nvidia cards for example)

Each month we release new features, so it's hard to tell, it depends on which feature you are expecting exactly

Upstream inclusion is ultra recent, but you can always add drivers yourself (still requiring a relatively recent kernel IIRC). Anyway, we have the hardware and it will be in the roadmap at least to explore

Yes but in order to see the VF I need a working driver in the Dom0 first Probably a lot easier with a more recent kernel in XCP-ng 9.0

No, I have an Intel Flex 170

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

I received one card, I quickly tested it, you can actually see 2x GPU (as expected), PCI passthrough each to a different VM. So at least, basic stuff works.

A next step (when we can staff someone) is to check how to manually enable SRIOV on the device and pass it to the VMs, and in the end, get that done in XAPI to make it integrated with XO.

And I assume the task is created on the master regardless the restore place is?

Before the end of this month.

It's where the task is hosted. XO does not invent it, just fetch it from XAPI. It's using exactly the "resident on" field from there: https://xapi-project.github.io/xen-api/classes/task.html

So it's not an XO "problem". I don't know the mechanism behind the "resident on" logic, so pinging @Team-XAPI-Network

XO doesn't care where the previous/existing VM is running, restore creates an entirely new VM, so I'm not sure to get it either

I'm not sure to get it. If it's a restore, the source is not a SR but a BR. The question is the destination SR, so you do confirm it's a local SR to h2?