Context Navigation

← Previous Ticket
Next Ticket →

#13186 closed defect (duplicate)

Changing VM Group causes the .vbox snapshot statefile value to become corrupt, making snapshots invalid

Reported by:	Jacob Klein	Owned by:
Component:	GUI	Version:	VirtualBox 4.3.14
Keywords:	group groups statefile	Cc:	Jacob_W_Klein@…
Guest type:	Linux	Host type:	Windows

Description

Basically, I have some VMs that have several sequential snapshots taken. And sometimes I move those VMs into a group, and sometimes I move them out of a group. It turns out that this causes damage to the .vbox file, specifically the snapshot statefile value.

This is on a Windows 8.1 x64 host.

Inside of the .vbox file, I see lines like:

Every time I move the VM out of a group, and back into a group, the "chain" of ".sav" files for that value keeps growing.

This later causes problems, I believe, when snapshots are either copied in a cloning process, or attempted to be deleted.

Can you please confirm that this "stateFile" value is being corrupted?

Thanks, Jacob

Attachments (2)

boinc_8b569e4326cc68b6 Clone 17 - RNA World Clone 5.vbox (47.0 KB ) - added by Jacob Klein 10 years ago.
boinc_4c2c320f8d4ade95 Clone 17 - RNA World Clone 5.vbox (46.4 KB ) - added by Jacob Klein 10 years ago.

Download all attachments as: .zip

Change History (6)

by Jacob Klein, 10 years ago

Attachment:	boinc_8b569e4326cc68b6 Clone 17 - RNA World Clone 5.vbox added

by Jacob Klein, 10 years ago

Attachment:	boinc_4c2c320f8d4ade95 Clone 17 - RNA World Clone 5.vbox added

comment:1 by Jacob Klein, 10 years ago

I was using the "Oracle VM VirtualBox Manager" to change VM groups, including: Right-clicking a VM and clicking "New Group", right-clicking the group and renaming it, and dragging VMs into a group and out of a group.

comment:2 by aeichner, 8 years ago

Resolution:	→ obsolete
Status:	new → closed

Please reopen if still relevant with a recent VirtualBox release.

comment:3 by Jacob Klein, 7 years ago

Resolution:	obsolete
Status:	closed → reopened

This is still an issue. Reopening.

Here are some steps, that easily reproduce the issue on VirtualBox 5.1.12:

Add Machine
Start
Take Snapshot
Power Off
Restore Snapshot
Clone with options: Full Clone, Everything

... all good so far. Might want to save off the .vbox file, for later comparison.

Right-click Clone, select Group
Right-click "New group", select Ungroup
Right-click Clone, select Group
Right-click "New group", select Ungroup

... at this point, paths are mangled within the VM's .vbox file, I believe. Compare .vbox.

Restore Snapshot (on the Clone)
Try to Start (the Clone)
Get ERROR 1
Try to Remove -> Delete all files (on the Clone)
Get ERROR 2

ERROR 1:

Failed to open a session for the virtual machine boinc_99b9a92e31c966cf Clone 7 Clone 222.

The VM session was closed before any attempt to power it on.

Result Code: E_FAIL (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

ERROR 2:

Failed to remove the virtual machine boinc_99b9a92e31c966cf Clone 7 Clone 222.

Could not delete file 'E:\VirtualBox VMs\boinc_99b9a92e31c966cf Clone 7 Clone 222\Snapshots\2016-12-30T13-07-47-404339300Z.sav\Snapshots\2016-12-30T13-07-47-404339300Z.sav\Snapshots\2016-12-30T13-07-47-404339300Z.sav\Snapshots\2016-12-30T13-07-47-404339300Z.sav\Snapshots\2016-12-30T13-07-47-404339300Z.sav' (VERR_PATH_NOT_FOUND).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: MachineWrap Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Regards, Jacob Klein

comment:4 by Frank Mehnert, 7 years ago

Resolution:	→ duplicate
Status:	reopened → closed

Same problem as in #16745. Will be fixed in 5.1.24. The most recent 5.1.x test builds (>=115382) contain the fix as well.

Note: See TracTickets for help on using tickets.

Download in other formats: