Windows XP crashed after a while in Version 4.0.2 => Fixed in 4.0.4

[anonymous]

I was not in front of my PC, so the only think I could say is that a Windows XP guest that run for one or two hours crashed unexpected. The log is added.

[anonymous]

the log of a windows xp crash

[anonymous]

Could be the same crash two days later

[John Huong]

I experienced the same problems. Happened rather quickly sometimes. Downgrading to 3.2.12 made things work again.

[Frank Mehnert]

Sounds like a duplicate of #8008. Please could you try the VBoxManage settings posted there and check if it helps? Make sure to power-down your VM before doing VBoxManage setextradata ...

[anonymous]

Happends on another machine (AMD)

[John Huong]

Ok will try after the 10th of February.

[Frank Mehnert]

john.doe, in your case S4 was entered. Apparently you did not

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

[anonymous]

Replying to frank:

john.doe, in your case S4 was entered. Apparently you did not

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

I did it(hope so): Here is the terminal output. If trieed it two times. The second one with a less withespace in VBoxInternal/Devices/acpi/0/Config/ PowerS4Enabled 0

Seems to work, because of no feedback from the console.

Could I please get feedback if it is correct? And what now? Starting the machine, waiting until it crashes and file the log?

user@linux-3zjc:~> VBoxManage setextradata 'Windows XP' \

VBoxInternal/Devices/acpi/0/Config/ PowerS4Enabled 0

Oracle VM VirtualBox Command Line Management Interface Version 4.0.2_OSE (C) 2005-2011 Oracle Corporation All rights reserved.

Usage:

VBoxManage setextradata global|<uuid>|<name>

<key> [<value>] (no value deletes key)

Syntax error: Too many parameters user@linux-3zjc:~> VBoxManage setextradata 'Windows XP' \

VBoxInternal/Devices/acpi/0/Config/PowerS4Enabled 0

user@linux-3zjc:~>

[anonymous]

O.k I´ve read #8008. I´ve also done VBoxManage setextradata 'Windows XP' \

VBoxInternal/Devices/acpi/0/Config/PowerS1Enabled 0

Also with no return from the console.

[Frank Mehnert]

Doing these commands you change a hidden VM setting permanently. Getting no feedback is correct. I will close this ticket as duplicate of the tickets #8008 and #8126.

[John Huong]

I tried the steps you had mentioned but didn't work.

[Frank Mehnert]

Ok, in that case it is still a duplicate and it will be fixed in the next maintenance release. Your log clearly shows that the guest tried to enter S1, which was not allowed, then it tried to enter S4, which was not allowed either and then the guest decided to enter S5. The reason for this strange behavior is that VBox 4.0 and VBox 4.0.2 announce that the guest is allowed to switch into the ACPI states S1 and S4. The commands you tried from #8008 make the VMM ignore the requests for entering S1 and S4, and then it decides to enter S5.

The next maintenance release will not announce S1 and S4 to be available anymore, so the old behavior of 3.2.12 will be restored.

[Frank Mehnert]

Fixed in 4.0.4

[khh]

This bug is back in the latest release (still WinXP SP3). As before running the below commands fixes it.

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

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.