From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VICCg-0000Kg-4V for qemu-devel@nongnu.org; Sat, 07 Sep 2013 02:41:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VICCX-0005t1-3F for qemu-devel@nongnu.org; Sat, 07 Sep 2013 02:41:06 -0400 Received: from indium.canonical.com ([91.189.90.7]:58116) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VICCW-0005rz-ID for qemu-devel@nongnu.org; Sat, 07 Sep 2013 02:40:56 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1VICCV-0000am-8u for ; Sat, 07 Sep 2013 06:40:55 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 41B6D2E8043 for ; Sat, 7 Sep 2013 06:40:55 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Sat, 07 Sep 2013 06:19:29 -0000 From: will Sender: bounces@canonical.com References: <20130907061929.18417.73048.malonedeb@wampee.canonical.com> Message-Id: <20130907061929.18417.73048.malonedeb@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1222034] [NEW] QEMU + SPICE + AUDIO = FAILURE Reply-To: Bug 1222034 <1222034@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: 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. ** Affects: qemu Importance: Undecided Status: New ** Description changed: 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 M5A99X EVO R2.0 = - = Example command line: = - qemu-system-x86_64 -m 1024 -cdrom - /common/stor8/torrents/Sabayon_Linux_DAILY_x86_Xfce.iso -soundhw hda - -vga qxl -spice port=3D5999,addr=3D0.0.0.0,disable-ticketing -enable-kvm - = + 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 = 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. = 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 t= he race message that happens in the guest but I am assuming at this point t= hat my configuration is not exotic and it should be very easy to see the is= sue. + 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. ** Description changed: 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 M5A99X EVO 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 = 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. + for a very long period of time and play no audio through spice. It + doesn't seem to matter what guest 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) = 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. ** Description changed: 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 M5A99X EVO 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 = 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 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) + 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) = 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. ** Description changed: 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 M5A99X EVO R2.0 + 64 bit linux , AMD SVM, IOMMUv1 ASUS M5A99X EVO 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 = 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) = 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. ** Description changed: 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 M5A99X EVO R2.0 + 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 = 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) = 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. ** Description changed: 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 + -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) = 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. ** Description changed: 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) + -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. -- = 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: New 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