#12118 closed defect (fixed)
Snapshot can not be deleted - line 421 of file VBoxManageSnapshot.cpp
Reported by: | wege_2 | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 4.2.18 |
Keywords: | snapshot | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
Machine is up and running with an applied snapshot (Host Ubuntu 12.04/64, Guest Ubuntu 12.04 32 & 64 current extensions applied). Trying to delete the snapshot with the gui results in "Fehler beim Löschen des Sicherungspunktes). No comments in the Logfile. I have also tried to delete the snapshot by hand with the same result. Upgraded from 4.2.14 to 4.2.18 before.
system@ubhost:~$ vboxmanage snapshot zarafa64 list
Name: CPVBOXSicherung (UUID: 95b738d8-34f5-4422-ade8-17a4ca1d5868) *
Description:
2013-09-16
system@ubhost:/vbox/vms$ vboxmanage snapshot zarafa64 delete 95b738d8-34f5-4422-ade8-17a4ca1d5868
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Snapshot operation failed
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: "int handleSnapshot(HandlerArg*)" at line 431 of file VBoxManageSnapshot.cpp
It makes no difference if the machine is paused or running. If I can supply any further information please let me know. Thanks in advance.
Attachments (5)
Change History (19)
by , 12 years ago
comment:1 by , 12 years ago
In this case it'd be better to have zarafa64.vbox, because the log does not have a description of the snapshot structure. From VBox.log this seems to be a very simple snapshot structure, but there must be something special. Deleting the only snapshot (VBox.log shows the base image + 1 diff, so looks like 1 snapshot) has been tested so many times that it can't have a bug which shows up in normal conditions.
comment:2 by , 12 years ago
Thanks for your fast response. Attached you will find zarafa64.vbox. The Snapshot is done for backup purpose - it worked over many month with different virtualbox versions, alltough we'd have to adapt our script from time to time due to changing snapshot functionality.
comment:3 by , 12 years ago
Scratching my head... this VM config is so simple that it's hard to imagine what could possibly go wrong. Probably no other way than using your config (complemented with some dummy disk images with the appropriate UUIDs) to reproduce, but I can't promise fast progress because everyone is super busy.
comment:4 by , 12 years ago
It seems I've got the problem!
It is not possible to delete a snapshot from a running or paused machine. I've taken a snapshot from a powered down machine and deleted it sucessfully. Than I tried it with an other machine with an undeletable snapshot - powered the machine down with acpi power down and deleted thereafter successfully the snapshot. Finally I repeated the procedure with zarafa64 vm.
So it seems to be clearly a problem in the new snapshot code. Hope this helps - kind regards.
PS: If I can do anything else (testing), please let me know.
comment:5 by , 12 years ago
This still doesn't make much sense. VirtualBox supports deleting the only snapshot of running VMs for a long time (and yes, that's far more complicated than you can probably imagine), so it's still a mystery why it's not working for you. The snapshot deletion code hasn't been changed in quite some time and there are no known bugs (at least not in the normal case, there are still situations which could be handled better if the system is running out of disk space)...
comment:6 by , 12 years ago
As the situation is reproduceable, would you like to get remote access (ssh) to our hostsystem? As I've mentioned before the system worked flawlessly before uprading some ubuntu packages (security packages from within a month up to 12.04.3) and virtualbox from version 4.2.14 to 4.2.18. - kind regards from carinthia
comment:7 by , 12 years ago
Meantime I reverted to virtualbox 4.2.14 - snapshots are working as expected again ...
by , 12 years ago
Attachment: | VBox.2.log added |
---|
comment:8 by , 12 years ago
After upgrading to VirtualBox 4.2.18 on my Mac (running OS X 10.8.5) yesterday, the nighly snapshots don't work anymore for running VMs:
VBoxManage snapshot Repo-Test delete 81ff7387-8950-4398-85ce-7c0a413a0d57 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Snapshot operation failed VBoxManage: error: Medium '/Users/ks/Library/VirtualBox/Machines/Repo-Test/Snapshots/{069321fd-6afd-4634-9273-90733f1a69c7}.vdi' is not locked for writing VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium VBoxManage: error: Context: "int handleSnapshot(HandlerArg*)" at line 431 of file VBoxManageSnapshot.cpp
There's nothing in VBox.log (attached) wrt deleting the snapshot. (Taking a snapshot works fine.)
comment:9 by , 12 years ago
Same problem here after upgrading to 4.2.18
Host:
- Linux my-server 3.2.0-39-generic 62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
- Ubuntu 12.04.3 LTS fully updated at 30/10/2013
- Vbox Version: 4.2.18r88780
Guest:
- Windows 2003
root@my-server:~# su --login --shell /bin/bash -c "vboxmanage snapshot desktop delete snapshot" virtualbox 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Snapshot operation failed VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available) VBoxManage: error: Context: "int handleSnapshot(HandlerArg*)" at line 431 of file VBoxManageSnapshot.cpp
Will add attachments with vminfo and .vbox.
I'm also available for any further tests.
Best regards,
Eric
by , 12 years ago
Attachment: | showvminfo.txt added |
---|
by , 12 years ago
Attachment: | desktop.vbox added |
---|
comment:10 by , 11 years ago
Hi,
I have just found this:
#9255 (live snapshot broken, Guru Meditation -2701 ... - VirtualBox https://www.virtualbox.org/ticket/9255 After upgrading to VirtualBox 4.1, I can no longer take snapshots of some virtual machines while they are running. .... demand but in the mean time it's indeed the right fix to disable that functionality until this bug is fixed. ... Fixed in VBox 4.2.18.
Maybe that fix has some relation with this new bug??? I'm still hopefully waiting for a solution. How long do you think may it take, more or less? Just to consider to wait or to rollback to a previous version (I use the version provided for Ubuntu 12.04 LTS "Precise").
Best regards,
Eric
comment:11 by , 11 years ago
problems seems to be solved in version 4.2.20 - no problems so far whether the VM's are online or offline. THX
comment:12 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thank you for the feedback! The fix should be part of VBox 4.3.4 as well.
comment:13 by , 11 years ago
Hi,
We have also tested the new version and it is now working fine!
Host:
- Linux my-server 3.2.0-39-generic 62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
- Ubuntu 12.04.3 LTS fully updated at 05/12/2013
- Vbox Version: 4.2.20r90983
Guest:
- Windows 2003
Thank you very much!
Best regards,
Eric
Current Logfile