3.6 Unassigned Servers Folder

The Unassigned Servers navigation folder in the navigation tree contains the Oracle VM Servers that are not a member of a server pool within Oracle VM Manager. The structure of the navigation provided in the navigation tree is discussed in more detail in Section 3.2, “Summary”.

Clicking on the Unassigned Servers folder in the navigation tree allows you to access different perspectives in the management pane. Each perspective provides its own view of all of the unassigned Oracle VM Servers within Oracle VM Manager. Most of the perspectives also include separate toolbars that enable you to perform various configuration or management tasks specific to the view currently displayed in the management pane. The Unassigned Servers folder offers the following perspectives in the management pane:

Within the Unassigned Servers navigation folder, individual Oracle VM Server navigation items are displayed if there are Oracle VM Servers in your environment that have not been assigned to a server pool. Each Oracle VM Server item has the same associated perspectives and toolbars available as an Oracle VM Server item listed in a server pool. For information on the perspectives and toolbars associated with an Oracle VM Server navigation item, see Section 3.5, “Server Item”.

3.6.1 Servers Perspective

The Servers perspective lists the different servers that belong to either a server pool or the Unassigned Servers folder, depending on the item selected in the navigation pane. The following columns are displayed in the management pane:

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

  • Status: The running status of the server.

  • Tag(s): Any tags that have been applied to the server.

  • Maintenance Mode: Whether or not the server is configured to be in maintenance mode.

  • IP Address: The IP address that is used by Oracle VM Manager to access the server on the management network channel.

  • Memory (GiB): The available memory, in GiB, on the server.

  • Processors: The number of processors that the server contains.

  • Speed (GHz): The speed that the processors for the server are configured to run at.

  • Product: The physical host brand and type reported by the server bios.

  • Owned: Whether or not the server is owned by the current Oracle VM Manager instance.

  • Update Required: Whether or not a server update is available for the server from its server update repository.

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

Table 3.28 Servers Perspective Toolbar Icon Options

Toolbar Icon Option

Icon

Description

Create Virtual Machine...

Create Virtual Machine... icon

Displays the Create Virtual Machine wizard. Use this option to create a virtual machine in the selected server pool.

Edit...

Edit... icon

Displays the Edit Server dialog box. Use this option to edit the name and description for an Oracle VM Server. This is also used to put the Oracle VM Server into maintenance mode, take ownership of it, and to configure remote management of the Oracle VM Server using IPMI (Intelligent Platform Management Interface).

Note that placing an Oracle VM Server in maintenance mode is indicated in the navigation pane with this icon: Oracle VM Server Maintenance mode icon

Delete

Delete icon
Displays the Delete Confirmation dialog box. Use this option to delete the selected Oracle VM Server.

Start

Start icon

Starts a stopped Oracle VM Server.

Stop

Stop icon
Stops a running Oracle VM Server.

Restart

Restart icon
Restarts a running Oracle VM Server.

Kill

Kill icon

Powers off an Oracle VM Server. This is the equivalent of physically pushing the Off button on the hardware.

Rediscover Server

Rediscover Server icon

Rediscovers the Oracle VM Server. Use this to refresh information about the Oracle VM Server.

Rescan Physical Disks

Rescan Physical Disks icon
Rescans the local storage on an Oracle VM Server. Use this option to rescan the storage presented to an Oracle VM Server when the storage configuration is changed, for example, a new storage array is added.

Update Server

Update Server icon

Updates or upgrades the Oracle VM Server if an update is available in the server update repository.

Send VM Messages...

Send VM Messages... icon

Send one or more virtual machines a message. Use this option to send messages to virtual machines that have the Oracle VM Guest Additions installed.

This option is not available in the Unassigned Servers folder. Virtual machines must be running on a server to receive messages.

Generate Report

Generate Report icon

Generate an XML report on one or more Oracle VM Servers.

Help

Help icon

Displays context sensitive help.


3.6.1.1 Create Virtual Machine

This section explains how to create a virtual machine using a template, and creating a virtual machine from an ISO file, or from physical or virtual disks.

To create a virtual machine using a template:

  1. Click the Servers and VMs tab.

  2. Click Create Virtual Machine Create Virtual Machine icon in the toolbar.

  3. The Create Virtual Machine wizard is displayed.

    Select the Clone from an existing VM Template option and then click Next.

  4. The Create Virtual Machine wizard prompts you to specify details for the virtual machine.

    Enter or select the following details:

    • Clone Count: The number of virtual machines to create from the template.

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

    • Repository: The repository in which to create the virtual machine configuration files.

    • VM Template: The template to use to create the virtual machines.

    • VM Name: An optional name for the virtual machines. 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 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 VM 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.

    • Server Pool: The server pool in which to deploy the virtual machines.

    • Description: An optional description of the virtual machines.

  5. Click Finish. The virtual machines are created and deployed to the server pool.

To create a virtual machine using a virtual appliance:

  1. Click the Servers and VMs tab.

  2. Click Create Virtual Machine Create Virtual Machine icon in the toolbar.

  3. The Create Virtual Machine wizard is displayed.

    Click the Clone from an existing Virtual Appliance option and then click Next.

  4. The Create Virtual Machine wizard prompts you to specify details for the virtual machine.

    Enter or select the following details:

    • Repository: The repository in which to create the virtual machine configuration files.

    • Virtual Appliance: The virtual appliance from which you want to create the virtual machines.

    • Server Pool: The server pool in which to deploy the virtual machines.

      If you select None, the virtual machines are deployed into the Unassigned Virtual Machines folder.

    • Available Virtual Appliance VM(s): The virtual machines that are available to create from the virtual appliance.

    • Selected Virtual Appliance VM(s): The virtual machines to create from the virtual appliance.

      You can select multiple virtual machines if the virtual appliance contains more than one. Oracle VM Manager creates a separate virtual machine for each one that you select.

  5. Click Finish.

    Oracle VM Manager creates the selected virtual machines from the virtual appliance and deploys them to the server pool you specified.

    You can then migrate each virtual machine to a compatible server or server pool.

To create a virtual machine using all other media:

  1. Click the Servers and VMs tab.

  2. Click Create Virtual Machine Create Virtual Machine icon in the toolbar.

    The Create Virtual Machine wizard is displayed.

  3. Click the Create a new VM option and then click Next.

  4. The Create Virtual Machine step is displayed in the wizard.

    Enter or select the following details:

    • Server Pool: The server pool on which to create the virtual machine.

    • Server: The server that the virtual machine should be created on. The default option is Any, but the drop-down selection lists the servers that exist in the server pool that you have selected. Selecting a particular server forces the virtual machine to be created on that server. This has implications for the Start Policy discussed later.

    • Repository: The repository in which to create the virtual machine configuration file.

    • Name: A name for the virtual machine. The maximum name length is 256 characters and may contain any character. The name need not be unique.

    • Enable High Availability: Whether to enable High Availability (HA). See How does High Availability (HA) Work? in the Oracle VM Concepts Guide for more information on HA.

    • Enable Huge Pages: Whether to enable HugePages.

      • The HugePages feature is deprecated for virtual machines with a domain type of PVM in Oracle VM Release 3.4.1. You should not enable HugePages when creating or editing virtual machines. This feature will be removed in a future release of Oracle VM.

        If you have HugePages enabled for any PVM guests, Oracle recommends that you change the domain type for virtual machines from Paravirtualized (PVM) to Hardware virtualized, with paravirtualized drivers (PVHVM). If you cannot change the domain type for a virtual machine, you should disable the HugePages setting and then restart the virtual machine.

      • Huge Page support is enabled by default for virtual machines with a domain type of HVM or PVHVM. You cannot set this parameter for those virtual machines.

      • This option does not take effect on virtual machines deployed on SPARC-based server pools. Virtual machines running on SPARC-based servers can access the page sizes that the server platform supports, regardless of this setting.

      See How is the HugePages Feature Enabled for Virtual Machines?, in the Oracle VM Concepts Guide, for more information on Huge Page support.

    • Description: An optional description of the virtual machine.

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

    • Enable Viridian: Whether to enable Viridian.

      • Viridian support enables the exposure of Windows virtualization compatible entitlements to Microsoft Windows guest operating systems. Enabling viridian support is strongly recommended to ensure improved performance for Microsoft Windows guest operating systems.

      • Enabling viridian support is permitted for all Microsoft Windows guest operating system types. However, it is only effective from Microsoft Windows Vista and Microsoft Windows Server 2008 onwards.

      • Viridian support is enabled by default when creating virtual machines running Microsoft Windows guest operating systems.

    • Mouse Device Type: The mouse type to use for the virtual machine. This option is not available for virtual machines in SPARC-based server pools.

    • Keymap: The keyboard mapping to use for the virtual machine. This option is not available for virtual machines in SPARC-based server pools.

    • Domain Type: The domain type of the virtual machine.

      • Xen HVM: Hardware virtualization, or fully virtualized. When you select this option you can supply an ISO file in a repository (in the Arrange Disks step of the wizard) from which to install an operating system on the virtual machine. See Section 4.5.1.1, “Import ISO” for information on importing an ISO file into a repository. Alternatively, you may consider setting up an environment to perform a network installation for the virtual machine.

      • 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 typically used to run Microsoft Windows guest operating systems with an acceptable performance level. Installation of the guest operating system is usually performed either using an ISO file in a repository or via a network installation.

      • 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. Do not select this option if the virtual machine Operating System is set to either Oracle Linux 7 or RedHat Enterprise Linux 7. These operating systems do not support the Xen PVM domain type.

        Important

        As of Oracle VM Release 3.4.6, support for PVM guests is removed. For more information, see Disabling Paravirtualized Guests on Oracle VM Server in the Oracle VM Administrator's Guide.

      • OVM/SPARC: Specifies that the virtual machine is deployed on a server pool running on Oracle VM Server for SPARC.

      • Unknown: This option is informational in the event that Oracle VM Manager is unable to determine the domain type for an existing virtual machine. It is not possible to actually set a virtual machine's domain type to this value. Attempting to do so generates a rule violation when you try to save the virtual machine settings and an error message is returned.

    • Start Policy: The policy that should be used to start the virtual machine. Select one of:

      • Best Server: This is the legacy algorithm that optimizes virtual machine placement on Oracle VM Servers that are in use before moving to unused servers in the pool.

      • Balance Server: This algorithm distributes virtual machines across all the available Oracle VM Servers in the server pool, starting with the least utilized Oracle VM Server first. CPU and memory utilization statistics are used to balance the virtual machine distribution across the server pool, with CPU utilization taking precedence over memory utilization.

      • Current Server: The virtual machine is started on the Oracle VM Server to which it is assigned. If you selected a particular server to create the virtual machine on, then it is started on this server.

      • Use Pool Policy: The virtual machine is started using the start policy defined for the entire server pool. See Section 3.1.2, “Create Server Pool” for more information on setting the start policy for a server pool.

    • Max. Memory (MB): The maximum memory size the virtual machine can be allocated. This value must be between 32 and 512000. The default is 512.

      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. If you have enabled Huge Pages, the value must be a multiple of 2 MB.

      Note

      For HVM and PVHVM guests, the maximum memory size value must equal the memory size value. If these values are different, the following job failure message is generated for HVM/PVHVM guests: "The memory limit cannot be different than the current memory size on an HVM/PVHVM Virtual Machine."

    • Memory (MB): The memory size the virtual machine is allocated. When creating a virtual machine, this is the memory allocation used when starting the virtual machine. This value must be between 32 and 512000. The default is 512.

      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. If you have enabled Huge Pages, the value must be a multiple of 2 MB.

      You can change the memory allocated to a running virtual machine without the need to restart the virtual machine if the domain type is PVM or PVHVM and where the guest is running a Linux OS on an x86-based platform or an Oracle Solaris OS on a SPARC-based platform.

      Note

      For x86-based PVHVM guests running on Oracle Solaris OS, you cannot change the memory if the virtual machine is running.

      See the Oracle VM Paravirtual Drivers for Microsoft Windows documentation for information about the availability of hot memory modification on PVHVM guests that are running a Microsoft Windows OS. You must use a Windows PV Driver that supports hot memory modification or you must stop the guest before you modify the memory.

    • Max. Processors: The maximum number of processors the virtual machine can be allocated. 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.

        Important

        As of Oracle VM Release 3.4.6, support for PVM guests is removed. For more information, see Disabling Paravirtualized Guests on Oracle VM Server in the Oracle VM Administrator's Guide.

      • HVM: 128; or 32 for Microsoft Windows guests.

        Note

        As of Release 3.4.6, the HVM limit is 64 for Microsoft Windows guests.

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

        Note

        As of Release 3.4.6, the PVHVM limit is 64 if using Oracle VM Paravirtual Drivers for Microsoft Windows.

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

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

    • Priority: The CPU priority of the virtual machine. The higher the priority value, the more physical CPU cycles are given to the virtual machine. This option is not available for virtual machines in SPARC-based server pools. This should be a number between 1 and 100. The default priority is set at 1.

    • 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. Use this parameter to keep low priority virtual machines from consuming too many CPU cycles on a Virtual Machine Server. This option is not available for virtual machines in SPARC-based server pools.

    • 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. 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.

      This option cannot be modified for a running virtual machine. You must stop the virtual machine before you are able to change this option, if you select to edit the virtual machine later.

    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.

    Note

    For information on performance optimization goals and techniques for Oracle VM Server for x86, see Optimizing Oracle VM Server for x86 Performance, on Oracle Technology Network at: http://www.oracle.com/technetwork/server-storage/vm/ovm-performance-2995164.pdf.

    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.

    Click Next.

  5. The Set up Networks step is displayed in the wizard.

    This step of the wizard allows you to add VNICs to the virtual machine.

    1. To specify the MAC address for a VNIC, select Specify MAC Address and enter the MAC address. Otherwise, leave the default Dynamically Assign MAC.

    2. Select a network with the virtual machine role from the Network drop-down list.

      If no networks are available, you must first create a network with the virtual machine role as a dedicated network for virtual machine traffic. See Section 5.1.1, “Create New Network” for information on creating a network.

    3. Click Add VNIC.

      • The VNIC order specified determines the order in which the VNICs are presented to the virtual machine. You can control the ordering of the VNICs using the up and down arrows on the right of the table.

      • If you are editing the networking of an existing stopped virtual machine, you can change the network to which the VNIC belongs using the Network drop-down list in the table. It is important that the VNIC belongs to a network already associated with the Oracle VM Servers on which it can run, or you cannot start the virtual machine. See Section 5.1.1, “Create New Network” and Section 5.1.2, “Edit Existing Network” for more information on associating Oracle VM Servers with networks.

      • If you are editing an existing running virtual machine, you can add VNICs to the virtual machine, but you cannot remove VNICs that are already in use. You also cannot reorder VNICs on a running virtual machine. If you choose to add a VNIC to a running machine you must ensure that the VNIC belongs to a virtual machine network already associated with the Oracle VM Servers on which it can run, by selecting the appropriate network from the Network drop-down list.

      • A virtual machine can have up to eight (8) VNICs for HVM guests and up to 31 for PVM guests. A PVM guest requires network connectivity to perform the operating system install and must have at least one VNIC.

    4. Click Next.

  6. The Arrange Disks step of the wizard is displayed.

    Select the desired storage configuration of your virtual machine, such as virtual disks, 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. You cannot add an empty CDROM on a SPARC-based server.

    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.

    Tip

    When editing a running virtual machine, you can change the CD/DVD using this dialog box and the CD/DVD is mounted in the operating system.

    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.

      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. The dialog box lists the available virtual disks in a table that indicates the following information:

      • Selected: Whether or not the disk has been selected. This is indicated using radio button.

      • Name: The name of the virtual disk as stored in Oracle VM Manager.

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

      • Repository: The repository in which the virtual disk is located.

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

      • VM(s): A comma separated list of the names of any virtual machines that may already be using this virtual disk.

      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. 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.

    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. The dialog box lists the available physical disks in a table that provides the following information:

      • Selected: Whether or not the disk has been selected. This is indicated using radio button.

      • Name: The name of the physical disk as stored in Oracle VM Manager.

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

      • SAN Server: The SAN Server where the physical disk is located.

      • Volume Group: The volume group that the physical disk belongs to.

      • Shareable: Whether the physical disk is configured to be shareable (read/write) with other virtual machines.

      • VM(s): A comma separated list of the names of any virtual machines that may already be using this physical disk.

      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

    When you have set up the virtual machine's disks, click Next.

  7. The Boot Options step is displayed in the wizard.

    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 PXE option available. In this case, the PXE option refers to a network style boot. If the PXE option appears in the right-hand-side column, you must enter the location of the mounted ISO file from which to perform the operating system installation in the Network Boot Path field that is shown when editing or creating a PVM, for example

    http://example.com/EL6-x86

    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.

    If you have defined tags and want to add any to this virtual machine, click Next. Otherwise, click Finish to create and deploy the virtual machine to the server pool.

  8. The Tags step is optional and displays in the wizard if you clicked Next in the previous step.

    Note

    The virtual machine has already been created and deployed to the server pool at this point. This step is entirely optional. Cancelling the operation within this dialog does not prevent the virtual machine from being created.

    If you have previously created tags, they appear in the Available Tags column. Select the tags you want to apply to the virtual machine and move them to the Selected Tags column. See Section 1.17, “Tags and Tag Filters” for more information on creating and managing tags. Click Finish.

If you created a PVM, there are some steps you should take after the operating system installation is completed:

  1. Stop the virtual machine. See Section 3.5.2.4, “Stop Virtual Machines” for information on stopping a virtual machine.

  2. Edit the virtual machine and remove PXE from the Boot Order column in the Boot Options step of the Edit Virtual Machine wizard. See Section 3.5.2.1, “Edit Virtual Machine” for information on editing a virtual machine.

  3. Start the virtual machine and complete the installation if necessary. See Section 3.5.2.3, “Start Virtual Machines” for information on starting a virtual machine.

To edit the virtual machine configuration information, see Section 3.5.2.1, “Edit Virtual Machine”.

3.6.1.2 Edit Server

You can edit the configuration information for an Oracle VM Server to change the name, description, any server pool roles, and to take it off-line to perform system maintenance. You can always edit the name and description of an Oracle VM Server, even if it is not owned by the Oracle VM Manager instance. You cannot edit any other information if the Oracle VM Server, is not owned by the Oracle VM Manager instance. If you want to edit these other options, you should first take ownership of the server using the Take Ownership of Server field as described in the procedure below.

To edit the configuration information of an Oracle VM Server:

  1. Click the Servers and VMs tab.

  2. Select the Oracle VM Server in the navigation pane. Click Edit Server Edit Server icon in the toolbar.

  3. The Edit Server dialog box is displayed. In the Configuration tab, edit the information about the Oracle VM Server:

    • Name: The name of the Oracle VM Server.

    • Description: A description of the Oracle VM Server.

    • NTP Server(s): Allows you to specify the NTP server settings for each individual Oracle VM Server. You can add multiple NTP servers using a comma-separated list.

      Note

      If you need to batch edit the NTP servers for a large number of Oracle VM Servers in your environment, you should use the Oracle VM Manager Command Line Interface, edit Server, or the Oracle VM Web Services API to do this programmatically.

    • Server in Maintenance Mode: Select whether to place the Oracle VM Server in maintenance mode.

      An Oracle VM Server can be placed into maintenance mode to perform hardware or software maintenance. When an Oracle VM Server is placed in maintenance mode, it is not possible to start any new virtual machines on the server. Furthermore, any virtual machines running on the Oracle VM Server are automatically migrated to other Oracle VM Servers in the server pool, if they are available. If any of these automatic processes fail, check the Oracle VM Server event log (Section 3.5.10, “Events Perspective”) for reasons why the failure occurred.

      Note

      • When a virtual machine is migrated to an alternate Oracle VM Server, no checks are performed to detect whether the target Oracle VM Server is configured correctly or capable of running the virtual machine correctly. It is up to you to ensure that the Oracle VM Servers within a server pool have consistent configurations.

      • It is possible that some virtual machines fail to migrate if no target Oracle VM Server is found. In this case, maintenance mode may be set, but some virtual machines may continue to run on the Oracle VM Server.

      • If a virtual machine relies on local storage, then no target Oracle VM Server is identified as the migration target. These virtual machines should be manually migrated using the Storage Live Migration feature. For more information, see Section 3.5.2.11, “Migrate or Move Virtual Machines”

      You must determine the appropriate course of action for these virtual machines and perform the required actions manually using the tools provided within Oracle VM Manager.

      When an Oracle VM Server is placed into maintenance mode its icon: Maintenance Mode icon is updated in the navigation pane. When you have finished performing maintenance on the Oracle VM Server and you are ready for it to rejoin the server pool, ensure that the Maintenance Mode check box is unchecked.

    • Take Ownership of Server: Select to take ownership of the Oracle VM Server. Server rediscovery is performed as part of this process, so that Oracle VM Manager can correctly determine whether or not the server is in an unowned state and the action can be completed successfully.

      Note

      Configuration of NTP for each Oracle VM Server takes place when a server changes ownership. If you release ownership of a server, its NTP configuration is updated to point locally to itself. When Oracle VM Manager takes ownership of a server, the server's NTP configuration is usually automatically updated to point to the Oracle VM Manager instance. This may only be evident after the server has been refreshed. You can find out more about the configuration of NTP in Configure the NTP Service on the Oracle VM Manager Host in the Oracle VM Installation and Upgrade Guide.

      Tip

      You cannot edit the ownership of an Oracle VM Server if it is included in a server pool or if a repository is presented to it.

    • Inbound Migration Locked: Select whether to allow additional virtual machines to run on the Oracle VM Server. Selecting this option prevents new or migrated virtual machines to run on the Oracle VM Server. See How Can I Protect Virtual Machines? for more information on inbound migration lock.

      Note

      If you have HA configured for a server, this option does not protect a server from inbound migrations when failover occurs.

    • Oracle VM Agent password: The password to connect to the Oracle VM Agent. The value for this field is required if you select to take ownership of the Oracle VM Server.

    • Utility Server: Select to designate the Oracle VM Server to perform utility functions such as importing, cloning and storage refresh.

    • VM Server: The virtual machine role is required to run virtual machines.

  4. In the IPMI tab, select the Enable Server IPMI check box to enable the Intelligent Platform Management Interface (IPMI). IPMI allows you to remotely power on or power off an Oracle VM Server. If IPMI is either not available or not enabled on the Oracle VM Server, Oracle VM Manager may still be able to remotely power on an Oracle VM Server using a Wake on LAN message without having to physically press the power button, and it may be able to send a system power off message to shut it down. Select the Change IPMI Password check box if your IPMI setup requires a password to change the configuration. The Change IPMI Password check box is automatically selected when you enable IPMI.

    To configure IPMI enter the following information in the fields:

    • IP Address: The IP address of the IPMI.

    • Access Username: The optional user name for the IPMI.

    • Password: The optional password for the IPMI. Note that this field is always blank, regardless of whether the password has been set or not.

  5. To edit the tags associated with the server, click the Tags tab. Using the controls provided, you can add or remove tags that can be used to identify the server and to group it with other objects within Oracle VM Manager. See Section 1.17, “Tags and Tag Filters” for more information on creating and managing tags.

Click OK. The Oracle VM Server is updated.

Batch Editing Oracle VM Servers

You can edit the information for more than one Oracle VM Server at a time by using the multi-select functionality provided within the Oracle VM Manager interface to select multiple items before clicking on the Edit Server Edit Server icon icon in the toolbar.

When editing a group of Oracle VM Servers in batch mode the options available to you are limited to actions that can be applied to all selected items. The following options are available:

  • Server in Maintenance Mode: Checking this check box sets all selected items into Maintenance Mode.

  • Take Ownership of Server: Checking this check box allows Oracle VM Manager to take ownership of all of the selected items.

  • Oracle VM Agent password: The password to connect to the Oracle VM Agent. The value for this field is required if you select to take ownership of the selected items.

  • Utility Server: Checking this check box changes the role of all selected items to Utility Servers.

  • VM Server: Checking this check box changes the role of all selected items to Virtual Machine Servers.

Note

If the values set for the options provided vary across the selected servers, the dialog displays the values for the first server in the selection. Clicking OK updates all of the selected servers to have the same status.

3.6.1.3 Delete Server

When you delete an Oracle VM Server, it is removed from the Oracle VM Manager repository and becomes unmanaged. The Oracle VM Server is not stopped, nor is anything physically done to the Oracle VM Server.

Before you can delete an Oracle VM Server, you must stop any running virtual machines, or place the Oracle VM Server into maintenance mode to automatically migrate the running virtual machines.

To delete Oracle VM Servers from Oracle VM Manager:

  1. Stop or migrate any running virtual machines. To stop the virtual machines see Section 3.5.2.4, “Stop Virtual Machines”. To automatically migrate the virtual machines to other Oracle VM Servers in the server pool, place the Oracle VM Server into maintenance mode, see Section 3.4.2.2, “Edit Server”.

  2. Click the Servers and VMs tab.

  3. Select the Unassigned Servers folder in the navigation tree. Select Servers from the Perspective drop-down list.

  4. Select one or more Oracle VM Servers in the management pane. Click Delete Delete icon in the perspective toolbar.

  5. The Delete Confirmation dialog box is displayed. Click OK to delete the Oracle VM Servers.

The Oracle VM Servers are deleted from Oracle VM Manager.

3.6.1.4 Start Server

When you start an Oracle VM Server, it is started using the Intelligent Platform Management Interface (IPMI), or Wake-on-LAN (WOL). If neither IPMI nor WOL have been configured, the job to start the Oracle VM Server cannot be completed and may need to be aborted. The Oracle VM Server must then be powered on manually. See Section 3.4.2.2, “Edit Server” for information on configuring IPMI. See Section 8.1.5, “Abort Jobs” for information on aborting a hanging job.

To start Oracle VM Servers:

  1. Click the Servers and VMs tab.

  2. Select the server pool in which the Oracle VM Server resides in the navigation tree.

  3. Select Servers from the Perspective drop-down list. Select one or more Oracle VM Servers in the management pane, and click Start Server Start Server icon in the perspective toolbar.

The Oracle VM Servers are started.

3.6.1.5 Stop Server

When you stop an Oracle VM Server, it is stopped using the Intelligent Platform Management Interface (IPMI), or a system power off command. Before you can stop an Oracle VM Server, you must stop any running virtual machines, or place the Oracle VM Server into maintenance mode to automatically migrate the running virtual machines.

Warning

Make sure that the IPMI is properly configured on the Oracle VM Server, otherwise it cannot be started again remotely. See Section 3.4.2.2, “Edit Server” for IPMI configuration. Alternatively, make sure that you activate the Wake-on-LAN (WOL) feature in the Oracle VM Server BIOS and that you have tested that it is properly working. If an Oracle VM Server cannot start through IPMI or WOL, it must be power-cycled manually.

To stop Oracle VM Servers:

  1. Stop or migrate any running virtual machines. To stop the virtual machines see Section 3.5.2.4, “Stop Virtual Machines”. To automatically migrate the virtual machines to other Oracle VM Servers in the server pool, place the Oracle VM Servers into maintenance mode , see Section 3.4.2.2, “Edit Server” .

  2. Click the Servers and VMs tab.

  3. Select the server pool in which the Oracle VM Server resides in the navigation tree.

  4. Select Servers from the Perspective drop-down list. Select one or more Oracle VM Servers in the management pane, and click Stop Server Stop Server icon in the perspective toolbar.

The Oracle VM Servers are powered off.

3.6.1.6 Restart Server

When you restart an Oracle VM Server, an operating system restart command is sent and the Oracle VM Server is restarted. Before you can restart an Oracle VM Server, you must stop any running virtual machines, or place the Oracle VM Server into maintenance mode to automatically migrate the running virtual machines.

When the Oracle VM Server is restarted and rejoins the server pool, any pending HA operations in the server pool are initiated. When Oracle VM Manager is notified that the Oracle VM Server is online and available, any pending state changes are reconciled before any policy actions are resumed.

There is more information on the implications of restarting servers covered in Rebooting and Changing Power State of Oracle VM Servers in the Oracle VM Concepts Guide.

To restart Oracle VM Servers:

  1. Stop or migrate any running virtual machines. To stop the virtual machines see Section 3.5.2.4, “Stop Virtual Machines”. To automatically migrate the virtual machines to other Oracle VM Servers in the server pool, place the Oracle VM Servers into maintenance mode , see Section 3.4.2.2, “Edit Server” .

  2. Click the Servers and VMs tab.

  3. Select the server pool in which the Oracle VM Server resides in the navigation tree.

  4. Select Servers from the Perspective drop-down list. Select one or more Oracle VM Servers in the management pane, and click Restart Restart icon in the perspective toolbar.

The Oracle VM Servers are restarted.

3.6.1.7 Kill Server

To kill an Oracle VM Server is equivalent to performing a power off of an Oracle VM Server, similar to unplugging the power cable from the physical machine. This is not the recommended method of shutting down an Oracle VM Server, but may be used if the shut down command fails to shut down the Oracle VM Server.

To kill Oracle VM Servers:

  1. Click the Servers and VMs tab.

  2. Select the server pool in which the Oracle VM Server resides in the navigation tree.

  3. Select Servers from the Perspective drop-down list. Select one or more Oracle VM Servers in the management pane, and click Kill Kill icon in the perspective toolbar. Click OK in the Confirmation dialog.

The Oracle VM Servers are powered off.

3.6.1.8 Rediscover Server

If there are either changes to the physical state of an Oracle VM Server or its attached storage, you should discover it again to update the configuration information in Oracle VM Manager.

To rediscover Oracle VM Servers:

  1. Click the Servers and VMs tab.

  2. Select the server pool in which the Oracle VM Servers reside in the navigation tree.

  3. Select Servers from the Perspective drop-down list. Select one or more Oracle VM Servers in the management pane, and click Rediscover Server Rediscover Server icon in the perspective toolbar.

The configuration and storage information about the Oracle VM Servers is updated in Oracle VM Manager.

3.6.1.9 Rescan Physical Disks

You can rescan the physical disks available to an Oracle VM Server to determine if any disks have been changed, added, or removed.

To rescan the physical disks on Oracle VM Servers:

  1. Click the Servers and VMs tab, and select the server pool in which the Oracle VM Servers reside in the navigation tree. Select Servers in the Perspective drop-down list in the management pane. Select the Oracle VM Servers in the management pane table.

    Alternatively, on the Servers and VMs tab, expand the Server Pools or Unassigned Servers folder, to select a particular server in the navigation tree. Select the Physical Disks option in the Perspective drop-down list.

  2. Click Rescan Physical Disks Rescan Physical Disks icon in the perspective toolbar.

  3. A confirmation dialog box is displayed. Click OK.

3.6.1.10 Update Server

Software updates and upgrades to Oracle VM Servers can be performed using the global server update repository configured in the Server Updates subtab of the Reports and Resources tab. See Section 7.3, “Server Update Groups” for information on configuring a global server update repository. A repository can be overridden for a server pool if required. See Section 3.4.6, “Server Update Repositories Perspective” for information on overriding a global update repository for a server pool.

To see which version of the Oracle VM Server software is installed before and after an upgrade, click the Servers and VMs tab, select the Oracle VM Server in the navigation tree, and then select Control Domains in the Perspective drop-down list. See Section 3.5.8, “Control Domains Perspective” for information on control domains.

When an Oracle VM Server update is available, an event is posted to the Oracle VM Server and Yes is displayed in the Update Required column in the Servers perspective in the management pane.

Before upgrading Oracle VM Servers using the Oracle VM Manager Web Interface you should refer to the Oracle VM Installation and Upgrade Guide. The Oracle VM Manager Web Interface can only be used to perform upgrades for servers that are running Oracle VM Server 3.3.x and up.

To update an Oracle VM Server, the virtual machines on the Oracle VM Server must first be stopped or migrated to another Oracle VM Server. You can manually stop or migrate the virtual machines, or, if you prefer, have the upgrade server job perform the virtual machine migrate automatically.

To update Oracle VM Servers:

  1. Click the Servers and VMs tab, and select the server pool in which the Oracle VM Servers reside in the navigation tree.

  2. Select Servers in the Perspective drop-down list in the management pane.

  3. Select the Oracle VM Servers in the management pane table and click Update Server Update Server icon from the perspective toolbar.

    A confirmation dialog is displayed. Click OK. Each Oracle VM Server is placed into maintenance mode, and the update performed. Any virtual machines on the Oracle VM Servers are automatically migrated to another Oracle VM Server when it is put into maintenance mode. When the update is complete the Oracle VM Server is restarted and remains in maintenance mode.

  4. To have the Oracle VM Servers rejoin the server pool as a fully functioning member, edit each the Oracle VM Server and take it out of maintenance mode.

For information on manually migrating virtual machines, see Section 3.5.2.11, “Migrate or Move Virtual Machines”. For information on taking an Oracle VM Server out of maintenance mode, see Section 3.4.2.2, “Edit Server”.

Note that you can upgrade multiple Oracle VM Servers in a server pool by using the multi-select functionality described in Section 1.15, “Multi-Select Functionality”.

3.6.1.11 Generate Report

You can generate an XML report on one or more Oracle VM Servers. For more information about object reporting, see Section 7.1, “Reports”.

To generate a report on Oracle VM Servers:

  1. Select a server pool in the Server Pools folder in the navigation pane.

  2. Select the Servers perspective in the management pane.

  3. Select one or more Oracle VM Servers in the management pane table.

  4. Click Generate Report icon Generate Report in the management pane toolbar.

  5. The report is generated and sent to the browser.

3.6.2 Events Perspective

The Events perspective is common to many elements within the Oracle VM Manager Web Interface. The Events perspective generally appears as an option within the Perspectives drop-down menu on the management pane of tabs that include a navigation tree. In this case, the Events perspective displays events specific to the item selected in the navigation tree and presents these in the management pane.

The Events perspective may also appear within a dialog that is triggered from a Display Selected Events... Display Selected Events... icon perspective toolbar option. In this case, the Events perspective dialog displays events specific to one or more elements selected in the management pane.

If an object has an error event associated with it you must acknowledge the event to clear the error and return the object to normal operations. For example, this can occur if an Oracle VM Server or virtual machine appear as Stopped (Error) in the status. The object in error is flagged with a red icon in the navigation tree. Oracle VM Servers, virtual machines, repositories and storage objects can have error events associated with them.

Since Oracle VM Manager attempts to resolve issues automatically as much as possible, not all events can be acknowledged by a user within the Oracle VM Manager Web Interface. Therefore, a flag is set for events that are user acknowledgeable. If an event does not have this flag set, you are unable to acknowledge it, since it is handled internally by Oracle VM Manager.

The Events perspective or dialog contains a table with the following columns of information for each event:

  • Severity: The severity level assigned to the event.

  • Timestamp: The date and time that the event occurred.

  • Modify Time: The last recorded date and time that the event was modified.

  • Type: The type of event according to Oracle VM Manager's event categorization model.

  • Summary: A summary description of the event.

  • Acknowledged: Whether an error event has been acknowledged.

  • User Acknowledgeable: Whether or not an event can be acknowledged by the user.

Event Descriptions

An arrow displays next to each event in the table. Click the arrow to expand and view the Description section that provides additional details for the event.

The Events perspective or dialog contains a perspective toolbar with the following options:

Table 3.29 Events Perspective Toolbar Icon Options

Toolbar Icon Option

Icon

Description

Acknowledge

Acknowledge icon

Acknowledge a selected error event to clear the error and return the object to normal operations. Note that this option is only available for user acknowledgeable events.

Acknowledge All

Acknowledge All icon

Acknowledge all error events associated with an object to clear the errors and return the object to normal operations. Note that only user acknowledgeable events are cleared. This button is always clickable, even if there are no user acknowledgeable events. Clicking it when there are no user acknowledgeable events results in an error dialog.

Display Count

 

A drop-down menu that allows you to select the number of events that should be displayed in the management pane, while you are currently in this perspective.


Acknowledging Events/Errors

If an object has an error event associated with it you must acknowledge the event to clear the error and return the object to normal operations. For example, this can occur if an Oracle VM Server or virtual machine appear as Stopped (Error) in the status. The object in error is flagged with a red icon in the navigation tree. Oracle VM Servers, virtual machines, repositories and storage objects can have error events associated with them. The following procedures show you how to clear errors and return the object to normal operations.

To acknowledge Oracle VM Server error events:

  1. Click the Servers and VMs tab.

  2. Select the Oracle VM Server in the navigation tree.

  3. Select Events from the Perspective drop-down list in the management pane.

  4. Select the user acknowledgeable error event and click Acknowledge Acknowledge icon , or click Acknowledge All Acknowledge All icon to clear all user acknowledgeable errors.

To acknowledge virtual machine error events:

  1. Click the Servers and VMs tab.

  2. Select the server pool, or Oracle VM Server on which the virtual machine resides in the navigation tree.

  3. Select Virtual Machines from the Perspective drop-down list in the management pane.

  4. Select the virtual machine in the management pane table. Click Display Selected VM Events... Display Selected VM Events... icon .

  5. The Events dialog box is displayed. Select the user acknowledgeable error event and click Acknowledge Acknowledge icon , or click Acknowledge All Acknowledge All icon to clear all user acknowledgeable errors. Click Close.

To acknowledge storage repository error events:

  1. Click the Repositories tab.

  2. Select the repository in the navigation tree.

  3. Select Events from the Perspective drop-down list in the management pane.

  4. Select the error event and click Acknowledge Acknowledge icon , or click Acknowledge All Acknowledge All icon to clear all errors.

To acknowledge storage error events:

  1. Click the Storage tab.

  2. Select File Servers, SAN Servers, or a storage server in the navigation tree.

  3. Select Events from the Perspective drop-down list in the management pane.

  4. Select the user acknowledgeable error event and click Acknowledge Acknowledge icon , or click Acknowledge All Acknowledge All icon to clear all user acknowledgeable errors.