Skip to content
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

Open
kroese opened this issue Jun 6, 2024 · 13 comments
Open

viogpudo /virtio-vga broken in recent Windows builds #1102

kroese opened this issue Jun 6, 2024 · 13 comments
Assignees

Comments

@kroese
Copy link

kroese commented Jun 6, 2024

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 the viogpudo driver and stays black.

Using the std VGA device everything works.

The problem even exists with the new beta drivers, version 0.1.258.

@kostyanf14
Copy link
Member

@kroese Please provide QEMU CLI, QE can't reproduce this issue.

image

@6-dehan
Copy link
Contributor

6-dehan commented Jun 6, 2024

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
Dehan Meng

@kroese
Copy link
Author

kroese commented Jun 6, 2024

@6-dehan The commandline is:

-nodefaults
-cpu host,kvm=on,l3-cache=on,migratable=no,+hypervisor,hv_passthrough,+invtsc
-smp 2,sockets=1,dies=1,cores=2,threads=1
-m 4G
-machine type=q35,smm=off,graphics=off,vmport=off,dump-guest-core=off,hpet=off,accel=kvm
-enable-kvm
-global kvm-pit.lost_tick_policy=discard
-display vnc=:0,websocket=5700
-vga virtio
-monitor telnet:localhost:7100,server,nowait,nodelay
-daemonize
-D /run/shm/qemu.log
-pidfile /run/shm/qemu.pid
-name windows,process=windows,debug-threads=on
-serial pty
-device qemu-xhci,id=xhci
-device usb-tablet
-netdev tap,ifname=qemu,script=no,downscript=no,id=hostnet0
-device virtio-net-pci,romfile=,netdev=hostnet0,mac=02:BA:F0:B0:CC:13,id=net0
-drive file=/storage/windows.iso,id=cdrom0,format=raw,readonly=on,media=cdrom,if=none
-device virtio-scsi-pci,id=cdrom0b,bus=pcie.0,addr=0x5,iothread=io2
-device scsi-cd,drive=cdrom0,bus=cdrom0b.0,bootindex=10
-drive file=/storage/data.img,id=data3,format=raw,cache=none,aio=native,discard=on,detect-zeroes=on,if=none
-device virtio-scsi-pci,id=data3b,bus=pcie.0,addr=0xa,iothread=io2
-device scsi-hd,drive=data3,bus=data3b.0,channel=0,scsi-id=0,lun=0,rotation_rate=1,bootindex=3
-object iothread,id=io2
-rtc base=localtime
-global ICH9-LPC.disable_s3=1
-global ICH9-LPC.disable_s4=1
-drive file=/storage/windows.rom,if=pflash,unit=0,format=raw,readonly=on
-drive file=/storage/windows.vars,if=pflash,unit=1,format=raw
-object rng-random,id=objrng0,filename=/dev/urandom
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pcie.0,addr=0x1c

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).

  • When changing the vga device from virtio to std, it does not occur.
  • When removing the viogpudo folder from the drivers, it does not occur.
  • When changing the ISO from 24H2 to older Windows versions ( 23H2 and lower) it does not occur.

@6-dehan
Copy link
Contributor

6-dehan commented Jun 7, 2024

Thanks @kroese ,
After investigating your qemu-cli with @kostyanf14 , we found the 'smm=off' should change to on and all 'scsi-hd' should change to IDE. then virtio-vga works. so maybe virtio-scsi has some problem.
image

@kroese
Copy link
Author

kroese commented Jun 7, 2024

@6-dehan Thanks! But it is on purpose that I did not enable Secure Boot (smm=off), because there are other problems (not related to virtio-win) when enabling Secure Boot on hosts with certain CPU models. Also I reported before that vioscsi is having problems, see #1100 . But they said it was not a virto-win issue.

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 IDE or Secure Boot, because it will affect thousands of users. I guess I have no other option to wait until the drivers for 24H2 / Server 2025 are more mature, before I can offer those operating systems as an option.

@kroese
Copy link
Author

kroese commented Aug 17, 2024

Problem still present in v0.1.262

@6-dehan Also it does not seem to be related to having smm=off or smm=on, it occurs in both cases for me. And both with scsi or ide disks.

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.

@6-dehan
Copy link
Contributor

6-dehan commented Aug 20, 2024

Hi @kroese,
I could reproduce this issue on

  1. win2025/Win11 24H2/win2022 with the latest 262prewhql.iso.
  2. win2025/Win11 24H2 with the 258prewhql.iso

scenario:

  • After loading virtio-GPU driver. the screen gotta black situation and couldn't login system.

@vrozenfe
Copy link
Collaborator

@6-dehan

Do we have a Jira issue for tracing this problem?
Thanks,
Vadim.

@6-dehan
Copy link
Contributor

6-dehan commented Aug 20, 2024

@vrozenfe , yeah, I'll paste issue here later. I was testing for more details update.

@6-dehan
Copy link
Contributor

6-dehan commented Aug 20, 2024

Update:
If use the signed driver like 'virtio-win-1.9.40-0.el9_4.iso', the system and vio-GPU driver will be installed successfully without any black screen kind of issue. so I'll try the latest virtio-win rpm after the @vrozenfe makes it.

@6-dehan
Copy link
Contributor

6-dehan commented Aug 20, 2024

@vrozenfe @kroese
Update the latest result:
I tried draft virtio-win.iso (not release, test-only) 2025/win11 24h2/2022 will not hit any black screen problem. anyway we have this issue ‘RHEL-55254’ for tracking this problem. feel free to contact us if needed. thanks

@kroese
Copy link
Author

kroese commented Aug 20, 2024

@6-dehan Is there anywhere I can download that ISO to confirm if it solves the problem?

@6-dehan
Copy link
Contributor

6-dehan commented Aug 21, 2024

@6-dehan Is there anywhere I can download that ISO to confirm if it solves the problem?

@kroese That's a draft build for internal testing. But no worry for sure, it will be published soon as our latest virtio-win.iso.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants