If you use the default configuration when making a virtual machine, then the problem you are facing now is the exhaustion of physical space on MAC OS X, which is related to VMware's dynamic growth disk technology. As we all know, the "hard disk" of a virtual machine is actually just a file (*. Vmdk file) represents the hard disk on the host. When creating a virtual machine's hard disk, there is a key choice: allocate all the space now and use dynamic growth-"allocate all the space now" is actually very simple, that is, directly put *. The vmdk file on the host is as big as the hard disk of the virtual machine. For example, if I create a 50G virtual machine hard disk under the 80G host hard disk using the "immediately allocate all space" method, then my host can use hard disk space. "Use dynamic growth" is to make *. With the use of virtual machines, vmdk files become larger and larger. For example, when I create a hard disk with a virtual machine size of 50G by "using dynamic growth", *. The vmdk file is small at first. When I use this * to install the 1.86G system into a virtual machine. Vmdk file as the only hard disk, this *. The vmdk file will grow to1.86g. When I put 20G of things in it, this *. The vmdk file will grow to 2 1.86G but, of course, because I can't make this *. For vmdk files larger than 50G, I can't fit anything larger than 28. 14G. By default, VMware uses Use Dynamic Growth to create a virtual machine's hard disk. At this point, I believe that the landlord should also understand the problem-although *. The vmdk file of the landlord's virtual machine has not reached the growth limit (so it still shows 18G), and there is no room for this * in the actual space of the host. Vmdk files continue to grow. In addition: the phenomenon mentioned on the first floor is not caused by Microsoft's whimsy, but because hard disk manufacturers use 1000 as the conversion value between adjacent single bits (except bits to bytes, the same below) for convenience, while software manufacturers all over the world still use the original 1024 as the conversion value between adjacent two units. That is to say, the hard disk with the nominal 1MB loses 24 software standards KB and 24000B MB of 1MB that the software actually thinks. Then the loss will be more serious after amplification to G and T levels. If you are interested, please use your own calculator to calculate, and the result will be amazing, so that you can understand why you have never bought "sufficient" storage equipment (except memory).