#10849 closed defect (obsolete)
Changing VM names breaks snapshot path, Causes ProgressProxy error
回報者: | Era Scarecrow | 負責人: | |
---|---|---|---|
元件: | virtual disk | 版本: | VirtualBox 4.1.20 |
關鍵字: | ProgressProxy, Rename, Renaming, Multi-Attach | 副本: | |
Guest type: | Windows | Host type: | Windows |
描述
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.
更動歷史 (2)
comment:2 9 年 前 由 編輯
狀態: | new → closed |
---|---|
處理結果: | → obsolete |
Please reopen if still relevant with a recent VirtualBox release, looking at the other mentioned ticket this should be actually fixed for a long time now.
Related or identical issue: Ticket #10264