Hard drive resizing of rotten mud virtual machines

I am writing this blog today to avoid so many detours when using virtual machines to resize Virtual Machine hard disks for lunch. Environment Introduction: Virtual Machine: VMware Workation 8 operating system: windows server 2008 hard disk capacity: 10 Gwindows server 2003 hard disk capacity: 6 GB the correct way to resize a virtual machine hard disk is: delete all snapshots of the VM. Otherwise, the system will prompt you that you cannot resize the hard disk of the VM with the snapshot. To give you a real picture of the operation step, I will first perform the following: first, we will scale up the virtual machine windows server 2008 with a snapshot, and check the system prompts, is it consistent with what I mentioned above. From the above, we can see that the system does prompt that we cannot resize hard disks for virtual machines with snapshots. Now we can resize windows server 2003 for a virtual machine without a snapshot to see how it works. At the same time, one thing I want to talk about here is that VMware 8 supports resizing hard disks of cloned virtual machines. Take a look at the following operations: we can see that if no virtual machine has a snapshot, it can expand the capacity of the Virtual Machine hard disk. At the same time, we have another problem. That is, if we are on a cloned virtual machine, can we expand the disk capacity of the virtual machine? The answer is no. To expand the capacity of a VM's hard disk, you must be on the primary Vm, rather than the cloned VM. To verify this argument, let's look at the experiment: Then, we will continue the experiment. That is, some operations and steps after expansion. Our current windows server 2003 Virtual Machine hard drive is 6 GB, And it will reach 7 GB after expansion. Now, after the host windows server 2003, let's see what the disk is like in the system. We can see that the computer is only 6 GB in size, but we noticed that 1 GB of space is not allocated in disk management, the 1 GB Space is our capacity expansion. Next, we will allocate the 1 GB space to the edisk. We can adjust it through the partition assistant. (For how to use the partition assistant, you can see my other article "rotten mud: easily resizing the disk C space of the server".) We have successfully resized the hard disk of the Virtual Machine windows server 2003. There is another problem, that is, the clone machine. Now let's start the clone server and see how it works. We can see that the clone server cannot be started. Therefore, we can conclude that the clone server cannot be started after the capacity of the VM's hard disk is adjusted. That is to say, all previous clone servers need to be deleted and re-created. The above are the problems we should pay attention to when resizing the virtual machine's hard disk. So can we reduce the disk space? Let's try and see if we can. Now I still follow the above steps.

We can see that we can only resize the hard disk space, but not smaller.



From: http://lanni654321.blog.51cto.com/526870/759014