Change History

I noticed this problem also, restoring a BOINC Test4Theory (T4T) VM (which does not use VT-X) snapshot. I tried to restore a different T4T work unit's snapshot, though, and the second one worked. So, for me, it seems there might be an additional step needed to reproduce the error, or it is somewhat sporadic. But it is still a major issue.

Also, if you happen to find out (via code inspection) that there are additional steps to reproduce this, could you indicate what those steps might be? I'm having difficulty reproducing this problem, but it for sure did happen once for me (as noted in prior message and attached log file)

Actually this was a very nasty problem. It is not always reproducible (depends on the guest) and therefore our testing didn't catch it immediately. VBox 4.3.4 contains a fix for a related bug in VBox 4.3.2. For the fix, there were some pedantic error checks enabled for writing saved states. Unfortunately some of these checks did fail without reporting the error back to the controlling function. The result was that the outer function was not aware of the problem and the operation succeeded but only apparently.

The unfortunate result is that saved states created with VBox 4.3.4 for VMs with VT-x/AMD-V disabled are broken and cannot be restored! This applies to VMs which are terminated by saving the state as well as for snapshots. Sorry for that!

VBox 4.3.6 contains the complete fix. With VBox 4.3.6 it should be possible to load saved states created with VBox 4.3.2 but saved states created by VBox 4.3.4 must be discarded. Again, this applies only to VMs running in software virtualization mode (VT-x/AMD-V disabled).