qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Idar Lund <1839060@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1839060] Re: HDA device non functional in Windows 10 1903
Date: Mon, 26 Aug 2019 16:22:20 -0000	[thread overview]
Message-ID: <156683654037.2796.15158145615868241306.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 156507518934.25260.15982229597694445610.malonedeb@soybean.canonical.com

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


  parent reply	other threads:[~2019-08-26 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2019-08-26 19:02 ` Idar Lund
2019-09-02  1:36 ` Geoffrey McRae
2019-09-12  7:15 ` Idar Lund
2020-01-05 10:07 ` Idar Lund
2020-01-05 10:07 ` Idar Lund

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=156683654037.2796.15158145615868241306.malone@chaenomeles.canonical.com \
    --to=1839060@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).