I just tested this on the lastest binary 3.1 from
VirtualBox.org download, and this bug still exists.
(1)
It's very easy to reproduce. Just enable 3D/2D, create a
XP vm (I am using 32-bit Vista host), then start the vm, and hiberante
it from command line:
VBoxManager controlvm "testvm1" savestate
you will get the crash. Try a few times if not getting it
1st time.
(2) another hard way is to shutdown the xp vm from Windows
Start menu, Shutdown
After many tries, you will get the crash. Make sure to
enable 2D/3D.
I spent quite some time to track down the bug, still not
yet find it. It's to do with some thread starting, judged from
following crash call stack.
Unhandled exception at 0x038734b2 in VirtualBox.exe:
0xC0000005: Access violation reading location 0x038734b2.
038734AF ???
038734B0 ???
038734B1 ???
038734B2 ??? <===
038734B3 ???
038734B4 ???
038734B5 ???
--- On
Mon, 11/23/09, Huihong Luo <[email protected]>
wrote:
From: Huihong Luo <[email protected]>
Subject: [vbox-dev] 3.1 beta 2 vm freezes when hibernating
To: [email protected]
Date: Monday, November 23, 2009, 10:18 PM
|
sometimes, vm console becomes non responding when
closing with Saving state. It's XP guest on Vista host, 32-bit.
It seems to do with 3D/2D enbling. The problem
occurs much often when 3D/2D is enabled. If 3D/2D is off, the
problem seldom occurs.
|
-----Inline Attachment Follows-----