HP microserver Gen8, no more iommu groups after the latest firmware upgrade

[uxbeginner22]

I have a Gen8 HP Microserver.
Until the last firmware update iommu and pci pass-trough works fine (except for multi function devices like videocards with hdmi audio).
Yesterday I have update the ilo firmware and..no more iommu.
Xen failed to pass a pci device

libxl: error: libxl_pci.c:1434:pci_add_dm_done: Domain 4:xc_assign_device failed: Operation not supported
libxl: error: libxl_pci.c:1721:device_pci_add_done: Domain 4:libxl__device_pci_add failed for PCI device 0:8:4.0 (rc -3)

Intel VT-D is enabled in the server

rbsu> SHOW CONFIG INTEL(R) VT-D
Intel(R) VT-d
1|Enabled <=
2|Disabled

This is dmesg output

[ 1.223464] DMAR: IOMMU enabled
[ 1.504966] iommu: Default domain type: Translated
[ 1.788001] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.
[ 2.037115] intel_iommu=on

This is the cmdline for kernel

intel_iommu=on mitigations=auto,nosmt l1tf=full,force systemd.unified_cgroup_hierarchy=0 quiet

What I miss? Is a bug of firmware or misconfiguration?
The system is Debian 11, Xen hypervisor, Latest firmware on HP Gen8 Microserver.
Cpu is Xeon v2 and iommu/vt-d is supported

[Suman_1978]

Hi,

What is the PCI device in "PCI device 0:8:4.0"?

Have you tried this method mentioned in this (non-HPE) post?

Thank You!
I work with HPE but opinions expressed here are mine.
Recent Support Video Releases

[uxbeginner22]

@Suman_1978 

Is a sound card for Asterisk server vm.

Until the last week works perfect, after firmware upgrade stop working.

Is possible a downgrade of ilo4 firmware?

[Suman_1978]

Hi,

Have you tried removing that Sound card to check if the error goes away?

Downgrading iLO FW?  Certain versions may not be able to downgrade, please refer to the Revision History for downgrading info.

Version: 2.80 (8 Apr 2022)
Changes included to ensure that iLO 4 firmware cannot be downgraded below iLO 4 v2.54 directly from iLO 4 v2.80. This is to ensure users are not impacted by security vulnerability CVE-2017-12542 that has been fixed.

If none of these works, you may need to contact HPE Support for help.

Thank You!
I work with HPE but opinions expressed here are mine.
Recent Support Video Releases