virtualbox.org

I'm running VirtualBox 4.0.2 on an OpenIndiana 148 host, trying to shut off a guest running debian6-rc2. RUnning VBoxManage controlvm "debian6-rc2" poweroff yields

0%...10%...20%...30%...40%...50%...

at which point it stops, waiting. If I try to get statistics,

VBoxManage debugvm debian6-rc2 statistics
VBoxManage: error: Machine is not running
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component MachineDebugger, interface IMachineDebugger, callee nsISupports
Context: "GetStats(bstrPattern.raw(), fWithDescriptions, bstrStats.asOutParam())" at line 396 of file VBoxManageDebugVM.cpp

Is there any information I should get from this before I kill it? And is kill -9 on the appropriate process instance the best way to kill it?

Same here on solaris 11 express with latest vbox. Guests are server 2008r2 and centos 5.5.

Need to kill the process...not happy.

Did not have the issue with opensolaris 111b 2009.06

What do you need to help debug?

This is getting ridiculous!

I now suspect this is related to my other issue...which in turn I suspect is related to power management....

" Since 4.0, there are some more ACPI options available and when you have the GA installed, they become enabled in the VM OS. Open the Guest OS power management and disable the actions for hibernate and suspend."

Ie. If I solve the lockup, I solve the power down issues.