QEMU-Devel Archive on lore.kernel.org
 help / color / Atom feed
* [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903
@ 2019-08-06  7:06 Martin Schrodt
  2019-08-26 16:16 ` [Qemu-devel] [Bug 1839060] " Idar Lund
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: Martin Schrodt @ 2019-08-06  7:06 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

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.

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: windows

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Qemu-devel] [Bug 1839060] Re: HDA device non functional in Windows 10 1903
  2019-08-06  7:06 [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903 Martin Schrodt
@ 2019-08-26 16:16 ` " Idar Lund
  2019-08-26 16:22 ` Idar Lund
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Idar Lund @ 2019-08-26 16:16 UTC (permalink / raw)
  To: qemu-devel

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Qemu-devel] [Bug 1839060] Re: HDA device non functional in Windows 10 1903
  2019-08-06  7:06 [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903 Martin Schrodt
  2019-08-26 16:16 ` [Qemu-devel] [Bug 1839060] " Idar Lund
@ 2019-08-26 16:22 ` Idar Lund
  2019-08-26 19:02 ` Idar Lund
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Idar Lund @ 2019-08-26 16:22 UTC (permalink / raw)
  To: qemu-devel

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

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Qemu-devel] [Bug 1839060] Re: HDA device non functional in Windows 10 1903
  2019-08-06  7:06 [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903 Martin Schrodt
  2019-08-26 16:16 ` [Qemu-devel] [Bug 1839060] " Idar Lund
  2019-08-26 16:22 ` Idar Lund
@ 2019-08-26 19:02 ` Idar Lund
  2019-09-02  1:36 ` Geoffrey McRae
  2019-09-12  7:15 ` Idar Lund
  4 siblings, 0 replies; 6+ messages in thread
From: Idar Lund @ 2019-08-26 19:02 UTC (permalink / raw)
  To: qemu-devel

Created Windows feedback as instructed by Andre:
https://aka.ms/AA5wlk7
Please upvote this to get attention by Microsoft.

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Qemu-devel] [Bug 1839060] Re: HDA device non functional in Windows 10 1903
  2019-08-06  7:06 [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903 Martin Schrodt
                   ` (2 preceding siblings ...)
  2019-08-26 19:02 ` Idar Lund
@ 2019-09-02  1:36 ` Geoffrey McRae
  2019-09-12  7:15 ` Idar Lund
  4 siblings, 0 replies; 6+ messages in thread
From: Geoffrey McRae @ 2019-09-02  1:36 UTC (permalink / raw)
  To: qemu-devel

Hi,

I am trying to dig into this issue, can you please provide the verb
debug trace from the working version of windows.

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Qemu-devel] [Bug 1839060] Re: HDA device non functional in Windows 10 1903
  2019-08-06  7:06 [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903 Martin Schrodt
                   ` (3 preceding siblings ...)
  2019-09-02  1:36 ` Geoffrey McRae
@ 2019-09-12  7:15 ` Idar Lund
  4 siblings, 0 replies; 6+ messages in thread
From: Idar Lund @ 2019-09-12  7:15 UTC (permalink / raw)
  To: qemu-devel

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.

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, back to index

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-06  7:06 [Qemu-devel] [Bug 1839060] [NEW] HDA device non functional in Windows 10 1903 Martin Schrodt
2019-08-26 16:16 ` [Qemu-devel] [Bug 1839060] " Idar Lund
2019-08-26 16:22 ` Idar Lund
2019-08-26 19:02 ` Idar Lund
2019-09-02  1:36 ` Geoffrey McRae
2019-09-12  7:15 ` Idar Lund

QEMU-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git
	git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \
		qemu-devel@nongnu.org qemu-devel@archiver.kernel.org
	public-inbox-index qemu-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox