No sound available in host system after installation.

[t.gu]

After installing "VirtualBox_1.3.8_Ubuntu_edgy_i386" no sound is available any longer under Kubuntu 7.04 and earlier.

For additional information please I refer to the following links (German)

1. logs: ​http://www.ubuntuusers.de/paste/9303/

2. another description: ​http://forum.ubuntuusers.de/topic/85815/

Kind regards

Torsten

[Frank Mehnert]

Torsten, please attach your ~/.VirtualBox/Machines/vm_name/VBox.log here.

[t.gu]

VBox.log

[t.gu]

Three additional logs are available. Please let me know in case of interest for you.

[Frank Mehnert]

The virtual soundcard is not activated for this virtual machine. Please check your VM settings.

[t.gu]

Frank, sorry for the misunderstanding, but the vm is not the problem: I do not have any sound on my linux system any longer after installation After installing virtualbox and rebooting my hardware my ubuntu linux does not give any audio output until now.

[Frank Mehnert]

Oh, I see. This very is strange. Do I understand you correct that you reboot your host, start Ubuntu and have no sound card, even if VirtualBox was not yet started?

Does it change anything if you remove the vboxdrv module (/etc/init.d/vboxdrv stop)? You can also try to prevent this module from loading during runtime (add exit 0 at the start of this script) and reboot.

[t.gu]

No, unfortunately not: I realized the problem after my first reboot after the installation. A reboot does not help. In the meantime

-I removed virtualbox

• upgraded to feisty

• made 'dpkg-reconfigure alsa-base'

• re-installed the linux headers

All with no success. The strange thing is that my system detects my soundcard but does not give any output.

You can find some more information of my system feedback here:

​http://www.ubuntuusers.de/paste/9303/

I supposed that virtualbox made modifications in some config files but I do not have an idea what they might be.

[Frank Mehnert]

VirtualBox does not change any sound-related files on installation. Does the mixer work? Try alsamixer.

[t.gu]

Frank, alsamixer works fine.

[androvsky]

I'm having the same problem. Kubuntu Feisty host, installed virtualbox and sound no longer works. Alsamixer works, but kmix reports no audio card. Mplayer also cannot use the sound card. All sound-related modules are loaded. My computer has an nforce4 motherboard.

Oddly, I managed to get sound in mplayer if I run mplayer as root both with OSS and ALSA output. Looks like virtualbox changed the permissions on something...

[Frank Mehnert]

Did you try with VirtualBox 1.4.0?

[t.gu]

androvsky,

I found support in the German ​http://www.ubuntuusers.de/ forum after the virtualbox-support denied to give me any further advice...

You can find the soultion (in German) here <​http://forum.ubuntuusers.de/topic/85815/?highlight=virtualbox> and here <​http://forum.ubuntuusers.de/topic/100388/?highlight=virtualbox>.

Please check your group dependencies: it seems that virtualbox is changing /etc/groups and deleting your user from all the groups beside vbox. Others told that virtualbox also deleted some groups but I was not able to verify that.

Good luck!

[Frank Mehnert]

The second reference clearly states that the user removed himself from all groups. And the first reference isn't much clearer. The only action of the VirtualBox packages regarding to changing groups/users is to create a group vboxusers

groupadd vboxusers

This doesn't change any permission of any user in the ssytem.

[t.gu]

Frank,

thank you for your answer. But as described in one of those threads my user was missing in all further groups. After correcting that issue I was able to use the application with sound for the system again.

Torsten.

[Frank Mehnert]

The question is just why. Did you any call usermod -G without the -a option or something like that? We cannot fix anything if we don't know the reason.

[t.gu]

I just installed it thru the package you prepared on your homepage just accepting the recommendations you gave during the installation process. Perhaps Androvsky can provide additional input. Sorry to not be able to submit more information.

[Scott]

I also have this same Issue! My laptop is a Asus a6km, After installing Vbox I lost sound on my host system, Ubuntu Gutsy.

Skype phone callers cant hear me.

I have uninstalled and re installed, after I tested the different audio options on Vbox. no luck,

What makes me more angry is the fact that after un install, still no change.

Im happy to help share logs or anything u need, just let me know. I dont want to have to re load my system from scratch after using Vbox, the software looks very good if i get can it working.

Scott, NZ.

[Scott]

Replying to t.gu:

I also have this same Issue! My laptop is a Asus a6km, After installing Vbox I lost sound on my host system, Ubuntu Gutsy.

Skype phone callers cant hear me.

I have uninstalled and re installed, after I tested the different audio options on Vbox. no luck,

What makes me more angry is the fact that after un install, still no change.

Im happy to help share logs or anything u need, just let me know. I dont want to have to re load my system from scratch after using Vbox, the software looks very good if i get can it working.

Scott, NZ.

After installing "VirtualBox_1.3.8_Ubuntu_edgy_i386" no sound is available any longer under Kubuntu 7.04 and earlier.

For additional information please I refer to the following links (German)

1. logs: ​http://www.ubuntuusers.de/paste/9303/

2. another description: ​http://forum.ubuntuusers.de/topic/85815/

Kind regards

Torsten

[Frank Mehnert]

Sorry for this question, but did you reboot your host computer after you de-installed VirtualBox with dpkg --purge virtualbox?

[Frank Mehnert]

And what is the output of

groups

when you are logged in? How did you add the group vboxusers to the current user, I mean which command did you use?

[Scott]

HI, Thanks for your Prompt reply and support! In Ubuntu Gutsy I clicked - System, Administration, Users and Groups, Manage Groups, Vboxusers, Properties, and put a tick in my username. To add myself to the Vbox group. scotthammy@scotthammy-laptop:~$ groups scotthammy adm dialout cdrom floppy audio dip video plugdev scanner netdev lpadmin powerdev admin vboxusers Yours Scott, NZ. www.virtualbox.org/ticket/277

[Scott]

Hi, After uninstall with your --purge command, still no luck, I guess if could reinstall the sound card in Gutsy it would reset the sound card settings? do u know the command?

[Frank Mehnert]

Ui Scott, I still have no clue what was going wrong with your installation. The groups look correct. Reinstalling the sound card is not that easy before I know what is missing. More to test:

Does

lsmod|grep snd

show anything? And what is the content of /dev/snd

/bin/ls -l /dev/snd

? And another question: Which version of VirtualBox did you install on your Gutsy box: virtualbox from our website (I assume virtualbox_1.5.2-25433_Ubuntu_gutsy_i386.deb) or virtualbox-ose from the official Ubuntu packages?

[Karel Krema]

Hello,

I seem to be in the same situation as Scott (his last reply is quite old, could he give up and reinstall? :-)

Well, my situation:

I am running kubuntu 7.10 GG on laptop HP 6715b laptop. After installing virtualbox (ose) using apt (synaptic), soundcard is not working any more...

My user (elk) is a member of groups "elk adm dialout voice cdrom floppy audio dip www-data video plugdev scanner lpadmin admin netdev powerdev vboxusers"... Root is only member of "root".

"lsmod | grep snd" returns nothing, so does "/bin/ls -s /dev/snd" (/dev/snd does not exist).

I have tried to purge and reinstall again too.

alsamixer says "alsamixer: function snd_ctl_open failed for default: No such device"

Another strange thing - Usualy I am connected using UTP cable, but sometimes I use ndiswrapper to connect via WiFi.

Since I installed VirtualBox, typing modprobe ndiswrapper returns FATAL: Module ndiswrapper not found

Could this be because of virtualbox too?

Can you help me somehow? I do not want to reinstall since it would not help me - I want to use VirtualBox :-)

Thanx, elk

[Karel Krema]

Hello,

I seem to be in the same situation as Scott (his last reply is quite old, could he give up and reinstall? :-)

Well, my situation:

I am running kubuntu 7.10 GG on laptop HP 6715b laptop. After installing virtualbox (ose) using apt (synaptic), soundcard is not working any more...

My user (elk) is a member of groups "elk adm dialout voice cdrom floppy audio dip www-data video plugdev scanner lpadmin admin netdev powerdev vboxusers"... Root is only member of "root".

"lsmod | grep snd" returns nothing, so does "/bin/ls -s /dev/snd" (/dev/snd does not exist).

I have tried to purge and reinstall again too.

alsamixer says "alsamixer: function snd_ctl_open failed for default: No such device"

Another strange thing - Usualy I am connected using UTP cable, but sometimes I use ndiswrapper to connect via WiFi.

Since I installed VirtualBox, typing modprobe ndiswrapper returns FATAL: Module ndiswrapper not found

Could this be because of virtualbox too?

Can you help me somehow? I do not want to reinstall since it would not help me - I want to use VirtualBox :-)

Thanx, elk

[Frank Mehnert]

Thanks elk for the additional information. This is a very strange problem. Which kind of soundcard does your host have? And I guess you even don't get sound back after you rebooted your host, right?

After you boot your host, there shouldn't be any vboxdrv module loaded, is that right?

[Frank Mehnert]

elk, please could you attach the file /var/log/udev of your host to this report please?

[Karel Krema]

My /var/log/udev file as you requested... elk

[Karel Krema]

I am not sure which sound card it is. It is probably integrated - There is only written on www.hp.cz, that the sound system is "High Definition Audio specification". (AMD X2 64bit TL-60 CPU, M690T Chipset) Should I find out more?

Concening vboxdrv module - it is loaded and VirtualBox works just fine.

I also tried to boot with Kubuntu live CD (where the sound card works properly) and look for differences between my curent host`s configuration and "live configuration" - but there was too many of them.

Could anything from well-working live configuration be usefull for you?

elk

[Frank Mehnert]

1. Please could you edit /etc/init.d/vboxdrv and add exit 0 to the very beginning of that file and then reboot. Does sound work now?
2. Please attach the output of dmesg.
3. Please attach the output of lsmod.

[Karel Krema]

I needed sound urgently, so I had to reinstall...

I have a lot of work these days, but on weekend, I will backup my system, install VirtualBox again and post all the files/ouputs you mentioned...

Or I can check changes in files/directories before/after install, if you tell me which ones are important.

elk

[Rob Versluis]

Hi,

I had the same problem with Ubuntu 7.10. After uninstalling the VirtualBox package I also uninstalled the server kernel and replaced it with the generic one. The server kernel modules does not contain support for all sound cards, in my case the "snd-hda-intel".

So I think it is not a VirtualBox issue, but an Ubuntu one.

Kind Regards, Rob.

[Franco Ropelato]

Hi, may I join?

I have an Ubuntu 7.10 machine (installed from a 7.04 previous one) on which I installed VirtualBox 1.5.2. I created an XP guest. If the guest's sound is set to OSS:

• the guest has sound,
• but the regular Ubuntu user at console doesn't
• and the guest sound is also audible in the main speaker of the Ubuntu machine.

If the guest's sound is set to ALSA:

• the guest has sound,
• and also the regular Ubuntu user at console has sound,
• but the guest sound mixed with the console sound is audible in the main speaker of the Ubuntu machine.

So my problem is: how to stop the guest sound from flowing into the main machine speakers?

Ciao, Franco

[Frank Mehnert]

Replying to francorop:

I have an Ubuntu 7.10 machine (installed from a 7.04 previous one) on which I installed VirtualBox 1.5.2. I created an XP guest. If the guest's sound is set to OSS:

• the guest has sound,
• but the regular Ubuntu user at console doesn't
• and the guest sound is also audible in the main speaker of the Ubuntu machine.

This is exactly as it is supposed to be: OSS only allows one client to connect to /dev/dsp. So if VirtualBox uses this backend, no other client on the host will be able to use the sound device. Known limitation of OSS.

If the guest's sound is set to ALSA:

• the guest has sound,
• and also the regular Ubuntu user at console has sound,
• but the guest sound mixed with the console sound is audible in the main speaker of the Ubuntu machine.

So my problem is: how to stop the guest sound from flowing into the main machine speakers?

I don't understand the problem here: Don't you want to mix the guest's sound output with the host's sound output? Or use guest and host different channels?

[Franco Ropelato]

So, ok for the OSS behavior.
For the ALSA: no, I don't want that the sound of the guest (or those from the guests) are sent to the main system speaker, it's a kind of an eavesdropping... interesting at times, but boring! :-)
How to set each guest on a different and independent channel, so neither the console, nor guests can hear each other?

Thanks.

[Frank Mehnert]

I don't know exactly. The ALSA sound device VBox is sending its output is "default". So you could try to play with the output device (consult an ALSA manual) and change the device name with export VBOX_ALSA_DAC_DEV=<device> before starting VirtualBox from a text console.

[Richard]

I have intermittent sound issues as well on one of my boxes. won't work for either host or guest for a bit then start working again.

[Richard]

sorry ubuntu gutsy x86 host and xp pro sp2 guest

[Frank Mehnert]

Please try a newer release of VBox and reopen if still reproducible.

[zerothis]

well, I just managed to accidentally reproduce this with virtualbox-2.0_2.0.2-36488_Ubuntu_hardy_i386.deb. I tried every 'fix' mentioned here except for a complete reinstall which is my next step after this post. removing virtualbox-2.0 had no effect. If anybody is still interested, I backed up my machine logs before doing a complete purge of virtualbox-2.0. I should note that my speakers popped and clicked a few times while I was purging the package (but not when I only removed it). I purged a few games to see if it was the purge itself that caused the noises. The speakers remained totally silent before and after. They only made noise when I purged virtualbox.

[zerothis]

Rather than reinstall, I decided to upgrade to Ubuntu 8.10rc2. This fixed my sound. I will still keep the logs for a few more months in case they could be useful to anybody else that encounters this problem.

[mvyver]

OK I have run into this problem too - it took me a while to work out that VB may well be (is definitely?) the culprit.

uname -a

Linux localhost 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 i686 i686 i386 GNU/Linux

cat /etc/SuSE-release

openSUSE 11.1 (i586) VERSION = 11.1

# rpm -qa |grep -i virtual VirtualBox-2.2.4_47978_openSUSE111-1

After running a system update (zypper dup) I was able to get my sound working. This update included a kernel upgrade, so when trying to start VB it indicated some error (can't recall exact text) and suggested running /etc/init.d/vboxdrv setup as root. I do so and VB starts, I then mount the additions ISO and install the guest additions - I did not really notice anything being installed. However, the /host/ system's alsa sound is no longer working!

When I run service alsasound restart the VB guest crashes. Perhaps the following information helps:

cat /etc/asound.state &>/tmp/asound-state.log

Finally I'd like to provide an strace log of service alsasound restart crashing the VB. However I'm struggling to get the VB to start from the command line using strace.

I've tried: # strace -f -u mv sh -c "/usr/bin/VirtualBox &>/tmp/VB-strace.log"

sudo strace -f /usr/bin/VirtualBox &>/tmp/VB-strace.log strace -f /usr/bin/VirtualBox &>/tmp/VB-strace.log

All give some form of error and do not start VB. Any suggestions?

[mvyver]

opensuse 11.1 /etc/asound.state

[mvyver]

In the meantime ?I was able to get some starace log as follows:

> VirtualBox
> sudo strace -o /tmp/VB-strace.log -p 31327

[mvyver]

openSUE 11.1 strace log of guest crash on service alsasound restart

[mvyver]

starce log of guest crash on alsasound restart VB-3beta2

[Frank Mehnert]

mvyver, when you do service alsasound restart that service script will do kill -9 on every application which has an open sound device. This is not a bug of VirtualBox. If you don't have sound when VirtualBox is active then your sound card does not support multiple concurrent audio channels on your host. Use PulseAudio in that case.

[mvyver]

My apologies - I'was quite exasperated trying to work out what caiused my sound to stop working.

Anyway, service alsasound restart is only done to try and recover host sound after running /etc/init.d/vboxdrv setup so this still leaves the bug open and confirmed by several people? While crashing the guest with service alsasound restart is not a VB bug. But you might like to flag this in some list of known issues/gotcha's - pulseaudio is not an option just yet, if ever (?) e.g. my understanding is KDE won't be heading down that path and most audio-problem threads end up advising to uninstall PulseAudio.

To be clear, and return to topic, like others posting above, after installing VB and running /etc/init.d/vboxdrv setup, I don't have sound on the host system period - regardless of whether or not a guest OS is running. I test the speakers using:

# speaker-test -c2 -l5 -twav

and

# speaker-test -Dplug:front -c2 -l5 -twav

Let me know which information mentioned in the guide below you'd find helpful: ​http://en.opensuse.org/AudioTroubleshooting

In the mean time I provide some of the info requested in some of the comments above (/var/log/udev is not present on openSUSE 11.1):

# lsmod|grep snd
snd_pcm_oss            42548  0
snd_mixer_oss          14864  1 snd_pcm_oss
snd_seq                52556  0
snd_seq_device          7412  1 snd_seq
snd_intel8x0           31684  2
snd_ac97_codec        101464  1 snd_intel8x0
ac97_bus                1752  1 snd_ac97_codec
snd_pcm                77496  3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              19728  2 snd_seq,snd_pcm
snd                    63376  12 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc          8320  2 snd_intel8x0,snd_pcm
soundcore               6660  1 snd

# /bin/ls -l /dev/snd
total 0
crw-rw----+ 1 root audio 116,  9 Jun 25 16:40 controlC0
crw-rw----+ 1 root audio 116,  8 Jun 25 16:40 pcmC0D0c
crw-rw----+ 1 root audio 116,  7 Jun 25 20:24 pcmC0D0p
crw-rw----+ 1 root audio 116,  6 Jun 25 16:40 pcmC0D1c
crw-rw----+ 1 root audio 116,  5 Jun 25 16:40 pcmC0D2c
crw-rw----+ 1 root audio 116,  4 Jun 25 16:40 pcmC0D3c
crw-rw----+ 1 root audio 116,  3 Jun 25 18:46 pcmC0D4p
crw-rw----+ 1 root audio 116, 10 Jun 25 16:40 seq
crw-rw----+ 1 root audio 116,  2 Jun 25 16:40 timer

> groups
users disk dialout audio cdrom video trusted vboxusers bacula pulse-rt

HTH?

[Sander van Leeuwen]

Is this still valid? Reopen if it is please.