virtualbox.org

Hi,

I am running VirtualBox 4.3. After installing Symantec Sytem Recovery 2013 (backup imaging software) on my guest the VM will crash and reboot in a loop. This does not occur in VirtualBox 4.2.18. Additions are installed. I have attached the Vbox log. Please let me know what else I need to provide.

Host/Guest are both Windows 7 Pro SP1 x64.

Thanks!

Anyone have any ideas on how to troubleshoot this? I've rolled back to 4.2.18 for now.

Is the VM crashing or the guest inside?
If it is the guest inside (looks like it), then you would get a BSOD. What is the error message?

Ok, what happens is that after I log in to the Windows 7 guest a message comes on my screen saying the VirtualBox VM Manager has stopped working. There is no error in the Guest OS. Here is the detailed error from the above-mentioned screen:

Problem signature:
Problem Event Name: BEX64
Application Name: VirtualBox.exe
Application Version: 4.3.0.0
Application Timestamp: 525d1b9c
Fault Module Name: StackHash_2264
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 0000000000000000
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2264
Additional Information 2: 2264db07e74365624c50317d7b856ae9
Additional Information 3: 875f
Additional Information 4: 875fa2ef9d2bdca96466e8af55d1ae6e

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

At this point my computer is extremely slow with keystrokes taking up to 10 seconds each to appear until I close the error message. Then the VM is listed in VirtualBox as Aborted with a red negative sign.

I also uninstalled the Additions to make sure they were not the issue with the same result. Booting the guest in safe mode does work.

If the issue only occurs after installed Symantec Sytem Recovery 2013 in the guest, then I would first seek support at Symantec and see what are they requirements for running the software, and specifically inside a VM (if that's even supported by them).

noteirak wrote:If the issue only occurs after installed Symantec Sytem Recovery 2013 in the guest, then I would first seek support at Symantec and see what are they requirements for running the software, and specifically inside a VM (if that's even supported by them).

It is supported inside VMs. I've had it running inside Hyper-V for about 4 years now and it works flawlessly in VMware. I was just hoping to track down whatever is causing the issue in VirtualBox. Is there a debug build available somewhere? Otherwise I can just switch to VMware and periodically see if the issue is fixed in Vbox. Also, it does work in Vbox 4.2.x so the issue points to the code overhaul in 4.3.

cpontus wrote:Is there a debug build available somewhere?

If you build one yourself, yes.

What you really should do is create a bug ticket, describe how to reproduce the problem, and most importantly attach a minidump with the crash information. The "detailed" information you posted unfortunately isn't detailed enough to even start looking into this. See https://www.virtualbox.org/wiki/Bugtracker