Templates can be edited at any time. However, if a template was cloned, you must first detach the clones before you can edit it. For more information, see Section 8.2, Detaching Clones from Templates.
The following steps include information for all possible template fields and pages. Depending on VM type, you might not be able to edit the template or the template might not have all of the fields and pages.
To edit a template, run the Virtual Machine Properties Wizard:
If you want to retain your edits on a VM, click the VM Client, right-click the VM that you want to edit, then select .
view in theDo one of the following in the
view to start the wizard:Select a template, then click the button.
Select a template, then click
> .Select a template, then press Ctrl+E.
Right-click any listed template, then select
.The following wizard page is displayed:
If a template currently has cloned VMs associated with it, you cannot edit the template. The following dialog box is displayed when you attempt to edit such a template:
After noting which VMs are involved, click Section 8.2, Detaching Clones from Templates.
to close the dialog box, then determine whether you want to detach those VMs in order to edit the template. For more information on detaching the clones from the template in the Development Client, seeFill in the available fields:
Description: Note the purpose and any other specifics you might require of the template. These notes apply to all versions of this template.
Guest Operating System: The clones of the template inherit the operating system of the VM from which this template was created. Therefore, you should only change it if it is incorrect. The following are supported:
There is also an “(other)” option for the following:
Additional Arguments: This field applies only to paravirtual installations. These are Linux install arguments, which are operating system parameters similar to the information entered in a GRUB boot loader when running on bare hardware in SUSE Linux Enterprise Server (SLES) and SUSE Linux Enterprise Desktop (SLED). Additional network installation information can be added here, which is used during the build process to find the installation source for the VM build process.
Click
to display the following wizard page:Fill in the available fields to define the kind of hardware to be virtualized for the template:
Processors: The number of virtual processors the template has.
Memory Size: The amount of virtual RAM the template has, or paravirtualized memory that can be used by the VM if it is paravirtualized.
Max: The amount of virtual RAM the template has, or paravirtualized memory that can be used by the VM if it is paravirtualized.
Display Driver: The properties of the VM’s display. If you have chosen paravirtualization for this VM, your only option is
. If you have chosen full virtualization, you can select between or the on-board VGA. If you do not need a display, you can turn off the display on a fully virtualized machine.Remote Console Password: The password for remotely controlling the VM. Use the two fields to confirm that the password is typed correctly.
Click
to display the following wizard page:The example shown is for a template.
The Storage Devices page is for defining the hard drives and CD or DVD drives that you want to include in the template profile. The first device must always be a hard disk that cannot be removed unless another hard disk has been put into the first slot. This is the only disk (Disk 0) that is stored and version controlled. All other disks are virtual and are created upon launching the VM. You can add any other storage devices you want to the template and move them according to priority in the list.
To fill in the storage device information, select a task from the following table:
Tasks |
Steps |
Additional Details |
---|---|---|
Adding a hard disk to your VM |
|
The following restrictions apply per VM:
WARNING:Do not select iSCSI or NPIV when defining or editing a template. This causes all VMs cloned from the template to use the same iSCSI or NPIV location, thus corrupting the disk. While adding an additional NPIV disk to a VM, ensure that the disk values for Fabric ID, World Wide Name, Target ID, and LUN are unique for each NPIV disk of the VM. Creation of a block-based VM is not supported for NPIV. |
Adding a CD-ROM or DVD ROM to your VM |
|
IMPORTANT:If you add a CD-ROM or DVD-ROM, any VMs created from this template can only be moved, migrated, or used to create another template if the CD-ROM’s or DVD-ROM’s ISO or image is accessible through shared storage. |
Rearranging the order in which each storage device is accessed |
|
The first storage device in the list must be a hard disk, which is the only one actually stored in the VM image. |
Deleting a storage device |
|
Removes the selected storage device from the table. WARNING:If the storage device is based on a disk image, that could also be deleted. To preserve the disk image, manually copy it to another location before deleting the storage device. |
Click
to display the following wizard page:The example shown is for a template.
The network devices are added, deleted, and defined on the Network page, where you add specific information about your network connections or intended network connections for your template. You can define more detailed NIC settings in your auto-install files or when performing a guest installation.
To fill in the NIC information, select a task from the following table:
To complete and close the wizard, click
.You can click
to make further changes before applying the edits.Applies the wizard configuration changes and saves the template in the
view.Focus is returned to the
view after you exit the wizard with the edited template selected in the list.After editing a template, you can then use it to clone new VMs. For more information, see Section 8.1, Cloning Templates.