Guest freezes until there is a keyboard input on Windows version

[Abdurrahim]

I am using Qemu for Windows and when I try to run this for Windows guests then the guests are freezing and waiting for keyboard input and it continues to function after I press a key. I am using Windows10 Home and below is the command I use to run the guest. I have suspected if this is caused by random entropy but even with mouse moving it gives same random locks and it continues to work as soon as I press a key so maybe its not about entropy at all,

startwinguest.bat:
qemu-system-x86_64 ^
 -name "win" ^
 -machine type=q35,accel=whpx ^
 -cpu EPYC,hv_relaxed,hv_time,topoext ^
 -nodefaults ^
 -usb ^
 -rtc base=localtime,driftfix=slew ^
 -smp 6,sockets=1,cores=3,threads=2 ^
 -m 8192 -mem-prealloc ^
 -soundhw hda ^
 -usbdevice tablet ^
 -netdev user,id=mynet0,hostfwd=tcp::3390-:3389 -device virtio-net,netdev=mynet0 ^
 -vga std ^
 -display gtk ^
 -boot d ^
 -device virtio-scsi-pci,id=scsi0 ^
 -drive "file=%~dp0win10.qcow2,if=none,format=qcow2,discard=unmap,aio=threads,cache=writethrough,id=someid" ^
 -device scsi-hd,drive=someid,bus=scsi0.0 ^
 -drive "file=D:\Setups\OS\Windows\en_windows_server_2019_updated_dec_2020_x64_dvd_36e0f791.iso,media=cdrom,index=1" ^
 -drive "file=%~dp0virtio-win-0.1.185.iso,media=cdrom,index=2"

[Ivan Vulovic (ivanvx)]

I run into this behavior too. Win10 Home guest, PCI-passthrough graphics (GTX 1650), host cpu (Ryzen 7 3800XT). Occurs whether or not I use the qcow disk drive.

qemu-system-x86_64
  -cpu host,kvm=on,l3-cache=on,hv_relaxed,hv_vapic,hv_time,hv_spinlocks=0x1fff,hv_vendor_id=hv_dummy
  -smp 8
  -rtc clock=host,base=localtime
  -machine type=q35,accel=kvm,kernel_irqchip=on
  -enable-kvm
  -drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd
  -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd
  -m 32G
  -usb
  -device usb-tablet
  -vga none
  -serial none
  -parallel none
  -boot cd
  -nographic
  -device usb-host,vendorid=0x045e,productid=0x00db
  -device usb-host,vendorid=0x1bcf,productid=0x0005
  -drive id=disk0,index=0,format=qcow2,if=virtio,cache=off,file=./win10_boot_priv.qcow2
  -drive id=disk2,index=2,aio=native,cache.direct=on,if=virtio,cache=off,format=raw,discard=unmap,detect-zeroes=unmap,file=/dev/vg0/win10_hdpriv
  -device vfio-pci,host=09:00.0,addr=0x02.0x0,multifunction=on
  -device vfio-pci,host=09:00.1,addr=0x02.0x1
  -device vfio-pci,host=09:00.2,addr=0x02.0x2
  -device vfio-pci,host=09:00.3,addr=0x02.0x3
  -netdev tap,id=netid,ifname=taplan,script=no,downscript=no
  -device e1000,netdev=netid,mac=52:54:00:01:02:03

[Ivan Vulovic (ivanvx)]

PS - My host is Debian 4.19.171-2

[Thomas Huth (th-huth)]

The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.

If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".

If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:

1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:

    https://gitlab.com/qemu-project/qemu/-/issues

and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.

2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).

Thank you and sorry for the inconvenience.

[Thomas Huth (th-huth)]

This ticket has been moved here (thanks, Abdurrahim):
https://gitlab.com/qemu-project/qemu/-/issues/289
... thus I'm closing this ticket on Launchpad now.