%BOOK_ENTITIES; ]>

Virtual machines are usually created from a template. Users can also create blank virtual machines. A blank virtual machine is a virtual machine without an OS template. Users can attach an ISO file and install the OS from the CD/DVD-ROM. You can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A request parameter, startVM, in the deployVm API provides this feature. For more information, see the Developer's Guide

Log in to the &PRODUCT; UI as an administrator or user. In the left navigation bar, click Instances. Click Add Instance. Select a zone. Select a template, then follow the steps in the wizard. For more information about how the templates came to be in this list, see . Be sure that the hardware you have allows starting the selected service offering. Click Submit and your VM will be created and started. For security reasons, the internal name of the VM is visible only to the root admin.

(XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown. Log in to the &PRODUCT; UI as an administrator or user. In the left navigation bar, click Instances. Click Add Instance. Select a zone. Select ISO Boot, and follow the steps in the wizard. Click Submit and your VM will be created and started.

(For ESX hypervisor in conjunction with vCenter) VMs can be created as either linked clones or full clones on VMware. For a full description of clone types, refer to VMware documentation. In summary: A full clone is a copy of an existing virtual machine which, once created, does not depend in any way on the original virtual machine. A linked clone is also a copy of an existing virtual machine, but it has ongoing dependency on the original. A linked clone shares the virtual disk of the original VM, and retains access to all files that were present at the time the clone was created. The use of these different clone types involves some side effects and tradeoffs, so it is to the administrator's advantage to be able to choose which of the two types will be used in a &PRODUCT; deployment. A new global configuration setting has been added, vmware.create.full.clone. When the administrator sets this to true, end users can create guest VMs only as full clones. The default value is false. It is not recommended to change the value of vmware.create.full.clone in a cloud with running VMs. However, if the value is changed, existing VMs are not affected. Only VMs created after the setting is put into effect are subject to the restriction.