@nick-lloyd thanks, I did! Passthrough for AMD consumer Hardare iGPUs seams not to properly function… or, I should say, the Linux VMs are experiencing troubles correctly dealing with it: the devices are correctly passing down to the VM, but for some reason the ROCm kernel module is not capable of dealing with them. Could it be be ause it expected them to be on a specific bus? (They are assigned a different bus id)
Could it be because it expected them to be under the same bus id? (They are scattered around different dedicated bus ids)
Not sure, but the end result is the iGPU cannot be correctly initialized, albeit detected.

@gleveque @olivierlambert Is there any update on this topic?

Am curious as am seeing the same exact behavior with Ubuntu 24.04.1 on a Beeline EQR6 with a Ryzen 9 (6900HX + 680M iGPU).

What would be the best option to pass through the iGPU from Dom0 to a VM?

@olivierlambert probably dumb question... but where can I find a clear complete overall document listing all endpoints for the Xen Orchestra API?

Tried the Vagrant plug-in mentioned above but I do agree it would be better to have a version of it targeting XO API rather than directly Xen/XCP-ng XAPI...

@olivierlambert was thinking about this specifically...

https://github.com/xapi-project/vagrant-xenserver/releases

It looks like it did not receive that much love recently, but it should work...

@olivierlambert sad to know! Most of all as it was working beautifully until very recently...

Thanks for the feedback though.

Do you have suggestion for CI using Vagrant to spin up machines hosted on XCP-ng? Is Vagrant xen-server plug-in considered robust enough? (Not judging from its latest version number... 0.0.6... double-O is license to kill, right?!)

Thanks!

Am experiencing a weird behavior and wondering if anybody experienced something similar or has some hints/guidance about it.

On a server running XCP-ng, VMs (running Ubuntu 18.04) with nested virtualization ON are rebooting abruptly when Vagrant (2.2.14) is trying to bring up a libvirt/kvm “sub-guest” machine (NO issue if the machine uses QEMU rather… although too slow for the purpose!). The last line logged by vagrant before the XCP-ng VM restarts itself are something like:

==> vagrant-5-project-2-concurrent-0-job-681: Creating shared folders metadata...
==> vagrant-5-project-2-concurrent-0-job-681: Starting domain.
==> vagrant-5-project-2-concurrent-0-job-681: Error when updating domain settings: undefined method 'strip' for nil:NilClass
==> vagrant-5-project-2-concurrent-0-job-681: Waiting for domain to get an IP address...
==> vagrant-5-project-2-concurrent-0-job-681: Waiting for SSH to become available...

The VM just blows up and it reboots. It was working fine until some time ago. It looks like an update of XCP-ng might have broken it?

Anyone experiencing similar problems?
Is anyone able to provide some advice?

Thank!