Vates group | XCP-ng and XO forum

Danp

Hi,

You may want to follow this thread for the VDI not visible issue.

Dan

TeddyAstie

@benapetr said in New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client:

@Pilow I know them a little bit, I will have a look, but I am now working on another new cool thing! It's called xen_exporter: https://github.com/benapetr/xen_exporter

It's a prometheus exporter that hooks directly to xen kernel via xenctrl library from dom0 and extract all low-level metrics from the host, allowing very detailed graphs with very low granularity with stuff I always missed in both XenOrchestra and XenAdmin:

...

We have a similar project : https://github.com/xcp-ng/xcp-metrics, but unfortunately it's not used as of today (though it could get revived as Rust for Xen matures, i.e easier to build).
There is also Xen Orchestra OpenMetrics support but it's not on XCP-ng itself.

olivierlambert

That's a very good question, let me ask internally. Ping @pdonias he might know the answer

olivierlambert

@vanny you can say you are working for Vinchin, I prefer when it's clearly told

olivierlambert

That's very interesting, let me make sure @florent got this

olivierlambert

I know it's actively worked as we speak (ACLv2). So I would say this year at least It's in our (soon published) roadmap in the "Next" section, just after the "now".

TeddyAstie

@DustyArmstrong

EDIT: It looks like I may just have a fake BIOS? The settings to enable all the relevant components (IOMMU, DMAr support etc) don't actually seem to do anything, they might just be for show - dmesg | grep -i iommu returns nothing, dmesg | grep -i -e dmar -e vfio -e pciback only shows pciback info, and cat /proc/cmdline contains nothing about IOMMU. Oddly, XO is still reporting that IOMMU is enabled:

dmesg in the Dom0 will not report the information you're looking for.
To know if PCI Passthrough is supported (e.g IOMMU enabled), you should check xl info | grep virt_caps and look for hvm_directio. You can also look for IOMMU-related stuff in xl dmesg.
As you managed to passthrough the device (even if not working in the guest), I don't see a issue there.

[ 4.655776] amdgpu 0000:00:08.0: amdgpu: Unable to locate a BIOS ROM
[ 4.655797] amdgpu 0000:00:08.0: amdgpu: Fatal error during GPU init
[ 4.655812] amdgpu 0000:00:08.0: amdgpu: amdgpu: finishing device.
[ 4.656681] amdgpu 0000:00:08.0: probe with driver amdgpu failed with error -22

Is there a trick to this, has anyone had success with this kind of AMD GPU? On my old hosts, enabling pass through was enough for it to just kind of work (Intel HD 530). The host machine outputs to a display normally when the card is in-use by the host. I am of the understanding the ROM is just part of the motherboard/GPU, there is some suggestion it can be dumped from the host-side, but I'm unsure on this.

Looks like the GPU ROMBAR is missing in the guest, while it's ok for many devices, many others will fail to work without it (like this GPU).
To me, there's something missing on the PCI Passthrough logic, I just brought the topic internally to see what we can do.

florent

@ItzJay said in Problems import vm Vmware to Xcp-ng from import Vmware and OVA:

@florent By base OS you mean the based Debian XOA appliance?

yes , I was not sure it was a XOA. If it's a xoa, how old is it ? would it be ok to open a ticket so we can check it on monday ?

bleader

@ditzy-olive Hello, be careful with that, your script installs it to /etc/sysconfig/iptables which is part of the iptables-services package, so it could be overwritten by a package update.

Granted, I don't think we ever updated it, but an upgrade to a newer version (when v9.0 comes) will for sure replace it.

Vates

Posts

Member List