VBox 5.0.12 on Debian host + Windows Vm = Segmentation Fault

[vbox_user23351]

This is my first post, and decided to create a new topic after researching and not finding this problem documented.

So I have a Debian Server (no GUI) and a few Windows and Linux VM's. I was on version 5.0.10 and all of my VMs were working with no issues. After upgrading to 5.0.12, I am no longer able to start my Windows VM's. I have an Ubuntu VM that I run in headless mode, and that one does not seem to be affected and works great. I have a Windows 7 VM and a Windows Server 2012 VM which I use for testing applications, and everytime I attempt to start them ("vboxheadless -s Server2012") I get a "Segmentation Fault" error message. I thought that maybe my VM/VDI were shot, so I blew them away and attempted to start over and create a new VM and install Windows again, but I got the same Segmentation Fault error message. Since I am only getting this error message on the Windows VM's and not other OS's like Ubuntu, I believe that it is a problem with 5.0.12 and Windows guest machines.

I wanted to post this to see if anybody else was having similar issues, and also to document the problem with Oracle, and have someone take a look at my scenario.

Thanks again for all of your help, and I hope that this gets resolved quickly.

I am in the IT field, and would appreciate any suggestions to try out. Thanks again!

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[vbox_user23351]

Thank you very much for your help. I have attached the Log file.

[Perryg]

I don't see much that would cause the segfault as far as the guest is concerned except that you assign all of the true cores to the guest that the host has. Try setting it to 2 or no more than 3 and see if it helps. If not take a look at the host syslog and dmesg to see if it points to the actual cause.

PS you did reboot this host to see if that helped as well, right?

[JLD]

I have the same issue on a Debian Wheezy host.

When starting a guest, I get a segfault like this one:

Code: Select all

[ 1532.287065] EMT-1[8084]: segfault at 18 ip 00007f9cf426950b sp 00007f9cfc9c6bf0 error 4 in VBoxDD.so[7f9cf41ee000+27a000]

[Perryg]

I have the same issue on a Debian Wheezy host.

When starting a guest, I get a segfault like this one:

Code: Select all

[ 1532.287065] EMT-1[8084]: segfault at 18 ip 00007f9cf426950b sp 00007f9cfc9c6bf0 error 4 in VBoxDD.so[7f9cf41ee000+27a000]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[JLD]

I've updated the guest additions and restarted the host. I have now a few lines before the segfault:

Code: Select all

[  543.463318] vboxdrv: ffffffffa056b020 VMMR0.r0
[  543.531277] vboxdrv: ffffffffa0661020 VBoxDDR0.r0
[  543.532265] vboxdrv: ffffffffa010c020 VBoxDD2R0.r0
[  543.608592] EMT-1[7515]: segfault at 18 ip 00007f6ee9dc450b sp 00007f6eee4d6bf0 error 4 in VBoxDD.so[7f6ee9d49000+27a000]

The log looks pretty much the same as the one posted above.

Notes:
* When I've upgraded from 5.0.10 to 5.0.12 (with aptitude), I had this message at the end:

Code: Select all

ln: target `setup' is not a directory

* I run VirtualBox on a server in headless mode.
* I've removed the network interface, but same problem

[Perryg]

I've updated the guest additions and restarted the host. I have now a few lines before the segfault:

Given that the gust additions are actually installed in the guest and never on the host, how exactly did you do this since the guest does not boot? You didn't install them on the host did you?

[JLD]

Sorry, that's not clear... I've updated the GA at the host level (with "VBoxManage extpack install"), not on the guest.

Anyway, it seems the segfault happens quickly, I don't think it's related to the guest additions.

Edit: I cannot boot a guest without guest additions.

[Perryg]

Code: Select all

 I've updated the GA at the host level (with "VBoxManage extpack install")

That makes more sense. The Extension pack and the guest additions are two separate packages and the ExtPack is installed on the host. The GAs are installed on the guest.

If this was working on a previous version I would consider raising a ticket at bugtracker and see what the DEVs have to say since this is actually a host side issue and probably a regression.

[JLD]

I've opened a ticket on the bugtracker: https://www.virtualbox.org/ticket/14960

Thank you for your help Perryg.

[Crasherz]

I had the same issue as soon as I installed v5.0.12. Tried several fixes and a reinstall to no avail....I removed 5.0.12 and reinstalled v5.0.10 and all are working again. I suspect an issue in the the .12 update.

[vbox_user23351]

Thanks to everyone for their assistance in this matter.

I have made some progress, and after some troubleshooting (reducing cores, changing VRDE port and address, etc...) I was able to figure out that my audio settings are what is causing the segfault error message. Here are my audio settings below:

Code: Select all

--audio oss --audiocontroller hda --audiocodec stac9221

Using these settings, Windows VM appear to be broken, but after disabling the audio, by using "--audio none", the Windows VM does start up.

I am OK with changing these settings, but does anybody know of a different way to get audio on a Windows box without using the settings above?

Thanks again for all of everyone's help!

[loukingjr]

For most Linux hosts, the Audio settings for the guest would be Host Driver: PulseAudio , Audio Controller: ICH AC97.

If you don't have PulseAudio installed in your host, try changing the Host Driver to Alsa Audio Driver.

FWIW, I changed the Host Driver to OSS and my Windows guests immediately aborted.

[Richard H.]

I have the same problem with Ubuntu Server 15.10, and disabling the audio works indeed as a work-around... But hope that it will be fixed quickly...