Opened 16 years ago
Closed 14 years ago
#3799 closed defect (fixed)
Audio output stops working on Linux guest
Reported by: | Matt Kassawara | Owned by: | |
---|---|---|---|
Component: | audio | Version: | VirtualBox 3.0.2 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
I'm running VirtualBox 2.2.0 on a 64-bit Debian 5.0 (Lenny) host with 32-bit Ubuntu 8.10 (Intrepid) and Windows XP guests. I configured AC97 virtual sound devices on both guests using ALSA because PulseAudio can't find the correct output on my particular variant of Intel HDA hardware (Dell Optiplex 755). Sound initially functions great on both guests but audio output stops working on Ubuntu after a random amount of time (typically a couple of days) with no errors. Media applications still seem to recognize and use the sound device, but I can't hear anything. Restarting the Ubuntu guest temporarily fixes the problem. The Windows guest doesn't have this issue.
Attachments (2)
Change History (12)
by , 16 years ago
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Version: | VirtualBox 2.2.0 → VirtualBox 3.0.0 |
---|
comment:3 by , 16 years ago
Summary: | Audio output stops working on Linux guest (Ubuntu 8.10) → Audio output stops working on Linux guest |
---|
comment:4 by , 16 years ago
How can I subscribe for this bug? (I also would like to update VirtualBox affected versions, for example).
p.s.: doesn't wokr on fedora 11 guest with kde 4.3 (latest rc).
comment:5 by , 16 years ago
Version: | VirtualBox 3.0.0 → VirtualBox 3.0.2 |
---|
I assume you are saying that it still happens with 3.0.2... and you were automatically subscribed when you commented.
comment:7 by , 16 years ago
Congratilations, dear VirtualBox! After today's fedora kernel (and something else too) update we can close this bug! Sound works! I can hear now!
comment:9 by , 16 years ago
masoris, just to be sure: you indeed have the sound working for some time and later the sound output stops? Please could you attach a VBox.log file for such a session?
Bug also manifests itself after upgrading to VirtualBox 3.0 with the same host/guest configuration. Upgrading the Ubuntu guest to 9.04 (Jaunty) did not correct the issue.