VBox 4.3.8: MS Excel 2013 File Menu Virtual Box Crash

[Brian T. McKee]

This is a VMWare retargeted Windows 7 PRO 64 bit virtual machine, created by copying a vmware vmdk, creating a new virtualbox and then connecting the virtual box drive to the vmdk.

vmware utilities have been removed. There was a vmware share folder that was unmounted after the virtualbox was created.

The VM has Office 2013 installed (updated to latest to see if problem goes away, it didn't)

Its also running latest from MS update for Windows 7.

I created a new excel spread sheet, clicked on the File tab, and went to the "save" button. Hovering over it is enough to crash the VM which exits with no messages on the console.

/var/log/messages had this:

Mar 18 16:08:55 shanti kernel: [106274.596909] device eth0 entered promiscuous mode
Mar 18 16:09:57 shanti kernel: [106335.887059] traps: INTNET-RECV[12488] general protection ip:7f2868b57d50 sp:7f281a81fc78 error:0 in VBoxRT.so[7f2868b01000+17d000]
Mar 18 16:09:57 shanti kernel: [106336.014377] device eth0 left promiscuous mode
Mar 18 16:09:57 shanti kernel: [106336.031849] vboxnetflt: 0 out of 256 packets were not sent (directed to host)
Mar 18 16:10:01 shanti cron[12529]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons)

I suspect(ed) its trying to connect to network drives that I used to have mapped, but I removed them all after the first crash in an attempt to stop the crash from happening.

Host is Linux:

Linux shanti 3.10.5-gentoo #2 SMP PREEMPT Mon Dec 23 13:45:32 PST 2013 x86_64 Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz GenuineIntel GNU/Linux

Any assistance would be appreciated. If you tell me how to run the VM with debugging turned on I can get a gdb backtrace for you. This failure happens every time I try to save my excel spread sheet.

Thanks.

[Brian T. McKee]

Just confirmed. I have this problem with 4.3.10 as well.

[misha]

Could you attach a VM log please?

[Brian T. McKee]

VirtualBox Log of Excel Failure.

[Brian T. McKee]

I just noticed a message "00:00:07.080867 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE"

It looks like there's a missing kernel module. Could this be the source of the issue?

[Brian T. McKee]

Actual Log...

[Brian T. McKee]

Here's another log.

[Brian T. McKee]

Sorry, I attached the wrong file before. Now there are two logs attached. Please ignore the first.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.