VirtualBox

Ticket #9421 (new defect)

Opened 3 years ago

Last modified 2 years ago

VM inaccessibe after restore to snapshot

Reported by: Clipper87 Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.0 Keywords:
Cc: Guest type: other
Host type: other

Description

I have Virtualbox v 4.1.0 r73009 on Windows 7 64 bit with Systematically after I restore to a snapshot the VM becomes inaccessible, in the snapshot folder there appears a 2nd snapshot. After quitting Virtualbox & then relaunching Virtualbox the VM is normally accessible but the 2nd snapshot worries me. Never seen this with older versions.

Attachments

vbox_logs.zip Download (32.5 KB) - added by jjlin 2 years ago.

Change History

comment:1 Changed 3 years ago by frank

Should be finally fixed in VBox 4.1.4. Please confirm.

comment:2 Changed 3 years ago by Clipper87

I confirm that indeed this seems to work. I was not aware of v4.1.4 because check for updates continued to tell me that I had the latest version...

comment:3 Changed 3 years ago by Clipper87

Unfortunately I have to come back on this; it still does not work correctly. After you restore to a snapshot you just created all seems fine but when you restore to an older snapshot things go wrong again.

comment:4 Changed 3 years ago by poetzsch

Would it possible to attach the .vbox file of the VM before you restore the snapshot? Also a detailed description of what exactly you have done, would be helpful.

comment:5 Changed 3 years ago by poetzsch

I still can't reproduce this. Can you give a little bit more details about how your snapshots where arranged and what you have done exactly? Is there one disk attached to the VM or more? Where DVD/CD images involved?

Changed 2 years ago by jjlin

comment:6 Changed 2 years ago by jjlin

Just ran into the same problem on 4.1.10. Win7 64-bit host, WinXP guest. I was simply restoring to the most recent snapshot; the same operation was successful when I last restored 2 days ago. My snapshot tree isn't very complicated either. I've attached various logs, but I'm not sure how helpful they'll be. As others have mentioned (e.g., #9457, #9526), this problem doesn't happen consistently, but is frequent enough to be a pain. This last happened to me about a month ago (2/25), though I don't use my VM very frequently, so I'd say this has actually happened twice in my last 5 restores, which is not a good success ratio.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use