Page 1 of 1

Can't start Vbox instances after upgrading to 5.0.12r104815

Posted: 3. Jan 2016, 17:52
by Weikai
My VBox instances were working fine under Ubuntu 14.04 until I upgraded VB to 5.0.12. It complained at the sound driver and refused to start until I disabled the audio in the VB instances. I have never experienced the problem on the previous VB upgrades. I also saw an error message saying something similar to "ln: setup is not a directory" during upgrade. Has anybody experienced the same problem and found a solution without disabling the audio?

Code: Select all

vbox@cloud:~$ VBoxHeadless -s Varnish
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.

ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4727:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4727:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4727:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:4248:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4727:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM default
Segmentation fault (core dumped)
vbox@cloud:~$ VBoxManage --version
5.0.12r104815

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 6. Jan 2016, 15:09
by frank
Which version of VirtualBox did you run before?

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 10. Jan 2016, 21:36
by Weikai
I'm running an upgrade on the machine on every VB upgrade. I have upgraded to 5.0.2, 5.0.4, 5.0.8, and 5.0.10. The last previous version was 5.0.10.

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 14. Jan 2016, 17:31
by kketchmark
I to was having issues with this version. Worked for 2 days, could not get guest to run. Removed 5.0.12, and installed 5.0.10 and the guest systems run again. Something with version 5.0.12.

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 15. Jan 2016, 20:15
by ecfs
Hello,

can confirm this bug(?) in 5.0.12 - running it on an ubuntu 14.04. LTS Host with an WinXP Client - couldn't start the client with "VBoxManage startvm clientname --type headless" in headless mode. Can confirm the solution too - downgraded to 5.0.10 and it works ... thanks for the hint.

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 16. Jan 2016, 01:42
by Torchwood
I'm running Virtualbox 5.0.12r104815 ok on Mint 17.3 Cinnamon 64-bit (based on Ubuntu 14.04). This is also a LTS, long term support release, good until 2019. I'm using Linux kernel 3.19.0-32-generic at this time.

Windows XP guest and various Linux guests perform great, with the 5.0.12 guest additions installed.

I have noticed that the Ubuntu 14.04.3 point release also uses the 3.19 kernel.

So I would think it should work!

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 21. Jan 2016, 18:57
by Weikai
It works on your Mint because you have GUI with sound driver installed. In my case, it's just a headless Ubuntu 14.04 server without any sound driver installed. The thing bothers me is that why system without sound driver worked fine on previous VB version but not on 5.0.12r104815.
Torchwood wrote:I'm running Virtualbox 5.0.12r104815 ok on Mint 17.3 Cinnamon 64-bit (based on Ubuntu 14.04). This is also a LTS, long term support release, good until 2019. I'm using Linux kernel 3.19.0-32-generic at this time.

Windows XP guest and various Linux guests perform great, with the 5.0.12 guest additions installed.

I have noticed that the Ubuntu 14.04.3 point release also uses the 3.19 kernel.

So I would think it should work!

Re: Can't start Vbox instances after upgrading to 5.0.12r104

Posted: 30. Jan 2016, 20:07
by Weikai
Thank you all.

I have upgraded to 5.0.14 today and found this problem was fixed.

Re: Can't start Vbox instances after upgrading to 5.0.12r104815

Posted: 17. Aug 2017, 01:49
by Hamza M
Apologies for the thread resurrection here but I'm getting the same error running version 5.1.26r117224 on Ubuntu Server 16.04 LTS.

Has this bug been re-introduced or am I looking at a different problem?