03-31-2016, 05:42 AM
(This post was last modified: 03-31-2016, 05:47 AM by stop0x0000000a.)
I've been using VB for ~5 years, prefer export/import ova.
1) ova = zipped virtual machine folder (or tar.gzipped, you may unpack it manually), takes less space in case you need a backup.
2) ova it is an open format, you may copy your VM to VMWare or Hyper-V host.
3) you've got additional CRC here, to be sure the files are copied fully and not corrupted.
Tried once to run VMWare images with VB, worked fine for me.
VM shrinking is a matter of file deletion, deleted files are still present on disk, so your guest still takes that space.
So you need to:
1) Defrag (for windows guests)
2) Fill empty space with zeros
3) Run VBoxManage then
See here:
https://www.maketecheasier.com/shrink-yo...ualbox-vm/
1) ova = zipped virtual machine folder (or tar.gzipped, you may unpack it manually), takes less space in case you need a backup.
2) ova it is an open format, you may copy your VM to VMWare or Hyper-V host.
3) you've got additional CRC here, to be sure the files are copied fully and not corrupted.
Tried once to run VMWare images with VB, worked fine for me.
VM shrinking is a matter of file deletion, deleted files are still present on disk, so your guest still takes that space.
So you need to:
1) Defrag (for windows guests)
2) Fill empty space with zeros
3) Run VBoxManage then
See here:
https://www.maketecheasier.com/shrink-yo...ualbox-vm/