I had sound working just fine with a Win 2K guest and a Kubuntu 8.04 host. But after the most recent reboot, it quit. Specifically, I got the message Some audio devices [PCM_out] could not be opened. The message also instructed Check the logfile for error messages of the audio subsystem. But what logfile does this refer to, and where can I find it?
I'm using PulseAudio and ACH 97. Using other host drivers had a different effect: substituting the null driver.
This error is particularly mysterious because I wasn't aware of changing anything before the most recent reboot. I might have done a system update (the usual one), though I'm not sure, but that shouldn't account for the problem. Just before the reboot I lost the keyboard (even CapsLock didn't work) but I don't see how that would be relevant.
Sound stopped working in Win 2K guest
I've had that when I've been using an audio application on the host
and then tried to use another audio application on the guest (Ubuntu
8.04 host, W2K guest). Even after the original host application had
ended I still couldn't use sound from the guest.
I don't recall if it always happened, or if there are just some
applications that don't work well together. In the end I gave up
trying to share the audio resources and NULL'd out the sound driver
on the guest.
I also tried installing a USB based, external, audio device that was
mapped through to the guest - but that didn't work too well either:
the sound was too choppy to be recognisable.
and then tried to use another audio application on the guest (Ubuntu
8.04 host, W2K guest). Even after the original host application had
ended I still couldn't use sound from the guest.
I don't recall if it always happened, or if there are just some
applications that don't work well together. In the end I gave up
trying to share the audio resources and NULL'd out the sound driver
on the guest.
I also tried installing a USB based, external, audio device that was
mapped through to the guest - but that didn't work too well either:
the sound was too choppy to be recognisable.
-
Sasquatch
- Volunteer
- Posts: 17798
- Joined: 17. Mar 2008, 13:41
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP, Windows 7, Linux
- Location: /dev/random
What if you use ALSA for audio instead of PulseAudio? PulseAudio is quite new, so there are sure to be bugs here and there, and it seems that this is one of them. See if switching to ALSA fixes it. If it does, it's probably a problem with PulseAudio and not VB.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
-
Paul Abrahams
- Posts: 141
- Joined: 2. Jun 2008, 17:49
ALSA sound doesn't work for me.
Alsa sound doesn't work for me in Vbox -- I get the message that the null driver is being used instead. OSS doesn't work either. But I solved my Vbox sound problems, along with some other sound problems, by executing the command alsactl store, which I learned about from another forum.