-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-10.0
-
No
-
Low
-
rhel-virt-windows
-
2
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
*Is your feature request related to a problem? Please describe.*
The current VirtIO GPU driver for Windws has a hardcoded subsystem and revision:
```
[VioGpu.NTamd64.10.0]
%VioGpuDod.DeviceDesc% = VioGpuDod_Inst, PCI\VEN_1AF4&DEV_1050&SUBSYS_11001AF4&REV_01
```
This works fine for QEMU, but other virtualization tools that implement VirtIO GPU might have different subsystem and/or revision IDs.
*Describe the solution you'd like*
Change the driver to allow for any VirtIO GPU with Vendor 1AF4 and Product 1050. Just changing it to this should do the trick:
```
[VioGpu.NTamd64.10.0]
%VioGpuDod.DeviceDesc% = VioGpuDod_Inst, PCI\VEN_1AF4&DEV_1050
```
*Describe alternatives you've considered*
I have tried modifying the INF file manually, but that of course breaks the driver signature, making it unusable.
*Additional context*
I am running Windows inside Apple's Virtualization Framework on macOS. It implements the VirtIO GPU but with a different subsystem ID. Because of this, the driver does not automatically bind to the GPU. Manually binding it through device manager works fne, and there is no problem running the VM with the driver.