VirtualBox

Ticket #10849 (new defect)

Opened 20 months ago

Last modified 20 months ago

Changing VM names breaks snapshot path, Causes ProgressProxy error

Reported by: Era Scarecrow Owned by:
Priority: minor Component: virtual disk
Version: VirtualBox 4.1.20 Keywords: ProgressProxy, Rename, Renaming, Multi-Attach
Cc: Guest type: Windows
Host type: Windows

Description

I'm not sure if it didn't work at all or if this is because the original (base) VM was running at the time. But here's the steps that took place.

Created new (base) VM Changed Drive to Multi-Attach (after setting the VM how I wanted it) Created new VM attached to first VM's hard drive (not cloned)

Once a snapshot/difference was generated, changing the VM of the second (attached) VM.

Results:

The Base VM (with the original hard drive image and redivided snapshopts) had all it's snapshot attachments pointing to their original directories. Example:

<HardDisk uuid="{xxx}" location="C:/Users/Era/VirtualBox VMs/Base/DirectVM.vdi" format="VDI" type="Normal">

<HardDisk uuid="{5xxx}" location="C:/Users/Era/VirtualBox VMs/newVM1/Snapshots/{5xxx}.vdi" format="VDI"/>

<HardDisk uuid="{7xxx}" location="C:/Users/Era/VirtualBox VMs/newVM2/Snapshots/{7xxx}.vdi" format="VDI"/>

</HardDisk>

In this case if newVM1 or newVM2 gets renamed, the base system didn't update the directory location to their new spot(s) since the directory changed. Fixing it manually is trivial in notepad++ but annoying.

Change History

comment:1 Changed 20 months ago by Technologov

Related or identical issue: Ticket #10264

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use