After upgrading to 1.5.4 I can no longer load my virtual machine from a saved state. After the restoring state dialog and progress meter completes I get the following error:
Failed to restore VM state from '/export/nic/.VirtualBox/Machines/WindowsXP/Snapshots/{fe1b0054-d7ad-4408-9980-ce88e25eb99c}.sav' (VERR_SSM_LOADED_TOO_MUCH).
VBox status code: -1819 (VERR_SSM_LOADED_TOO_MUCH).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
I dunno what the deal is...
Cannot start virtual machine in saved state
-
misiu_mp
- Posts: 2
- Joined: 23. May 2009, 15:26
- Primary OS: Fedora other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: ubuntu
Re: Cannot start virtual machine in saved state
I wonder if they are supposed to be incompatible between different architectures.
A state saved in 32bit VirtualBox 2.2.4 (on 32bit Fedora 11) refuses to load in 64bit VirtualBox 2.2.4 (on 64bit Fedora 11).
Is this the currently expected behavior?
A state saved in 32bit VirtualBox 2.2.4 (on 32bit Fedora 11) refuses to load in 64bit VirtualBox 2.2.4 (on 64bit Fedora 11).
Is this the currently expected behavior?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Cannot start virtual machine in saved state
I don't think that it matters if it is 32 or 64 in your case just that it was not shut down when moved.
-
sandervl
- Volunteer
- Posts: 1064
- Joined: 10. May 2007, 10:27
- Primary OS: MS Windows Vista
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, Solaris
Re: Cannot start virtual machine in saved state
You can't yet move saved states between different architectures. That's a known limitation.
As for my comment from 2008 above; since version 1.6 we try not to break saved state backwards compatibility.
As for my comment from 2008 above; since version 1.6 we try not to break saved state backwards compatibility.