-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
viogpudo /virtio-vga broken in recent Windows builds #1102
Comments
@kroese Please provide QEMU CLI, QE can't reproduce this issue. |
Hi @kroese, could you please provide more details like when you installed the driver? during the installation of system or installed virtio-vga after installing system. And yes, please provide us the qemu-cli. Thanks |
@6-dehan The commandline is:
it happens when the driver is installed during the setup (automaticly via unattended install, or when loading it manually when windows asks for boot-critical drivers).
|
Thanks @kroese , |
@6-dehan Thanks! But it is on purpose that I did not enable Secure Boot ( I am using these drivers in my project ( https://github.com/dockur/windows ) which has a large userbase, so I cannot just switch the whole project to |
Problem still present in v0.1.262 @6-dehan Also it does not seem to be related to having The only new thing I discovered is that if you just wait a couple minutes with the black screen, the image comes back and the installation will actually proceed. |
Hi @kroese,
scenario:
|
Do we have a Jira issue for tracing this problem? |
@vrozenfe , yeah, I'll paste issue here later. I was testing for more details update. |
Update: |
@6-dehan Is there anywhere I can download that ISO to confirm if it solves the problem? |
In recent Windows versions, like Server 2025 and Windows 11 IoT 24H2, when using the
virtio-vga
graphics device, the screen turns black when installing theviogpudo
driver and stays black.Using the
std
VGA device everything works.The problem even exists with the new beta drivers, version
0.1.258
.The text was updated successfully, but these errors were encountered: