[4.2.16] unable to restore from snapshots

[Cuchulain]

Hi folks,

I'm having issues with the latest versions of VBox, I believe that it's incorrectly appending snapshot names together in the .vbox file.

I use a Windows 7 VM for programming

08-14-13 installed some windows updates and saved the vm state.

08-16-13 installed V 4.2.16 of VBox

08-19-13 Tried to restore the snapshot i get the following...

**Please see the attached file - as a new forum member I am not allowed post hyperlinks (which the forum post process believes the snippets from the .vbox files are)

Has anyone had the same issues?

Thanks
/Cuchulain

[Cuchulain]

Downgrading VBox doesn't resolve the issue as any VM opened with V4.2.16, and a snapshot saved corrupts the .vbox file

[mpack]

The error message is regarding a saved state file, not a snapshot. It just happens to be stored in the folder called "Snapshots".

Right click the VM and select "Discard saved state".

It is indeed odd that it has concatenated the filename several times.

[Cuchulain]

Thanks for the reply mpack, I'll test discarding the saved state in a little while.

I've analysed the disk files and the .vbox file further and believe that V4.2.16 is pre-appending the path for the 'Current State' to the path for all snapshot files.

Unfortunately I can't upload the file with a .xlsx extension (where the formatting makes the issue more apparent), but I've attached a screenshot of the Excel screen

/C

[mpack]

If you want to upload a .vbox file, just rename it to .txt. Or, you can upload anything if you zip it first and attach the .zip. An Excel spreadsheet is a proprietary format, and not very useful to me.

[Cuchulain]

I get you. - here's one of my .vbox files attached with .txt extension. Were you able to open the .csv file in your spreadsheet program. Attached is a zipped .ods Open Document spreadsheet file otherwise (I'm assuming this is an open standards file.)

Thx
/C

[mpack]

I have manually corrected your .vbox file - see the attached zip file.

You need to rename your existing .vbox file (for safekeeping) and replace it with the one from the zip. After testing you should eventually delete the old renamed file plus all ".sav" files from the Snapshots subfolder.

I don't know how VirtualBox managed to get itself into a twist about the state file path. Please check that you don't have anything silly in File|Preferences|General|Default Machine Folder or in any system path.

[Cuchulain]

Hi mpack,

I've had a chance to test that new .vbox file.

With vbox not running
- renamed old .vbox file
- replaced with your edited file
- ran machine ok - machine state correct

-looked at .vbox file - same issues with multiple .sav files being appended
-removed .sav files from snapshot dir
-replaced .vbox with your edited file again
- ran machine ok
- tried switching between snapshots
- same errors as before

attached zip contains .vbox file i nit's different states

Value of File|Preferences|General|Default Machine Folder is "V:\virtual box"

Best
/C

[mpack]

What about host paths?

If those are ok then I must bow out of this conversation since I have not experienced the problem, I have not heard of anyone else experiencing the problem, and I never use snapshots or saved states anyway. All you can do is post a ticket on BugTracker.

[Cuchulain]

thanks anyway for devoting so much of your time.

I'll investigate a little more before posting a ticket

Best regards
/C