Immediate Reboots of Vista64 host + XML corruption when loading saved W2K guest by VBox 2.0.4 64bit => Fixed in 3.1.4

[Libor]

Hello,

I run guest W2K SP4 professional on Free version of VirtualBox 2.0.4 -64 ( czech localization ) on host Vista64 Home Premium SP1, ( all patches applied ). As other sw running Avast Home AV and Comodo CIS 3.5( firewall + HIPS ) .

This issue happened for second time in last few days by exactly the same way:

When loading saved state of W2K VM, the screen gets suddenly black and Vista OS reboots immediately without warning. Not sure at 1st time, at 2nd time R/O manually run chkdsk showed no problem at any partitions.

When run VBox again, it shows W2K machine is not available with "one-way-road red traffic sign".

When 1st time it occured, I was not able to use as emergency solution another freshly created W2K guest, using any of existing W2K disk states. Virtual disk manager showed that all snapshots are unavailable. Counting this time it will be the same.

In 1st time W2K was just installed and updated and some system installs, so I wiped it and installed guest from the scratch. But I am definitely not going to perform it every week :-)

In details window is written this (btw I could not copy it even if VBox context menu offers it, so retyped ):

---

Could not load the settings file: L:\.VirtualBox\Machines\Win2000SP4\Win2000SP4\W2K.xml Premature end of data in tag VirtualBox line 3.

Location: 'L:\.VirtualBox\Machines\Win2000SP4\Win2000SP4\W2K.xml', line 400(3), column 43

Return code: E-FAIL (0x80004005) Component: VirtualBox Interface: IVirtualBox {557a07bc-e6ae-4520-a361-4a8493199137}

---

[Libor]

Note that VBox additions installed

[Libor]

As noticed last lines of corrupted XML are Disk related, I would add I have set my Vista64 and Bios ( gigabyte MB GA-G33M-S2L ) to use AHCI, having recent SATA II disk.

Guest W2K is configured to use IDE interface to disk. Note that In both crash cases guest was rebooted, saved or reloded many times before crash occured.

[Libor]

Hm, sorry for confusion - I should say previously not open source version, but available Windows 64bit binary 2.0.4 .

[Libor]

The same occured twice for VBOX 2.1.0(closed source)/Vista 64 with Fedora 10 32b Linux, once during installing Fedora 10 32b guest from ISO, for second time when saving Fedora guest state while Fedora was busy.

[Libor]

I do not understand why is not here at least small note that anybody has ever read it ?

[Sander van Leeuwen]

Try it with 2.1.4 or 2.2.0 please.

[Libor]

I have VBox 2.2.0 already installed. The bug was reported when 2.0.4 was a current version.

Since the situation repeated several times even on VBox 2.1.x, I installed W2K on VirtualPc 2007, especially when I had later difficulties to install W2KSP4 again in VBox.

Now I use VBox only for Linux distros on Vista64 HPremium host, not problem there.

[Frank Mehnert]

We think we found the problem and finally fixed it. Version 3.1.4 will contain the fix (you can check VBox 3.1.4 Beta as well). Such symptoms you describe did only occur when restoring a saved state in software virtualization mode (that is, VT-x/AMD-V off). There are other reports somewhere so I will close this one as duplicate.