Virtual Box 5 and Open Suse 13.2

[Kester]

I am getting the below error after upgrading from VirtualBox 4.3.30 when starting my windows 7 VM

Failed to open a session for the virtual machine Ninja.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

[noteirak]

Please read Minimum information needed for assistance and provide zipped attachment of the VM log file and the guest settings.

[Kester]

see attached

[noteirak]

I'll also need the rest

[Kester]

More...

[noteirak]

Nothing giving a definitive answer. Could you also provide the VBoxSVC.log file found under $HOME/.config/VirtualBox? Try to start the VM first before giving the log.

[Kester]

there you go

[noteirak]

The plot thickens...

Let's try some ideas which caused issues in the past. Could you try the following, one change at the time:
- Remove the guest additions from VM Virtual drive
- Reconfigure the 2nd virtual NIC in the VM config so it doesn't use NAT, and then disable it
- Reduce RAM usage

[Kester]

have done all that but same error pops up

[noteirak]

I don't have a better idea right now. I'll let the other mods help too, but if nothing comes up, I can only suggest to post on the BugTracker.

[Perryg]

I would like to see the complete guests log file ( as an attachment ) compressed if it is too big other wise.

[mborodin]

Hi,
I'm having the same issue on my openSUSE 13.2 with kernel 4.1.2-1-desktop from factory.
Additionally to the same VBox log messages I can see segfault in VBoxVMM.so im dmesg output:
vboxdrv: ffffffffa0991020 VMMR0.r0
EMT[27091]: segfault at 1036d0000 ip 00007f8a41413449 sp 00007f8a29b1dc38 error 6 in VBoxVMM.so[7f8a412f2000+297000]

I updated related ticket 14286 with the same information.

[estebanc]

Hello there,

I am having exactly the same problem after installing a SUSE patch on SUSE 13.2 which installed VBox 5.0. Before installing the update, I had up and running VBox 4.3.36.

I think the update upgrades VBox to 5.0 and for some reason fails to open up the VMs that I had created on VBox 4.3.36.

I can see that this issue was reported last year, however I cannot find a workaround for it.

Any help will be appreciated.