Virtual machines simulate real disk operations, and all written and uncovered disks will grow and expand (dynamic disks).
When I use VPC, I usually hang three virtual disks after completing the system. Starting from the third system disk, I delete the unnecessary files of the disk to be processed, and then clone it to the second disk (the basis of slimming). Then I create a differentiated disk based on the second disk, and backup and restore the smallest image, instantly restoring the pure system.
When you are using a VM, you can use a special slimming tool, precompact.exe, to clean up the "no data area" of the disk (actually the file group marked as deleted in the header), and then use a special "disk defragmentation" for the VM.
Respondent: k4me- ranking125-617:14.
##############3
supplement
Do you still have 8G space on the actual disk where you store the virtual disk of the virtual machine?
##############
Supplement 2
Precompact.exe used it first? It is useless not to clear the deleted files. Also, do you use the VM disk utility for disk optimization? It's not disk defragmentation in the virtual machine, is it?
VM is not a good thing, I can't remember it clearly.
Virtual machines eat disk space very quickly, which is slightly different from real disks. After deleting a file, once it needs to be written to disk, the location of the deleted file will be overwritten. In the virtual machine, whether you write this location or not, as long as it has been used in the past, it will always occupy this location.
Make more room for virtual machines. According to your different operation requirements, you usually need 300 m-10 g. If there is cloning or disk testing, the required capacity will be doubled.
In addition, you can create a new virtual disk, let the virtual machine hang two disks, and then use ordinary cloning to copy only visible files. After cloning, reset the virtual machine configuration, suspend only the newly created disk, and take a snapshot of the system immediately after startup.
###########
I summarized that cloning is the most cost-effective, fastest and life-saving disk (the sorting process is about 65,438+0,000 times of Birkelund's disk consumption), and the files are sorted automatically after cloning.
The whole process of making a virtual system is roughly as follows.
1, create a normal A system.
2. Hang the A disk in the B system, and delete the A file to the minimum (it will not affect the operation and all the functions that the virtual machine needs to provide in the future). (VM can directly hang the disk in the real system to run)
3. create virtual disk B.
4. clone A-> B
5. Delete A, create B's differential disk C, back up C 1, and hang up the virtual system system disk C. 。
After that, the system needs to be restored, and "copy C 1 C" is just right, which is 100 times faster than the system snapshot.
As for the disk space, hehe, it only needs the size of the original virtual system when cloning, and it is quite cool to delete the original virtual disk after cloning. ....
If the requirements for extended functions are not high, it is strongly recommended to use VPC 5.1before Microsoft acquisition (5.2 people think the stability is not good).