Crash on opening of the VM settings.

[yaromir]

I'm running VBox 4.2.12 on Debian 6.0.6 Squeeze AMD64

After update from 4.2.8 to 4.2.12 opening of settings of any VM cause X-session crash. Crash occurs both on existing and newly created VMs. After downgrade to 4.2.8 or 4.2.6 there is the same behavior.

Here is an exported VM on which this behavior is reproducable on my machine: ​https://www.dropbox.com/s/37bpy57r2smabzz/SmartOS-CrashOnOpenSettings.ova

Sorry, because of X-session crash i don't know how can i make a core dump (gnome-terminal with VirtualBox process crashes with X.org). Is there any way to run a VirtualBox from other terminal (tty) while running it's X-session on tty8?

Thanks.

[Frank Mehnert]

I've downloaded that .ova and can open the VM settings of this VM. Can you create an archive of your complete settings tree (the complete '~/.VirtualBox' directory together with the complete '~/VirtualBox VMs' directory without any virtual hard disk and iso image?

[GabyB]

I do observe the same behavior with VirtualBox-4.2 (Version : 4.2.12_84980_el6) on CentOS release 6.4 with kernel 2.6.32-358.6.1.el6.x86_64

I just wanted to create a new Fedora-18 virtual machine and the same moment when i clicked on the change button the X-server terminates and all processes are gone

I'm using VirtualBox with the language "German/Deutsch"

Thanks

[Frank Mehnert]

If the X server crashes then this is a problem of the X server and/or the 3D driver. When opening the settings, VBox does a simple test if 2D video acceleration would be possible on this host. It executes

VBoxTestOGL -test 2D

I assume that you will observe the same crash if you execute this binary manually (it's located in the VBox installation directory). To work around this problem, renaming this binary so that the VBox GUI can't find it should be sufficient.

This binary is very simple and it shouldn't be able to crash the X server.

[GabyB]

You are wright this program cashes the Xserver too You may find the strace on ​ftp://ftp.bruker.de/outgoing/VBoxTestOGL.log.23319 and ​ftp://ftp.bruker.de/outgoing/VBoxTestOGL.log.23320

and renaming fixed the problem

I'm using the NVIDIA driver 310.19

[yaromir]

X crash happens on all VMs except SmartOS

[yaromir]

Settings within which the X crash happens

[yaromir]

I've attached ~/.VirtualBox and ~/VirtualBox VMs . Sorry for the delay.

Actually i imported my own SmartOS VM and the X crash doesn't happen when i open settings of this machine. Looks like VM export solves this problem somehow.

Could this be a corruption in my settings that i got during an update and the VM export somehow manages to generate correct settings for the .ova using a VirtualBox-specific ones that got corrupted?

Thanks for your attention to the problem.

[GabyB]

Today I updated to VirtualBox-4.2-4.2.18_88780_el6-1.x86_64 and there is still the same behavior! If the File /usr/lib/virtualbox/VBoxTestOGL exists, the Xserver crashes

In /var/log/messages I found: Sep 23 13:36:21 hoya kernel: VirtualBox[27374]: segfault at 19f79bf0 ip 00000038eb035d35 sp 00007fff117b9cd0 error 4 in libc-2.12.so[38eb000000+18a000] Sep 23 13:36:21 hoya kernel: SHCLIP[27363]: segfault at 50ee36b0 ip 00000038eb035d35 sp 00007f7da40b39b0 error 4 Sep 23 13:36:21 hoya kernel: SHCLIP[27450]: segfault at 3f42fbb0 ip 00000038eb035d35 sp 00007f7306d229b0 error 4 in libc-2.12.so[38eb000000+18a000] in libc-2.12.so[38eb000000+18a000] Sep 23 13:36:21 hoya kernel: Sep 23 13:36:21 hoya kernel: device vboxnet0 left promiscuous mode Sep 23 13:36:21 hoya kernel: vboxnetflt: dropped 11542 out of 12320 packets Sep 23 13:36:21 hoya kernel: device eth0 left promiscuous mode Sep 23 13:36:21 hoya kernel: vboxnetflt: dropped 271 out of 66179 packets

[Frank Mehnert]

Let me emphasis that this is an X.org / Mesa bug. The X.org server should not crash when executing a simple 3D test application. All what we can do is to introduce some setting to bypass this test which would be set by the user on such systems.