VB will not open - error message is
Failed to open a session for the virtual machine Windows XP.
Unsupported version 13 of data unit 'pgm' (instance #1, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
Help! What have I done/what do I need to do??
Thanks
Error Message following upgrade to 3.2.12
-
lambchops88
- Posts: 12
- Joined: 22. Nov 2010, 20:29
- Primary OS: Mac OS X Leopard
- VBox Version: OSE other
- Guest OSses: Windows XP
-
rpmurray
- Volunteer
- Posts: 918
- Joined: 3. Mar 2009, 00:29
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 7, Mac OS X (various flavors)
- Location: Between Heaven and Hell
Re: Error Message following upgrade to 3.2.12
Did you update VirtualBox while your VM was in a saved state?
-
lambchops88
- Posts: 12
- Joined: 22. Nov 2010, 20:29
- Primary OS: Mac OS X Leopard
- VBox Version: OSE other
- Guest OSses: Windows XP
Re: Error Message following upgrade to 3.2.12
Yes I did - which obviously was the wrong thing to do?
-
rpmurray
- Volunteer
- Posts: 918
- Joined: 3. Mar 2009, 00:29
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 7, Mac OS X (various flavors)
- Location: Between Heaven and Hell
Re: Error Message following upgrade to 3.2.12
No need to put the question mark at the end of your sentence. Yes, it was the wrong thing to do!
It's like leaving your computer running while you swap out the motherboard.
You have two choices at this point. One is to revert back to 3.2.12 and see if you can shut down the VM properly before updating again. The other is you can discard the saved state and see if the VM will boot (you will lose any changes you've made since the last time you shut down the VM).
In both cases I recommend making a backup first, just in case.
It's like leaving your computer running while you swap out the motherboard.
You have two choices at this point. One is to revert back to 3.2.12 and see if you can shut down the VM properly before updating again. The other is you can discard the saved state and see if the VM will boot (you will lose any changes you've made since the last time you shut down the VM).
In both cases I recommend making a backup first, just in case.
-
lambchops88
- Posts: 12
- Joined: 22. Nov 2010, 20:29
- Primary OS: Mac OS X Leopard
- VBox Version: OSE other
- Guest OSses: Windows XP
Re: Error Message following upgrade to 3.2.12
Thanks very much - the discard option has restored the programme.
Re: Error Message following upgrade to 3.2.12
It's funny how something that seems totally unacceptable to me (not being able to open a saved state from a recently updated VirtualBox application) seems not only acceptable but expected by other people.rpmurray wrote:No need to put the question mark at the end of your sentence. Yes, it was the wrong thing to do!
It's like leaving your computer running while you swap out the motherboard.
Too bad for everyone who uses the VirtualBox saved states as backups.
I don't recall any warnings not to perform an application update when I clicked on the "Save State" button.
Call me nutty but I would have expected the "feature" of being able to load/convert saved images of any prior version a requirement before a new application version is deemed releasable.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Error Message following upgrade to 3.2.12
"Too bad" is right. Evolution soon takes care of mistakes like that, we probably shouldn't interfere.mungoman wrote:Too bad for everyone who uses the VirtualBox saved states as backups