Opened 14 years ago
Closed 13 years ago
#8763 closed defect (fixed)
Restore to snapshot crashes VM and leaves it inaccessible in VMM
| Reported by: | simon marshall | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.6 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
I installed 4.0.6, ga, rebooted, shutdown, saved snapshot, booted. I played around in the VM, before deciding to just throw away current state and restore to snapshot via clicking on the top-right close window button. The VM window went black and eventually win7 reported it as having crashed. Unfortunately win7 deleted the minidump when I oked through its popup.
In the VMM, the VM is now shown as inaccessible. Under Details, it suggests to "inspect the error message shown below", but there isn't one. Refresh does not change that.
Host is win7 64b, guest is ubuntu 10.10 32b.
Attachments (4)
Change History (10)
by , 14 years ago
comment:1 by , 14 years ago
Happily, when I restarted the VMM, the VM is no longer shown as inaccessible and appears to be normal (I can boot it etc). I could not reproduce the above crash, but if I do I'll be smarter about capturing the minidump. I guess the ticket priority can be reduced...
comment:2 by , 14 years ago
This happened to me too. I am running Win7x64 Host and Win7x64 guest. After I shutdown the guest, and followed by restoring the snapshot, Windows popup a message stating that VB has crash, then VBox displayed as inaccessible.
But after delete the listing and re-adding it, it is able to restart.
comment:3 by , 14 years ago
Just another note on the above: After re-adding, I am then able to restore the snapshot and restart...
comment:4 by , 14 years ago
I encountered another situation that also has the inaccessibility problem, which I believe could be due to the same reason. The following is the step to replicate this situation:
- Ensure that you have 1 VB Machine listed in Virtual Box Manager.
- Exit Virtual Box Manager.
- Make a copy of your existing VB Machine and give it a different directory name.
- Run Virtual Box Manager and remove the earlier VM Machine from the list.
- Immediate, go to Add a new VB Machine (the one that you have manually copied).
You should get an error stating some inaccessibility, due to some IDs.
Regards, Jacky
comment:5 by , 14 years ago
Please could you check if you still experience this problem with VBox 4.0.8? We fixed a related bug.
comment:6 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The final fix should be in VBox 4.1.4.
log