4.7 VM Templates Item

The management pane includes the default VM Templates perspective, and toolbars that enable you to perform various configuration or management tasks specific to virtual machine templates.

4.7.1 VM Templates Perspective

The VM Templates perspective lists the virtual machine templates configured in your environment. The following columns are displayed in the management pane:

  • Name: The name that has been configured for the template.

  • Domain Type: The domain type.

  • Max. Memory (MB): The maximum memory that can be allocated.

  • Memory (MB): The memory that is allocated.

  • Max. Processors: The maximum number of CPUs that can be allocated.

  • Processors: The number of CPUs that are allocated.

  • Operating System: The operating system type.

  • Description: The description of the template.

An arrow displays next to each virtual machine template in the table. Click the arrow to expand the view and display the Configuration, Networks, and Disks tabs. These tabs display the following information:

Configuration

  • Name: The name that has been configured for the virtual machine.

  • Operating System: The operating system type.

  • Max. Processors: The maximum number of CPUs that can be allocated.

  • Processors: The number of CPUs that are allocated.

  • Max. Memory (MB): The maximum memory that can be allocated.

  • Memory (MB): The memory that is allocated.

  • Processor Cap: The percentage value configured for the processor cap.

  • Priority: The CPU priority allocated for the virtual machine.

  • Mouse Type: The mouse type configured for the virtual machine.

  • Domain Type: The hypervisor and virtual machine type configured for the virtual machine.

  • High Availability: Whether or not the High Availability flag is set for the virtual machine.

  • Huge Pages: Whether or not the Huge Pages flag is set for the virtual machine.

  • Boot Order: The configured boot order for disks attached to the virtual machine

  • Network Boot Path: The network boot path configured for the virtual machine.

  • Restart Action On Crash: The configured restart action in the instance that the virtual machine crashes.

  • Restart Action On Power Off: The configured restart action in the instance that the virtual machine receives the power-off signal.

  • Restart Action On Restart: The configured restart action in the instance that the virtual machine receives the restart signal.

  • ID: The ID allocated by Oracle VM Manager for the virtual machine.

  • Origin: The URL that was used to import the virtual machine or template, if it was imported.

  • Description: The description of the virtual machine.

  • Config File Absolute Path: The absolute path to the virtual machine configuration file.

  • Config File Mounted Path: The mount point where the virtual machine configuration file is located on an Oracle VM Server.

Networks

  • VNIC: The name of a VNIC configured for the virtual machine.

  • Ethernet Network: The name of the ethernet network that the VNIC is attached to.

  • IP Addresses: IP addresses configured for the VNIC.

Disks

  • Slot: The slot number for the disk.

  • Disk Type: The type of disk that is attached.

  • Name: The name of the disk within Oracle VM Manager.

  • Size (GiB): The size of the disk.

  • Repository: The repository where the disk is located.

  • Absolute Path: The absolute path to the location of the disk.

  • Mounted Path: The mount point where the disk is located on an Oracle VM Server.

  • Location: The location of the disk as reported by Oracle VM Manager.

This perspective includes a toolbar that consists of the following options:

Table 4.6 VM Templates Perspective Toolbar Icon Options

Toolbar Icon Option

Icon

Description

Import VM Template...

Import VM Template... icon

Displays the Import VM Template dialog box. Use this option to import a virtual machine template.

Edit Selected VM Template...

Edit Selected VM Template... icon

Displays the Edit VM Template dialog box. Use this option to edit a virtual machine template.

Delete Selected VM Template

Delete Selected VM Template icon

Displays the Delete Confirmation dialog box. Use this option to delete the selected virtual machine template.

Clone Template...

Clone Template icon

Displays the Clone Template wizard. Use this option to clone, or create a copy of, a virtual machine template.

Move Template...

Move Template icon

Displays the Move Template wizard. Use this option to move the disks and configuration file to another storage repository.

Manage Clone Customizers...

Manage Clone Customizers... icon

Displays the Manage Clone Customizers for VM dialog box. Use this option to manage the clone customizers for a virtual machine template.

Display VM Config File Content...

Display VM Config File Content... icon

Displays the VM Config File Content dialog box. Displays a read-only view of the configuration file for the selected virtual machine. Use this option to view the content of the virtual machine configuration file.

Help

Help icon

Displays context sensitive help.


4.7.1.1 Import Template

To import a virtual machine template:

  1. The Oracle VM template should be accessible to your Oracle VM environment from a location that can be reached using HTTP, HTTPS or FTP.

  2. Click the Repositories tab. Select the repository in which to store the template. Select VM Templates in the navigation tree.

  3. Select Import VM Template... Import VM Template... icon in the toolbar in the management pane.

  4. The Import VM Template dialog box is displayed. Select or edit the following:

    • VM Template URLs: The URLs for the templates. The URL schemes supported are HTTP, HTTPS, and FTP. For example:

      http://example.com/mytemplate.tgz

      To import a template using FTP, use the standard FTP syntax:

      ftp://user:password@server/path/filename.tgz

      If your template files are split into multiple compressed files [1] , concatenate those files and enter the URL for the concatenated file, for example to concatenate a number of compressed files to one compressed file, enter

       $ cat template.tgz.1of3 template.tgz.2of3 template.tgz.3of3 > template.tgz

      Then enter the URL to the single compressed template file, in this case, template.tgz.

      To import a template that is not compressed as a single file, each component must be a complete file (if not, concatenate them to one file), for example to enter a virtual disk image and a virtual machine configuration file that together make up a complete template, you could enter:

      http://myexample.com/System-sda.img
      http://myexample.com/vm.cfg

      Each template component should be listed on a new line. Each URL must be a reference to a complete file.

      Alternatively, you can place all the files in the same directory on a web server, and import the vm.cfg file, and all the supporting virtual disk files are also imported.

    • Proxy: The IP address or hostname of an optional proxy server to use when importing the template.

    Click OK to import the template. When the import job is complete, the new template is displayed in the table in the management pane. Expand the table row to see more information about the template.

4.7.1.2 Edit Template

You can edit a virtual machine template to change the configuration, networking, disks and boot order.

To edit a virtual machine template:

  1. Click the Repositories tab. Select the repository in which the template is saved. Click VM Templates in the navigation tree.

  2. Select the template to edit in the table in the management pane and click Edit Selected VM Template... Edit Selected VM Template... icon .

  3. The Edit VM Template dialog box is displayed. The dialog has four separate tabs:

    • Configuration: This tab allows you to edit the following information:

      • VM Template Name: The name of the template. The maximum name length is 256 characters and may contain any character. The name need not be unique.

      • Enable Huge Pages: Whether to enable HugePages. If you enable HugePages, you must disable support for HugePages in the guest operating system. This option is not available for virtual machines in SPARC-based server pools.

      • Description: An optional description of the template.

      • Operating System: The guest operating system of the virtual machine in the template. This setting enables or disables certain virtual machine settings that your guest operating system may require.

      • Mouse Device Type: The mouse type to use for the template. This option is ignored if using a SPARC-based server pool.

      • Domain Type: The domain type of the virtual machine. Oracle recommends you create paravirtualized virtual machines if possible, as the performance of a paravirtualized virtual machine is superior to that of a hardware virtualized machine guest. This option is not available for virtual machines in SPARC-based server pools.

        • XEN_HVM: Hardware virtualization, or fully virtualized. When you select this option you must supply an ISO file in a repository (in the Arrange Disks step of the wizard) from which to create the virtual machine. See Section 4.5.1.1, “Import ISO” for information on importing an ISO file into a repository.

        • XEN_HVM_PV DRIVERS: Identical to XEN_HVM, but with additional paravirtualized drivers for improved performance of the virtual machine. See What are Virtualization Modes or Domain Types? in the Oracle VM Concepts Guide for more information about using paravirtualized drivers. This domain type is used to run Microsoft Windows guest operating systems with an acceptable performance level.

        • XEN_PVM: Paravirtualized. Enables you to select a location for the mounted ISO file from which to create the virtual machine. Before you create the virtual machine using the paravirtualized method, mount the ISO file on an NFS share, or HTTP or FTP server. You supply the location of the mounted ISO file in the Network Boot Path field in the Boot Options step of the wizard. For information on creating a mounted ISO file, see Provisioning ISO Files for PVM Guest Installations in the Oracle VM Administrator's Guide.

        • OVM/SPARC: This domain type should be selected if the server pool and hypervisors use Oracle VM Server for SPARC as the hypervisor instead of Oracle VM Server for x86.

        • Unknown: This hypervisor should be selected if the domain type is unknown.

      • Max. Memory (MB): The maximum size of the memory the virtual machine is to be allocated. When you edit a running virtual machine, this is the maximum amount of memory that can be allocated. This value must be between 32 and 2000000. For x86-based virtual machines, this value is incremented by 32 each time you click the up arrow, and, conversely, decreased by 32 if you click the down arrow. For SPARC-based virtual machines, the up arrow adds 512, and the down arrow subtracts 512.

      • Memory (MB): The size of the memory the virtual machine is to be allocated. This is the memory allocation to use when starting the virtual machine. This value must be between 32 and 2000000. For x86-based virtual machines, this value is incremented by 32 each time you click the up arrow, and, conversely, decreased by 32 if you click the down arrow. For SPARC-based virtual machines, the up arrow adds 512, and the down arrow subtracts 512. You can change this when editing a running virtual machine, up to the value of the maximum memory set in the previous field. For HVM guests, increasing or decreasing the memory requires a restart of the virtual machine. For PVM guest, no restart is required.

      • Max Processors: The maximum number of processors to be used by the virtual machine. The number of processors is expressed in number of physical CPU cores. The maximum number of processors depends on the domain type, as follows:

        • PVM: 256.

        • HVM: 128.

        • PVHVM: 128; or 32 if using Oracle VM Paravirtual Drivers for Microsoft Windows.

        • OVM/SPARC: Equivalent to the number of available CPUs on the server.

        You cannot change the maximum number of processors if the virtual machine is running. To edit this value, you must first stop the virtual machine.

      • Processors: The number of processors to be used by the virtual machine. The number of processors is expressed in number of physical CPU cores, up to the value of Max. Processors.

        You can change the number of processors if the virtual machine is running.

      • Priority: The CPU priority of the virtual machine. You can select a high (100), intermediate (50), or low (1) priority for the virtual CPUs, or a self-defined priority, by moving the slider. The higher the priority, the more physical CPU cycles are given to the virtual machine.

        This option is ignored if using a SPARC-based server pool.

      • Processor Cap %: Increase or decrease the percentage to which the virtual CPUs can receive scheduled time. This parameter defines the maximum percentage to which the virtual CPUs can receive scheduled time. You can select a high (100), intermediate (50), or low (1) percentage of scheduled time for the virtual CPUs, or a custom percentage, by moving the slider. Use this parameter to keep low priority virtual machines from consuming too many CPU cycles on a virtual machine server.

        This option is ignored if using a SPARC-based server pool.

        The Priority and Processor Cap% parameters are passed to the Xen hypervisor for use by the credit scheduler, which automatically load balances guest VCPUs across all available physical CPUs using an algorithm that combines these two parameters. Therefore, these parameters are a key factor for the performance of the virtual machine on x86 hardware.

        On SPARC, each virtual machine uses dedicated physical CPU threads and CPUs are not shared between virtual machines, being exclusively assigned to a single virtual machine.

      • Restart Action on Crash: The action to perform if a virtual machine crashes. This option is only available for virtual machines that are running on the Xen hypervisor and that have been configured to run on a particular Oracle VM Server, otherwise, this option is ignored. Options include the following:

        • Restart: Restarts the virtual machine operating system.

        • Stop: Stops the virtual machine. If Enable High Availability is selected, this option is not available.

        • Restart After Dump: Restarts the virtual machine operating system after first creating a core dump file for the virtual machine.

        • Stop After Dump: Stops the virtual machine after first creating a core dump file for the virtual machine. If Enable High Availability is selected, this option is not available.

        Core dump files are saved to /var/xen/dump on the Oracle VM Server where the virtual machine is hosted. Each core dump file is named uniquely so that files are not overwritten. This can use up disk space rapidly. You must make sure there is either enough disk space available at this path on the Oracle VM Server where the virtual machine will run; or you should mount additional storage at this path to avoid using up disk space required to host dom0.

    • Networks: This tab allows you to manage which networks to use. Use the arrow buttons to move the networks between the Available Ethernet Networks field and the Selected Ethernet Networks field. If no networks are available, you must first create a network with the virtual machine role as a dedicated network for virtual machine traffic is required. See Section 5.1.1, “Create New Network” for information on creating a network.

    • Disks: This tab allows you to edit the storage configuration of your template, such as virtual disk, physical disks, and ISO files. On a separate slot, add one or more of the following disk types:

      • Empty: An empty slot.

      • Virtual Disk: This allows you to add or create a virtual disk. Virtual disks may be shared by virtual machines, or only available to a single virtual machine.

      • Physical Disk: The physical disks are the disks in a storage array. Physical disks may be shared by virtual machines.

      • CD/DVD: This adds an ISO file in a storage repository and can be used to create HVM and PVHVM virtual machines. When creating a virtual machine from an ISO file, you must use a single file. Installations that span multiple ISO files are not supported. ISO files cannot be used to create PVM virtual machines.

      Add or create any virtual disks to use as the virtual machine's hard disk, select any physical disks to add, and select any ISO files to use to create the virtual machine. Add the disks in the order they should appear in the virtual machine. The disk with the boot partition or installation media should be the first disk listed. An HVM guest can have up to four disks, including empty CD/DVD drives. A PVM guest can have up to 104 disks. A PVHVM guest can have up to 107 disks. An OVM/SPARC guest can have up to 1024 disks. Only one slot can contain an empty CD/DVD.

      To create or add a virtual disk:

      1. To create a virtual disk, select Virtual Disk from the Disk Type drop-down list and click Create a Virtual Disk Create a Virtual Disk icon .

      2. The Create Virtual Disk dialog box is displayed. Enter or select the following to create a virtual disk:

        • Repository: The repository in which the virtual disk is to be created.

        • Virtual Disk Name: The name of the virtual disk to be created and made available to the virtual machine. See How are Virtual Disks Managed? in the Oracle VM Concepts Guide for more information about using virtual disks.

        • Size (GiB): The disk size of the virtual disk, in GiB.

        • Description: A description of the virtual disk.

        • Shareable: Whether the virtual disk should be shareable (read/write) with other virtual machines.

        • Allocation Type: Whether to use a Sparse Allocation or Non-sparse Allocation. Sparse Allocation creates a sparse disk, so the size of the disk is initially small and increases as it is used. Sparse allocation is faster than using Non-Sparse Allocation when creating a virtual machine. Non-Sparse Allocation creates the entire disk when the virtual machine is created, and so is slower than creating a sparse disk. This information is not persistent and is not stored within Oracle VM Manager, so it is not possible to determine what allocation type was used to create a virtual disk in the future.

        Click OK.

      3. To search for an existing virtual disk to add to the virtual machine, click Select a Virtual Machine Disk Select a Virtual Machine Disk icon . The Select a Virtual Machine Disk dialog box is displayed. Select the virtual disk to use and Click OK.

        Note

        If your virtual machine needs more than one disk, you can create the disk(s) afterwards in the repository, and add them to the virtual machine. See Section 4.9.1.1, “Create Virtual Disk” and Section 3.5.2.1, “Edit Virtual Machine” for more information on creating a virtual disk and editing a virtual machine.

      To add a physical disk:

      1. To add a physical disk to the virtual machine, select Physical Disk from the Disk Type drop-down list. Click Select a Virtual Machine Disk Select a Virtual Machine Disk icon . The Select a Physical Disk dialog box is displayed. Select a physical disk from the list of available disks. If you want to leave the slot empty, select Leave Slot Empty. Click OK.

      To add an ISO file:

      1. To add an ISO file to the virtual machine, select CD/DVD from the Disk Type drop-down list. Click Select a Virtual Machine Disk Select a Virtual Machine Disk icon . The Select an ISO dialog box is displayed. Select a Iso file from the list of available files. If you want to leave the slot empty, select Leave Slot Empty. Click OK.

        Note

        When adding an ISO file to an existing virtual machine, the ISO file is available to the operating system, but may not be mounted. To access the ISO file, you may need to mount it, for example:

        # mkdir /cdrom
        # mount -o loop /dev/xvdb /cdrom
    • Boot Order: This tab allows you to edit the boot media order for your virtual machine.

      Select the boot media order for your virtual machine.

      If you are creating a hardware virtualized machine virtual machine (HVM), you can choose the PXE boot option. If so, remember to put PXE first in the Select your boot options field, and change the boot order again after installation and before rebooting the virtual machine. To use PXE, you must configure a PXE/tftp environment to offer the necessary boot media and instructions to the virtual machine.

      If you are creating a paravirtualized virtual machine (PVM), you also have the Network option available (not shown in here). If so, specify Network to be at the top of the right-hand-side column, and enter the location of the mounted ISO file from which to perform the operating system installation in the Network Boot Path field (also not shown in here), for example

      http://example.com/Enterprise-R6-U1-Server-x86_64-dvd.iso/

      For information on creating a mounted ISO file, see Provisioning ISO Files for PVM Guest Installations in the Oracle VM Administrator's Guide.

      You cannot use the Network Boot Path field to boot a virtual machine using PXE. This field can only be used to specify the path to a mounted ISO file to use when installing a PVM guest.

  4. When you have finished editing the virtual machine template, click OK to save the changes, or Cancel to exit out of the dialog without saving any changes.

4.7.1.3 Delete Template

You can delete a virtual machine template, and the virtual disk associated with it.

To delete a virtual machine template:

  1. Click the Repositories tab. Select the repository in which the template is saved. Click VM Templates in the navigation tree.

  2. Select one or more templates in the table in the management pane and click Delete Selected VM Template... Edit Selected VM Template... icon .

  3. The Delete Confirmation dialog box is displayed. Select the virtual disks associated with the templates you want to delete, if any. Click OK to delete the templates.

4.7.1.4 Clone a Virtual Machine or Template

Cloning a virtual machine or a template means making a copy of it, so that you can create multiple virtual machines or templates from the original.

A clone can also be performed using two other file copy methods: sparse copy, and non-sparse copy. These two cloning methods can be used when cloning from and to different repositories, and when the storage used for the storage repository uses a generic Oracle VM Storage Connect plug-in. These cloning methods are slower than thin cloning, but more versatile.

Note

The virtual machine cloning procedure below uses the same dialog box to clone a virtual machine and a template.

To create a clone of a virtual machine or template:

  1. Select the virtual machine or template to clone and display the Clone dialog box. You display this dialog box from different locations, depending on whether you are cloning a virtual machine or a template.

    • Virtual Machine: Click the Servers and VMs tab. Select the server pool on which the virtual machine resides in the navigation tree. Select Virtual Machines from the Perspective drop-down list. Select the virtual machine to clone in the management pane, and click Clone Virtual Machine Clone Virtual Machine icon .

    • Virtual Machine Template: Click the Repositories tab. In the navigation tree, select the repository in which the template resides, then VM Templates. Select the template in the management pane and click Clone Template Clone Template icon .

  2. The Clone (Virtual Machine or Template) dialog box is displayed.

    This figure shows the Clone (Virtual Machine or Template) dialog box with the Clone to a Virtual Machine option selected.

    Select or enter the following:

    • Clone to a: Select the clone type, either Virtual Machine or Template, to specify the objects to create from the clone.

    • Clone Count: The number of clones to create.

    • Name Index: The start index number to use for the clone name suffix. The default is 0. This is used in conjunction with the Clone Name field to create the name for each clone.

    • Clone Name: An optional name for the virtual machines or templates. The maximum name length is 256 characters and may contain any character. The name need not be unique. If no value is given, the default is the name of the virtual machine or template being cloned. Each clone is suffixed with a dot (.) and the clone index number, starting with the value for the Name Index field. For example, if the Clone Name field is set to MyVM, and the Name Index field is set to 1, the resulting clones would be named MyVM.1, MyVM.2 and so on.

    • Target Server Pool: The server pool on which the clone is to be deployed.

      Note

      The list of server pools that are available in the drop-down is limited to valid server pools that are capable of handling the cloning process correctly. This helps you to prevent cloning to a server pool that may fail to process the request. If this list is empty, you should refer to the table presented under the Why don't I see other server pools to clone to? element in this dialog.

    • Description: A description for the virtual machines or templates.

    • Advanced Clone: Whether to use a clone customizer to set preferences for the clone operation.

    • Clone Customizer: The clone customizer to create the clones. This is used to set virtual disk mappings to enable you to copy disks to other storage locations. It also allows you to create network mappings so you can use new VNICs and other networks for the clone. Click Create... to create a new clone customizer. See Section 3.5.2.14, “Manage Clone Customizers” for information on creating a clone customizer. This field is enabled if Advanced Clone is checked.

    • Target Repository: The repository to store the cloned virtual machine configuration file. This does not affect any clone disk mappings you set using a clone customizer; this option is only for the virtual machine configuration file. This field is enabled if Advanced Clone is checked.

    • Why don't I see other server pools to clone to? A collapsed window element, providing a table of server pools that do not meet the requirements to accept a clone request. Expanding any of the entries in this table displays the reason that the server pool does not qualify.

    Tip

    If you clone a virtual machine or template without using a clone customizer, the storage repository is locked for the duration of the cloning job; this may be some time in some circumstances. To quickly create clones and not lock the storage repository, use a clone customizer.

    Click OK.

The virtual machines are created and deployed to the server pool. The templates are created in the storage repository.

It is important to understand that older templates may use a different device type to attach virtual disks. This may affect your ability to attach new virtual disks, such as a virtual CDROM device. There are some limitations on mixing virtual disks of differing device types on a virtual machine. See How are Virtual Disks Managed? in the Oracle VM Concepts Guide for more information about how device types are allocated to virtual disks and what you may need to do to solve any issues surrounding this problem.

4.7.1.5 Move a Template

You can move a virtual machine template's resources, such as the virtual disk and virtual machine configuration files, to a different storage repository, or change the location of the disks and network used in the template. You can change the location of disks and the network to use when you move a virtual machine template using a clone customizer.

To move a virtual machine template:

  1. Click the Repositories tab. Select the repository in which the template is saved. Click VM Templates in the navigation tree.

  2. Select the template to move in the table in the management pane and click Move Template Move Template icon .

  3. The Move Template dialog box is displayed.

    Select a clone customizer from the Clone Customizer drop-down list. If no clone customizers are displayed or you want to create a new one, click Create. See Create a Clone Customizer for information on creating a clone customizer.

    Select the repository to which you want to move the template's virtual machine configuration from the Target Repository drop-down list.

    Click Finish to move the template.

4.7.1.6 Manage Clone Customizers

Cloning a virtual machine or template means making a copy of it, so that you can create multiple virtual machines or templates from the original. You can create a clone customizer to set up the clone parameters, such as networking, and the virtual disk, and ISO resources. A clone customizer is also used when moving a virtual machine or template.

Create a Clone Customizer

To create a clone customizer:

  1. Select the virtual machine or template and display the Manage Clone Customizers for (Virtual Machine or Template) dialog box by:

    • Virtual Machine: Click the Servers and VMs tab. Select the server pool on which the virtual machine resides in the navigation tree. Select Virtual Machines from the Perspective drop-down list. Select the virtual machine to clone in the management pane, and click Manage Clone Customizers... Manage Clone Customizers... icon .

    • Virtual Machine Template: Click the Repositories tab. In the navigation tree, select the repository in which the template resides, then VM Templates. Select the template in the management pane and click Manage Clone Customizers Manage Clone Customizers icon .

  2. Select Create Clone Customizer... Create Clone Customizer... icon .

  3. The Create a Clone Customizer wizard is displayed.

    In the Name and Description step of the wizard, enter a Name and Description for the clone customizer, and click Next.

  4. The Storage Mappings step of the wizard is displayed.

    Select the following storage mappings:

    • Disk: The disks to include in the clone.

    • Clone Target Type: The type of storage location where the disk is to be created, either a Repository or a Physical Disk.

    • Clone Target: The location on the storage type where the disk is to be created.

    • Clone Type: Whether to use a sparse or non-sparse files for the disk.

      Caution

      When sparse virtual disk space allocation is used, the available space in a repository can be over-subscribed. Sparse allocation is useful to increase virtual machine density. However, errors occur if the space allocated to a storage repository becomes exhausted, so the administrator must carefully monitor disk space.

    Click Next.

  5. The Network Mappings step of the wizard is displayed.

    Select the Virtual NICss to include in the clone customizer, and the Ethernet Network to which they should belong.

    Note

    The network configuration is not changed when moving a virtual machine or template. It is only used when cloning a virtual machine or template.

    Click Finish.

The clone customizer is now available to use to create a virtual machine, or template. See Section 4.7.1.4, “Clone a Virtual Machine or Template” for information on using the clone customizer to create a virtual machine or template.

Edit a Clone Customizer

To edit a clone customizer:

  1. Select the object to which the clone customizer belongs, either a virtual machine, or a virtual machine template. Click Manage Clone Customizers... Manage Clone Customizers... icon .

  2. The Manage Clone Customizers for (VM or Template) dialog box is displayed. Select the clone customizer to edit and click Edit Clone Customizer... Edit Clone Customizer... icon .

  3. The Edit Clone Customizer dialog box is displayed. Edit the clone customizer.

    Click OK. The changes to the clone customizer are saved.

Delete a Clone Customizer

To delete a clone customizer:

  1. Select the object to which the clone customizer belongs, either a virtual machine, or a virtual machine template. Click Manage Clone Customizers... Manage Clone Customizers... icon .

  2. The Manage Clone Customizers for (VM or Template) dialog box is displayed. Select the clone customizer to delete and click Delete Clone Customizer Delete Clone Customizer icon .

  3. A dialog box is displayed to confirm you want to delete the clone customizer. Confirm you want to delete the clone customizer and click OK. The clone customizer is deleted.

4.7.1.7 View Virtual Machine Configuration File

You can view the content of a virtual machine configuration file. The content is not editable but you can view and copy the text according to your needs.

To view a virtual machine configuration file:

  1. Click the Repositories tab.

  2. Select the repository in which the virtual machines is located in the navigation tree.

  3. Select the virtual machine to which the configuration file belongs in the table in the management pane. Click VM Config File Content... Display VM Config File Content... icon.

  4. The VM Config File Content dialog box is displayed with the content of the virtual machine configuration file. You can view and copy the text according to your needs.

  5. Click OK to close the dialog.



[1] Templates can get very large, so it is not unusual that they are split into manageable chunks. This splitting is done without any attempt at preserving the structure, so the structure must be reconstructed by amalgamating the various files together again before import.