VBoxManage --compact option destroyed my vdi image!!!

[danythebat]

I'm trying the VBoxManage --compact option that is reactivated in VBox v. 2.2.2 and the output was:

VBoxManage...
10% 20% 30% .... 90%
C:\>

So i looked at the VDI file and it was shrinked from 3GB to 34MB... It was a fully working Ubuntu Desktop 9.04 x86, now is a "non bootable disk image"

I'll try it on other vdi so I can give you more useful informations and...
...be carefull with your vdi!!!

UPDATE:
I try another image but this time VBoxManage fail at 0% saying that

Instruction at "0x10006ee9" referred to the memory location "0x011d2000". Memory cannot be "written".

(sorry for the bad translation )

PS: the command was

Code: Select all

VBoxManage.exe modifyhd 6c150247-da04-4408-8ff2-14dd188e077f --compact

6c150247-da04-4408-8ff2-14dd188e077f is the vdi ID

[vbox4me2]

Instruction at "0x10006ee9" referred to the memory location "0x011d2000". Memory cannot be "written".

This specific error usually mean you have a corrupted .exe/dll of some sort, mostly caused by harddisk bad blocks, check your windows event logs.

[danythebat]

I've checked my physical disks: they are all ok... the vdi is working fine (I've also moved it on another disk) but I cannot compact it. I can't imagine why the first vdi I shrinked is gone...

[bitummen]

ubuntu command:
command: VBoxManage modifyhd --compact /media/HardDrives/vbox/massey/massey_50gig.vdi

not used the windows version

VBoxManage.exe modifyhd 6c150247-da04-4408-8ff2-14dd188e077f --compact

[danythebat]

I tryied it on 6 different vdi's but sometimes it returns

VBoxManage...
0% ...

and exit without any error, other times it returns the same message then popup the window with the message

Instruction at "0x10006ee9" referred to the memory location "0x011d2000". Memory cannot be "written".

It's not related to the vdi that I try to compact, I can receive the first or the second message on the same vdi (random):
I've no idea about this strange behavior...

[klaus]

Was able to reproduce the crashes (heap corruption), but not the VDI corruption. However as it's unpredictable what happens in the case of a heap corruption I can't rule out that it's possible that VDI files can be destroyed.

[carmelov]

I'am the same problem:
mandriva.vdi destroyed using a DOS prompt in Xp host, and this command:
vboxmanage modyfyvdi mandriva.vdi compact

VBoxManage...
10% 20% 30% .... 90%
c:\

And the file is reduced from 3.92 G to a 196K file (destroyed)

If I use clonevdi the problem not occour.