Win 7 VM crashing now

[Jits]

Hi,

I just updated VirtualBox to 4.0.2 (from 4.0.0) on host: Ubuntu 10.04 x64.

Then updated the virtual additions on an existing Win 7 x32 VM.

Now it starts up okay but crashes after a while and the VM shuts down.

I believe this is happening at the instance when it *previously* was automatically pausing the VM (on 4.0.0).

Relevant log attached.

Any help with this would be greatly appreciated!

Jits

[Jits]

Ah, looking at the logs again... seem's like the Win 7 in the VM was set to automatically suspend after a period of time. I am disabling this and trying again.

Will report back!

Jits

[bobfranklin]

Same issue - crashes the vm

Host Fedora 14 64bit
Guest Windows 7 32 bit

VirtualBox 4.0.2
Guest Additions: 4.0.2

Didn't encounter this issue in 4.0

[mdailey]

I'm seeing the same behavior today after upgrading from 3.2.12 to 4.0.2. Logs show the same messages as Jits:

Code: Select all

01:15:31.730 Ignoring guest attempt to enter S1 power state (powered-on suspend)!
01:15:31.730 Entering S4 power state (suspend to disk)
01:15:31.730 Changing the VM state from 'RUNNING' to 'POWERING_OFF'.

Checked some old logs from before upgrading, and never saw the Win7 guest try to call S1 power state.

I'm going to try setting the guest's Power Options control panel to "High performance" (i.e. turn off sleep of the computer) and see what happens.

[Jits]

Hi,

Setting the VM to not automatically go on standby prevents the shutdown/crash.

However, the pre 4.0.2 behaviour of pausing the machine is much better!

Jits

[frank]

This will be fixed in the next maintenance release.

Code: Select all

VBoxManage setextradata VM_NAME VBoxInternal/Devices/acpi/0/Config/PowerS1Enabled 0
VBoxManage setextradata VM_NAME VBoxInternal/Devices/acpi/0/Config/PowerS4Enabled 0

should disable S1 and S4 completely.

Code: Select all

VBoxManage setextradata VM_NAME VBoxInternal/Devices/acpi/0/Config/PowerS1Enabled 1
VBoxManage setextradata VM_NAME VBoxInternal/Devices/acpi/0/Config/PowerS4Enabled 1

should restore the 4.0 behavior.

[sej7278]

This will be fixed in the next maintenance release.

not meaning to sound rude/ungrateful, but is that likely to be soon frank?

i half expected to see 4.0.3 the day after 4.0.2 was released as it seems flakier than 4.0.0 and we're already using 4.0.3 ga's for linux.

[Jits]

Thanks Franck!

[stewartv]

I was directed here from:

http://forums.virtualbox.org/viewtopic. ... 55#p175055

I'm unclear whether this is the same problem and would be grateful for your help/opinion.

My W7 guest doesn't suspend properly and I first noticed this when I resumed the host (Ubuntu 10.10) and when restarting the guest found that it wouldn't resume, it needed to be cold booted. I changed the host to suspend "never" and found that the guest on it's own wouldn't suspend and restart. That seems to suggest that it's this problem. If it is, I'll stop worrying about it, if not I'll keep trying.

Also in Frank's post there are some configuration lines. Can I change these myself? I saw that you said that this would be changed in the next maintenance release so that would seem to imply not but I'm not sure.

S