virtualbox.org

I'm running the latest (installed today) VB with a Windows 10 guest. The host system is Ubuntu 12.04 with Linux kernel 3.13.0-92-generic.

The computer is Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz

I find that it suddenly crashes without warning. I see that in dmesg there is:

[384887.115231] EMT-3[7104]: segfault at 10 ip 00007f261161621d sp 00007f264241db80 error 4 in VBoxDD.so[7f2611502000+286000]

the first time tonight and

[388546.537415] EMT-3[7167]: segfault at 10 ip 00007f9f5f61221d sp 00007f9fac75fb60 error 4 in VBoxDD.so[7f9f5f4fe000+286000]

the second time.

I notice that either side of the messages in each case are:

[384304.593518] device eth0 entered promiscuous mode

and

[384887.472859] device eth0 left promiscuous mode

in case that is relevant.

In settings network advanced for the guest it has "deny" against promiscuous mode.in case that is relevant.

I have no other VMs running at the time.

Is there something I need to do or is this a fault?

Just happened again. As before it seems to be "promiscuous mode" that does it:

[435324.441172] device eth0 entered promiscuous mode
[464658.332045] EMT-3[9504]: segfault at 10 ip 00007f303e61421d sp 00007f3072ffdb60 error 4 in VBoxDD.so[7f303e500000+286000]
[464658.694015] device eth0 left promiscuous mode

Just tried switching from Bridged to NAT and it crashes somewhere else without the promiscuous mode bit.

[466938.255705] EMT-3[12007]: segfault at 7fb56413e75c ip 00007fb5a8289206 sp 00007fb5d6afab60 error 4 in VBoxDD.so[7fb5a8175000+286000]

I'll try turning networking off altogether for a bit.

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.

Here it is.

It's crashed similarly on another computer same OS but Interl i7 same version of VB but running WXP this time.

My wife's using that computer right now but when she goes to bed I'll send the logfrile for that.

Mine seems to have stayed up since I turned networking off.

dmesg on my wife's computer shows:

[471102.107026] VirtualBox[24129]: segfault at 18 ip 00007f9f46e0de1f sp 00007ffe6f309940 error 4 in libQt5XcbQpaVBox.so.5[7f9f46da4000+145000]
[471102.107038] VirtualBox[24181]: segfault at 18 ip 00007f6a4b68ee1f sp 00007ffdde5b9ad0 error 4 in libQt5XcbQpaVBox.so.5[7f6a4b625000+145000]

Further to my previous message here is the logfile from my wife's computer I just interrupted her for a minute.

Just crashed again on both computers.

Here is the last message in dmesg (on my machine)

[518911.642570] EMT-3[15263]: segfault at 10 ip 00007f9fb839021d sp 00007f9ffcc1ab60 error 4 in VBoxDD.so[7f9fb827c000+286000]

The log (which I have compressed) is attached. This is "hot off ye press" immediately after the crash.

Networking is turned off as I thought that helped.

I wish I'd kept the previous version of VB.

The logs are not showing a crash or a reason. The latest log stops recording about 48 seconds after the start. Can you describe the crash and what it means to you? does the guest disappear and show as aborted, or does it hang, freeze?

Another thing that is curious, you said "Just crashed again on both computers", does this happen often where they crash at the same time?

You can always revert back to the last install that worked. I will provide a link to previous releases below. Oh and one more thing, since you have "crashes" in various modules, Is your host BIOS up-to-date?

http://download.virtualbox.org/virtualbox/

The logs are not showing a crash or a reason. The latest log stops recording about 48 seconds after the start. Can you describe the crash and what it means to you? does the guest disappear and show as aborted, or does it hang, freeze?

The Guest OS window just disappears without warning and the Manager window shows "aborted" against the VM. It seems to restart OK without going into "safe mode" or anything.

Another thing that is curious, you said "Just crashed again on both computers", does this happen often where they crash at the same time?

No it was just a coincidence I think. It did seem to be just a few minutes apart, first on hers (the i7) and then on mine (the Xeon).

You can always revert back to the last install that worked. I will provide a link to previous releases below. Oh and one more thing, since you have "crashes" in various modules, Is your host BIOS up-to-date?

I've gone back to 5.0 on my machine which hasn't crashed since then (famous last words!). My wife's machine hasn't crashed since this morning but I've said if it crashes again I'll put that version in.

Both machines have about 2 year old BIOSes - we got them for primarily running Linux, just using VB for the benefit of things that we can only get for Windows. Everything we do on Linux works just fine, but my wife likes to run her games things for which we run VB. (Actually her machine is my old machine but I had bits upgraded by the supplier when I got my machine).

5.1.* has moved to QT5 ( one of the modules that segfaulted ) and I am not sure how you updated Ubuntu 12.04 to the version needed but it might be a reason you should check into. One thing I did learn from experience with my system ( a beast like yours ) is the chipset can have an effect on how VirtualBox operates. I had to upgrade the BIOS to stop a lot of crashing ( because of the quad channel memory ) but only when using VBox or compiling. I originally found it from compiling various programs and after updating all was fine.

BTW: My Linux host (Debian type/based) is self-compiled as well but the base was around the 14.04 era plus I build my own packages of QT, Etc. and probably why I don't see a lot of issues others see.

Of course this may all be a non-starter for your system and is all just a guess. From what I read the guest is trying to do something that is out of bounds somehow and aborts to keep from causing a real problem. You might be better off to report this to bugtracker so the DEVs can have a look.

I've got QT5 loaded but surely that wouldn't affect guest support?

I 've submitted a bug tracker report.(15677).

See what they say.

Meanwhile 5.0 seems to be OK at the moment.