summary refs log tree commit diff stats
path: root/results/classifier/118/all/1839060
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/all/1839060')
-rw-r--r--results/classifier/118/all/1839060137
1 files changed, 137 insertions, 0 deletions
diff --git a/results/classifier/118/all/1839060 b/results/classifier/118/all/1839060
new file mode 100644
index 000000000..78fefb49c
--- /dev/null
+++ b/results/classifier/118/all/1839060
@@ -0,0 +1,137 @@
+permissions: 0.964
+user-level: 0.964
+peripherals: 0.959
+device: 0.959
+debug: 0.955
+hypervisor: 0.954
+virtual: 0.953
+assembly: 0.952
+arm: 0.951
+mistranslation: 0.951
+socket: 0.950
+network: 0.950
+vnc: 0.950
+performance: 0.949
+architecture: 0.948
+risc-v: 0.948
+graphic: 0.948
+boot: 0.948
+semantic: 0.947
+kernel: 0.947
+register: 0.946
+PID: 0.946
+files: 0.942
+ppc: 0.940
+VMM: 0.934
+KVM: 0.929
+x86: 0.915
+TCG: 0.907
+i386: 0.899
+
+HDA device non functional in Windows 10 1903
+
+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.
+
+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 posted on Microsoft answers; https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/qemu-hda-device-non-functional-in-windows-10-1903/9a5309bc-073f-469b-8743-16df7e6e1dbd
+
+Created Windows feedback as instructed by Andre:
+https://aka.ms/AA5wlk7
+Please upvote this to get attention by Microsoft.
+
+Hi,
+
+I am trying to dig into this issue, can you please provide the verb debug trace from the working version of windows.
+
+Tried sending you a message @ginf, but haven't heard back from you so I'm posting here instead;
+What kind of debug trace do you want me to give you logs from?
+$ /opt/qemu4/bin/qemu-system-x86_64 -d help
+Log items (comma separated):
+out_asm         show generated host assembly code for each compiled TB
+in_asm          show target assembly code for each compiled TB
+op              show micro ops for each compiled TB
+op_opt          show micro ops after optimization
+op_ind          show micro ops before indirect lowering
+int             show interrupts/exceptions in short format
+exec            show trace before each executed TB (lots of logs)
+cpu             show CPU registers before entering a TB (lots of logs)
+fpu             include FPU registers in the 'cpu' logging
+mmu             log MMU-related activities
+pcall           x86 only: show protected mode far calls/returns/exceptions
+cpu_reset       show CPU state before CPU resets
+unimp           log unimplemented functionality
+guest_errors    log when the guest OS does something invalid (eg accessing a
+non-existent register)
+page            dump pages at beginning of user mode emulation
+nochain         do not chain compiled TBs so that "exec" and "cpu" show
+complete traces
+trace:PATTERN   enable trace events
+
+Use "-d trace:help" to get a list of trace events.
+
+
+Microsoft has updated their driver to 10.0.18362.356 and the sound is now working with the audoidev hda.
+
+Microsoft has fixed their hda driver
+