![]() ![]() That’s probably an excessive amount unless you also intend to install applications on its boot partition. If you’ve ever done that, then you know that this VM was born with a 127 GB virtual hard disk. Let’s say you’ve got a brand new systems administrator that created a new virtual machine using Hyper-V Manager’s wizard and just accepted all the defaults. The above image represents a plausible scenario. ![]() ![]() The “shrink” operation, the topic of this article, reduces the physical consumption of a VHDX and reduces the disk size reported to the guest OS. Furthermore, “compact” does not work on fixed VHDX at all. Compacting does not alter the maximum size of the disk, nor does it report anything different to the guest operating system. The “compact” operation squeezes the empty bits out of a dynamically expanding hard disk to reduce the amount of space that it consumes on physical disk. Lots of people confuse “shrink” with “compact” for virtual hard disks. The VHDX “Shrink” Operation Means Something Different than “Compact” Making a virtual hard disk smaller requires a significant level of effort. If need to remove an entire disk, you can do that easily. The most difficult resource to remove from a Hyper-V virtual machine is drive space. On the other hand, you have more work to do if you need to take resources away. You can add or grow almost all virtual resources with very little, and sometimes no impact. I have a standing recommendation for virtual machine resource allocation: start small. ![]()
0 Comments
Leave a Reply. |