Virtualbox general protection fault

[adimanav]

I am running Virtualbox on Gentoo 64 bit OS kernel linux-4.14.13 and am getting general protection fault while running the VM and Virtualbox crashes.

[adimanav]

kernel: traps: INTNET-RECV[8693] general protection ip:7f67e3d098a3 sp:7f67610e5cb8 error:0 in VBoxRT.so[7f67e3c7a000+245000]

[adimanav]

This is happening with bridged network. On changing to NAT there is no GP fault. There is an issue with bridged networking.

[Socratis]

There is an issue with bridged networking.

Or your host's network drivers. Or a 3rd party software that might interfere. Or... or..., the possibilities are endless. Can you make sure that you have no 3rd party software installed, like wireshark for example?

[tabascoz]

Same here - gentoo - 64 bit OS kernel linux-4.14.13

[Socratis]

Just a friendly reminder; you remember the requirements in the new ticket page? They're actually listed before the ticket form, so I'm not sure how you missed it. I don't see any of them fulfilled, not even a log...

[tabascoz]

Log of an aborted sesson

[tabascoz]

Please find the information. Sorry for not posting it earlier;

Vbox 5.2.2 (downgraded from 5.2.4 in attempt to fix the bug) 5.1.30 works fine.

Summary: guest execution ( w7 64bits ) ends abruptly and randomly when using bridge network. Using default network setup. It does not happen when using nat network.

when it happens i get kernel's log event below:

[33757.444255] traps: INTNET-RECV[25724] general protection ip:7f19d687e8b0 sp:7f1952ffabc0 error:0 in VBoxRT.so[7f19d67d2000+2ea000]

Running Gentoo Linux - portage snapshot from 01/14/18 - zen kernel 4.14.13. System compiled with GCC 7.2.0 / lto & graphite. Virtualbox compiled with standard gcc optimization ( no lto or graphite ).

Issue is also present with binary package from gentoo ( virtualbox-bin )

[tabascoz]

Same issue with kernel-4.14.14

traps: INTNET-RECV[5641] general protection ip:7fa50dfc28b0 sp:7fa496d83bc0 error:0 in VBoxRT.so[7fa50df16000+2ea000]

[Socratis]

From your log:

VirtualBox VM 5.2.2_Gentoo r119230 linux.amd64 (Jan 15 2018 17:11:17) release log

It looks like you're using the distro's fork version of VirtualBox. You can either ask in their forums for help, or completely remove/uninstall/delete/purge their version and install the official version from the Downloads section.

If that doesn't work you should try the latest test builds, especially with all the Spectre/Meltdown patches coming in from all sides.

[tabascoz]

OK will do it right now and report. Thanks

[tabascoz]

With binary everything is fine. bridge works without issues. However due to choppy sound had to get back to 5.1.32.

Probably something related to GCC 7.2 or spectre/meltdown...

[Valery Ushakov]

Thanks for the update. This is probably gcc 7.2 squeezing anything it can from the more obscure corners of the C standard (googling for something like "gcc undefined behavior optimizations" should bring up a few horror stories).

[Ervin Peters]

I'm running gentoo, too. I run into the same segfaults. As pointed out in ​https://bugs.gentoo.org/644142 it seems to me that it is related to the choice of the network hardware emulation. After trying several things virtualbox 5.1.32 crashed repeately with this segfault, after the guest windows 10 started it's update procedure. Upgrade to gentoo unstable 5.2.26 the same segfaults occur. I guessed that it is related to some network traffic. Playing around I tried to switch the network adapter emulation from intel pro ...desktop ... to the paravirtual device - but unfortunately that wasn't recognized by Windows. Then I switched to the intel ... Server ... device emulation and restarted vbox. Windows (re-)installed some drivers and updated successfully. No crash since then.

I assume there is either a bug in the network card emulation of the 'desktop card', if it is different from the server one, or windows installs a incompatible driver which got somehow confused...

HTH someone.

Ervin