This chapter includes the following sections:
Oracle VM Server for x86 is a platform that provides a fully equipped environment to leverage the benefits of x86 virtualization technology. Oracle VM Server enables you to deploy operating systems and application software within a supported virtualization environment.
Oracle VM Server for x86 is a Xen-based server virtualization technology which supports Linux, Oracle Solaris, and Windows guests, and provide features to manage guests lifecycle operations, allocate and monitor guest resource consumption. The components of Oracle VM are:
Oracle VM Manager: Provides the user interface to manage Oracle VM Servers, virtual machines, and resources.
Oracle VM Server: A self-contained environment that is designed to produce a lightweight, secure server-based platform for running virtual machines. The Oracle VM Server can perform one or more of the following functions:
Server Pool Master: The master is the core of the server pool operations and it acts as the contact point for the server pool to Oracle VM Manager, and also as the dispatcher to other Oracle VM Servers in the server pool.
Utility Server: Its function focuses on the creation and removal operations of virtual machines, Oracle VM Servers, and server pools.
Virtual Machine Server: The primary function of virtual machine server is to run virtual machines.
This table lists the tasks and the role required to complete the task. Contact your administrator if you do not have the necessary role or privilege to complete a task.
See the Related Resources for Oracle VM Server for x86 section for information about the different roles and the permissions they grant.
Table 6-1 Oracle VM Server for x86 Tasks and Roles
Task | Role |
---|---|
Discover Oracle VM Manager and Oracle VM Server |
Virtualization admin |
Provision Oracle VM Manager |
Ops Center admin |
Manage Oracle VM Manager |
Virtualization admin |
Create Link Aggregation |
Network admin |
Create, manage, update, and delete virtual machines |
Virtualization admin |
Set monitor threshold |
Asset admin |
Manage storage resources |
Storage admin |
Create and manage profiles and plans |
Profile and plan admin |
The integration of Oracle VM Server for x86 with Oracle Enterprise Manager Ops Center provides the platform to manage Oracle VM Manager, Oracle VM Servers, server pools, and the virtual machines through Oracle Enterprise Manager Ops Center UI.
The following operations can be done through Oracle Enterprise Manager Ops Center to manage Oracle VM Server for x86 deployments:
Discover deployed Oracle VM Managers
Provision Oracle VM Servers
Discover existing Oracle VM Servers
Launch Oracle VM Manager UI
Create virtual machines
Provision OS on virtual machines
Create server pools
Connect to Oracle VM Manager console
Manage storage repositories of Oracle VM Server for x86
Perform management operations on Oracle VM Servers and virtual machines
This table lists where to find different information for Oracle VM Server for x86 in the UI.
Table 6-2 Location of Oracle VM Server for x86 Information
To See | Location |
---|---|
Discovered Oracle VM Manager |
Expand Administration in the Navigation pane. All the discovered Oracle VM Managers are displayed under Oracle VM Manager. |
Discovered Oracle VM Server |
Expand Assets in the Navigation pane. All the discovered Oracle VM Servers are displayed in the All Assets tree. |
Server Pools |
Expand Assets in the Navigation pane and select Server Pools in the Resource Management Views |
Virtual Machine |
Expand Assets in the Navigation pane and select Server Pools in the Resource Management Views. The virtual machines are listed under corresponding Oracle VM Servers. |
Options for managing Oracle VM Servers from Oracle VM Manager |
Expand Administration in the Navigation pane and select the Oracle VM Manager. All options to manage Oracle VM Servers are listed in the Actions pane. |
Installation of Oracle VM Manager is outside the scope of this document.
For detailed instructions about how to install the Oracle VM Manager, see Oracle VM Installation and Upgrade Guide for x86 at http://www.oracle.com/technetwork/documentation/vm-096300.html
.
By default, the Enterprise Controller, Proxy Controller, and Agent Controller use the most recent version of JDK available on the system. However, Oracle VM Server for x86 code will not work when the JDK version on the Proxy Controller is higher than JDK version 6. If the Proxy Controller has a higher version, you must manually set the JDK to version 6 on the Proxy Controller by editing the JAVA_HOME variable to force the use of JDK 6.
Discover the Oracle VM Manager in Oracle Enterprise Manager Ops Center and launch the console to access it.
When you discover the Oracle VM Manager in Oracle Enterprise Manager Ops Center, the following Oracle VM resources are automatically discovered and populated in the UI:
Oracle VM Servers
Server pools
Virtual machines
Storage servers
Storage repositories
Networks
To discover an existing Oracle VM Manager, you must have the following information:
Discovery profile for Oracle VM Manager
Credentials for Oracle VM Manager access
You must create a discovery profile for discovering the installed Oracle VM Manager. The discovery profile provides options to create the discovery profiles for all the components related to Oracle VM Server for x86.
Figure 6-1 shows the different assets that are available under Oracle VM in the Discovery Profile Wizard.
The following procedure outlines the steps to create a discovery profile for Oracle VM Manager:
Select Discovery from the Plan Management section.
Click Create Profile in the Actions pane.
The Create Profile-Discovery Wizard is displayed.
Enter a name and description for the discovery profile.
Select the Asset Type as Oracle VM Manager from the list.
Click Next to define the tags.
(Optional) Define the tags for the asset to be discovered. Tags help to group the assets.
Click Next to enter the IP range.
(Optional) Enter the IP address of the Oracle VM Manager to be discovered. Enter the host name or IP Address when you execute the profile.
Click Next to select the credentials of the Oracle VM Manager.
When you have the credentials of the Oracle VM Manager, click Select and the list of saved credentials are displayed. Select the appropriate credential from the list.
Click New to display the Create Credentials window. Enter the following information:
Name and description for the credential.
Enter the username and password of the Oracle VM Manager. Re-enter the password to confirm.
Select the protocol and enter the port number.
Click Ok to create the credential and click Next to review the summary of the Oracle VM Manager discovery parameters.
Click Finish to create the profile.
After creating the profile, execute the profile to discover the Oracle VM Manager. The following procedure describes how to execute the profile:
The Oracle VM Manager is considered an independent entity with which Oracle Enterprise Manager Ops Center integrates. The Oracle VM Manager appears in the Administration section of the UI, not as an asset in the Assets tree.
Figure 6-2 shows the Oracle VM Managers displayed in the Administration section of the UI.
When you discover an Oracle VM Manager, all of the Oracle VM Servers managed in it are also discovered and displayed in the Assets section. Existing server pools in the Oracle VM Manager are also displayed in the Server Pools view of the UI.
When you discover and manage an Oracle VM Manager, all of the known Oracle VM Servers to the manager are also discovered and displayed in the software UI. When you have manually installed Oracle VM Servers and not discovered in the Oracle VM Manager, you can still discover the Oracle VM Server in the Oracle Enterprise Manager Ops Center UI.
When you create a discovery profile for Oracle VM Server, you must define the Oracle VM Manager to which it can be associated. This makes the Oracle VM Server known to the Oracle VM Manager.
You must use SSH discovery of the Oracle VM Server when you want access to the serial console and perform advanced configuration in the Control Domain.
The creation of discovery profiles is similar to Oracle VM Manager except for selecting the Discovery Type as Oracle VM Server. When you provide the Oracle VM Server host name or IP address, select the Oracle VM Manager with which you want to associate the Oracle VM Server.
Figure 6-3 shows the IP Ranges step of the Discovery Profile Wizard in which the user must select the Oracle VM Manager to discover the Oracle VM Server.
Execute the profile and discover the Oracle VM Server. This is a very basic discovery of the server. The storage and network configuration of the server are not populated in the UI and only basic information is displayed in the UI.
Use this method when you want to access the serial console of the Oracle VM Server and perform advanced configuration.
To use SSH for discovery, define the credentials for the Oracle VM Server as explained in this procedure:
Create a discovery profile for the Oracle VM Server and select the credential created for ssh discovery. Discover the Oracle VM Server using the profile. Since the discovery of the Oracle VM Server is through the SSH discovery, the network and storage configuration of the server is populated in the UI.
You can provision Oracle VM Servers using Oracle Enterprise Manager Ops Center. You can download an Oracle VM Server image into the storage libraries, create OS provisioning profiles and then deploy a plan with the profile on the selected target. When you import an image into Oracle Enterprise Manager Ops Center, a default profile and plan are created automatically.
See the Related Resources for Oracle VM Server for x86 section for more information.
Oracle VM Server is a managed virtualization environment based upon the Xen hypervisor technology and includes a small Linux-based management operating system.
For hardware and software requirements for installing Oracle VM Server, see Oracle VM Installation and Upgrade Guide for x86 at http://www.oracle.com/technetwork/documentation/vm-096300.html
.
When you install Oracle VM Server through Oracle Enterprise Manager Ops Center, the Oracle VM Server is installed without Agent Controller. The Oracle VM Agent is installed automatically when you install Oracle VM Server. The Oracle VM Agent enables communication between the Oracle VM Manager and Oracle VM Server for all management tasks.
The provisioning profile of installing Oracle VM Server is similar to installing a Linux OS profile with additional steps to provide the Oracle VM Server password and the management interface. The Oracle VM Server password is different from the root password. This password is used by the Oracle VM Manager to manage and monitor the Oracle VM Server and the virtual machines running in it. You must use this password while discovering the Oracle VM Server from Oracle VM Manager.
You can create OS provisioning profile for provisioning Oracle VM Servers.
The list of Oracle VM Managers discovered and managed in Oracle Enterprise Manager Ops Center are displayed in the Administration section.
Select an Oracle VM Manager and the following information is displayed as shown in Figure 6-5.
The Summary page displays information about the Oracle VM Manager, the list of server pools, the discovered Oracle VM Servers, and the virtual machines that are created in the corresponding Oracle VM Servers.
To use the Oracle VM Servers in the server pool and create virtual machines, it is required that you take ownership of the Oracle VM Server from the Oracle VM Manager.
Oracle VM Manager must take ownership of the Oracle VM Servers. Either assign ownership from the Oracle VM Server or take ownership through the Oracle VM Manager.
When you select an Oracle VM Server in the Assets section, the Assign Ownership and Release Ownership actions are available in the Actions pane.
Figure 6-6 shows the options Assign Ownership and Release Ownership displayed in the Actions pane.
Figure 6-6 Assign and Release Ownership From Oracle VM Server
When you select the Oracle VM Manager from the Administration section, the Take Ownership and Release Ownership options are available in the Actions pane.
When you take ownership of the Oracle VM Servers, add them to server pools and create virtual machines in them.
When you discover an Oracle VM Manager, Oracle Enterprise Manager Ops Center provides the option to discover the storage servers attached to it.
The following discovery options are available from the Oracle VM Manager:
File system storage
iSCSI storage
SAN storage
Figure 6-7 shows the options to discover the storage resources from Oracle VM Manager.
Figure 6-7 Discover Storage Resources from Oracle VM Manager
Create discovery profiles for the storage servers and save them.
When you select to discover a storage server, existing discovery profiles are searched for the selected storage type. You can select from an available profile. When there are no profiles available, then the wizard to discover the corresponding storage server appears.
When you discover a storage resource, existing resources such as virtual disks, templates, ISO images, and virtual machine metadata are also discovered and displayed.
See Storage Libraries for Virtualization for more information about the storage servers and the discovering them in Oracle Enterprise Manager Ops Center.
The following type of libraries setup are supported for storage of Oracle VM resources:
Filesystem Storage Libraries
Oracle Enterprise Manager Ops Center provides an option to create Oracle VM Storage Repositories. A storage repository is a logical disk space made available through a file system on top of physical storage hardware. The supported types of file system are NFS and OCFS. When the storage repository is created on an NFS file server, it is a NFS based storage repository. The NFS file server consists of NFS file systems. When the storage repository is created on a LUN, it is a LUN-based repository. The OCFS file system is created on the storage server. Create storage repositories on these file servers to be used by Oracle VM Servers to store resources. The resources include virtual machine metadata, templates, assemblies, ISO images and virtual disks.
To create Oracle VM storage repositories, you must have an Oracle VM Server discovered. Only NFS-based repositories can be shared by multiple server pools.
Static Block Storage Libraries
The LUNs from the storage arrays that are not managed by Oracle Enterprise Manager Ops Center form the static storage libraries. The LUNs are addressed by iSCSI or Fibre Channel protocols. This forms the iSCSI and SAN static storage libraries. Also, add LUNs exported from managed storage arrays. The LUNs can belong to one library at a time.
Dynamic Block Storage Libraries
The storage servers that are discovered and managed in Oracle Enterprise Manager Ops Center are presented under dynamic block storage libraries. The dynamic block storage libraries contains the exported LUNs from the storage array servers.
See Storage Libraries for Virtualization for more information about discovering your storage servers, storage connect plug-ins, creating storage libraries and managing the libraries.
During the installation of Oracle VM Server, the network interface used for the management is configured as a bonded interface. The bond is created with one interface and named as bond0
. You can create additional bonds to add redundancy and load balancing of your network environment.
Attach networks to the Oracle VM Server or to the server pool that consists of a group of Oracle VM Servers on an Oracle VM Manager. Configure the network interfaces or the bonds to the network to be attached. You can assign different roles or functions to the networks attached to the Oracle VM Server.
The following are the network roles available for an Oracle VM Server:
Server Management: Manages the Oracle VM Servers in a server pool. The Oracle VM Manager has one Server Management network.
Live Migrate: Migrates the virtual machines from one Oracle VM Server to another in the server pool, without changing the state of the virtual machine.
Cluster Heartbeat: Verifies that the Oracle VM Servers in the server pool are running.
Virtual Machine: Monitors the network traffic between the virtual machines in a server pool.
Storage: Transfers between virtual machines and virtual disks.
The management network created during the installation of Oracle VM Server has the following roles:
Server Management
Cluster Heartbeat
Live Migrate
You can add and remove the roles of this management network, except for the Server Management role.
Depending on the available network interfaces on the Oracle VM Server, you can attach networks to Oracle VM Server and assign different roles to the networks. For example, you can attach the network in which your storage servers are placed and assign the Storage role to that network. You can assign a network with Live Migrate to be used only for migration.
For more information about setting different roles for network, refer to the Oracle VM User's Guide.
When you install or discover the Oracle VM Server through the Oracle Enterprise Manager Ops Center UI, take ownership of the server from the Oracle VM Manager. This helps to place the Oracle VM Servers in the server pool. The following are some functions available for managing Oracle VM Servers:
Edit Oracle VM Server information
Reboot the server
Shutdown the server
Update the server
Edit IPMI configuration
Select the Oracle VM Server and click Edit Attributes in the Actions pane. You can edit the following Oracle VM Server information:
Name
Description
Tags
Intelligent Platform Management Interface (IPMI) allows you to remotely power off an Oracle VM Server, and to send a Wake-on-LAN message to power on an Oracle VM Server without having to physically press the power button. You can edit the IPMI configuration using the following procedure:
To perform hardware or software maintenance, an Oracle VM Server can be placed in maintenance mode. When an Oracle VM Server is placed in maintenance mode, all of the virtual machines running on the Oracle VM Server are automatically migrated to other Oracle VM Servers in the server pool, if they are available, otherwise they are stopped. When the Oracle VM Server is the master Oracle VM Server in the server pool, this role is moved to another Oracle VM Server in the server pool, if available.
When you have finished with the maintenance on the Oracle VM Server and you are ready for it to rejoin the server pool, select the option Remove From Maintenance Mode.
Using a YUM repository, update or upgrade Oracle VM Servers. To access patch updates for Oracle VM, contact Oracle to purchase an Oracle VM Support contract and gain access to the Unbreakable Linux Network (ULN) which contains updates for Oracle VM. When you have access to ULN, you can use this to set up your own Yum repository to use when updating your Oracle VM Servers.
A YUM repository is required to update or upgrade Oracle VM Servers that are attached to an Oracle VM Manager. Set up a YUM repository and configure for automatic updates of the Oracle VM Servers managed by an Oracle VM Manager. Setting up a YUM repository is beyond the scope of this document.
After you set up a YUM repository, select the Oracle VM Manager and click Configure YUM Repository in the Actions pane. Enter the following details of the repository to configure it.
Yum Repository Name: A name for the Yum repository.
YUM Base URL: The URL to access the Yum repository, for example, the Oracle public YUM repository is at:
Enable GPG Key: Select whether to use the GPG Key for the Yum repository. The GPG key or GnuPG key is the GNU project's implementation of the OpenPGP key management standard.
Yum GPG Key: This field is enabled when you select Enable GPG Key. Enter the GPG key for the Yum repository, for example:
http://public-yum.oracle.com/RPM-GPG-KEY-oracle-e15
The GPG key must be available through HTTP, FTP, or HTTPS protocols. The GPG key for Oracle-signed updates from ULN is pre-installed on the Oracle VM Server at /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
. When you want to use this GPG key, enter as:
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
You can update an Oracle VM Server for x86.
When you update the Oracle VM Server, the server is placed into maintenance mode and then the update is performed. When there are virtual machines in the Oracle VM Server, they are migrated to other Oracle VM Servers in the server pool, if they are available, otherwise they are stopped. After the update, the Oracle VM Server remains in maintenance mode. Select the option Remove From Maintenance Mode.
You can group one or more Oracle VM Servers in an Oracle VM Manager and create server pools.
You must create server pools before you start creating virtual machines. You can apply the virtual machines plans only on Oracle VM Servers that are in a server pool.
This section describes only how to create server pools using Oracle Enterprise Manager Ops Center. For more information about server pool policies, and managing server pools, see Server Pools.
When you create a server pool for Oracle VM Server for x86 systems, you must have the following information defined:
Cluster file system
Server pool master
Virtual IP address for the server pool master
Shared access to the server pool resources is a must for providing for high availability for the virtual machines running in the Oracle VM Servers of the server pool. This is achieved by cluster file system OCFS2 which allows multiple Oracle VM Servers to access the same disk at the same time. OCFS2 ensures that the Oracle VM Servers in a server pool can access and modify resources in the shared repositories in a controlled manner.
When you create a server pool, you must specify the server pool file system for the cluster heartbeat and other cluster information. The file system can be NFS shares or LUNs of iSCSI or SAN-based storage servers. Oracle VM formats the server pool file system as OCFS2 file system.
In Oracle Enterprise Manager Ops Center, the cluster is always enabled by default. The cluster configuration is pushed out to all the Oracle VM Servers in the server pool and the cluster heartbeat starts when the server pool is created. You can set a separate network for this cluster heartbeat. See Manage Networks for more information about setting up the networks and its role for an Oracle VM Server.
An Oracle VM Server is internally elected as Server Pool Master.
You cannot set the role for an Oracle VM Server. When the elected Oracle VM Server fails, the role is set for another Oracle VM Server in the server pool. The virtual IP address provided while creating the server pool is assigned to the Oracle VM Server that has been elected as server pool master.
The server pool policies that are applicable for Oracle VM Server for x86 are as follows:
Set the CPU utilization threshold. Places the virtual machines on the Oracle VM Server that has the lowest relative load.
Set the CPU utilization threshold. Places the virtual machines on minimum number of Oracle VM servers to minimize the power consumption.
You can select the automatic load balancing so that the virtual machines can be migrated automatically in the server pool whenever the thresholds are exceeded.
When you enable automatic load balancing for Oracle VM Server for x86 server pool, the server pool is checked continuously for the selected placement policy. When the threshold exceeds, the virtual machines are migrated from one Oracle VM Server to another.
When you have selected power minimization and automatic load balancing policy, and the servers in the server pool are not overloaded, some Oracle VM Server host servers are freed from the logical domains and powered off to minimize power consumption.
When the servers are overloaded and there are no other servers in the pool to host the virtual machines, then the policy decides to start a powered-off server using its Wake-on-LAN capability and live migrate the virtual machines to take up the load. The Wake-on-LAN capability must be enabled on the BIOS of the Oracle VM Server.
When an Oracle VM Server fails, the virtual machines are migrated to another Oracle VM Server in the server pool, when you have selected Enable High Availability while creating the virtual machine.
A virtual machine comprises configurable set of resources and its own operating system. The resources include virtual CPU, memory, network, and virtual disk. You can start, stop, and restart each virtual machine independently.
You can create virtual machines using one of the following installation sources:
Templates
Existing virtual machines
ISO images in storage libraries
Mounted ISO images on NFS, HTTP or FTP server
Netboot
The operating system provisioned on the virtual machines can be hardware virtualized, paravirtualized and, hardware virtualized with paravirtualized drivers. Based on these virtualization types, you select the appropriate option to create the virtual machines.
Note:
You can create virtual machines only in an Oracle VM Server for x86 server pools.
The following virtualization types are available for a virtual machine:
HVM
Hardware virtualization or fully virtualized. For HVM, select an ISO image from the storage library and create a virtual machine. You must activate the hardware virtualization in the BIOS of the Oracle VM Server in which you want to create the virtual machine. The OS might be completely unmodified.
PVM
Paravirtualized. You must use an ISO file mounted from an NFS share, HTTP, or FTP server. The OS is modified and recompiled to be made aware of the virtual environment. The paravirtualized guests run at near native speed, since most memory, disk and network accesses are optimized for maximum performance.
PVHVM or HVM with PV Drivers
Hardware assisted virtualization with a paravirtualized driver. Install paravirtualized drivers on the hardware virtualized machines for optimized performance. This is mainly used for running Microsoft Windows guest operating systems.
Capture the virtual machine requirements in the form of profile in Oracle Enterprise Manager Ops Center. Create a deployment plan with this profile and apply it on the selected targets. Use these profiles and plans to create more than one virtual machine at a time.
Create a deployment plan with this profile and apply the plan to create virtual machines. Except for the installation source Netboot, all the other source types results in creating a virtual machine with the OS installed. For virtual machine created with Netboot installation source, you must provision the OS on it separately using an OS provisioning plan.
The next section describes the different methods of deployment of virtual machine plans to create virtual machines.
This section describes how to create virtual machines and provision OS in an Oracle VM Server using Oracle Enterprise Manager Ops Center.
The two new deployments plans for provisioning and creating multiple virtual machines are:
Single step deployment plan to create only virtual machines
Multi-step deployment plan to create virtual machine, provision OS, and install other applications.
In the single step deployment plan, the virtual machine can be created using Oracle VM templates or ISO images stored in Oracle VM repositories. Or only a virtual machine is created with ready to be booted using a separate OS provision plan.
In the complex deployment plan, you can configure and install the virtual machine, provision the OS, install software applications, apply monitoring profiles, and operational plans.
This is a single step virtual machine plan that creates a virtual machine and the OS is installed depending on the installation source selection. When you create HVM or PVHVM type virtual machines, select the ISO image to be used to create the virtual machine. You can select only one ISO image and multiple ISO files are not supported. While selecting the virtual disks, you have the option to select the ISO image. The following procedure describes how to apply the plan for creating a virtual machine:
Except for the virtual machine created with Netboot as the installation source, all the other virtual machines are installed and provisioned with the OS.
Use the complex plan Configure and Install Virtual Machines to install the virtual machine and provision the OS on it. See the Related Resources for Oracle VM Server for x86 section for more information about complex plans.
You can install an OS on virtual machines created on the Oracle VM Server. Use OS provisioning profiles to install the OS.
See the Related Resources for Oracle VM Server for x86 section for more information about creating provisioning profiles and plans to install an OS.
Oracle Enterprise Manager Ops Center provides options to manage the lifecycle operations of virtual machines. You can start, suspend, resume, shut down, and delete virtual machines on the UI.
When you select the Oracle VM Server in the Assets section, the Summary tab in the center pane lists all the virtual machines that are currently running. All the options required to manage a virtual machine is available on the UI.
Figure 6-9 shows the actions available for a virtual machine from Oracle VM Server.
Figure 6-9 Action Icons for Virtual Machines
Select the virtual machine and click the Start Selected Guest icon. The job is initiated to start the virtual machine.
Select the virtual machine and click the Suspend Selected Guest icon. When you suspend a virtual machine, you cannot use the virtual machine. Click Ok to confirm the suspend action.
Select the virtual machine in the running state and click the Reboot Selected Guest icon. Click Reboot Guest to confirm the action.
Select the virtual machine and click the Shut Down Guest icon. When you shut down a virtual machine, it is disconnected from its network. Click Ok to shut down the virtual machine.
Select the virtual machine and click the Delete Selected Guest icon. Click Ok to confirm deleting the virtual machine. When you delete a virtual machine, all the references to the virtual machine such as the metadata and disk images are deleted from the system.
All these options are also available in the Actions pane when you select the virtual machine in the Assets section.
The boot order that you have set during virtual machine installation is displayed. You can modify the boot order. You must specify the appropriate boot order depending on the installation source of the virtual machine.
The following list shows the preferred boot options for different installation source:
Hardware Virtualized Machine (HVM): CDROM and Disk
Paravirtualized Virtual Machine (PVM): Network and Disk
Templates and existing virtual machines: Disk
Netboot: Network
If the virtual machine is in running state, then the modified boot order takes effect on the next reboot. Ensure to select the correct boot order for the virtual machine.
The Edit Boot Order option is available in the Actions pane of a selected virtual machine. Figure 6-10 shows the Edit Boot Order window that is displayed to edit the boot order of the virtual machine.
Modify the boot order and click Save Boot Order to save the changes.
You can enable high availability for a virtual machine while creating a virtual machine profile. When the virtual machines are selected to be highly available and the Oracle VM Server shuts down or fails, the virtual machine is restarted on another available Oracle VM Server in the server pool.
You can also use the options Enable Automatic Discovery and Disable Automatic Discovery for a virtual machine to manage the high availability.
For instructions in performing actions or to learn more about the role of this feature, go to one of the following resources:
See the following chapters of the Oracle Enterprise Manager Ops Center Configure Reference:
See the Manage Assets chapter for information about discovering and managing assets.
See the Create Plans and Profiles chapter for information about complex plans for installing virtual machines and provisioning operating systems.
See the Operating System Management chapter of the Oracle Enterprise Manager Ops Center Operate Reference for more information about creating provisioning profiles and plans to install an OS.
See the Software Libraries chapter of the Oracle Enterprise Manager Ops Center Configure Reference to upload or import images into the software library.
See the Oracle Enterprise Manager Ops Center Administration Guide for information about users and roles.
For current discussions, see the product blog at https://blogs.oracle.com/opscenter
.