Difference between revisions of "Virtual Machines"

Jump to navigation Jump to search
714 bytes added ,  10:42, 5 August 2010
→‎Increase Disk Size: Updated for Win2008 and many disk VM's
(Added "Rename a VM")
(→‎Increase Disk Size: Updated for Win2008 and many disk VM's)
Line 92: Line 92:


== Increase Disk Size ==
== Increase Disk Size ==
 
Increasing the virtual disk size provided to a VM is straight forward (though be aware that snapshots need to be deleted 1st, if any exist)...
Increasing the virtual disk size provided to a VM is straight forward...
# Go into the VM's settings
# Go into the VM's settings
# Increase the size of the disk and apply
# Increase the size of the disk and apply
# Within the VM's OS, rescan the disk, and the new space will be visible
# Within the VM's OS, rescan the disk, and the new space will be visible


The trick is to extend the logical partition, and depending on the original partition type, the options vary. Generally boot or system disks cannot be extended whilst the OS is up, whereas normal data disk can be in later OS's, but this is still not ideal.  Its generally most reliable to plan for system down time, and use a utility to extend the partition whilst its offline. Especially in a virtual environment there is no excuse for not making a backup of the partition 1st. For older Windows machines (excluding Win7 and Win2k8)...
The trick is to extend the logical partition within the OS.  Depending on the original partition type and the OS, the options vary.
 
=== Increase Logical Partition ===
Generally boot or system disks cannot be extended whilst the OS is up, whereas normal data disk can be in later OS's, but this is still not ideal.  Its generally most reliable to plan for system down time, and use a utility to extend the partition whilst its offline. Especially in a virtual environment there is no excuse for not making a backup of the partition 1st.  
 
For Windows 2008 machines this isn't a problem.  


For Windows 2003 machines...
{|cellpadding="4" cellspacing="0" border="1"
{|cellpadding="4" cellspacing="0" border="1"
|- style="background-color:#bbddff;"
|- style="background-color:#bbddff;"
Line 111: Line 116:
|}
|}


=== Increase Logical Partition ===
Download a copy of the GParted Live CD - http://gparted.sourceforge.net/livecd.php, this will need to be booted to by the VM
Download a copy of the GParted Live CD - http://gparted.sourceforge.net/livecd.php, this will need to be booted to by the VM
* '''Note''' There is a bug in some recent versions of GParted (v0.5.0-3 and v0.5.1-1 are known to have issues), whereby the boot fails with the following error, v0.4.6-1 is known to work
* '''Note''' There is a bug in some recent versions of GParted (v0.5.0-3 and v0.5.1-1 are known to have issues), whereby the boot fails with the following error, v0.4.6-1 is known to work
Line 124: Line 128:
# Restart VM and verify all is good
# Restart VM and verify all is good
# Turn off snapshotting
# Turn off snapshotting
=== VM's With Lots Of Disks ===
It can be very difficult to identify the correct disk within VMware to increase when a VM has a large number of VMDK's.
* Disk numbering behalves differently, with Windows starting at Disk 0, and VMware starting a Disk 1
* SCSI ID's will match, but Windows SCSI bus numbers are normally 0, whereas VMware bus numbers will increment (so VM disk 35 (Win disk 34), could be 2:4 in VMware, but 0:4 within the OS)
* Disk size can be a useful method of validation (if differing disk sizes are used)
* Windows drive letters are useless, never assume D: is disk 2 for example


== Rename a VM ==
== Rename a VM ==

Navigation menu