From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41440) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f8pcB-0003sT-PJ for qemu-devel@nongnu.org; Wed, 18 Apr 2018 12:07:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f8pc8-0001Tt-0a for qemu-devel@nongnu.org; Wed, 18 Apr 2018 12:07:23 -0400 Received: from indium.canonical.com ([91.189.90.7]:32806) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f8pc7-0001TW-Qi for qemu-devel@nongnu.org; Wed, 18 Apr 2018 12:07:19 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1f8pc7-0002Y0-2d for ; Wed, 18 Apr 2018 16:07:19 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 0EB782E80C8 for ; Wed, 18 Apr 2018 16:07:19 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 18 Apr 2018 15:46:16 -0000 From: Thomas Huth <1222034@bugs.launchpad.net> Reply-To: Bug 1222034 <1222034@bugs.launchpad.net> Sender: bounces@canonical.com References: <20130907061929.18417.73048.malonedeb@wampee.canonical.com> Message-Id: <152406637689.12425.4472208097462172857.malone@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1222034] Re: QEMU + SPICE + AUDIO = FAILURE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU and a recent guest kernel? Or could we close this ticket nowadays? ** Changed in: qemu Status: New =3D> Incomplete -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1222034 Title: QEMU + SPICE + AUDIO =3D FAILURE Status in QEMU: Incomplete Bug description: Hello it's my first time doing this, since the major round of timer/block changes in August I have not been able to have audio working in any guest with the spice protocol. 64 bit linux , AMD SVM, IOMMUv1 ASUS M5A99FX PRO R2.0 Example command line: qemu-system-x86_64 -m 1024 -cdrom Sabayon_Linux_DAILY_x86_Xfce.iso -soundhw hda -vga qxl -spice port=3D5999,addr=3D0.0.0.0,disable-ticketing -enable-kvm -device virtio-serial-pci -device virtserialport,chardev=3Dspicechannel0,name=3Dcom.redhat.spice.0 -chardev spicevmc,id=3Dspicechannel0,name=3Dvdagent Any time the guest tries to access the emulated hardware it will hang for a very long period of time and play no audio through spice. It doesn't seem to matter what guest (x86_64 or x86) I run (the above is just one example) and it also doesn't matter what sound hardware I choose to emulate or which command line method I use to specify it (ie -soundhw doesn't work and neither does -device) or whether a vdagent service has been configured correctly inside the guest or not. This issue does not happen with the 1.6.0 release. If you are unable to replicate this I will go to the trouble of getting the race message that happens in the guest but I am assuming at this point that my configuration is not exotic and it should be very easy to see the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1222034/+subscriptions