-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.6
-
qemu-kvm-9.1.0-25.el9
-
No
-
Moderate
-
rhel-virt-hwe-x86e
-
ssg_virtualization
-
20
-
26
-
None
-
False
-
False
-
-
None
-
None
-
Pass
-
Manual
-
None
QE found during experimental testing that when running a Windows guest with the virtual amd iommu device, Windows complains that a device driver could not be found.
As a POC, something like this fixes this issue:
diff --git a/hw/i386/amd_iommu.c b/hw/i386/amd_iommu.c
index 464f0b666e..357a756af4 100644
— a/hw/i386/amd_iommu.c
+++ b/hw/i386/amd_iommu.c
@@ -1655,6 +1655,7 @@ static void amdvi_pci_class_init(ObjectClass
*klass, void *data)
k->vendor_id = PCI_VENDOR_ID_AMD;
k->class_id = 0x0806;
+ k->device_id = 0x1419;
k->realize = amdvi_pci_realize;
set_bit(DEVICE_CATEGORY_MISC, dc->categories);
AMD is still evaluating the correct approach to fix this issue.
- blocks
-
RHEL-29192 Ask for AMD IOMMU support on qemu-kvm downstream according to the latest windows security feature
-
- Release Pending
-
- is cloned by
-
RHEL-85650 [RHEL 10]Qemu/amd-iommu: Advertise a suitable device id
-
- Planning
-
- split to
-
RHEL-104771 Run "Signed Driver Check(ChekLogo)" test when the virtio-win package released
-
- Closed
-
- links to
-
RHBA-2025:147368 qemu-kvm bug fix and enhancement update