2,187
edits
Difference between revisions of "Virtual Machines"
Jump to navigation
Jump to search
Added "Clone a VM"
(→Troubleshooting: Added "Can't Customise") |
(Added "Clone a VM") |
||
| Line 154: | Line 154: | ||
# <code> vmware-cmd -s register /vmfs/volumes/datastore/vm-new/vm-new.vmx </code> | # <code> vmware-cmd -s register /vmfs/volumes/datastore/vm-new/vm-new.vmx </code> | ||
The above was taxed from http://www.yellow-bricks.com/2008/02/10/howto-rename-a-vm/ | The above was taxed from http://www.yellow-bricks.com/2008/02/10/howto-rename-a-vm/ | ||
== Clone a VM == | |||
This can done as | |||
* '''Hot clone''' - Source VM is left running, its disks are quiesced, and cloned. Can cause problems as new machine behaves as if it was ungracefully shutdown when first started, but normally successful. Source machine needs to be relatively quiet. | |||
* '''Cold clone''' - Source VM is shutdown 1st, preferable to a warm clone if possible. | |||
=== Snapshots and Cloning === | |||
Snapshots are deleted during a clone, in that cloning a machine that has existing snapshots results in the post-snapshot changes being merged into the new machine. | |||
In order to retain the snaphosts, the virtual machine needs to be cloned manually ''(untested procedure!!)''... | |||
# Copy all of the VMs files into a new directory (using vmkfstools --nosparse option). | |||
# Correct the .vmx file to match new paths, update VM name, and delete the UUID line (VMware will prompt to generate a new one when the VM is started). | |||
# Register the new VM in vCentre and double check the VM is as expected. | |||
# Power on (you'll get an IP conflict if its on the same portgroup as the original) | |||
== Shutdown VM via Service Console == | == Shutdown VM via Service Console == | ||