I've got the same issue. Had to rollback to 1809.
The working driver is named:
10.0.17763.1 (WinBuild.160101.0800) from 14th sept 2018
The non-working driver is:
10.0.18362.1 (WinBuild.160101.0800) from 18th march 2019
My versions (both tested):
$ /opt/qemu4/bin/qemu-system-x86_64 --version
QEMU emulator version 4.1.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
$ qemu-system-x86_64 --version
QEMU emulator version 3.1.1 (qemu-3.1.1-2.fc30)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
My qemu startup line is:
/path/to/correct/qemu-system-x86_64 \
-runas idarlund \
-name win10,process=win10 \
-machine type=q35,accel=kvm,kernel_irqchip=on \
-cpu
host,kvm=off,hv_vendor_id=1234567890ab,hv_vapic,hv_time,hv_relaxed,hv_spinlocks=0x1fff,l3-cache=on,-hypervisor,migratable=no,+invtsc
\
-smp 12,sockets=1,cores=12,threads=1 \
-m 24G \
-rtc clock=host,base=localtime \
-vga none \
-nographic \
-serial none \
-parallel none \
-usb \
-soundhw hda \
-device vfio-pci,host=2a:00.0,multifunction=on \
-object
input-linux,id=mouse1,evdev=/dev/input/by-id/usb-Logitech_Gaming_Mouse_G402_6D8A12705348-event-mouse
\
-object
input-linux,id=kbd1,evdev=/dev/input/by-id/usb-Logitech_HID_compliant_keyboard-event-kbd,grab_all=on,repeat=on
\
-device ivshmem-plain,memdev=ivshmem,bus=pcie.0 \
-object
memory-backend-file,id=ivshmem,share=on,mem-path=/dev/shm/looking-glass,size=128M
\
-audiodev pa,id=pa1,server=/run/user/1000/pulse/native \
-drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \
-drive if=pflash,format=raw,file=/tmp/my_vars.fd \
-boot order=dc \
-drive
id=disk0,if=virtio,cache=none,format=qcow2,aio=threads,file=/var/lib/libvirt/images/windowstest.qcow2
\
-netdev type=bridge,id=net0,br=virbr1 \
-device e1000,netdev=net0,mac=00:16:3e:00:08:02
I'm not sure if this bug report should be reported to qemu tho. We
should probably file a bug report to Microsoft as well.
** Also affects: fedora
Importance: Undecided
Status: New
** No longer affects: fedora
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1839060
Title:
HDA device non functional in Windows 10 1903
Status in QEMU:
New
Bug description:
I made the update to 1903, and the HDA device stopped working.
The driver says the device is working correctly, but it does not.
When I try to open the Windows sound configuration, the dialog hangs and
never shows it's content.
Several people reported this back in May:
https://windowsreport.com/windows-10-v1903-ich6-ich9-virtio/
I can confirm I have exactly the same problem.
Host is Arch Linux, current (5.2.5) kernel, QEMU 4.0.
I enabled HDA debug output and compared an older, working Windows
version to 1903, but could not see the difference. The driver seems to
issue the same verbs.
I am happy to provide additional information if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1839060/+subscriptions
