VirtualBox

Opened 17 years ago

Closed 14 years ago

#955 closed defect (fixed)

Incorrect snapshot handling in Linux (VERR_ALREADY_EXISTS)

Reported by: tautrimas Owned by:
Component: VM control Version: VirtualBox 1.5.2
Keywords: snapshot VERR_ALREADY_EXISTS Cc:
Guest type: other Host type: other

Description

This is how it happens:

  1. I create a snapshot of running Win XP client.
  2. I use the client, and when I finish my work, I simly push "revert to current snapshot".
  3. It works many times, but one day, after reverting it says "aborted".
  4. Then, when I try to revert again (after starting client up and playing a bit), it says:

Could not copy the state file '/home/tautrimas/.VirtualBox/Machines/WinXP/Snapshots/{b2ec225f-3158-4dde-d1a7-dd58663d6426}.sav' to '/home/tautrimas/.VirtualBox/Machines/WinXP/Snapshots/{02b3e0da-9713-46f2-8e88-3e0806fb9da6}.sav' (VERR_ALREADY_EXISTS).

Result Code: 0x80004005 Component: Machine Interface: IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}

  1. Virtual Disk Manager says, that there are currently 2 difference disks (each 60.50 KB in size) for my single snapshot.

Problem is, that I can't revert my snapshot back. Problem appeared second time in a week (after reinstall of VBox).

Linux system: Sabayon Linux 3.4f

USB and sound enabled.

Attachments (1)

snapshot2.png (48.1 KB ) - added by Andrei ILIE 15 years ago.
the error message

Download all attachments as: .zip

Change History (12)

comment:1 by tautrimas, 17 years ago

If I want to discard a snapshot:

Normal hard disk '/home/tautrimas/.VirtualBox/VDI/HardDisk1.vdi' stored in the snapshot 'Snapshot 1' has more than one child hard disk (2).

Result Code: 0x80004005 Component: Machine Interface: IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}

comment:2 by tautrimas, 17 years ago

Problem still persists in 1.5.7

comment:3 by tautrimas, 17 years ago

Found a solution that works for me. You must start the machine, close saving state, and voila! You can revert.

comment:4 by Sylvain, 17 years ago

Got the same error (v. 1.5.6):

Could not copy the state file '/home/aleph/.VirtualBox/Machines/CentOS2/Snapshots/{f5e563cb-6447-4c6c-cb9c-8acd489f306d}.sav' to '/home/aleph/.VirtualBox/Machines/CentOS2/Snapshots/{090df291-9752-4458-e689-391e93ead9bf}.sav' (VERR_ALREADY_EXISTS).

Looking at /home/aleph/.VirtualBox/Machines/CentOS2/Snapshots/, I found 2 *.sav states, and deleted {090df291-9752-4458-e689-391e93ead9bf}.sav

Then Revert to current snapshot worked.

Details: aleph ~/.VirtualBox/Machines/CentOS2/Snapshots $ ls -1 {039815fa-78c8-4c16-bba2-f6bd7cf9fc62}.vdi {090df291-9752-4458-e689-391e93ead9bf}.sav {0b543081-2858-4e82-ca81-bfaf081b7030}.vdi {1c72af45-3a6f-476f-ecb5-0d202915d1a6}.vdi {34b0c58a-2b5d-4607-3982-e5d7f4a7be84}.vdi {547dd476-62ef-4d82-e1a3-76d428965bb6}.vdi {f5e563cb-6447-4c6c-cb9c-8acd489f306d}.sav aleph ~/.VirtualBox/Machines/CentOS2/Snapshots $ mv \{090df291-9752-4458-e689-391e93ead9bf\}.sav ~/.Trash/

comment:5 by Frank Mehnert, 16 years ago

Component: otherVM control

comment:6 by Frank Mehnert, 16 years ago

Resolution: fixed
Status: newclosed

No new comment for a long time. Please reopen if a same problem happens with the most recent release (2.2.2).

comment:7 by Andrei ILIE, 15 years ago

Resolution: fixed
Status: closedreopened

* exactly * the same problem here.

andrei@dfg3gjh5:~> VirtualBox --help Sun VirtualBox Graphical User Interface 3.1.6 (C) 2005-2010 Sun Microsystems, Inc.

by Andrei ILIE, 15 years ago

Attachment: snapshot2.png added

the error message

in reply to:  3 comment:9 by simpzan, 14 years ago

Replying to tautrimas:

Found a solution that works for me. You must start the machine, close saving state, and voila! You can revert.

yes, it works! Thank you!

comment:10 by Frank Mehnert, 14 years ago

Still relevant with VBox 3.2.10?

comment:11 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: reopenedclosed

No response, closing.

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