virtualbox.org

Host: HP Z640 Workstation (2 Monitors, 4 virtual Workspaces)
OS: Linux Mint 17.3 (Ubuntu 14.04) 64bit
Guest: Windows 7 64bit, 2 screens configured
VB: 5.1.2

Situation: VM is starting, showing Windows startup logo. Once the GUI is displayed, VB activates the 2nd screen and crashes

VirtualBox Window shows "aborted". I checked dmesg before and after starting the VM.
Following message appeared after the crash:

[428196.596712] traps: threaded-ml[92006] general protection ip:7f52fd087680 sp:7f52cdce2d70 error:0 in libpulse.so.0.16.2[7f52fd066000+47000]

I observed the problem as well with 5.1.0 but I thouhgt it was related to something else.
Now it happened the 2nd time and I am convinced thats related to VB.

VB log of the VM attached.

All virtual machines are running on their dedicated Linux virtual Workspace. Is this probably related to this problem?

VirtualBox VM 5.1.2 r108956 linux.amd64 (Jul 21 2016 16:56:51) release log
00:00:00.372412 Oracle VM VirtualBox Extension Pack (Version: 5.1.0 r108711; VRDE Module: VBoxVRDP)
00:00:00.386316 VRDE: Warning: failed to launch VRDE server (VERR_NET_ADDRESS_IN_USE): VirtualBox Remote Desktop Extension server can't bind to the port(s): 3389

You can disable the audio for the guest to see if the Pulse driver is causing your issue but the mismatch of the Extension Pack will also cause this.

If the version of the extension pack is important, please provide a mechanism to report the mismatch or block execution of the VM.
Crashing is not an option IMHO.

Normally the guest would not boot at all and you would see a mismatch in the main manager.

Here you go, my guest was booting - obviously.
So the bug we search is hidden in the detection and matching of VB and extpack version.

I remember with former versions of VirtualBox 5.0 etc. the software did not show an error message when the extension pack was outdated.
The green arrow sometimes turned orange but it never refused to start (as far as I remember).

As said, if there is a probability of crash when the version of extension pack does not match, please consider refusing the VM to start until an updated version has been installed.

b-roth wrote:when the version of extension pack does not match, please consider refusing the VM to start until an updated version has been installed.

+5
(except on dev builds)

Is this minor issue solved already?
Does VB still start if an older/incompatible version of the extensions is installed?