Got everything set up in QEMU and the windows-side drivers installed but the VioGpuDod service is not starting and it falls back to basic VGA. On the other hand, setting it up to use QXL works just fine, just no acceleration.
Been through a few tutorials and just not seeing what I may have overlooked. Unless, I have to set up boot parameters or BIOS settings like I would for GPU pass through? Not seeing those instruction in any tutorials for Virtio though.
Device PCI\VEN_1AF4&DEV_1050&SUBSYS_11001AF4&REV_01\3&11583659&0&08 had a problem starting.
Driver Name: oem17.inf
Class Guid: {4d36e968-e325-11ce-bfc1-08002be10318}
Service: VioGpuDod
Lower Filters:
Upper Filters:
Problem: 0x0
Problem Status: 0xC00000E5
I’m seeing the same VioGpuDod fallback to basic VGA in a Windows 10 QEMU guest, while QXL works normally. The Problem Status 0xC00000E5 alongside the installed oem17.inf driver should help narrow this to the Virtio GPU driver or device configuration rather than a general display issue.
From what I can gather, the 0x0 code means it ignored the error and the 0xC00000CE5 means it didn’t start properly. So, expected level of insight from Microsoft error reporting ;). I did try shutting off Windows Defender thinking that might be the issue but, no luck.
All I need is enough to smoothly playback videos on the windows side (and stop just falling back to VGA) but, so far, the windows virtio drivers are worse than QXL. Although, there is this Github that seems to suggest building 3d drivers may be possible..
This project (and others like it) have been started/stopped for years. Maybe this one will finally work. For now, I would suggest using these tools: Windows Spice Tools
…as for playing with GPU pass-through, my motherboard is a little too basic for that. Although, if I were building one, I can envision a “Living Room / Entertainment PC” where it would use on-board graphics most of the time for streaming media or playing DVDs to save power. Then, for gaming, have it launch the VM which would access the power-hungry monster graphics card.
The 0xC00000E5 in that VioGpuDod entry points to a driver start failure, so Defender wasn’t confirmed. Since QXL works, I’d leave Virtio GPU aside rather than changing boot or BIOS settings.
That rules out Defender as the cause. With QXL working and Virtio reporting 0xC00000E5, QXL is the safer choice for this guest rather than chasing Windows 3D acceleration.
Yes, it’s fun to tinker with and perhaps something to consider for a future build. The main reason I broke down and installed windows in the first place was to update the firmware on my portable guitar amp. Went ahead and added MS 365 as well since I have the family subscription. It’s doing that just fine on QXL