VirtualBox

Opened 16 years ago

Closed 8 years ago

#2533 closed defect (obsolete)

Can not unregister disk or vm when there are snapshots registered, but not present

Reported by: camper Owned by:
Component: VM control Version: VirtualBox 2.0.4
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by aeichner)

How to reproduce:

  • create a virtual machine and a virtual disk
  • create one or more snapshots of the virtual machine
  • delete the .vdi files in the snapshot directory of the virtual machine
  • you can't unregister the virtual disk or virtual machine any more => zombi virtual machine

Attachments (5)

VirtualBox2.10_Error_002.jpg (26.3 KB ) - added by MrX1980 16 years ago.
VirtualBox2.10_Error_003.jpg (54.3 KB ) - added by MrX1980 16 years ago.
VirtualBox2.10_Error_004.jpg (40.7 KB ) - added by MrX1980 16 years ago.
VBox_cannot_unregister.log (44.6 KB ) - added by MrX1980 16 years ago.
714a_appcompat.txt (23.5 KB ) - added by MrX1980 16 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 by MrX1980, 16 years ago

I have a similar failure:

VirtualBox 2.1.0 (updated from 2.0.4) Host: WinXP Pro 64-bit Guest: Win2003 64-bit

Machine -> Delete "Cannot unregister the machine ... because it has 1 snapshots." VirtualBox2.10_Error_002.jpg

If I try to delete the snapshot in VirtualBox, I get a windows error report: VirtualBox2.10_Error_003.jpg VirtualBox2.10_Error_004.jpg 714a_appcompat.txt VBox_cannot_unregister.log

by MrX1980, 16 years ago

by MrX1980, 16 years ago

by MrX1980, 16 years ago

by MrX1980, 16 years ago

Attachment: VBox_cannot_unregister.log added

by MrX1980, 16 years ago

Attachment: 714a_appcompat.txt added

comment:2 by Frank Mehnert, 16 years ago

Component: otherVM control
Description: modified (diff)

comment:3 by Dmitry A. Kuminov, 16 years ago

priority: criticalmajor

Yes, this is a known limitation. The reason why unregistering the VM with snapshots is forbidden in the first place is because there is no legal way to register it back afterwards. And also because it would most likely leave a lot of data (other diffs, saved states) on the user's hard disk which he may not notice.

The only way to remove such a broken VM from the list of known VMs for now is to manually edit VirtualBox.xml (and delete the relevant VM subdirectory if needed).

The problem will be addressed as part of the VM portability feature (which is being worked on).

comment:4 by aeichner, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette