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 => 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 = 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=5999,addr=0.0.0.0,disable-ticketing
-enable-kvm -device virtio-serial-pci -device
virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev
spicevmc,id=spicechannel0,name=vdagent
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
