Opened 9 years ago
Last modified 5 years ago
#15839 reopened defect
Attempting to output audio causes processes in guest to hang
| Reported by: | Sam Morris | Owned by: | |
|---|---|---|---|
| Component: | audio | Version: | VirtualBox 5.1.4 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Since upgrading to 5.1.4 audio output in the guest has become unreliable. A process that attempts to play sound freezes. Sometimes, if I kill off all processes trying to play sounds, I can run aplay or speaker-test a couple of times, but a few moments later they still stop working again.
Guest is running 64-bit Linux 4.6.0, host is 64-bit Windows 10 Home. The sound card is ICH AC97.
Attachments (2)
Change History (17)
by , 9 years ago
comment:1 by , 9 years ago
aplay hangs in the call to poll on 842. After a while I interrupt it, otherwise it remains there forever.
comment:2 by , 9 years ago
I have similar issue, and even no sound is comming now after this upgrade. I have experienced the same issue in windows 10 and windows 7 hosts.
comment:3 by , 9 years ago
I've been trying to debug this further and I think the problem is within pulseaudio, so I reported https://bugs.freedesktop.org/show_bug.cgi?id=97627 to see what the pulseaudio developers think.
comment:4 by , 9 years ago
Still seeing this with 5.1.8. And it's not pulseaudio, as far as we can tell; rather it's the virtual hardware acting up.
comment:7 by , 7 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:8 by , 6 years ago
Sorry what is this a duplciate of? I am still seeing it with VirtualBox 6.0.8...
follow-up: 11 comment:9 by , 6 years ago
- Start from the Bugtracker main page.
- Click on the "Advanced Search".
- In the "Filters" section, remove all the filters, and add a new one with "Component=audio".
- Optionally in the "Group results by", select "Version, descending".
Last count was 312 open bugs. One of them is your duplicate. Actually most of them are duplicates, people tend to open a new ticket instead of subscribing to one, their ticket is more important that the other users' tickets...
comment:10 by , 5 years ago
I'm having the same problem on vbox 6.1.10. What is the duplicate bug number?
comment:11 by , 5 years ago
Replying to socratis:
Last count was 312 open bugs. One of them is your duplicate. Actually most of them are duplicates, people tend to open a new ticket instead of subscribing to one, their ticket is more important that the other users' tickets...
What an unhelpful comment!
comment:13 by , 5 years ago
| Resolution: | duplicate |
|---|---|
| Status: | closed → reopened |
comment:14 by , 5 years ago
Here's an interesting behaviour that I hadn't noticed before (it may or may not be new as of some release since 5.1.4).
If I run mpv some_file.mp3, mpv hangs, as it has done since I filed this bug.
However, if I leave it running, and then run pasuspender -- aplay -D sysdefault /usr/share/sounds/alsa/Front_Left.wav, aplay is able to play the WAV file. Once pasuspender exits, mpv starts playing its file. From then on sound plays normally.
I've not tested this extensively, so I don't know if that fixes things permanently until the VM reboots or not.
comment:15 by , 5 years ago
I confirm that yrro's comment does help restore audio functionality with Virtualbox 6.1.12 and openSUSE tumbleweed as guest on MacOS host.
strace aplay -D plughw:CARD=I82801AAICH,DEV=0 /usr/share/sounds/alsa/*.wav