Oracle VM Manager User's Guide, Release 2.2

Release 2.2

E15441-02

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

What's New in Oracle VM Manager

- New Features in Release 2.2.0

- New Features in Release 2.1.5

- New Features in Release 2.1.2

- New Features in Release 2.1.1

1 Overview of Oracle VM Manager

- 1.1 What Is Virtualization?

- 1.2 Why Virtualize?

- 1.3 Introduction to Oracle VM

- 1.4 Configuration of Oracle VM Manager

- 1.5 Roles in Oracle VM Manager

- 1.6 Main Features of Oracle VM Manager

2 Getting Started with Oracle VM Manager

- 2.1 Registering an Account with Oracle VM Manager

- 2.2 Logging In to Oracle VM Manager

- 2.3 Using the Wizard to Create a Server Pool

3 Managing Server Pools

- 3.1 Designing a Server Pool

- 3.2 Creating a Server Pool

- 3.3 Searching For a Server Pool

- 3.4 Editing a Server Pool

- 3.4.1 Editing Server Pool

- 3.4.2 Editing Server Pool Servers

- 3.4.3 Editing Server Pool Users

- 3.5 Enabling High Availability (HA)

- 3.6 Deleting a Server Pool

- 3.7 Restoring a Server Pool

- 3.8 Viewing Server Pool Logs

4 Managing Servers

- 4.1 Adding a Server

- 4.2 Searching For a Server

- 4.3 Viewing a Server

- 4.4 Editing a Server

- 4.4.1 Edit Server

- 4.4.2 Change Oracle VM Agent Password

- 4.4.3 Change Utility Server Password

- 4.5 Shutting Down a Server

- 4.6 Restarting a Server

- 4.7 Putting a Server Into Maintenance Mode

- 4.8 Deleting a Server

- 4.9 Viewing Server Logs

5 Managing Resources

- 5.1 Managing Virtual Machine Templates

- 5.1.1 Importing a Virtual Machine Template

- 5.1.1.1 Selecting from the Server Pool

- 5.1.1.2 Downloading from External Source

- 5.1.1.3 Converting a Linux or Windows Host to a Virtual Machine Template (P2V)

- 5.1.2 Statuses of Virtual Machine Templates

- 5.1.3 Searching For a Virtual Machine Template

- 5.1.4 Reimporting a Virtual Machine Template

- 5.1.5 Approving the Imported Virtual Machine Template

- 5.1.6 Editing a Virtual Machine Template

- 5.1.7 Deleting a Virtual Machine Template

- 5.2 Managing Virtual Machine Images

- 5.2.1 Importing a Virtual Machine Image

- 5.2.1.1 Selecting from the Server Pool

- 5.2.1.2 Downloading from External Source

- 5.2.1.3 Converting a Linux or Windows Host to a Virtual Machine (P2V)

- 5.2.2 Statuses of Virtual Machine Images

- 5.2.3 Searching For a Virtual Machine Image

- 5.2.4 Reimporting a Virtual Machine Image

- 5.2.5 Approving the Imported Virtual Machine Image

- 5.2.6 Editing a Virtual Machine Image

- 5.2.7 Deleting a Virtual Machine Image

- 5.3 Managing ISO Files

- 5.3.1 Importing an ISO File

- 5.3.1.1 Selecting from the Server Pool

- 5.3.1.2 Downloading from External Source

- 5.3.2 Statuses of ISO Files

- 5.3.3 Searching For an ISO File

- 5.3.4 Reimporting an ISO File

- 5.3.5 Approving the Imported ISO File

- 5.3.6 Changing Status of an ISO File

- 5.3.7 Deleting an ISO File

- 5.4 Managing Shared Virtual Disks

- 5.4.1 Creating a Shared Virtual Disk

- 5.4.2 Statuses of Shared Virtual Disks

- 5.4.3 Searching For a Shared Virtual Disk

- 5.4.4 Importing a Shared Virtual Disk

- 5.4.5 Deleting a Shared Virtual Disk

6 Managing Virtual Machines

- 6.1 Overview of Virtual Machines

- 6.1.1 Virtual Machine Types

- 6.1.2 Virtual Machine Statuses

- 6.1.2.1 Creating

- 6.1.2.2 Initializing and Running

- 6.1.2.3 Pausing, Paused and Unpausing

- 6.1.2.4 Suspending, Suspended and Resuming

- 6.1.2.5 Shutting Down and Powered Off

- 6.1.2.6 Saving

- 6.1.2.7 Cloning

- 6.1.2.8 Migrating

- 6.1.2.9 Error

- 6.1.3 Life Cycle Management of a Virtual Machine

- 6.1.4 Viewing Virtual Machine Logs

- 6.2 Supported Guest Operating Systems

- 6.3 Creating a Virtual Machine

- 6.3.1 Creating Virtual Machine From a Template

- 6.3.2 Creating a Virtual Machine From Installation Media

- 6.3.3 Creating a Network Bootable (PXE boot) Virtual Machine

- 6.4 Starting and Shutting Down a Virtual Machine

- 6.4.1 Starting a Virtual Machine

- 6.4.2 Shutting Down a Virtual Machine

- 6.4.3 Pausing and Unpausing a Virtual Machine

- 6.4.4 Suspending and Resuming a Virtual Machine

- 6.4.5 Resetting a Virtual Machine

- 6.5 Connecting to a Virtual Machine's Console

- 6.5.1 Installing the Console Plug-In

- 6.5.2 Logging In to a Virtual Machine

- 6.6 Viewing Virtual Machine Details

- 6.7 Editing a Virtual Machine

- 6.7.1 General

- 6.7.2 Network

- 6.7.3 Storage

- 6.7.3.1 Virtual Disks

- 6.7.3.2 Boot Source/CDROM

- 6.7.4 Policies

- 6.7.4.1 High Availability

- 6.7.4.2 Placement Policy

- 6.7.5 Profiles

- 6.7.5.1 Login/Password

- 6.7.5.2 Operating System

- 6.8 Reproducing Virtual Machines

- 6.8.1 Deploying a Virtual Machine

- 6.8.2 Cloning Virtual Machines

- 6.8.3 Saving a Virtual Machine as a Template

- 6.9 Migrating a Virtual Machine

- 6.10 Deleting a Virtual Machine

- 6.10.1 Deleting a Virtual Machine in Powered Off or Error Status

- 6.10.2 Deleting a Stuck Virtual Machine

7 Managing Users and Groups

- 7.1 The Default Account

- 7.2 Managing Users

- 7.2.1 Creating a User

- 7.2.2 Viewing Details

- 7.2.3 Editing a User

- 7.2.4 Changing a Role

- 7.2.5 Deleting a User

- 7.3 Managing Groups

- 7.3.1 Default Groups

- 7.3.2 Creating a Group

- 7.3.3 Adding a User to a Group

- 7.3.4 Editing a Group

- 7.3.5 Deleting a Group

- 7.4 Viewing Logs

A Preparing Virtual Machines For Importing

B Backing Up and Restoring Oracle VM Manager

- B.1 Backing Up Oracle VM Manager

- B.2 Restoring Oracle VM Manager

C Web Services API

- C.1 Web Services API

- C.2 Creating a Web Service Client

- C.2.1 Creating a Proxy Class in Java

- C.2.1.1 Using Oracle JDeveloper

- C.2.1.2 Using wsimport

- C.2.2 Creating a Proxy Class in Python

- C.3 Authentication and Security

- C.4 Web Service Locations

- C.5 Web Services

- C.5.1 LifecycleService

- C.5.2 ResourceService

- C.5.3 PluginService

- C.5.4 ServerPoolService

- C.5.5 VirtualMachineService

- C.5.6 AdminService

D Troubleshooting

- D.1 Log Files

- D.2 Cannot Log In to Oracle VM Manager

- D.3 Cannot Create a Virtual Machine from Installation Media

- D.4 Insufficient Space in Repository for Creating a Virtual Machine

- D.5 The Virtual Machine Stuck in a Status

- D.6 The Status of the Virtual Machine Is Error

- D.6.1 HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS?

- D.6.2 Cannot find host server for vm('/OVS/running_pool/vm_name')

- D.6.3 Could not find '/OVS/running_pool/vm_name' in any storage repository

- D.6.4 /opt/ovs-agent-version/utils/rcp.py /OVS/running_pool/vm_name/ root@example.com:/OVS/running_pool/vm_name password=>encounter 'permission denied'!

- D.6.5 xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Domain 'vm_name' already exists with ID 'number'

- D.6.6 vm('/OVS/running_pool/vm_name') status ('RUNNING') not in ('DOWN', 'ERROR')

- D.6.7 No server selected to run vm('/OVS/running_pool/vm_name') memory=number

- D.6.8 xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Device number (vif) could not be connected. Could not find bridge device null

- D.6.9 No pxe bootable vif found

- D.6.10 virt-install options=>mount: can't get address for host umount: /var/lib/xen/xennfs.mkvX0Q: not mounted ERROR: Unable to mount NFS location!

- D.6.11 winxp_build failed: global name 'xen_handle_vif_qos' is not defined

- D.7 Cannot Access Virtual Machine Console

- D.8 Cannot Perform Live Migration

- D.9 Cannot Change CD in the Virtual Machine

- D.10 Cannot Import External Resources

- D.11 Remote Host Identification Error in Server Pool

E Third Party Licenses

- E.1 Apache XML-RPC

- E.1.1 Apache XML-RPC Software License

- E.2 Third-Party Products Included with Sun Microsystems Products

- E.2.1 CS CodeViewer v1.0

- E.2.2 DES and 3xDES

- E.2.3 Crimson v1.1.1

- E.2.4 NSIS 1.0j

- E.2.5 Some Portions licensed from IBM

- E.2.6 Portions Copyright Eastman Kodak Company 1992

- E.2.7 Lucida

- E.2.8 Portions licensed from Taligent, Inc.

- E.2.9 Additionally for JRE/JDK 1.5 / 5.0

Glossary

Index

Oracle® VM

Manager User's Guide

Release 2.2

E15441-02

November 2009

Oracle VM Manager User's Guide, Release 2.2

E15441-02

Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved.

Primary Author: Alison Holloway, Faxin Hou

Contributing Author: Prakash Jashnani, Carol Tian, Huili Wang

Contributor: Adam Hawley, Gaojun Liu, Julien Sero, Honglin Su, Charles Wang, Junjie Wei, Xiaodong Yang, Yanbing Zheng

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

This preface includes the following topics:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This document is intended for users of Oracle VM Manager.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Related Documents

For more information, see the following documents in the Oracle VM Release 2.2 documentation set:

- Oracle VM Server Quick Start Guide

- Oracle VM Manager Release Notes

- Oracle VM Manager Installation Guide

- Oracle VM Server Release Notes

- Oracle VM Server Installation Guide

- Oracle VM Server User's Guide

- Oracle VM Windows Paravirtual Drivers Installation Guide

- Oracle VM Template Builder Installation and User's Guide

- Oracle VM Manager Web Services API Reference

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

What's New in Oracle VM Manager

This preface introduces the new features and enhancements of Oracle VM Manager in the 2.x releases since the initial 2.1 release. This information is useful to users who have used a previous release of Oracle VM Manager.

New Features in Release 2.2.0

The new features and enhancements in Oracle VM Manager Release 2.2.0 include:

Server Pool Master Fail Over in HA

If the Server Pool Master fails in a High Availability set up, another Oracle VM Server is automatically selected from the server pool to act as the Server Pool Master. See Section 3.5, "Enabling High Availability (HA)".

Importing Virtual Machines in VHD (Virtual Hard Disk) Format

You can import virtual machines in VHD (Virtual Hard Disk) format. See Section 5.2, "Managing Virtual Machine Images".

Importing Shared Virtual Disks

You can import a shared virtual disk. See Section 5.4.4, "Importing a Shared Virtual Disk".

Importing Multipath Devices as Shared Virtual Disks

You can import multipath devices as shared virtual disks. See Section 5.4, "Managing Shared Virtual Disks".

Scheduling Priority for Virtual CPUs

You can set the scheduling priority for virtual CPUs in virtual machines, and cap the percentage to which the virtual CPUs can receive scheduled time. See Section 6.7.4, "Policies".

Placing a Server in Maintenance Mode

You can place an Oracle VM Server into maintenance mode and make it unavailable using the Set Maintenance button on the Servers page. See Section 4.7, "Putting a Server Into Maintenance Mode".

Virtual Machine Tree Views

A new tree view is available for virtual machines on the Virtual Machines page. The tree view enables you to display:

- All the virtual machines managed by Oracle VM Manager

- The virtual machines created in a server pool

- The virtual machines running on an Oracle VM Server

Resetting a Virtual Machine

You can reset a virtual machine from within the Oracle VM Manager user interface that may be having difficulties in starting or stopping, or performing some other action. Resetting a virtual machine was previously only available using a SQL command on the command line. See Section 6.4.5, "Resetting a Virtual Machine".

Changing the Group to Which a Virtual Machine Belongs

You can change the group to which a virtual machine belongs using the Group List drop down on the General page when editing a virtual machine. See Section 6.7.1, "General".

Improved Logging

Improved logging of activities, warnings and errors to aid in monitoring and troubleshooting. See Section 4.9, "Viewing Server Logs", Section 6.1.4, "Viewing Virtual Machine Logs", and Section 7.4, "Viewing Logs".

New Features in Release 2.1.5

The new features and enhancements in Oracle VM Manager Release 2.1.5 include:

Web Services API

A Web services Application Programming Interface (API) to enable integration of third party products with Oracle VM Manager. See Appendix C, "Web Services API".

Server Pool Management UI Enhancements

The server pool management pages in the user interface have been improved. See Chapter 3, "Managing Server Pools".

New Features in Release 2.1.2

The new features and enhancements in Oracle VM Manager Release 2.1.2 include:

Server Pool Wizard

If it is the first time you log in to Oracle VM Manager after installation, you are prompted to follow the Wizard to create a server pool containing only one physical server which will act as the Server Pool Master, the Virtual Machine Server, and the Utility Server. See Section 2.3, "Using the Wizard to Create a Server Pool".

High Availability (HA) for Server Pools and Virtual Machine Servers

In Release 2.1.2, various levels of high availability is implemented.

You can enable high availability for server pools and virtual machines when creating them. See Section 3.5, "Enabling High Availability (HA)" and Section 6.3, "Creating a Virtual Machine".

You can also enable high availability when importing virtual machine templates and images. See Section 5.1, "Managing Virtual Machine Templates" and Section 5.2, "Managing Virtual Machine Images".

You can choose to migrate the running virtual machines when restarting, shutting down, or deleting an Oracle VM Server. See Section 4.6, "Restarting a Server", Section 4.5, "Shutting Down a Server", and Section 4.8, "Deleting a Server".

Virtual Machine Conversions, V2V and P2V

Oracle VM allows you to convert a VMware virtual machine to an Oracle VM virtual machine (known as V2V), or to convert a Linux host to an Oracle VM virtual machine or template (known as P2V).

To convert a VMware virtual machine to an Oracle VM virtual machine (V2V), see Section 5.2.1, "Importing a Virtual Machine Image".

To convert a Linux host to an Oracle VM virtual machine or template (P2V), see Section 5.1.1.3, "Converting a Linux or Windows Host to a Virtual Machine Template (P2V)" and Section 5.2.1.3, "Converting a Linux or Windows Host to a Virtual Machine (P2V)".

Keyboard Layout Selection

Oracle VM Manager provides a keyboard selection when you create a virtual machine from installation media, or when you change configurations of a virtual machine. See Section 6.3.2, "Creating a Virtual Machine From Installation Media" and Section 6.7.5, "Profiles".

Rate Limit of Virtual Network Interface (VIF)

You can set up the rate limit of a virtual network interface (VIF) to customize the network traffic threshold. See Section 6.7.2, "Network".

Priority Class of Virtual Disk

The enhanced virtual disk feature enables you to set up the priority class of a virtual disk. See Section 6.7.3, "Storage".

New Features in Release 2.1.1

The new features and enhancements in Oracle VM Manager Release 2.1.1 include:

Network Bootable (PXE boot) Virtual Machines

Oracle VM Manager provides a new way of creating virtual machines in Release 2.1.1. Besides creating virtual machines from templates and installation media, you can create network bootable (PXE boot) virtual machines. See Section 6.3.3, "Creating a Network Bootable (PXE boot) Virtual Machine".

Hot Plugging Memory, Virtual Network Interface (VIF), and Virtual Disk

Some changes in the configuration of a virtual machine take effect immediately without restarting the virtual machine. See Section 6.7, "Editing a Virtual Machine".

Virtual Network Interface (VIF) Type

You can select the virtual network interface (VIF) type for a virtual machine. See Section 6.7.2, "Network".

Preferred Server

When creating a virtual machine, you can select a preferred server for a virtual machine. See Step 3 in Section 6.3.1, "Creating Virtual Machine From a Template".

Boot Source

After creating a virtual machine, you can choose to start the virtual machine from hard disk (HDD), CD-ROM, or through Preboot Execution Environment (PXE). See Section 6.7.3, "Storage".

Refresh Automatically

On the Virtual Machines page, you can choose to either refresh Web pages manually, or refresh every 30 seconds automatically. See Section 6.4.1, "Starting a Virtual Machine".

Deleting Related Directories

You can choose to either delete or retain the related directories when deleting a server pool. See Section 3.6, "Deleting a Server Pool".

1 Overview of Oracle VM Manager

This chapter gives an overview of Oracle VM Manager. It includes the following topics:

- What Is Virtualization?

- Why Virtualize?

- Introduction to Oracle VM

- Configuration of Oracle VM Manager

- Roles in Oracle VM Manager

- Main Features of Oracle VM Manager

1.1 What Is Virtualization?

Virtualization is the ability to run multiple virtual machines on a single piece of hardware. The hardware runs software that enables you to install multiple operating systems capable of running simultaneously and independently, in their own secure environment, with minimal impact on performance. Each virtual machine has its own virtual CPU, network interfaces, storage, and operating system.

1.2 Why Virtualize?

With increased server provisioning in the datacenter, several factors play a role in stifling growth. Increased power and cooling costs, physical space constraints, man power, and interconnection complexity all contribute significantly to the costs and feasibility of continued expansion.

Commodity hardware manufacturers have begun to address some of these concerns by shifting their design goals. Rather than focusing solely on raw gigahertz performance, manufacturers have enhanced the feature sets of CPUs and chip sets to include lower wattage CPUs, multiple cores per CPU die, advanced power management, and a range of virtualization features. By employing appropriate software to enable these features, several advantages are realized:

- Server Consolidation: By combining workloads from a number of physical hosts into a single host, a reduction in servers can be achieved as well as a corresponding decrease in interconnect hardware. Traditionally, these workloads would need to be specially crafted, partially isolated and well behaved, but with new virtualization techniques none of these requirements are necessary.

- Reduction of Complexity: Infrastructure costs are massively reduced by removing the need for physical hardware, and networking. Instead of having a large number of physical computers, all networked together, consuming power and administration costs, fewer computers can be used to achieve the same goal. Administration and physical setup is less time consuming and costly.

- Isolation: Virtual machines run in sand-boxed environments. They cannot access each other, so if one virtual machine performs poorly, or crashes, it does not affect any other virtual machine.

- Platform Uniformity: In a virtualized environment, a broad, heterogeneous array of hardware components is distilled into a uniform set of virtual devices presented to each guest operating system. This reduces the impact across the IT organization: from support, to documentation, to tools engineering.

- Legacy Support: With traditional bare-metal operating system installations, when the hardware vendor replaces a component of a system, the operating system vendor is required to make a corresponding change to enable the new hardware to function properly (for example, an ethernet card). As an operating system ages, the operating system vendor may no longer provide hardware enabling updates. In a virtualized operating system, the hardware remains constant for as long as the virtual environment is in place, regardless of any changes occurring in the real hardware, including full replacement.

1.3 Introduction to Oracle VM

Oracle VM is a platform that provides a fully equipped environment to better leverage the benefits of virtualization technology. Oracle VM enables you to deploy operating systems and application software within a supported virtualization environment. The components of Oracle VM are:

- Oracle VM Manager: Provides the user interface, which is a standard ADF (Application Development Framework) web application, to manage Oracle VM Servers, virtual machines, and resources. Use Oracle VM Manager to:

- Create virtual machines from installation media or from a virtual machine template

- Delete virtual machines

- Power off virtual machines

- Import virtual machines

- Deploy and clone virtual machines

- Perform live migration of virtual machines

- Import and manage ISOs

- Create and manage virtual machine templates

- Create and manage shared virtual disks

- Oracle VM Server: A self-contained virtualization environment designed to provide a lightweight, secure, server-based platform to run virtual machines. Oracle VM Server is based upon an updated version of the underlying Xen hypervisor technology, and includes Oracle VM Agent.

- Oracle VM Agent: Installed with Oracle VM Server. It communicates with Oracle VM Manager to manage virtual machines.

Figure 1-1, "Oracle VM Architecture" shows the components of Oracle VM.

Figure 1-1 Oracle VM Architecture

This book discusses Oracle VM Manager. See the Oracle VM Server Installation Guide and the Oracle VM Server User's Guide for information on installing and using Oracle VM Server.

1.4 Configuration of Oracle VM Manager

This section describes the configuration structure of Oracle VM Manager.

Figure 1-2 Deployment View of Oracle VM Manager

As shown in Figure 1-2, when you deploy Oracle VM Manager, the following components are involved:

- Oracle VM Manager Host: The host machine on which Oracle VM Manager is installed is known as an Oracle VM Manager host. It provides the interface where most of the virtual machine management tasks are performed. Its main function is to forward operational commands from users to other, possibly remote, servers and display their results.

- Servers: An Oracle VM Server, once added to a server pool, is assigned with one, two, or even all three functions, namely, Server Pool Master function, Utility Server function, and Virtual Machine Server function.
Oracle VM Agent provides the interface to each server function. Therefore, if An Oracle VM Server is assigned as a Server Pool Master only, then the Server Pool Master agent component is activated. Otherwise, if it is assigned as both a Server Pool Master, and a Utility Server, their respective agent components are activated, and so on.

An Oracle VM Server can perform one, two, or all of the three functions described below:

- Server Pool Master: The Server Pool Master is the core of the server pool operations. It acts as the contact point of the server pool to the outside world, and also as the dispatcher to other servers within the server pool.
The load balancing is implemented by the Server Pool Master. For example, when you start a virtual machine, the Server Pool Master chooses a Virtual Machine Server with the maximum resources available to run the virtual machine.

There is only one Server Pool Master at one time in a server pool. If the Server Pool Master fails or becomes unavailable, the role is automatically assigned to another Oracle VM Server in the server pool, if one available.

- Utility Server: The Utility Server is responsible for I/O intensive operations such as, copying, or moving files. Its function focuses on the creation and removal operations of virtual machines, servers, and server pools.
There can be one or more Utility Servers in a server pool. When there are several Utility Servers, the Server Pool Master chooses the Utility Server with the maximum CPU resources available to conduct the task.

- Virtual Machine Server: The primary function of the Virtual Machine Server is to run virtual machines, thus acting as a hypervisor. Oracle VM Agent is set up on the Virtual Machine Server to establish communication between the Server Pool Master, other Utility Severs, and Virtual Machine Servers.
There can be one or more Virtual Machine Servers in a server pool. When there are several Virtual Machine Servers, the Server Pool Master chooses the Virtual Machine Server with the maximum resources available (for example, memory) to start and run the virtual machine.

- Server Pools: A server pool is an autonomous region that contains one or more Oracle VM Servers. A server pool presents a unified view of the storage in which the virtual machines reside. Each server pool must have its own shared storage.
The server functions described above can be deployed in a server pool in a variety of ways as shown in Figure 1-2. For example, in Server Pool 1, each one of the three functions is implemented on an individual Oracle VM Server. In Server Pool 2, all of the three functions are performed by a single Oracle VM Server.

In medium to large scale environments with more than just a few virtual machines in a Server Pool, it is recommended that the Server Pool Master and Utility Server functions reside together or individually on a separate and dedicated physical server that does not host any guest virtual machines, as illustrated in Server Pool 3. This is to prevent any significant Server Pool Master or Utility Server usage from impacting the performance of the workloads hosted in the guest virtual machines.

- Storage: A storage resource is mounted to store virtual machines, external resources, and other data files that are shared among Oracle VM Servers in the server pool. In order to perform Live Migration of virtual machines between separate physical machines in the server pool, each machine involved must have shared access to storage.

1.5 Roles in Oracle VM Manager

As a user of Oracle VM Manager, you can have one of three roles: User, Manager, or Administrator.

- User: Creates and manages virtual machines, and also imports resources.

- Manager: Manages the server pools, resources, and servers. A manager also has all the privileges of the User role.

- Administrator: Performs administration tasks such as managing user accounts, importing resources, and approving imported resources. An Administrator also has all privileges of the User role and the Manager role.

Table 1-1 briefly lists the available functions for each user role.

Table 1-1 Available Functions for Each Role

Roles

Available Functions

User

- Importing resources. See Chapter 5, "Managing Resources".

- Managing virtual machines, including all the operations described in Chapter 6, "Managing Virtual Machines".

Manager

- Managing server pools, including all the operations described in Chapter 3, "Managing Server Pools".

- Managing servers, including all the operations described in Chapter 4, "Managing Servers".

- Managing resources, including all the operations described in Chapter 5, "Managing Resources".

- Managing virtual machines, including all the operations described in Chapter 6, "Managing Virtual Machines".

Administrator

- Managing server pools, including all the operations described in Chapter 3, "Managing Server Pools".

- Managing servers, including all the operations described in Chapter 4, "Managing Servers".

- Managing resources, including all the operations described in Chapter 5, "Managing Resources".

- Managing virtual machines, including all the operations described in Chapter 6, "Managing Virtual Machines".

- Managing users and groups, including all the operations described in Chapter 7, "Managing Users and Groups".

1.6 Main Features of Oracle VM Manager

Oracle VM Manager provides the following main features:

- Virtual machine life cycle management. This includes creating virtual machines from either installation media or from templates, starting, logging in, shutting down, and deleting virtual machines.

- Importing virtual machines

- Cloning virtual machines

- Deploying virtual machines

- Migrating virtual machines

- Creating and configuring server pools

- Managing servers

- Managing resources, including ISO files, virtual machine templates, virtual machine images, and shared virtual disks

- Managing Oracle VM Manager users, and groups

2 Getting Started with Oracle VM Manager

This Chapter describes how to start using Oracle VM Manager. It includes the following sections:

- Registering an Account with Oracle VM Manager

- Logging In to Oracle VM Manager

- Using the Wizard to Create a Server Pool

After you install Oracle VM Manager, go to one of the following Web sites to log into Oracle VM Manager:

- For local access: http[s]://127.0.0.1:port/OVS

- For remote access: http[s]://hostname:port/OVS

Where, hostname refers to the host name or IP address of the Oracle VM Manager host. For example, to connect to Oracle VM Manager using the standard port of 8888 on a host named example.com, use:

http://example.com:8888/OVS

To connect to Oracle VM Manager using the Secure Sockets Layer (SSL) port of 4443 on a host named example.com, use:

https://example.com:4443/OVS

2.1 Registering an Account with Oracle VM Manager

You can obtain an account using one of the following ways:

- If you have configured the default administration account admin when you installed Oracle VM Manager, you can use this account to log in to Oracle VM Manager directly. By default, this account is granted the Administrator role.

- Contact the administrator of Oracle VM Manager to create an account with any role you need, including Administrator, Manager, and User.

- If you only want to use the basic functions as a common user, such as creating and using virtual machines, or importing resources, you can register a new account by yourself. After registering the account, you need to ask the administrator to assign some server pools and groups to your account. By default, the account you register is granted the User role.

For more information about the roles, see Section 1.5, "Roles in Oracle VM Manager".

To register a new account with Oracle VM Manager:

1. On the Oracle VM Manager Login page, click Register.

2. The User Information screen is displayed. Enter the account information:

- Username: A descriptive user name for the login.

- Password: The password for the account.

- Retype Password: Re-enter the password.

- First Name: The first name.

- Last Name: The last name.

- Email: e-mail address.

Click Next.

3. Confirm the account details.

An account is created, and a confirmation message is displayed on the Oracle VM Manager Login screen.

Before using any features, you need to ask the administrator to assign some server pools and groups to your account. For more information on editing users, see Section 7.2.3, "Editing a User".

Now you can use the new account to log in to Oracle VM Manager.

2.2 Logging In to Oracle VM Manager

To open the Login page of Oracle VM Manager, enter either of the following addresses in a Web browser:

- For local access: http[s]://127.0.0.1:port/OVS

- For remote access: http[s]://hostname:port/OVS

Where, hostname refers to the host name or IP address of the Oracle VM Manager host. For example, to connect to Oracle VM Manager using the standard port of 8888 on a host named example.com, use:

http://example.com:8888/OVS

To connect to Oracle VM Manager using the Secure Sockets Layer (SSL) port of 4443 on a host named example.com, use:

https://example.com:4443/OVS

On the Oracle VM Manager Login page, enter your user name and password to log in. Now you can create virtual machines, import resources, and so on.

After logging in, the available tabs vary, depending on the role of your account, as shown in Table 2-1, "Available Tabs for Each Role". If you want to change the role of your account, contact the administrator. Only administrators can change the roles of accounts.

Table 2-1 Available Tabs for Each Role

Role

Available Tabs

User

- Virtual Machines

- Resources

Manager

- Virtual Machines

- Resources

- Servers

- Server Pools

Administrator

- Virtual Machines

- Resources

- Servers

- Server Pools

- Administration

To change your account information, such as e-mail address and password, click Profile on the upper-right part of any page.

If you forget your password, click Forgot Password on the Login page and submit your account name. A new password will be sent to your registered e-mail address.

Figure 2-1 Profile Link

2.3 Using the Wizard to Create a Server Pool

After installation, you can log in to Oracle VM Manager, and follow the Wizard to create a server pool containing a physical server which will act as the Server Pool Master, the Virtual Machine Server, and the Utility Server.

To create a server pool by following the Wizard:

1. On the Welcome page, click Next.

Figure 2-2 Welcome Page

2. On the Server Information page, enter the server pool information:

- Server Pool Name: The name of the server pool.

- Server Pool Virtual IP: The virtual IP address of the server pool. This IP address is used as the IP address for the Server Pool Master and will persist over any reassignments of the Server Pool Master due to HA fail over.

- High Availability Mode: Select whether to enable HA with the check box. To use HA, you must enable HA in the server pool, and on each virtual machine. For information about HA, see Section 3.5, "Enabling High Availability (HA)". For more information on how to set up HA prerequisites, see the Oracle VM Server User's Guide.

Enter the following information about the Oracle VM Server in the Server Details box:

- Server Host/IP: The host name, or IP address of the Oracle VM Server, for example:
192.168.2.20

or

hostname.example.com

- Server Name: A name for the Oracle VM Server. This must be unique.

- Server Agent Password: The password to access Oracle VM Agent installed on the Oracle VM Server.

- Server Username: The username to log in to the Oracle VM Server.

- Server Password: The password to log in to the Oracle VM Server.

- Location: The location of the Oracle VM Server. For example, Server Room 1.

- Description: A description of the Oracle VM Server.

To test the connection to the Oracle VM Server click Test Connection. If the information is incorrect, or the Oracle VM Server is not available, you cannot add it to the server pool.

Figure 2-3 Adding Servers to a Server Pool

Click Create to create the server pool.

Now you have created a server pool, you can continue to add more Virtual Machine Servers and Utility Servers, or add more users to the server pool. For more information on creating server pools and adding servers, see Section 3.2, "Creating a Server Pool" and Section 4.1, "Adding a Server".

Once the server pool is created, you can start importing resources, or creating virtual machines. See Chapter 5, "Managing Resources" and Chapter 6, "Managing Virtual Machines".

3 Managing Server Pools

A server pool is logically an autonomous region that contains one or more physical servers. It presents a unified view of the storage in which the virtual machines reside.

Before creating a server pool, make sure you have:

- Oracle VM Servers to deploy as the Server Pool Master, the Utility Server, or the Virtual Machine Server.

- A repository that is used for live migration of virtual machines and for local storage on the Oracle VM Servers. For information on managing repositories, see the Oracle VM Server User's Guide.

- IP addresses or host names for the Oracle VM Servers.

- Passwords to access Oracle VM Agent installed on these Oracle VM Servers.

This Chapter describes how to manage server pools and includes the following sections:

- Designing a Server Pool

- Creating a Server Pool

- Searching For a Server Pool

- Editing a Server Pool

- Enabling High Availability (HA)

- Deleting a Server Pool

- Restoring a Server Pool

- Viewing Server Pool Logs

Note:

Functions described in this Chapter are only available to users who are granted the Manager or Administrator role.

3.1 Designing a Server Pool

This section guides you through the ways of designing a server pool to meet your requirements.

Before creating a server pool, you need to consider how many physical Oracle VM Servers are to be included in the server pool, and what function(s) each physical Oracle VM Server is to perform. The more guest virtual machines you run in the server pool, the more resources these guest virtual machines will consume, and so the more physical Oracle VM Servers may be required to provide sufficient resources for the server pool.

A server pool is scalable. If you find a server pool does not have sufficient resources, such as CPU or memory, to run the virtual machines, you can expand the server pool by adding more Virtual Machine Servers.

There are three typical server pool configurations:

- Separate Configuration

- All-in-One Configuration

- Two-in-One Configuration

Separate Configuration

In a separate configuration, one single Oracle VM Server functions as a Server Pool Master, one or more Oracle VM Servers function as Utility Server, and one or more Oracle VM Servers function as Virtual Machine Servers.

This configuration is recommended when there area large number of virtual machines running on the Oracle VM Servers, or when applications on the virtual machines consume most of the hardware resources. This configuration makes sure that the performance of the hosted virtual machines is not impacted by any significant management activity handled by the Server Pool Master or Utility Servers.

Figure 3-1 Separate Configuration

All-in-One Configuration

In the all-in-one configuration, a single Oracle VM Server acts as the Server Pool Master, the Utility Server, and the Virtual Machine Server at the same time.

This configuration is recommended when there are only a few virtual machines running. In this case, the hardware resources of the Oracle VM Server are sufficient to support the virtual machines and the management activity handled by the Server Pool Master and Utility Server.

Figure 3-2 All-in-One Configuration

Two-in-One Configuration

In the two-in-one configuration, the Server Pool Master function, and the Utility Server function are grouped together on the same Oracle VM Server, while the Virtual Machine Server function is implemented separately on different Oracle VM Servers.

This configuration serves well for a scenario where the server pool resource consumption is moderate. Since Virtual Machine Servers potentially require a great deal more hardware resources than Server Pool Masters and Utility Servers, you can typically deploy both the Server Pool Master and Utility Server on the same Oracle VM Server.

Figure 3-3 Two-in-One Configuration

3.2 Creating a Server Pool

A server pool consists of at least one Server Pool Master, one Utility Server, and one Virtual Machine Server. See Section 3.1, "Designing a Server Pool". You can add multiple Oracle VM Servers to a server pool.

To create a server pool:

1. On the Server Pools page, click Create Pool. The Create Server Pool page is displayed.

Figure 3-4 Adding Servers to a Server Pool

2. Enter the Oracle VM Server information and add the Oracle VM Server to the server pool.

Note:

If you have registered a physical server to Oracle VM Manager, you cannot register it again, as this may result in duplicate host names or IP addresses.

- Server Pool Name: The name of the server pool.
A server pool name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum length of a server pool name is 200 characters.

- Server Pool Virtual IP: The virtual IP address of the server pool. This IP address is used as the IP address for the Server Pool Master and will persist over any reassignments of the Server Pool Master due to HA fail over.

- High Availability Mode: Select whether to enable HA with the check box. To use HA, you must enable HA in the server pool, and on each virtual machine. For information about HA, see Section 3.5, "Enabling High Availability (HA)". For more information on how to set up HA prerequisites, see the Oracle VM Server User's Guide.

Enter the following information on the Oracle VM Server in the Server Details box:

- Server Host/IP: The host name, or IP address of the Oracle VM Server, for example:
192.168.2.20

or

hostname.example.com

- Server Name: A name for the Oracle VM Server. This must be unique.
An Oracle VM Server name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.

- Server Agent Password: The password to access Oracle VM Agent installed on the Oracle VM Server.

Note:

If you want to use the Server Pool Master fail over feature, all the Oracle VM Agent passwords for the Oracle VM Servers in the server pool must be identical.

- Server Type: Select the checkbox for each role the Oracle VM Server should perform in the server pool:

- Server Pool Master

- Utility Server

- Virtual Machine Server

If you select Utility Server, you must enter the Oracle VM Server login credentials in the Utility Server Username and Utility Server Password fields. The user must have read/write privileges for the /OVS folder.

- Location: The location of the Oracle VM Server. For example, Server Room 1.

- Description: A description of the Oracle VM Server.

To test the connection to the Oracle VM Server click Test Connection. If the information is incorrect, or the Oracle VM Server is not available, you cannot add it to the server pool.

When you have entered the information about the Oracle VM Server, click Add. The Oracle VM Server is added to the server pool and listed in the table at the bottom of the screen. You can select it, and then edit it or delete it with the Edit and Delete buttons.

To add more Oracle VM Servers to the server pool, enter the parameters for each Oracle VM Server, and click Add.

After adding the Oracle VM Server(s), click Next.

3. On the User Information page, select the users from the Non-Administration User Information table for which you want to grant access to the server pool. Users with the Administrator role are automatically granted access to the server pool.

Figure 3-5 Adding Users to a Server Pool

To add new users, see Section 7.2.1, "Creating a User". To change a user role, see Section 7.2.4, "Changing a Role".

After adding users, click Next to proceed to the next page.

4. On the Confirmation page, confirm the information you have entered for the server pool. Click Confirm to create the server pool.

The Server Pools page is displayed and the new server pool is listed in the Server Pools table.

3.3 Searching For a Server Pool

To search for a server pool:

1. Click the Show Search link.

2. Enter the server pool name in the Server Pool Name field. Use % as a wildcard. All available server pools are displayed if you leave the Server Pool Name field empty.

3. Select the server pool status in the Status drop down. The server pool status reflects the status of the Server Pool Master.

- Active: The server pool is available.

- Inactive: The server pool is not available.

- Creating: The server pool is being created.

- Configuration Error: There are various versions of Oracle VM Server in the server pool. This may occur after an upgrade of Oracle VM Manager if the versions of the Oracle VM Servers in the server pool are mixed, or lower than that of Oracle VM Manager.

- Error: The cluster set up failed when creating the server pool.
Check the server pool log to view error logs. To view the server pool log, see Section 7.4, "Viewing Logs".

Delete the server pool, fix the problem described in the error log, and create the server pool.

4. Click Search. The search results are displayed in the Server Pools table.

3.4 Editing a Server Pool

You can change the server pool name, check HA infrastructure and enable or disable HA. You can also edit the servers in a server pool, view the logs, and add or remove users.

Figure 3-6 Editing Server Pool Page Links

3.4.1 Editing Server Pool

To edit a server pool:

1. Select the server pool in the Server Pools table and click Edit. The Edit Server Pool page is displayed.

Figure 3-7 Editing a Server Pool

2. Edit the server pool options:

- Server Pool Name: The name of the server pool.
A server pool name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum length of a server pool name is 200 characters.

- High Availability Infrastructure: Click Check to check the HA configuration is correct for the server pool.

- Enable High Availability: Set whether to enable HA.

- Server Pool Virtual IP: The IP address to dynamically assign to the Server Pool Master in for the server pool.

Click OK or Apply to save your changes.

3.4.2 Editing Server Pool Servers

To edit the servers in a server pool, click the Servers link in the Server Pools table. For more information, refer to Chapter 4, "Managing Servers".

3.4.3 Editing Server Pool Users

To add or remove users from the server pool:

1. Click the Users link in the Server Pools table. The Edit User Information for the Server Pool screen is displayed.

2. Select the users from the Non-Administration User Information table for which you want to grant access to the server pool. Users with the Administrator role are automatically granted access to the server pool. Click Apply.

To add new users, see Section 7.2.1, "Creating a User". To change a user role, see Section 7.2.4, "Changing a Role".

3.5 Enabling High Availability (HA)

You can set up HA in Oracle VM to guarantee the availability of virtual machines if the Virtual Machine Server they are running on fails or restarts. When a Virtual Machine Server is restarted or shut down, the virtual machines running on it are either restarted on, or migrated to, another Virtual Machine Server.

You manage HA with Oracle VM Manager. To implement HA, you must create a cluster of Virtual Machine Servers in a server pool and have them managed by Oracle VM Manager. HA cannot be implemented with Oracle VM Server alone.

To use HA, you must first enable HA on the server pool, then on all virtual machines, as shown in Figure 3-8, "Enabling HA". If you enable HA in the server pool and then for virtual machines, when a Virtual Machine Server is shut down or fails, the virtual machines are migrated or restarted on another available Virtual Machine Server. HA must be enabled for both the server pool and for virtual machines. If HA is not enabled for both, HA is disabled.

Figure 3-8 Enabling HA

If HA is enabled, when you restart, shut down, or delete the Virtual Machine Server in Oracle VM Manager, you are prompted to migrate the running virtual machines to another available Virtual Machine Server. If you do not migrate the running virtual machines, Oracle VM Agent attempts to find an available Virtual Machine Server on which to restart the virtual machines. The Virtual Machine Server is selected using the preferred server setting for the server pool when you create a virtual machine in Oracle VM Manager:

- Auto selects an available Virtual Machine Server.

- Manual selects an available preferred Virtual Machine Server.

If you do not select a preferred server when creating a virtual machine in Oracle VM Manager, Auto is set as the default.

If there is no preferred Virtual Machine Server or Virtual Machine Server available, the virtual machines shut down (Power Off) and are restarted when a Virtual Machine Server becomes available.

If the Server Pool Master fails, another Oracle VM Server is selected from the server pool to act as the Server Pool Master. The Oracle VM Server chosen to take over the Server Pool Master role is the first Oracle VM Server available to take the lock. To use the Server Pool Master fail over feature, you should make sure the Oracle VM Agent password is identical on all Oracle VM Servers in the server pool.

You can also dynamically change the Oracle VM Server which acts as the Server Pool Master without causing any outages. See Section 3.4.1, "Editing Server Pool".

If the Server Pool Master also performs the Utility Server role, and it fails, the Utility Server role is not moved to another Oracle VM Server. If you want fail over for the Utility Server role, make sure you set up more than one Utility Server in the server pool.

The possible HA scenarios are:

- If you shut down or restart a Virtual Machine Server in Oracle VM Manager, you are prompted which virtual machines to migrate to another available Virtual Machine Server. Any virtual machines which are not migrated, are restarted on an available Virtual Machine Server.

- If you shut down or restart a Virtual Machine Server at the Oracle VM Server command-line, Oracle VM Agent restarts the virtual machines on an available Virtual Machine Server.

- If a Virtual Machine Server fails, all running virtual machines are restarted automatically on another available Virtual Machine Server.

- If a Virtual Machine Server fails and no other Virtual Machine Servers are available, all running virtual machines are restarted when a Virtual Machine Server becomes available.

In all the above scenarios, if any virtual machines running on the Virtual Machine Server are not HA-enabled, they are shut down (Powered Off).

Figure 3-9 shows a Virtual Machine Server failing and the virtual machines restarting on other Virtual Machine Servers in the server pool.

Figure 3-9 HA in Effect for a Virtual Machine Server Failure

Figure 3-10 shows a Virtual Machine Server restarting or shutting down and the virtual machines migrating to other Virtual Machine Servers in the server pool.

Figure 3-10 HA in Effect for a Virtual Machine Server Restart or Shut Down

3.6 Deleting a Server Pool

To delete a server pool:

1. On the Server Pools page, select the server pool you want to delete, and click Delete.

2. On the Delete Confirmation page, select Remove all the working directories from the server pool if you want to delete all the related directories. If you do not select this option, only the server pool data is removed from the database, while the relevant directories and files of the server pool remain on the server. Select Force Remove to force the removal of the servers if one or more servers are unavailable.

Caution:

After you delete all the directories, all the servers and virtual machines on the server pool are then deleted as well. Ensure that the server pool is no longer in use before deleting it.

3.7 Restoring a Server Pool

If the server pool data on the server pool master is damaged, you can restore this data by synchronizing it with the data from the Oracle VM Manager database.

Note:

When you restore a server pool, all the data stored in the server pool master will be deleted, and will be synchronized with the latest information from the Oracle VM Manager database.

To restore a server pool, select it, and click Restore.

3.8 Viewing Server Pool Logs

To view the log information for a server pool, go to the Server Pools page, and click the View Logs link.

The log information includes:

- The time the message was generated.

- The message.

You can search for logs with a specific age in hours or days using the Logged within fields.

4 Managing Servers

There must be at least one Oracle VM Server in a server pool. You can change the parameters or functions of an Oracle VM Server, restart it, shut it down, or delete it.

A server pool is expandable. When more virtual machines are running in the server pool and consuming more resources, you can add more Virtual Machine Servers to expand the server pool resources, such as the number of CPUs and the size of memory. When there are several Virtual Machine Servers, the Server Pool Master chooses the Virtual Machine Server with the maximum available resources (including memory and CPU) to start and run the virtual machine.

You can also add more Utility Servers to enhance the processing ability of the server pool. When there are several Utility Servers, the Server Pool Master chooses the Utility Server with the maximum available CPU resources to conduct the task. However, you cannot add more Server Pool Masters, as a server pool can have only one Server Pool Master.

Before you add Oracle VM Servers to a server pool, you must:

- Identify the IP address, or host name of the computer that functions as the Utility Server or Virtual Machine Server.

- Identify the password to access Oracle VM Agent installed on the computer.

This Chapter describes how to manage Oracle VM Servers. It includes the following sections:

- Adding a Server

- Searching For a Server

- Viewing a Server

- Editing a Server

- Shutting Down a Server

- Restarting a Server

- Putting a Server Into Maintenance Mode

- Deleting a Server

- Viewing Server Logs

4.1 Adding a Server

To add a Utility Server, or a Virtual Machine Server to an existing server pool:

1. On the Servers page, click Add Server. The Add Server page is displayed.

Figure 4-1 Add Server Page

2. Enter the Oracle VM Server parameters. For information about these parameters, refer to Section 3.2, "Creating a Server Pool". In addition to the parameters in Section 3.2, "Creating a Server Pool", you must select a server pool for the Oracle VM Server. Select the search icon in the Server Pool Name field to search for a server pool.
After adding the server, click OK.

Note:

If you have already registered a physical Oracle VM Server in Oracle VM Manager, you cannot register it again, as this may result in host name or IP address duplication.

4.2 Searching For a Server

To search for an Oracle VM Server:

1. Click the Show Search link.

2. Enter the server pool name in the Server Pool Name field. Use % as a wildcard. All available server pools are included in the search if you leave the Server Pool Name field empty.

3. Enter the Oracle VM Server name in the Server Name field. Use % as a wildcard. All available Oracle VM Servers are included in the search if you leave the Server Name field empty.

4. Enter the host name or IP address for the Oracle VM Server in the Server Host/IP field. Use % as a wildcard. All available host names and IP addresses are included in the search if you leave the Server Host/IP field empty.

5. Select the Oracle VM Server status in the Status drop down:

- Active: The Oracle VM Server is available.

- Adding: The Oracle VM Server is being added to the server pool.

- Unreachable: The Oracle VM Server cannot be reached.

- Maintenance: The Oracle VM Server is in maintenance mode.

- Rebooting: The Oracle VM Server is restarting.

- Shutting Down: The Oracle VM Server is shutting down.

- Error: The cluster set up failed when adding the Oracle VM Server to a server pool.
Check the Oracle VM Server log to view error logs. To view the Oracle VM Server log, see Section 7.4, "Viewing Logs".

Delete the Oracle VM Server from the server pool, fix the problem described in the error log, and add the Oracle VM Server to the server pool.

6. Click Search. The search results are displayed in the Servers table.

4.3 Viewing a Server

To view an Oracle VM Server, click the Server Host/IP link in the Servers table. The General Information page is displayed listing information about the Oracle VM Server. The information displayed is:

- Model name

- Model

- CPU Family

- Number of cores

- Memory size

- Host IP address

- Host name

- Server pool name

- Server type

- Status

- Location

- Description

To edit the Oracle VM Server, click Edit.

4.4 Editing a Server

You can edit the general information about an Oracle VM Server, or change the Oracle VM Agent and Utility Server password using the Servers tab.

4.4.1 Edit Server

To edit an Oracle VM Server, select the server in the Servers table and click Edit. The Edit Server page is displayed.

Figure 4-2 Editing a Server

The Edit Server page contains three sub-tabs:

- Edit Server

- Change Oracle VM Agent Password

- Change Utility Server Password

For information about the parameters to edit a server, see Section 3.2, "Creating a Server Pool".

4.4.2 Change Oracle VM Agent Password

To change the password for Oracle VM Agent on an Oracle VM Server:

1. Select the server in the Servers table and click Edit. The Edit Server page is displayed.

2. Select the Change Oracle VM Agent Password tab.

Figure 4-3 Changing the Oracle VM Agent Password

3. Enter the existing Oracle VM Agent password in the Server Agent Password field.
Enter the new password in the New Server Agent Password field.Enter the new password again in the Re-type New Server Agent Password field.

4. Click OK to change the password.

4.4.3 Change Utility Server Password

To change the password for the Utility Server:

1. Select the server in the Servers table and click Edit. The Edit Server page is displayed.

2. Select the Change Utility Server Password tab.

Figure 4-4 Changing the Utility Server Password

3. Enter the existing Utility Server password in the Utility Server Password field.
Enter the new password in the New Utility Server Password field.Enter the new password again in the Re-type New Utility Server Password field.

4. Click OK to change the password.

4.5 Shutting Down a Server

You can remotely shut down the physical server that performs as the Oracle VM Server.

To shut down a server:

1. On the Servers page, select the server, and then click Power Off.

2. If there are running machines on the server, you are prompted to migrate them to another server. Select the virtual machine you want to migrate, and then click Migrate. For information on migrating virtual machines, see Section 6.9, "Migrating a Virtual Machine".
If you shut down the server without migrating the running virtual machines, the running virtual machines will be shut down, or be restarted, depending on whether high availability is enabled. If you have enabled high availability for both the server pool and virtual machines, the virtual machines will restart on other available servers; otherwise, they will be shut down. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

Click Refresh periodically until the server status changes from Shutting Down to Unreachable.

After you shut down the server, virtual machines based on this server cannot be used.

4.6 Restarting a Server

You can remotely restart the physical server with Oracle VM Server installed.

To restart a server:

1. On the Servers page, select the server, and click Reboot.

2. If there are virtual machines running on the server, you are prompted to migrate them to another server. Select the virtual machine you want to migrate, and then click Migrate. For information on migrating virtual machines, see Section 6.9, "Migrating a Virtual Machine".
If you restart the server without migrating the running virtual machines, the running virtual machines will be shut down, or be restarted, depending on whether high availability is enabled. If you have enabled high availability for both the server pool and virtual machines, the virtual machines will restart on other available servers; otherwise, they will be shut down. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

Click Refresh periodically until the server status changes from Rebooting to Active.

During the restarting process, the server may be temporarily unavailable, and all virtual machines involved are shut down.

4.7 Putting a Server Into Maintenance Mode

You can place an Oracle VM Server into maintenance mode and make it unavailable to the server pool. Putting an Oracle VM Server into maintenance mode enables you to perform system maintenance on it without interrupting the other servers in the server pool.

Putting Oracle VM Server into maintenance mode removes it from the available resources in the server pool. An Oracle VM Server in maintenance cannot create or run any virtual machines. You are prompted to migrate or power off any virtual machines before you can place the Oracle VM Server in maintenance mode.

To place a Utility Server into maintenance mode, there must be at least one other Utility Server in the server pool, or you must assign one. You cannot place a Utility Server into maintenance mode if there are no other Utility Servers in the server pool to take over that role. If there are no other Utility Servers in the server pool, you are prompted to assign the role to another Oracle VM Server before you can place it in maintenance mode.

You cannot place an Oracle VM Server into maintenance if it functions as a Server Pool Master, regardless of whether you have an HA-enabled server pool. You must first reassign the Server Pool Master role to another server in the server pool.

To place an Oracle VM Server into maintenance mode:

1. Select the Oracle VM Server in the Servers table on the Servers page and click Set Maintenance. The Maintain Server page is displayed.

2. Select OK to place the Oracle VM Server into maintenance mode.

To end maintenance mode for the Oracle VM Server:

1. Select the Oracle VM Server from the Servers table on the Servers page and click Set Normal.

2. The Oracle VM Server is active.

4.8 Deleting a Server

To delete an Oracle VM Server, select it, and then click Delete.

If there are running machines on the server, you are prompted to migrate them to another server. Select the virtual machine you want to migrate, and then click Migrate. For information on migrating virtual machines, see Section 6.9, "Migrating a Virtual Machine".

You cannot delete a server without migrating any running virtual machines, or shutting them down.

Caution:

When you delete an Oracle VM Server, all virtual machines on the server are no longer available. Ensure that the server is no longer in use before you delete it.

4.9 Viewing Server Logs

To view the log information for an Oracle VM Server, go to the Servers page, and click the View Logs link.

The log information includes:

- The time the message was generated.

- The message.

You can search for logs with a specific age in hours or days using the Logged within fields.

5 Managing Resources

Resources include virtual machine templates, virtual machine images, ISO files, virtual disks, and converted virtual machines.

- Virtual machine templates: Are imported into Oracle VM Manager and used to create virtual machines.

- Virtual machine images: Are imported into Oracle VM Manager and used directly, without the process of creating.

- ISO files: Are imported into Oracle VM Manager and used to create virtual machines from installation media.

- Shared virtual disks: Extend the storage capability of virtual machines.

This Chapter describes how to manage resources and includes the following sections:

- Managing Virtual Machine Templates

- Managing Virtual Machine Images

- Managing ISO Files

- Managing Shared Virtual Disks

Note:

Only an Administrator or Manager can approve, edit, and delete the imported virtual machine templates, virtual machines, and ISO files.

Figure 5-1 Resources Page

5.1 Managing Virtual Machine Templates

Virtual machine templates are shared among users to create new virtual machines. New virtual machines inherit the same contents and configurations from the template.

Typically, a virtual machine template contains basic configuration, such as the number of virtual CPUs, the size of memory, virtual disks, virtual network interfaces (VIFs), and so on. It may also contain some software applications.

You can obtain a virtual machine template by:

- Saving an existing virtual machine as template. For more information, refer to Section 6.8.3, "Saving a Virtual Machine as a Template". You can then use the virtual machine template directly without importing it.

- Downloading Oracle VM templates at:

http://www.oracle.com/technology/products/vm/templates.html

The password for the root user of all Oracle VM templates is ovsroot. The password for the oracle account in the OVM_EL4U5_X86_HVM_ORACLE_11G template is oracle. For more information on how to use these templates, see

http://download.oracle.com/otn_software/virtualization/README.templates

Before using the downloaded templates, you must import them into Oracle VM Manager.

- Creating a virtual machine template using Oracle VM Template Builder. See the Oracle VM Template Builder Installation and User's Guide for information on using Oracle VM Template Builder to build virtual machine templates.

This section includes the following topics:

- Importing a Virtual Machine Template

- Statuses of Virtual Machine Templates

- Searching For a Virtual Machine Template

- Reimporting a Virtual Machine Template

- Approving the Imported Virtual Machine Template

- Editing a Virtual Machine Template

- Deleting a Virtual Machine Template

5.1.1 Importing a Virtual Machine Template

Note:

Before you import a virtual machine template, rename the configuration file of the virtual machine to vm.cfg.

Depending on where your virtual machine templates are located, on the Virtual Machine Server, on other computers, or on the Internet, you can import virtual machine templates from the server pool or download them from external source. You can also convert a Linux or Windows host to a virtual machine template (P2V).

- Selecting from the Server Pool

- Downloading from External Source

- Converting a Linux or Windows Host to a Virtual Machine Template (P2V)

5.1.1.1 Selecting from the Server Pool

If you already have some virtual machine templates on your server pool, you can discover and register them in Oracle VM Manager directly.

Before you import a virtual machine template, make sure the uncompressed (unzipped or untared) component files of the virtual machine template are stored in the /OVS/seed_pool/template_name directory in the server pool's shared storage, and make sure the configuration file is named vm.cfg.

When importing, Oracle VM Agent can update the directory information in the vm.cfg file automatically. If you need to modify the vm.cfg file, refer to Appendix A, "Preparing Virtual Machines For Importing".

To select an existing virtual machine template from the server pool, and register it in Oracle VM Manager:

1. On the Resources page, click Virtual Machine Templates, and then click Import.

2. Select Select from Server Pool (Discover and register). Click Next.

3. On the General Information page, enter or select the following general information:

- Server Pool Name: The server pool on which the imported virtual machine template is to be located.

- Virtual Machine Template Name: The virtual machine template to be imported.

- Operating System: The guest operating system of the virtual machine in the template.

- Virtual Machine System Username: The user name used to log in to the virtual machine operating system.

- Virtual Machine System Password: The password used to log in to the virtual machine operating system.

- Description: A description of the virtual machine template.

Click Next.

4. Confirm the information you have entered.

5. After importing, the status of the virtual machine template is Pending. You need to approve it to make it available for creating virtual machines. See Section 5.1.5, "Approving the Imported Virtual Machine Template".

5.1.1.2 Downloading from External Source

To download a virtual machine template from outside of the server pool, such as OTN:

http://www.oracle.com/technology/software/products/virtualization/vm_templates.html

Or your own HTTP/FTP server:

1. On the Resources page, click Virtual Machine Templates, and then click Import.

2. Select Download from External Source (HTTP and FTP). Click Next.

3. On the General Information page, enter or select the following general information:

- Server Pool Name: The server pool on which the imported virtual machine template is to be located.

- Virtual Machine Template Name: A name for the imported virtual machine template. This must be unique. The name will be used as the name of the directory under /OVS/seed_pool, where the files associated with this virtual machine template are stored.
A template name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 48 characters.

- Operating System: The guest operating system of the virtual machine in the template.

- Virtual Machine System Username: The user name used to log in to the virtual machine operating system.

- Virtual Machine System Password: The password used to log in to the virtual machine operating system.

- Description: A description of the virtual machine template.

Click Next.

4. On the Import Information page, enter the URL where the virtual machine template is located. For example, enter either of the following:

http://host/vm
ftp://username:password@host/vm

When using a proxy, select Use Proxy, and enter the proxy address.

Click Next.

5. Confirm the information.

6. After importing, the status of the virtual machine template is Pending. You need to approve it to make it available for creating virtual machines. See Section 5.1.5, "Approving the Imported Virtual Machine Template".

5.1.1.3 Converting a Linux or Windows Host to a Virtual Machine Template (P2V)

You can convert a Linux or Windows host to an Oracle VM virtual machine template (Physical to Virtual, P2V). The conversion process is similar to downloading a template from external source.

Before conversion, you need to restart the Linux or Windows computer with the Oracle VM Server CD, and use P2V utility to start the conversion. For more information on how to use the P2V utility, see the Oracle VM Server User's Guide.

During the conversion, you are prompted to enter the number of virtual CPUs and memory size, and this information is configured in the vm.cfg file. The disk size in the virtual machine is determined by the size of the disks you have chosen to be included in the virtual machine. Make sure the Virtual Machine Server has sufficient resources for the conversion (disk space).

The converted virtual machine template is a hardware virtualized machine (HVM).

To convert a Linux or Windows host to a virtual machine template:

1. On the Resources page, click Virtual Machine Templates, and then click Import.

2. Select Linux/Windows P2V Import. Click Next.

3. On the General Information page, enter the following general information:

- Server Pool Name: The server pool on which the converted virtual machine template is to be located.

- Virtual Machine Template Name: A name for the converted virtual machine template. This must be unique. The name will be used as the name of the directory under /OVS/seed_pool, where the files associated with this virtual machine template are stored.
A template name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 48 characters.

- Operating System: The guest operating system of the virtual machine in the template.

- Virtual Machine System Username: The user name used to log in to the virtual machine operating system.

- Virtual Machine System Password: The password used to log in to the virtual machine operating system.

- Description: A description of the virtual machine template.

Click Next.

4. On the Import Information page, enter the host name or IP address of the Linux or Windows host. For example, enter:

hostname.example.com

When using a proxy, select Use Proxy, and enter the proxy address.

Click Next.

5. Confirm the information.

6. After importing, the status of the virtual machine template is Pending. You need to approve it to make it available. See Section 5.1.5, "Approving the Imported Virtual Machine Template".

5.1.2 Statuses of Virtual Machine Templates

The imported virtual machine template can be one of the following statuses.

- Importing: The virtual machine template is being imported. Alternatively, the virtual machine template is being created from a virtual machine. See Section 6.8.3, "Saving a Virtual Machine as a Template".

- Pending: The virtual machine template has been imported successfully, and is waiting for approval by the Manager.

- Active: The virtual machine template has been approved, and is ready to use.

- Inactive: The virtual machine template is imported, but not available.

- Import Error: There were errors when importing the virtual machine template. Reimport the template, or delete it.

- Error: There were errors creating the virtual machine template. Delete the template and try to save the virtual machine as the template again.

5.1.3 Searching For a Virtual Machine Template

To search for a virtual machine template:

1. Click Show Search on the Virtual Machine Templates page.

2. The search criteria include: Virtual Machine Template Name, Server Pool Name, and Status. Use % as a wildcard.

3. Click Search to display the virtual machine templates that match your search criteria.

5.1.4 Reimporting a Virtual Machine Template

If an error occurs during downloading from an external source, check if the URL or proxy URL is correct, and then reimport the virtual machine template.

To reimport a virtual machine template:

1. On the Virtual Machine Templates page, select the virtual machine template you want to reimport, and click Reimport.

2. Enter the URL. When using a proxy, select Use Proxy.

3. Click Reimport.

5.1.5 Approving the Imported Virtual Machine Template

After importing, the status of virtual machine templates is Pending. After the Manager or Administrator approves them, the status changes to Active and the virtual machine now becomes an available template.

To approve an imported virtual machine template, you must have the Manager or Administrator role. On the Virtual Machine Templates page, select the template you want to approve, and then click Approve.

5.1.6 Editing a Virtual Machine Template

To edit a virtual machine template:

1. On the Virtual Machine Templates page, select the template you want to update, and click Edit.

2. Update the template parameters. Click Apply.
For more information about the template parameters, refer to Section 5.1.1, "Importing a Virtual Machine Template".

5.1.7 Deleting a Virtual Machine Template

To delete a virtual machine template:

1. On the Virtual Machine Templates page, select the template you want to delete, and click Delete.

2. When prompted, confirm the delete operation.

5.2 Managing Virtual Machine Images

Oracle VM Manager allows you to import:

- Oracle VM virtual machines

- VMware virtual machines in VMDK (Virtual Machine Disk) format

- Virtual machines in VHD (Virtual Hard Disk) format

When you import non-Oracle VM virtual machines, Oracle VM Manager automatically converts them to Oracle VM virtual machines. This is known as virtual to virtual conversion, or V2V.

A virtual machine configuration file, vm.cfg, is required for each virtual machine that is to be imported. Virtual Iron virtual machines do not have a vm.cfg file, so you must create one before you import the VHD files as virtual machines.

Note:

If the VHD virtual machine does not have a vm.cfg file, one must be manually created. See the Oracle VM Server User's Guide for a sample guest configuration file (vm.cfg) to use when migrating Virtual Iron (VHD) virtual machines.
Also check the Oracle VM home page on the Oracle Technology Network (OTN) web site for a white paper on converting VHD virtual machines, when it becomes available:

http://www.oracle.com/technology/products/vm/index.html

This section includes the following topics:

- Importing a Virtual Machine Image

- Statuses of Virtual Machine Images

- Searching For a Virtual Machine Image

- Reimporting a Virtual Machine Image

- Approving the Imported Virtual Machine Image

- Editing a Virtual Machine Image

- Deleting a Virtual Machine Image

5.2.1 Importing a Virtual Machine Image

Note:

Before you import an Oracle VM virtual machine, make sure the configuration file is named vm.cfg.

Depending on where your virtual machines are located, on the Virtual Machine Server, on other computers, or on the Internet, you can import a virtual machine image from different sources. You can also convert a Linux or Windows host to a virtual machine. This is known as physical to virtual conversion, or P2V. This section discusses the options for adding virtual machines and contains:

- Selecting from the Server Pool

- Downloading from External Source

- Converting a Linux or Windows Host to a Virtual Machine (P2V)

Note:

When importing a VMware virtual machine, make sure you have enough free disk space in the /OVS/tmp directory to convert the VMware virtual machine to an Oracle VM virtual machine. Oracle VM requires at least twice the disk space of the VMware virtual machine.

5.2.1.1 Selecting from the Server Pool

If you already have virtual machine images (either native Oracle VM images, or supported non-Oracle VM images) in your server pool, you can discover and register them in Oracle VM Manager directly, without going through the downloading or copying process.

Before importing, make sure the component files of the virtual machine are stored in the /OVS/running_pool/virtual_machine_name directory on the Virtual Machine Server, and that the configuration file is named vm.cfg.

When importing, Oracle VM Agent updates the directory information in vm.cfg automatically. If you need to modify the vm.cfg file, refer to Appendix A, "Preparing Virtual Machines For Importing".

To discover and select an existing virtual machine image from the server pool, and register it in Oracle VM Manager:

1. On the Resources page, click Virtual Machine Images, and click Import.

2. Select Select from Server Pool (Discover and register). Click Next.

3. On the General Information page, enter the following general information:

- Server Pool Name: The server pool on which the imported virtual machine is to be located.

- Sharing: Whether you want to share this virtual machine.

- private: The virtual machine can only be used by the user who imports it.

- Shared (group_name): The virtual machine can be used by members of this specific group.

- Virtual Machine Image Name: The virtual machine to be imported.
Oracle VM Agent identifies the hypervisor type of the virtual machine directory. If both Oracle VM and non-Oracle VM virtual machines are stored in the same directory, Oracle VM Agent identifies the Oracle VM virtual machine only, and ignores other types of virtual machines. If a non-Oracle VM virtual machine is detected, V2V (virtual machine to virtual machine) conversion is started.

- Enable High Availability: You can enable high availability for the imported virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

- Operating System: The guest operating system of the imported virtual machine.

- Virtual Machine System Username: The user name used to log in to the virtual machine.

- Virtual Machine System Password: The password used to log in to the virtual machine.

- Console Password: The password to use for VNC access to the virtual machine.

- Confirm Console Password: Confirm the password to use for VNC access to the virtual machine.

Click Next.

4. Confirm the information on the Confirm Information page.
Select whether to retain or delete any non-Oracle VM virtual machine files in the server pool with the Delete V2V Source Image Files check box.

Click Confirm.

5. After importing, the status of the virtual machine is Pending. You need to approve it to make it available. See Section 5.2.5, "Approving the Imported Virtual Machine Image".
If the status is Import Error, click the error log link to check the detailed information.

5.2.1.2 Downloading from External Source

To download a virtual machine image from outside of the server pool using FTP or HTTP:

1. On the Resources page, click Virtual Machine Images, and click Import.

2. Select Download from External Source (HTTP and FTP). Click Next.

3. On the General Information page, enter the following general information:

- Server Pool Name: The server pool on which the imported virtual machine is to be located.

- Sharing: Whether you want to share this virtual machine, or keep it private.

- Private: The virtual machine can only be used by the user who imports it.

- Shared (group_name): The virtual machine can be used by members of a specific group.

- Virtual Machine Image Name: A name for the imported virtual machine. This must be unique. The name will be used as the name of the directory under /OVS/running_pool, where the files associated with this virtual machine are stored.
A virtual machine image name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 48 characters.

- Enable High Availability: You can enable high availability for the imported virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

- Operating System: The guest operating system of the imported virtual machine.

- Virtual Machine System Username: The user name used to log in to the virtual machine operating system.

- Virtual Machine System Password: The password used to log in to the virtual machine operating system.

- Console Password: The password to use for VNC access to the virtual machine.

- Confirm Console Password: Confirm the password to use for VNC access to the virtual machine.

Click Next.

4. On the Import Information page, enter the URL of the folder where the virtual machine you want to import is located. For example, enter either of the following:

http://example.com/vm
ftp://username:password@example.com/vm

If you are importing a non-Oracle VM virtual machine, enter the URL of the .vmx or .vhd file. For example, enter:

ftp://username:password@example.com/vm/vm.vmx

Oracle VM Manager copies the necessary files of the virtual machine to the server pool, then converts the virtual machine to an Oracle VM virtual machine, and generates the vm.cfg file.

Note:

Oracle VM Manager does not create a vm.cfg file for Virtual Iron, Citrix XenServer, and Microsoft Hyper-V virtual machines. You must manually create a vm.cfg file.

When using a proxy, select Use Proxy, and enter the proxy address.

Click Next.

5. Confirm the information on the Confirm Information page.
Select whether to retain or delete any non-Oracle VM virtual machine files in the server pool with the Delete V2V Source Image Files check box. Source files to be retained are saved in the /OVS/seed_pool directory/vm_name directory.

Click Confirm.

6. After importing, the status of the virtual machine is Pending. You need to approve it to make it available. See Section 5.2.5, "Approving the Imported Virtual Machine Image".
If the status is Import Error, click the error log link to check the detailed information.

5.2.1.3 Converting a Linux or Windows Host to a Virtual Machine (P2V)

You can convert a Linux or Windows host to an Oracle VM virtual machine template (P2V). The conversion process is similar to downloading a template from an external source.

Before conversion, you need to restart the Linux or Windows computer with the Oracle VM Server CD, and use P2V utility to start the conversion. For more information on how to use the P2V utility, see the Oracle VM Server User's Guide.

During the conversion, you are prompted to enter the number of virtual CPUs and memory size, and this information is configured in the vm.cfg file. The disk size in the virtual machine is determined by the size of the disks you have chosen to be included in the virtual machine. Make sure the Virtual Machine Server has sufficient resources for the conversion (disk space).

The converted virtual machine is a hardware virtualized machine (HVM).

To convert a Linux or Windows host to a virtual machine:

1. On the Resources page, click Virtual Machine Images, and then click Import.

2. Select Linux/Windows P2V Import. Click Next.

3. On the General Information page, enter the following general information:

- Server Pool Name: The server pool on which the imported virtual machine is to be located.

- Sharing: Whether you want to share this virtual machine, or keep it private.

- Private: The virtual machine can only be used by the user who imports it.

- Shared (group_name): The virtual machine can be used by members of a specific group.

- Virtual Machine Image Name: A name for the imported virtual machine. This must be unique. The name will be used as the name of the directory under /OVS/running_pool, where the files associated with this virtual machine are stored.

- Enable High Availability: You can enable high availability for the imported virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

- Operating System: The guest operating system of the imported virtual machine.

- Virtual Machine System Username: The user name used to log in to the virtual machine operating system.

- Virtual Machine System Password: The password used to log in to the virtual machine operating system.

- Console Password: The password for VNC access to the virtual machine.

- Confirm Console Password: Confirm the password for VNC access to the virtual machine.

Click Next.

4. On the Import Information page, enter the host name or IP address of the computer. For example, enter:

hostname.example.com

When using a proxy, select Use Proxy, and enter the proxy address.

Click Next.

5. Confirm the information.

6. After importing, the status of the virtual machine is Pending. You need to approve it to make it available. See Section 5.2.5, "Approving the Imported Virtual Machine Image".
If the status is Import Error, click the error log link to check the detailed information.

5.2.2 Statuses of Virtual Machine Images

The imported virtual machine can be one of the following statuses:

- Importing: The virtual machine is in the process of being imported.

- Pending: The virtual machine has been imported successfully, and is waiting for approval by the Manager.

- Import Error: There were errors during the importing process. Click the link to check the error log. You may need to reimport the virtual machine, or delete it.

5.2.3 Searching For a Virtual Machine Image

To search for a virtual machine image:

1. Click Show Search on the Virtual Machine Images page.

2. The search criteria include: Virtual Machine Image Name, Server Pool Name, and Status. Use % as a wildcard.

3. Click Search to display the virtual machine images that match your search criteria.

5.2.4 Reimporting a Virtual Machine Image

If an error occurs during downloading from an external source, check if the URL or proxy URL is correct, and then reimport the virtual machine.

To reimport a virtual machine:

1. On the Virtual Machine Images page, select the virtual machine you want to reimport, and click Reimport.

2. Enter the URL. When using a proxy, select Use Proxy.

3. Click Reimport.

5.2.5 Approving the Imported Virtual Machine Image

The process of approving and managing virtual machine images is similar to that of virtual machine templates. For more information, refer to Section 5.1.5, "Approving the Imported Virtual Machine Template".

After approving, click the Virtual Machines tab, and you can find the virtual machine is displayed in the Virtual Machines list.

You can change the preferred server and other configurations of the imported virtual machine. See Section 6.7, "Editing a Virtual Machine".

5.2.6 Editing a Virtual Machine Image

To edit a virtual machine image:

1. On the Virtual Machine Images page, select the virtual machine you want to update, and click Edit.

2. Update the virtual machine parameters. Click Apply.
For more information about the virtual machine parameters, refer to Section 5.2.1, "Importing a Virtual Machine Image".

5.2.7 Deleting a Virtual Machine Image

To delete a virtual machine image:

1. On the Virtual Machine Images page, select the virtual machine you want to delete, and click Delete.

2. If prompted, confirm the delete operation.

5.3 Managing ISO Files

You can import ISO files to provide installation media for creating virtual machines. This section includes the following topics:

- Importing an ISO File

- Statuses of ISO Files

- Searching For an ISO File

- Reimporting an ISO File

- Approving the Imported ISO File

- Changing Status of an ISO File

- Deleting an ISO File

5.3.1 Importing an ISO File

Common rules about ISO files management:

- Any user can import an ISO file.

- The Administrator or server pool Manager approves the imported ISO files.

- All ISO files of one image should belong to the same ISO group.

- All users in the same server pool can share ISO files on the server pool.

Depending on where your ISO files are located, on the Virtual Machine Server, on other computers, or on the Internet, you can import ISO files from different resources as follows:

- Selecting from the Server Pool

- Downloading from External Source

5.3.1.1 Selecting from the Server Pool

If you already have some ISO files on your server pool, you can discover and register them in Oracle VM Manager directly.

Before importing, make sure the ISO files are in the folder /OVS/iso_pool/iso_group_name on the Virtual Machine Server. You can also download ISO files from other computers, or from the Internet, and then copy them to this folder.

To select an existing ISO file on the server pool, and register it in Oracle VM Manager:

1. On the Resources page, click ISO Files, and then click Import.

2. Select Select from Server Pool (Discover and register). Click Next.

3. On the General Information page, select the following ISO file information:

- Server Pool Name: The server pool on which the ISO file is stored.

- ISO Group: The ISO group. One ISO group may contain multiple ISO files. An ISO group is created on the Oracle VM Server by creating a directory under the /OVS/iso_pool/ directory. ISO files must be placed in ISO groups (subdirectories) to be displayed in this field.

- ISO Label: The ISO file you want to import.

Click Next.

4. Confirm the information.

5. After importing, the status of the ISO file is Pending. You need to approve it to make it available to use. See Section 5.3.5, "Approving the Imported ISO File".

5.3.1.2 Downloading from External Source

To download an ISO file from outside of the server pool, such as your own HTTP or FTP server, or from the Internet:

1. On the Resources page, click ISO Files, and then click Import.

2. Select Download from External Source (HTTP and FTP). Click Next.

3. On the General Information page, enter the following ISO file information:

- Server Pool Name: The server pool on which the ISO file is to be used and stored.

- ISO Group: The name of the ISO group. One ISO group may contain multiple ISO files. The name is used to create the directory under /OVS/iso_pool, where the ISO files of this group are stored.

- ISO Label: The ISO label used to identify the imported ISO file. For example, enter CD1.
An ISO label must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum label length is 100 characters.

- URL: The URL of the ISO file. You can import the ISO file using FTP, or using HTTP. For example, enter an address similar to the following:
http://example.com/el5_img/disc1.iso

ftp://username:password@example.com/el5_img/disc1.iso

When using a proxy, select User Proxy and enter the proxy address. For example, enter a proxy address similar to the following:

http://example.com:8888

Click Next.

4. Confirm the information.

5. After importing, the status of the ISO file is Pending. You need to approve it to make it available for creating virtual machines. See Section 5.3.5, "Approving the Imported ISO File".

5.3.2 Statuses of ISO Files

The imported ISO file can be one of the following statuses:

- Importing: The ISO file is in the process of being imported.

- Pending: The ISO file has been imported successfully, and is waiting for approval by the Manager.

- Import Error: There were errors during the importing process. Reimport the ISO file, or delete it.

- Active: The ISO file has been approved, and is available for creating virtual machines.

- Inactive: The ISO file is imported successfully, but not available.

5.3.3 Searching For an ISO File

To search for an ISO file:

1. Click Show Search on the ISO Files page.

2. The search criteria include: ISO Label, Server Pool Name, and Status. Use % as a wildcard.

3. Click Search to display the ISO files that match your search criteria.

5.3.4 Reimporting an ISO File

If an error occurs during external import, check if the URL or proxy URL is correct, and then reimport the ISO file.

To reimport an ISO file:

1. On the ISO Files page, select the ISO file you want to reimport, and click Reimport.

2. Enter the URL. When using a proxy, select Use Proxy.

3. Click Reimport.

5.3.5 Approving the Imported ISO File

The process of approving, and managing ISO files is similar to that of virtual machine templates. For more information, refer to Section 5.1.5, "Approving the Imported Virtual Machine Template".

5.3.6 Changing Status of an ISO File

To change the status of the ISO files:

1. Select the ISO file and click Edit.

2. Select the status. It can be Active or Inactive. Click Apply.

Only active ISO files are available to users.

Note:

Only an Administrator or server pool Manager of the server pool can approve, and manage the imported ISO files and virtual machines.

5.3.7 Deleting an ISO File

If you do not need an ISO file, or there are errors during the ISO file importing process, you can delete it.

To delete an ISO file, from the ISO page, select the ISO file you want to delete, and click Delete.

5.4 Managing Shared Virtual Disks

You can create shared virtual disks, and use them to expand the storage capacity of your virtual machines. The available virtual disks can also be used by other users in the group.

Oracle VM supports using files as virtual disks. In this case, the prefix of the disk in the configuration file is file. Physical devices can be used, but cannot be changed through Oracle VM Manager. The following is an example of an entry for a file-based disk in the virtual machine configuration file:

disk = [ 'file:/OVS/seed_pool/system.img,hda,w', ]

As well as file-based shared virtual disks, you can share your physical devices (multipath devices, normal Storage Area Network (SAN) LUNS devices, and so on) with all Virtual Machine Servers in the server pool. In this case, the prefix of the disk in the configuration file is phy. Multipath devices can be used, but cannot be changed through Oracle VM Manager. The following is an example of an entry for a multipath disk in the virtual machine configuration file.

disk = [ 'phy:/dev/mpath/mpath1,hdd,w', ]

You must manually configure the multipath device on each Virtual Machine Server in a server pool, then you can add the multipath device to the server pool as a shared virtual disk. The prerequisite steps to use a multipath device as a shared virtual disk are:

- Manually set up the SAN connection to the multipath device on each Virtual Machine Server in the server pool.

- Manually configure the multipath device on each Virtual Machine Server in the server pool.

- Make sure the multipath device has the same device identifier and device path on each Virtual Machine Server in the server pool.
For example, if you want to use a multipath device with the device identifier mpath-36090a028301ffd14fca5a48246976baa a sharable disk for the virtual machines in the server pool, it must have same device path name on each Virtual Machine Server in the server pool, for example, /dev/mpath/mpath1. Do not use the path /dev/mapper/x for multipath devices, only use the path /dev/mpath/x.

- Make sure the multipath device is not used for any other purpose (for example, mounted as an FTP server) to avoid any possible data corruption.

For more information on how to assign shared hard disks to a virtual machine, refer to Section 6.7.3, "Storage".

This section includes the following topics:

- Creating a Shared Virtual Disk

- Statuses of Shared Virtual Disks

- Searching For a Shared Virtual Disk

- Importing a Shared Virtual Disk

- Deleting a Shared Virtual Disk

5.4.1 Creating a Shared Virtual Disk

You cannot create a multipath device to use as a shared virtual disk. You must manually create and mount a multipath device, then import it into Oracle VM Manager.

To create a file-based shared virtual disk:

1. On the Resources page, click Shared Virtual Disk, then click Create.

2. On the Add Shared Virtual Disks page, enter or select the following parameters:

- Virtual Disk Name: The name of the virtual disk.
A disk name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.

- Virtual Disk Size (MB): The size of the virtual disk, in MBs. Allocate at least 1024 MB for the virtual disk.

- Server Pool Name: The server pool in which the shared virtual disk can be used, and shared.

- Group Name: The group that can use this shared virtual disk. You can select one of the following groups:

- My Workspace: The virtual disk will be a private one, and only you can use it.

- group_name: Select a specific group with whom you want to share this virtual disk. If the virtual disk is available after creation, any member of this group can use it.

3. Confirm the information you have entered.

5.4.2 Statuses of Shared Virtual Disks

A shared virtual disk can be one of the following statuses:

- Importing: The shared virtual disk is in the process of being imported.

- Pending: The shared virtual disk has been imported successfully, and is waiting for approval by the Manager.

- Import Error: There were errors during the importing process. Reimport the shared virtual disk, or delete it.

- Active: The shared virtual disk has been approved and is available.

- Inactive: The shared virtual disk is imported successfully, but not available.

5.4.3 Searching For a Shared Virtual Disk

To search for shared virtual disk:

1. Click Show Search on the Shared Virtual Disks page.

2. The search criteria include: Virtual Disk Name, Server Pool Name, Group Name and Status. Use % as a wildcard.

3. Click Search to display the shared virtual disks that match your search criteria.

5.4.4 Importing a Shared Virtual Disk

You can import a shared virtual disk into a server pool.

To import a shared virtual disk:

1. Click Import.

2. Enter or select the following:

- Server Pool Name: The server pool in which the shared virtual disk can be used, and shared.

- Group Name: The group that can use the shared virtual disk. You can select one of the following groups:

- My Workspace: The virtual disk will be a private one, and only you can use it.

- group_name: Select a specific group with whom you want to share this virtual disk. If the virtual disk is available after creation, any member of this group can use it.

- Shared Virtual Disk Type: The type of shared virtual disk. The disk types you can select are:

- File-based Disks: All available file-based disks in the server pool group are discovered.

- Multipath-based Disks: All available multipath-based disks in the server pool group are discovered.

- Shared Virtual Disk Files: This field is displayed if you select File-based Disks above. A list of all the discoverable shared virtual disks in the group on the server pool.

- Multipath Devices: This field is displayed if you select Multipath-based Disks above. A list of all the discoverable shared virtual disks devices in the group on the server pool.

- UUID: This field is displayed if you select Multipath-based Disks above. Displays the UUID of the multipath device.

- Size (MB): This field is displayed if you select Multipath-based Disks above. Displays the size in MBs of the multipath device.

- Description: A description of the shared virtual disk.

Click Next.

3. Confirm the information you have entered and click Confirm.

The shared virtual disk is imported and available to the server pool.

5.4.5 Deleting a Shared Virtual Disk

Note:

Make sure no application is using the virtual disk before you delete it.

To delete a shared virtual disk:

1. Select the shared virtual disk, and click Delete.

2. Confirm the delete operation.

After you delete the virtual disk, all the files on it will be deleted as well.

6 Managing Virtual Machines

A virtual machine contains a guest operating system and some preinstalled applications. It runs on a Virtual Machine Server.

Before you create a new virtual machine, ensure that the following resources are available:

- A server pool

- A Virtual Machine Server to run the virtual machine

- Imported ISO files for creating virtual machines from installation media, or imported virtual machine templates for creating virtual machines based on templates

This Chapter describes how to create and use virtual machines. It includes the following sections:

- Overview of Virtual Machines

- Supported Guest Operating Systems

- Creating a Virtual Machine

- Starting and Shutting Down a Virtual Machine

- Connecting to a Virtual Machine's Console

- Viewing Virtual Machine Details

- Editing a Virtual Machine

- Reproducing Virtual Machines

- Migrating a Virtual Machine

- Deleting a Virtual Machine

Note:

As a user with the User role, you can only manage your virtual machines, and cannot manage virtual machines created by other users. Only the Manager or the Administrator can manage all the virtual machines in the server pool.

6.1 Overview of Virtual Machines

Virtual machines in Oracle VM Manager have various types and statuses during the life cycle. This section introduces virtual machine types and statuses and contains:

- Virtual Machine Types

- Virtual Machine Statuses

- Life Cycle Management of a Virtual Machine

- Viewing Virtual Machine Logs

6.1.1 Virtual Machine Types

This section describes the following types of virtual machines in Oracle VM Manager:

- Private Virtual Machine: By default, a virtual machine belongs to the user who created it. Only the user who created the virtual machine can view and manage the virtual machine. The My Workspace group contains all the private virtual machines which the user has created.

- Shared Virtual Machine: You can share virtual machines with members of specific groups. For example, when you deploy a virtual machine, you can grant access rights to members of another group. Such a virtual machine is then known as a shared virtual machine.

- Public Virtual Machine: Virtual machines that are shared among all users are known as public virtual machines. Everyone can view and deploy public virtual machines.

Note:

Users with the User role and Manager role may be restricted from accessing some specific virtual machines.

6.1.2 Virtual Machine Statuses

The status of a virtual machine reflects the operation process which the virtual machine is undergoing.

The status of a virtual machine can be one of the following:

- Creating

- Initializing and Running

- Pausing, Paused and Unpausing

- Suspending, Suspended and Resuming

- Shutting Down and Powered Off

- Saving

- Cloning

- Migrating

- Error

6.1.2.1 Creating

When the creation of a virtual machine is triggered, its status is set to Creating. This status indicates that the virtual machine is being created, and cannot be used.

6.1.2.2 Initializing and Running

When you start a virtual machine, the status changes from Powered Off to Initializing. Periodically refresh the virtual machine until the status changes from Initializing to Running. Now, you can log on to the running virtual machine, or perform live migration.

6.1.2.3 Pausing, Paused and Unpausing

After you pause a running virtual machine to stop it temporarily, its status changes from Running to Pausing. Periodically refresh the virtual machine until the status changes from Pausing to Paused.

When you unpause the virtual machine, the status changes from Paused to Unpausing. Periodically refresh the virtual machine until the status changes from Unpausing to Running.

6.1.2.4 Suspending, Suspended and Resuming

After you suspend a running virtual machine, its status changes from Running to Suspending. Periodically refresh the virtual machine until the status changes from Suspending to Suspended.

When you resume the suspended virtual machine, the status changes from Suspended to Resuming. Periodically refresh the virtual machine until the status changes from Resuming to Running.

6.1.2.5 Shutting Down and Powered Off

After you shut down a virtual machine, its status changes from Running to Shutting Down. Periodically refresh the virtual machine until the status changes from Shutting Down to Powered Off.

A virtual machine with the Powered Off status is available for deploying, cloning, or starting.

6.1.2.6 Saving

When you save a virtual machine as a template, the status of the original virtual machine is set to Saving. Periodically refresh the virtual machine until the status changes from Saving to Powered Off.

6.1.2.7 Cloning

During the cloning process, the status of the original virtual machine, based on which you clone the virtual machines, is set to the Cloning status. Periodically refresh the virtual machine until the status changes from Cloning to Powered Off.

6.1.2.8 Migrating

When you perform live migration, the status of the virtual machines changes from Running to Migrating. Periodically refresh the virtual machine until the status changes from Migrating to Running.

6.1.2.9 Error

The Error status indicates that there are some errors with the virtual machine, and it cannot be used. To solve the problem:

1. On the Virtual Machines page, click the Show link of the virtual machine and check the error log information for more details. See Appendix D, "The Status of the Virtual Machine Is Error".

2. Shut down the virtual machine, and then retry your operation.

3. If the error persists, delete the virtual machine and create a new one.

Figure 6-1 Virtual Machine Status Mechanism

6.1.3 Life Cycle Management of a Virtual Machine

Typically, the life cycle of a virtual machine consists of the following process:

1. Creating a Virtual Machine

2. Starting a Virtual Machine

3. Connecting to a Virtual Machine's Console (to access the virtual machine itself)

4. Shutting Down a Virtual Machine (to reduce system resource consumption when the virtual machine is not in use)

5. Deleting a Virtual Machine (when you no longer require the virtual machine)

The life cycle of a virtual machine created from template is slightly different from the one created from installation media, as shown in Figure 6-2 and Figure 6-3.

Figure 6-2 Life Cycle of a Virtual Machine Created from Template

Figure 6-3 Life Cycle of a Virtual Machine Created from Installation Media

During the life cycle of the virtual machine, the following actions can be taken:

- Viewing Virtual Machine Logs

- Pausing and Unpausing a Virtual Machine (temporarily halt the virtual machine)

- Suspending and Resuming a Virtual Machine (move data stored in the memory to the hard disk, and suspend the virtual machine)

- Editing a Virtual Machine

- Deploying a Virtual Machine (deploy the virtual machine to another server pool, and share it with other group members)

- Cloning Virtual Machines (create multiple copies of the virtual machine, and share them with other users)

- Saving a Virtual Machine as a Template (create a template of the virtual machine to use to create other identical virtual machines)

- Migrating a Virtual Machine (move the virtual machine to another Virtual Machine Server without shutting down the applications or operating system in the virtual machine)

- Resetting a Virtual Machine

- Deleting a Stuck Virtual Machine

6.1.4 Viewing Virtual Machine Logs

Any standard operational or error messages that may occur when you create or run a virtual machine are logged in Oracle VM Manager. The logs provides you with essential details for troubleshooting.

To view the log information, go to the Virtual Machines page, click the Show link, and click the Log link. The number displayed here reflects the number of log items.

The log information includes:

- The time the message was generated.

- The log level of the message:

- INFO denotes a normal operational message and is informational only.

- WARNING denotes a more serious message that may require your attention to resolve.

- ERROR denotes an error occurred.

- The target, or virtual machine name.

- The operation that generated the message.

- The message.

Appendix D, "The Status of the Virtual Machine Is Error" describes the error messages and how to use these to troubleshoot problems.

6.2 Supported Guest Operating Systems

An operating system installed inside a virtual machine is known as a guest operating system. Oracle VM supports a variety of guest operating systems. For information on supported guest operating system, see the Oracle VM Server Release Notes.

6.3 Creating a Virtual Machine

Depending on what resources you have, you can obtain a virtual machine by using one of the following methods:

- If you have created or imported virtual machine templates, you can create a new virtual machine by using a virtual machine template. See Section 6.3.1, "Creating Virtual Machine From a Template".

- If you have imported ISO files, you can create a new virtual machine and install the operating system from the installation media (ISO file). See Section 6.3.2, "Creating a Virtual Machine From Installation Media".

- If you want to start the virtual machine using Preboot Execution Environment (PXE) over a network, you can create a network bootable (PXE boot) virtual machine. See Section 6.3.3, "Creating a Network Bootable (PXE boot) Virtual Machine".

- You can also import a prebuilt virtual machine image directly. See Section 5.2.1, "Importing a Virtual Machine Image".

Before creating a new virtual machine, you must have a server pool that contains a Virtual Machine Server. See Section 3.2, "Creating a Server Pool" for information on creating server pools, and Section 4.1, "Adding a Server" for information on adding more Virtual Machine Servers.

Figure 6-4 shows the basic steps required to create a new virtual machine.

Figure 6-4 Basic Steps to Create a New Virtual Machine

6.3.1 Creating Virtual Machine From a Template

Typically, a virtual machine template can contain:

- An operating system

- The basic configuration, such as the number of virtual CPUs, the amount of memory, the size of disk, and so on

- Preinstalled applications

You can create a virtual machine template by:

- Saving a virtual machine as a template, see Section 6.8.3, "Saving a Virtual Machine as a Template".

- Importing a template, see Section 5.1, "Managing Virtual Machine Templates".

- Using Oracle VM Template Builder, see the Oracle VM Template Builder Installation and User's Guide.

You can create a virtual machine by cloning a template. The virtual machine inherits all the content and configuration from the template.

To create a virtual machine based on a template:

1. Click Create Virtual Machine on the Virtual Machines page.

2. Select Create virtual machine based on virtual machine template. Click Next.

3. Select the server pool from the Server Pool table in which to create the virtual machine.

Select the preferred server on which to run the virtual machine from the Preferred Server drop down. A preferred server is a Virtual Machine Server that provides resources such as memory, CPUs, virtual network interfaces (VIFs), and disk for the virtual machine. If you select only one Virtual Machine Server as the preferred server, the virtual machine then always starts from and runs on this server. If you select multiple preferred servers, each time the virtual machine starts, it will choose to run on the one with the maximum resources available (including memory and CPU).

When creating a virtual machine, there are two ways to select a Virtual Machine Server for the virtual machine:

- Auto: In the Auto mode, when the virtual machine starts, Oracle VM automatically assigns a Virtual Machine Server with the maximum resources available to run the virtual machine. The virtual machine then runs on this Virtual Machine Server temporarily, until it is shut down.

- Manual: In the Manual mode, you select one or more Virtual Machine Servers as the preferred servers. The virtual machine then starts from and runs on the preferred server with the maximum resources available.

Note:

If none of the preferred servers can provide sufficient resources, the virtual machine may fail to start.

Click Next.

4. Select the template to be used to create the virtual machine. Click the Show link to display more detailed information about the template, such as the memory size, number of virtual CPUs, virtualization mode, and operating system. Click Next.

5. Enter the following information for the virtual machine:

- Virtual Machine Name: Enter a unique name for the virtual machine. The name is used to create the directory under /OVS/running_pool on the Virtual Machine Server, where the files associated with this virtual machine are stored.
A virtual machine name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.

- Console Password: Set the console password used connect to the virtual machine from VNC. The console password requires at least 8 characters, comprising of at least one letter and one number.

- Confirm Console Password: Re-enter the console password.

- High Availability: If you want to enable high availability (HA) for this virtual machine, select this checkbox. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

- To add more virtual network interfaces (NICs), click Add Row in the Network Interface Card table. By default, virtual network interfaces are named VIF0, VIF1, VIF2, and so on. You can rename them after creating the virtual machine. See Section 6.7.2, "Network". Oracle VM automatically assigns a random MAC address to the virtual network interface.
Select a bridge from the Bridge drop down for the virtual network interface. By default, the number of bridges is the same as that of physical adaptors, and the bridges are named after physical adaptors. For example, if the Virtual Machine Server has several physical adaptors, eth0, eth1, eth2, and so on, the bridges are then named xenbr0, xenbr1, xenbr2, and so on.

When creating a virtual machine, you can set a maximum of three virtual network interfaces. After the virtual machine is created, you can set a maximum of eight virtual network interfaces. See Section 6.7.2, "Network".

Click Next.

6. Confirm the virtual machine information on the Confirm Information page and click Confirm.

7. The virtual machine is created. Periodically click Refresh, or set the page refresh rate to 30 seconds until the status of the virtual machine changes from Creating to Powered Off.
If the status is Error, refer to Section 6.1.2.9, "Error" for help troubleshooting the error.

Now you can start and log in to the virtual machine. By default, the virtual machine is private, and only you can access it.

To view detailed information about the virtual machine, click Show in the list of virtual machines in the Virtual Machines table.

Some parameters of the virtual machine, such as the virtual network interface and the boot source, are set by default. You cannot change them during the process of creating the virtual machine. If you want to change them after creating the virtual machine, see Section 6.7, "Editing a Virtual Machine".

6.3.2 Creating a Virtual Machine From Installation Media

If you have ISO files available, you can create a virtual machine from the installation media (ISO file), and manually configure the operating system parameters. To create a virtual machine from installation media:

1. Click Create Virtual Machine on the Virtual Machines page.

2. Select Create from installation media. Click Next.

3. Select the server pool from the Server Pool table in which to create the virtual machine.
Select the preferred server on which to run the virtual machine from the Preferred Server drop down. Select Auto to automatically assign the virtual machine to a Virtual Machine Server, or select Manual to specify one or more preferred servers manually. For more information on preferred servers, see Step 3 in Section 6.3.1, "Creating Virtual Machine From a Template".

Click Next.

4. Select the virtualization method from the Virtualization Method drop down:

- Fully Virtualized: Enables you to select an ISO file from which to create the virtual machine. For more information on supported guest operating systems, see Oracle VM Server User's Guide.
If you require more than one ISO file to create the virtual machine, select the first ISO file. After creating the virtual machine, you need to log in to the virtual machine to install the guest operating system. See Section 6.5.2, "Logging In to a Virtual Machine".

See Also:

For more information on importing ISO files, refer to Section 5.3.1, "Importing an ISO File".

Note:

If you use the Oracle VM Server ISO image to create a virtual machine you cannot start it.

In the fully virtualized method (also known as a hardware virtualized machine or HVM), the unmodified guest operating system runs on the virtual machine. It traps and emulates every I/O and hardware instruction.

To apply the fully virtualized mode, you must have either an Intel processor with Virtualization Technology (VT) extension, or an AMD processor with Secure Virtual Machine (SVM) extension (also called AMD-V) available on the host. A complete list of compatible processors is available at:

http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors

Note:

Make sure the CPU and operating system support HVM, and you have enabled it in the BIOS. For more information, see Appendix D, "Cannot Create a Virtual Machine from Installation Media".
If the CPU does not support HVM, use the paravirtualized method to create the virtual machine.

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

# mkdir mount-point
# mount -o loop,ro cd1.iso mount-point

Where mount-point refers to the directory to which you want to mount the files. If you have multiple ISO files, you can mount each ISO file and copy the contents into a single directory, and then mount that directory.

In the Resource Location field, enter the full path of the mount point. HTTP, FTP, and NFS are supported. For example, enter a path similar to the following:

http://example.com/EL5-x86

In the paravirtualized method, the guest operating system is recompiled before being installed on a virtual machine. Also, the virtual machine does not need to trap privileged instructions. Trapping is a method used to handle unexpected conditions, or conditions that are not allowed, which is time-consuming and can impact operating system performance. Without trapping privileged instructions, the paravirtualized operating system runs at near native speed.

Click Next.

5. Enter the following information for the virtual machine on the Virtual Machine Information page:

- Virtual Machine Name: Enter a unique name for the virtual machine. The name is used to create the directory under /OVS/running_pool on the Virtual Machine Server, where the files associated with this virtual machine are stored.
A virtual machine name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.

- Number of Virtual CPUs: Select the number of virtual CPUs for the virtual machine according to the operating system and application consumptions. You can allocate a maximum of 32 virtual CPUs. The larger number you select, the more CPU resources the virtual machine can use.
If the sum of virtual CPUs on all the running virtual machines exceeds that of physical CPUs, each virtual CPU will get that fraction of CPU time. For example, if the sum of virtual CPUs on all the running virtual machines is 8, and you have 4 physical CPUs on the Virtual Machine Server, then each virtual CPU will get 4/8, namely 50%, of CPU time, given that all the virtual CPUs are fully utilized at the same time.

- Keyboard Layout: Select the keyboard to use to interact with the virtual machine.

- Memory Size (MB): Allocate the amount of memory for the virtual machine. Allocate at least 256 MB of memory. When allocating memory, consider the following:

- Memory consumption of applications that will run on the virtual machine

- Memory consumption of applications that are running and will run on the Virtual Machine Server

- Memory resources to be allocated to other virtual machines

- Virtual Disk Size (MB): Allocate at least 1024 MB of virtual disk. When allocating disk, consider the following:

- Disk consumption of applications that will run on the virtual machine

- Disk consumption of applications that are running and will run on the Virtual Machine Server

- Disk resources to be allocated to other virtual machines

- Console Password: Set the console password used to connect to the virtual machine using VNC.

- Confirm Console Password: Re-enter the console password.

- High Availability: If you want to enable high availability (HA) for this virtual machine, select this checkbox. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

- To add more virtual network interfaces (NICs), click Add Row in the Network Interface Card table. By default, virtual network interfaces are named VIF0, VIF1, VIF2, and so on. You can rename them after creating the virtual machine. See Section 6.7.2, "Network". Oracle VM automatically assigns a random MAC address to the virtual network interface.
Select a bridge for the virtual network interface. By default, the number of bridges is the same as that of physical adaptors, and the bridges are named after physical adaptors. For example, if the Virtual Machine Server has several physical adaptors, eth0, eth1, eth2, and so on, the bridges are then named xenbr0, xenbr1, xenbr2, and so on.

When creating a virtual machine, you can set a maximum of three virtual network interfaces. After the virtual machine is created, you can set a maximum of eight virtual network interfaces. See Section 6.7.2, "Network".

Click Next.

6. Confirm the virtual machine information on the Confirm Information page and click Confirm.

7. The virtual machine is created. Periodically click the Refresh, or set the page refresh rate to 30 seconds until the status of the virtual machine changes from Creating to Running.
If the status is Error, refer to Section 6.1.2.9, "Error" for help troubleshooting the error.

8. Log in to the virtual machine and install the guest operating system. See Section 6.5, "Connecting to a Virtual Machine's Console". By default, the virtual machine is private, and only you can access it.

In the virtual machine list, click Show to view the detailed information of the virtual machine.

Some parameters of the virtual machine, such as the virtual network interface and the boot mode, are set by default. You cannot change them during the process of creating the virtual machine. If you want to change them after creating the virtual machine, see Section 6.7, "Editing a Virtual Machine".

6.3.3 Creating a Network Bootable (PXE boot) Virtual Machine

You can create a network bootable (PXE boot) virtual machine that has the minimum configuration information, then start the virtual machine through Preboot Execution Environment (PXE) over a network later to install the guest operating system.

To create a network bootable (PXE boot) virtual machine:

1. Select Create a network bootable virtual machine (pxeboot). Click Next.

2. Select the server pool from the Server Pool table in which to create the virtual machine.
Select the preferred server on which to run the virtual machine from the Preferred Server drop down. Select Auto to automatically assign the virtual machine to a Virtual Machine Server, or select Manual to specify one or more preferred servers manually. For more information on preferred servers, see Step 3 in Section 6.3.1, "Creating Virtual Machine From a Template".

Click Next.

3. Enter the following information for the virtual machine:

- Virtual Machine Name: Enter a unique name for the virtual machine. The name is used to create the directory under /OVS/running_pool on the Virtual Machine Server, where the files associated with this virtual machine are stored.
A virtual machine name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.

- Number of Virtual CPUs: Select the number of virtual CPUs for the virtual machine according to the operating system and application consumptions. You can allocate a maximum of 32 virtual CPUs. The larger number you select, the more CPU resources the virtual machine can use.
If the sum of virtual CPUs on all the running virtual machines exceeds that of physical CPUs, each virtual CPU will get that fraction of CPU time. For example, if the sum of virtual CPUs on all the running virtual machines is 8, and you have 4 physical CPUs on the Virtual Machine Server, then each virtual CPU will get 4/8, namely 50%, of CPU time, given that all the virtual CPUs are fully utilized at the same time.

- Keyboard Layout: Select the keyboard to use to interact with the virtual machine.

- Memory Size (MB): Allocate the amount of memory for the virtual machine. Allocate at least 256 MB of memory. When allocating memory, consider the following:

- Memory consumption of applications that will run on the virtual machine

- Memory consumption of applications that are running and will run on the Virtual Machine Server

- Memory resources to be allocated to other virtual machines

- Virtual Disk Size (MB): Allocate at least 1024 MB of virtual disk. When allocating disk, consider the following:

- Disk consumption of applications that will run on the virtual machine

- Disk consumption of applications that are running and will run on the Virtual Machine Server

- Disk resources to be allocated to other virtual machines

- Console Password: Set the console password used to connect to the virtual machine using VNC.

- Confirm Console Password: Re-enter the console password.

- High Availability: If you want to enable high availability (HA) for this virtual machine, select this checkbox. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

- To add more virtual network interfaces (NICs), click Add Row in the Network Interface Card table. By default, virtual network interfaces are named VIF0, VIF1, VIF2, and so on. You can rename them after creating the virtual machine. See Section 6.7.2, "Network". Oracle VM automatically assigns a random MAC address to the virtual network interface. You can change the MAC address in the Virtual Network Interface MAC Address column in the Network Interface Card table. The MAC address must begin with 00:16:3E.
Select a bridge for the virtual network interface. By default, the number of bridges is the same as that of physical adaptors, and the bridges are named after physical adaptors. For example, if the Virtual Machine Server has several physical adaptors, eth0, eth1, eth2, and so on, the bridges are then named xenbr0, xenbr1, xenbr2, and so on.

When creating a virtual machine, you can set a maximum of three virtual network interfaces. After the virtual machine is created, you can set a maximum of eight virtual network interfaces. See Section 6.7.2, "Network".

Click Next.

4. Confirm the virtual machine information on the Confirm Information page and click Confirm.

5. The virtual machine is created. Periodically click Refresh, or set the page refresh rate to 30 seconds until the status of the virtual machine changes from Creating to Powered Off.
If the status is Error, refer to Section 6.1.2.9, "Error" for help troubleshooting the error.

Before starting the virtual machine, you need to configure the DHCP and TFTP server first, and then start the virtual machine remotely over the network to install the guest operating system.

By default, the network bootable (PXE boot) virtual machine starts through PXE.

In the virtual machine list, click Show to view the detailed information of the virtual machine.

Some parameters of the virtual machine, such as the virtual network interface and the boot source, are set by default. You cannot change them during the process of creating the virtual machine. If you want to change them after creating the virtual machine, see Section 6.7, "Editing a Virtual Machine".

6.4 Starting and Shutting Down a Virtual Machine

After a virtual machine is created, you can start it or shut it down. When a virtual machine is running, you can pause it or suspend it to stop it temporarily.

- Starting a Virtual Machine

- Shutting Down a Virtual Machine

- Pausing and Unpausing a Virtual Machine

- Suspending and Resuming a Virtual Machine

- Resetting a Virtual Machine

6.4.1 Starting a Virtual Machine

Starting a virtual machine is analogous to starting a computer by pressing the Power On button.

Note:

Make sure that the virtual machine status is Powered Off before you start it.

To start a virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine you want to start.

3. Click the Power On button.

Periodically, click the Refresh button until the virtual machine status changes from Initializing to Running. You can choose to refresh manually, or to refresh every 30 seconds.

6.4.2 Shutting Down a Virtual Machine

When you do not use the virtual machine and log out, shut it down to release system resources.

Note:

Shut down the virtual machine only when the virtual machine status is Running.

To shut down a virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine you want to shut down. The virtual machine status should be Running.

3. Click Power Off.

Note that if you have enabled high availability for this virtual machine, you need to shut it down by clicking Power Off; otherwise, if you shut down the virtual machine through the guest operating system, high availability takes effect, and the virtual machine will restart instead of shutting down.

6.4.3 Pausing and Unpausing a Virtual Machine

Pausing a virtual machine allows you to save the virtual machine at a certain processing point, and resume it again quickly.

When you pause a virtual machine, the state of the virtual machine is saved, and the running operations will not be restarted as long as they have no persistent communication with other computers. All the settings in the virtual machine, and all the devices, such as CPUs, VIFs, amount of memory, and so on, remain the same. But the processes of the virtual machine are no longer scheduled by Oracle VM Server to be run on any CPU. Therefore if the virtual machine is running a server such as a Web server, it will appear to the clients that the virtual machine is shut down.

Note:

Pause the virtual machine only when the virtual machine status is Running.

To pause a running virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine you want to pause.

3. Select Pause, and click Go.

To unpause the virtual machine, select Unpause and click Go. Unpausing a virtual machine is much faster than starting a virtual machine.

After unpausing, the applications resume from where they were paused, and the virtual machine content remains unchanged.

6.4.4 Suspending and Resuming a Virtual Machine

Use the Suspend function to save the status information of a running virtual machine to the disk. You can suspend a virtual machine when you need to back up the current status information, and restore it quickly.

After you suspend the virtual machine, all the status information is saved to the disk, and virtual machine is no longer running, thus the memory allocated to the virtual machine will be released for other virtual machines to use. When the virtual machine is suspended, the network connections will no longer be available.

Note:

Suspend the virtual machine only when the virtual machine status is Running.

To suspend a running virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine you want to suspend.

3. Select Suspend, and click Go.

To resume the virtual machine, select Resume and click Go.

6.4.5 Resetting a Virtual Machine

You can reset a virtual machine that may be having difficulties in starting or stopping, or performing some other action. To reset a virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine you want to reset.

3. Select Reset, and click Go.

The virtual machine is reset and the status is set to the real status of the virtual machine, for example, Powered Off, Running, or Paused.

6.5 Connecting to a Virtual Machine's Console

If it is the first time you attempt to access a virtual machine, you need to install a plug-in to enable the Console button in Oracle VM Manager. After installing the plug-in, you can log in to the virtual machine.

- Installing the Console Plug-In

- Logging In to a Virtual Machine

6.5.1 Installing the Console Plug-In

The plug-ins you need to install vary, depending on which browser and operating system you are using to access Oracle VM Manager.

If you are using a Mozilla Firefox browser on Linux, download the Console Plug-in at: http://oss.oracle.com/oraclevm/manager/RPMS, and install it on the computer where your browser is running.

To install the Console Plug-in:

1. Install the Console Plug-in using the command:

# rpm -ivh ovm-console-version.rpm

Where, version refers to the ovm-console version. It can be 1.0.0-2.x86_64 or 1.0.0-2.i386.

2. If you have no standard installation of Mozilla Firefox, copy files:

# cp /opt/ovm-console/etc/mozpluggerrc /etc/
# cp /opt/ovm-console/bin/* /usr/bin
# cp /opt/ovm-console/lib/mozilla/plugins/ovm-console-mozplugger.so /opt/firefox/plugins

Where, /opt/firefox/plugins refers to the Firefox plug-in folder.

3. Restart Mozilla Firefox.

If you are using Internet Explorer on Windows, you need to download and install the TightVNC-Java applet on the Oracle VM Manager host. For information on installing the TightVNC-Java applet, see Oracle VM Manager Installation Guide.

6.5.2 Logging In to a Virtual Machine

The virtual machine is now running, and the Console Plug-in has been installed, and you can log in to it by using the Console.

To log in to the virtual machine:

1. On the Virtual Machines page, select the running virtual machine, and then click Console.

2. A VNC Authentication is displayed. Enter the console password, and click OK.

Figure 6-5 VNC Authentication

3. Enter the user name and password of the guest operating system to log in to the virtual machine.

After the VNC authentication, you may need to continue with some further tasks before you can use the virtual machine, depending on the method by which you created the virtual machine.

- If you created this virtual machine based on a template, you can directly use the guest operating system and applications installed in advance, without any further configurations.

- If you created this virtual machine using the fully virtualized method, the installation of the guest operating system is triggered after your first login. Follow the installation wizard to install the guest operating system.
If you need more ISO files to complete the installation, select the next ISO file and then click Change CD to continue the installation, as shown in Figure 6-6, "Changing CD". Repeat this step until all the ISO files are installed.

For information on the supported guest operating systems, see Oracle VM Server User's Guide.

For more information on creating virtual machines using the fully virtualized method, refer to Section 6.3.2, "Creating a Virtual Machine From Installation Media".

Figure 6-6 Changing CD

6.6 Viewing Virtual Machine Details

To view more details of the virtual machine:

1. Click the Virtual Machines tab.

2. In the Details column of the Virtual Machines table, click the Show link.

Figure 6-7 View Virtual Machine Details

You can see information such as, memory size, operating system, virtualization method, number of virtual CPUs, VNC port, creation time, power-on time, and a link to the log file.

If the virtual machine is running or shutting down, you can click the link of the VNC port number to open the VNC Authentication window and log in.

You can also click the link of the log number to view error log information. For more information about the error log, see Appendix D, "The Status of the Virtual Machine Is Error".

To view more detailed information or edit the virtual machine, see Section 6.7, "Editing a Virtual Machine".

6.7 Editing a Virtual Machine

When creating a virtual machine, you can configure some of the parameters, such as the number of virtual CPUs, the size of memory, and so on; while the other parameters, such as boot source and the type of virtual network interfaces (VIFs), are assigned default settings by Oracle VM Manager, and you cannot configure them when creating the virtual machine. If needed, you can configure such parameters after the virtual machine is created.

To edit a virtual machine:

1. Click the Virtual Machines tab.

2. In the Virtual Machines table:

- Select the virtual machine you want to configure, and click Configure.

- Click the name of the virtual machine.

On the Virtual Machine Configure page, you can modify the following information:

- General

- Network

- Storage

- Policies

- Profiles

Some parameters, including the increased memory size, and the modified network information and virtual disk, can take effect immediately without restarting the virtual machine; for the other modified parameters to take effect, you need to restart the virtual machine.

6.7.1 General

On the General Information page, you can modify the general parameters of the virtual machine, including:

- Virtual Machine Name: Enter a new name for the virtual machine.
A virtual machine name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.

- Group Name: Select the group to which the virtual machine belongs.

- Maximum Memory Size (MB): Enter the maximum size of memory that the virtual machine can consume. The default maximum size of memory is the same as the size you allocated when creating the virtual machine.
Change the maximum memory size only when the status of the virtual machine is Powered Off.

- Memory Size (MB): Increase or decrease the memory size of the virtual machine. Allocate at least 256 MB memory.
Increased memory takes effect immediately without restarting the virtual machine. If you decrease the size of memory, you need to restart the virtual machine for the change to take effect.

- Description: A description of the virtual machine.

Click Save to save the configurations you have modified.

There is some other information you can view on this page, as shown in Table 6-1.

Table 6-1 General Information

Item

Description

Created By

The user who now owns this virtual machine

Status

The current status of the virtual machine. For more information on the status, see Section 6.1.2, "Virtual Machine Statuses".

Server Pool Name

The server pool in which the virtual machine is located

PVDriver Initialized

Whether PVDriver is initialized on the hardware virtualized machine (HVM) or not. Paravirtualized virtual machines (PV) do not have this parameter.

The status can be one of the following:

- True: PVDriver is installed on this hardware virtualized machine (HVM).

- False: PVDriver is not installed on this hardware virtualized machine (HVM); or it is installed but not initialized.

- Unknown: The virtual machine is shut down; Oracle VM Manager cannot detect the status of PVDriver; or you need to upgrade Oracle VM Agent to support this feature.

Creation Time

The time when the virtual machine was created

Running Time

How long the virtual machine has been running

Size (MB)

The total size of the virtual machine

Figure 6-8 General Information

6.7.2 Network

On the Network page, you can add, edit, or delete virtual network interfaces. You can set a maximum of eight virtual network interfaces.

Select Virtual Machine Type

If the virtual machine is a fully virtualized (hardware virtualized) machine, you can configure the virtual network interface (VIF) type to be either:

- Fully Virtualized

- Paravirtualized

The paravirtualized driver, also known as the netfront driver, can be used with either a paravirtualized machine, or a fully virtualized machine. The fully virtualized driver, also known as the ioemu driver, can only be used with a fully virtualized machine. Both drivers contain the BIOS and device emulation code to support fully virtualized machines.

For fully virtualized machines, the type can be either Fully Virtualized (ioemu) or Paravirtualized (netfront), and the default is Fully Virtualized (ioemu). For paravirtualized machines, the default is Paravirtualized (netfront), and this cannot be changed.

After you configure the virtual network interface type for one virtual network interface, all the virtual network interfaces in the virtual machine will be set to the same type.

Add a Virtual Network Interface (VIF)

To add a VIF:

1. Click Add.

2. Enter a name in the Virtual Network Interface Name field. Select a bridge type from the Bridge drop down.

3. All virtual network interfaces (VIFs) share the physical network interface card (NIC) to communicate with the outside. If you have several VIFs, and you want to control how much bandwidth is granted to each VIF, you can configure the rate limit. Select Enable Rate Limit, and enter the rate value in Mbits in the Rate Limit (Mbit) field. The network traffic through the virtual network interface cannot exceed this limit.
Click Next.

Confirm the new VIF information, and click Confirm to add the new VIF. The change takes effect without restarting the virtual machine.

You can also edit or delete an existing VIF on this page.

Figure 6-9 Network Information

6.7.3 Storage

Virtual machine storage may consist of either a virtual disk, or a boot source/CDROM. This section discusses both storage types.

6.7.3.1 Virtual Disks

There are two ways to expand the storage capacity of a virtual machine: by creating non-sharable virtual disks, or by adding shared virtual disks.

Oracle VM Manager only supports file-based disks. Physical disks are not supported.

Note:

For a hardware virtualized machine (HVM), you can attach up to four IDE disks (including CD-ROM and shared virtual disks), and seven SCSI disks.
A paravirtualized machine (PV) has no such limitation. But you need to restart it for the disk changes to take effect.

Using Non-sharable Virtual Disks

To create a non-sharable virtual disk:

1. Click Create New Virtual Disk.

2. Enter the disk name in the Virtual Disk Name field.
Enter the disk size in MBs in the Virtual Disk Size (MB) field. Allocate at least 1024 MB to the virtual disk.

Select an disk type from the Hard Drive Type drop down. For a hardware virtualized machine (HVM), if you select Auto, Oracle VM Agent first selects IDE as the type of the hard drive. If the IDE disks have reached the maximum of four, Oracle VM Agent then selects SCSI. If the SCSI disks have reached the maximum of seven, you cannot add any more disks. To verify how many interfaces are available, see the message on the upper right of the page, as shown in Figure 6-10. For a paravirtualized machine, there is no limitation.

Figure 6-10 Available Disk Interfaces

If you want to prioritize the virtual disk, you can enable disk priority with the QoS Enabled check box, and select an appropriate priority class. The priority class ranges from 0 to 7. The priority class 0 has the highest priority, and 7 the lowest.

Rather than being confined to a particular virtual machine, the priority of a virtual disk is global on the entire Oracle VM Server. Virtual disks of the same priority class take the same priority on the Oracle VM Server, even if they belong to different virtual machines.

There are three IO scheduling classes: Idle, Best Effort, and Real Time. Oracle VM adopts the Real Time scheduling class. The Real Time scheduling class is given the first access to the disk, regardless of what else is going on in the system. The eight priority levels are defined denoting how big a time slice a given process will receive on each scheduling window.

3. Click Next, confirm the information you have entered, and click Confirm to create the disk.

The new virtual disk can only be used by this virtual machine. You cannot share it.

To delete the non-sharable virtual disk, select it, and then click the Delete button. After you delete the virtual disk, all the files on it are deleted as well.

To delete shared virtual disks, see Section 5.4.5, "Deleting a Shared Virtual Disk".

Using Shared Virtual Disks

Shared virtual disks can only be shared among virtual machines within the same server pool. For information on how to create shared virtual disks, see Section 5.4.1, "Creating a Shared Virtual Disk".

To attach a shared virtual disk to the virtual machine:

1. Click Attach/Detach Shared Virtual Disk.

2. Move the disk from the Available Shared Virtual Disks column to the Selected Shared Virtual Disks column.

3. Click OK. The selected virtual disk is displayed in the Virtual Disks table.

To detach a virtual disk from the virtual machine:

1. Click Attach/Detach Shared Virtual Disk.

2. Move the disk from the Selected Shared Virtual Disks column to the Available Shared Virtual Disks column.

3. Click OK. The selected virtual disk is removed from the Virtual Disks table.

Virtual Disks Table

Table 6-2 displays the information you can view in the Virtual Disks table.

Table 6-2 Column Headers in the Virtual Disks Table

Column Header

Description

Virtual Disk Name

The name of the virtual disk.

Size (MB)

The size of the virtual disk in MBs.

Front-end Device

The name of the disk displayed in the virtual machine.

Hard Disk Driver

The type of the hard disk. For a hardware virtualized machine (HVM), it can be IDE, SCSI, or Auto. For a paravirtualized machine (PV), it can be IDE, SCSI, XVD, or Auto.

QoS Enabled

Whether QoS is enabled.

Priority Class

If QoS is enabled, the value of the priority class is displayed.

Shared

Whether the virtual disk is shared.

Status - Disk Attachment

Whether the disk is attached to the virtual machine. It may be either of the following statuses:

- Attached: The disk is attached to the virtual machine and functioning normally.

- Detached: The disk is not attached to the virtual machine due to the lack of disk interfaces. For example, you create an IDE disk, but the number of IDE disks exceeds 4 and there are no more IDE interface available for this disk. Therefore, the disk is detached.
It is also possible that Oracle VM Agent cannot connect to the disk. In this case, you need to edit the storage and save your changes. Oracle VM Agent then reconnects to the disk.

Status - Disk Status

The status of the disk may be one of the following:

- Creating: The disk is being created. It may take a few minutes.

- Active: The disk is available.

- Deleting: The disk is being deleted.

- Error: Some error occurred with the disk. You need to delete the disk and create a new one.

6.7.3.2 Boot Source/CDROM

You can select whether the virtual machine boots from a CDROM, disk, or from a location on the network.

To select the virtual machine boot location:

1. Select the Boot Source/CDROM sub-tab.

2. Select the boot device from the Boot Device drop down. You can choose to start the virtual machine from any of the following:

- HDD: Starts the virtual machine from the hard disk.

- CDROM: Starts the virtual machine from the CDROM. This option is only available to hardware virtualized machines.

- PXE: Starts the virtual machine through a Preboot Execution Environment (PXE) from a location on the network.

3. Select the location of the CDROM from which to boot the virtual machine in the CDROM field. This is an ISO file to install the guest operating system of the virtual machine. This option is only available to hardware virtualized machines.

4. Click Apply to set the boot source and location.

6.7.4 Policies

You can set policies for managing virtual CPUs and for placement, and to set HA for the virtual machine. This section discusses these policy options.

To set policies for a virtual machine, select the Policies sub-tab. The Policies page contains two further sub-tabs:

- High Availability

- Placement Policy

6.7.4.1 High Availability

You can set up HA for the virtual machine, and the number and scheduling priority of virtual CPUs on the High Availability page.

Figure 6-11 High Availability Policies

The fields on the High Availability page are:

- Number of Virtual CPUs: Change the number of virtual CPUs. Restart the virtual machine for the changes to take effect.

- Scheduling Priority: Set the scheduling priority for the virtual CPUs. You can select High (100), Intermediate (50), or Low (1) priority for the virtual CPUs. You can also enter a custom priority by selecting Customize and entering a value out of 100 in the text area.

- Scheduling Cap: Set the percentage to which the virtual CPUs can receive scheduled time. You can select a High (100%), Intermediate (50%), or Low (10%) percentage of scheduled time for the virtual CPUs. You can also enter a custom percentage by selecting Customize and entering a percentage in the text area.

- Enable High Availability: Select to enable HA for the virtual machine. HA guarantees the availability of virtual machines in case of the physical server failure or restart. To make high availability take effect, you must enable high availability for both the server pool and the virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".

6.7.4.2 Placement Policy

You can set a virtual machine to automatically run on any Virtual Machine Server available in the server pool, or to run on a specific Virtual Machine Server on the Placement Policy page.

To run a virtual machine on a specific Virtual Machine Server, click Manual and select the Virtual Machine Server(s) in the Results table on which to run the virtual machine. Click Confirm to confirm your selection.

To run a virtual machine on any available Virtual Machine Server in the server pool, click Auto. For more information about the preferred server, see Step 3 in Section 6.3.1, "Creating Virtual Machine From a Template".

Note:

If none of the preferred servers provide sufficient resources to run the virtual machine, the virtual machine may fail to start.

When the virtual machine is Powered Off or Suspended, you can switch between the Auto mode and the Manual mode.

6.7.5 Profiles

On the Profiles page, you can set up or modify the user name and password for login, boot source, operating system, and keyboard.

To set the profile for a virtual machine, select the Profiles sub-tab. The Profiles page contains two further sub-tabs:

- Login/Password

- Operating System

6.7.5.1 Login/Password

The Login/Password page enables you to change the virtual machine and console login information.

Figure 6-12 Profile Information - Login/Password

The fields available on the Login/Password page are:

- Virtual Machine System Username: Enter the user name used to log in to the guest operating system.

- Virtual Machine System Password: Enter the password used to log in to the guest operating system.

- Confirm Virtual Machine System Password: Confirm the password used to log in to the guest operating system.

- Console Password: Enter the password for VNC authentication.

- Confirm Console Password: Confirm the password for VNC authentication.

Click Send me the password if you want these passwords to be sent to your registered e-mail.

Click Apply to apply the changes.

6.7.5.2 Operating System

You can select an operating system, according to which Oracle VM optimizes the virtual machine profile, such as the configuration information in the vm.cfg file, and the timer mode for hardware virtualized machines (HVM). There are other behaviors controlled by selecting the operating system type, for example, Windows guests can use USB tablet emulation instead of mouse emulation. By selecting the appropriate operating system, you can run the virtual machine with a better performance.

You can change the keyboard for the virtual machine on this page. Select an appropriate keyboard you need to use to interact with the virtual machine.

Figure 6-13 Profile Information - Operating System

6.8 Reproducing Virtual Machines

Oracle VM Manager enables you to reproduce one or multiple virtual machines easily based on an existing virtual machine.

Use one of the following to reproduce virtual machines:

- Deploying a Virtual Machine

- Cloning Virtual Machines

- Saving a Virtual Machine as a Template

6.8.1 Deploying a Virtual Machine

By deploying a virtual machine, you can clone a new virtual machine to a specific server pool, and share it with other users, or keep it private. After deploying a virtual machine, the original virtual machine remains in the original server pool. You can only deploy virtual machines to the server pools and groups to which you belong.

Note:

Make sure the status of virtual machine is Powered Off before you deploy the virtual machine.

To deploy a virtual machine:

1. Click the Virtual Machines tab.

2. Select the virtual machine you want to deploy. In the More Actions list, select Deploy, and click Go. You can only deploy one virtual machine at a time.

3. Enter the name of the new virtual machine.

4. Select the group with whom you want to share the virtual machine.

- Public Group: Deploy the virtual machine to the public group, so that all Oracle VM Manager users can use this new virtual machine.

- My Workspace: Deploy the virtual machine to a server pool that only you are allowed to use and make it private.

- group_name: Share the new virtual machine with members of a specific group.

5. If you have selected My Workspace or a specific group, continue to select a server pool to which you want to deploy this virtual machine.

6. On the Confirm Information page, confirm the virtual machine information and click Confirm.

7. The virtual machine is deployed. This process may take some time. After you deploy the virtual machine, click the Refresh button periodically until the status of the new virtual machine changes from Creating to Powered Off. You can choose to refresh manually, or to refresh every 30 seconds.
If the status is Error, see Section 6.1.2.9, "Error" to troubleshoot the error.

Note:

If you deploy a virtual machine to the Public Group, the deployed virtual machine image is compressed and copied to the /OVS/publish_pool of the Oracle VM Server. The deployed virtual machine cannot be Powered On. To make this virtual machine available to all users, download or copy the virtual machine image, uncompress it and import it as a virtual machine image or template. Alternatively, you can select the deployed virtual machine and deploy it again to My Workspace, or another group.

Now you have finished deploying the virtual machine. To start the new virtual machine, see Section 6.4.1, "Starting a Virtual Machine".

You can change the preferred server and other configurations of the new virtual machine. See Section 6.7, "Editing a Virtual Machine".

6.8.2 Cloning Virtual Machines

Cloning a virtual machine is a process to create one or more copies of an existing virtual machine. By cloning a virtual machine, you can save multiple copies to another server pool and share them with other users.

Note:

Make sure the status of the virtual machine is Powered Off before you clone the virtual machine.

To clone a virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine you want to clone. In the More Actions list, select Clone, and click Go.

3. Enter the required information.

- Virtual Machine Name Prefix: Enter the prefix used to name the virtual machine copies. For example, if you enter vm, the virtual machine copies will be named vm0, vm1, vm2, and so on.

- Number of Copies: Enter the number of copies you want to clone. For example, if you enter 5, five copies of the virtual machine will be created. You can clone a maximum of 10 copies.

- Server Pool Name: Select the server pool where the cloned virtual machine copies will be located.

- Group Name: Select the group who can use the cloned virtual machines copies.

4. This process may take some time. When the status of the original virtual machine changes from Cloning to Powered Off, click Refresh to check the latest virtual machine status. You can choose to refresh manually, or to refresh every 30 seconds. When the status of the cloned virtual machine changes from Creating to Powered Off, the cloning process is complete.
If the status is Error, see Section 6.1.2.9, "Error" to troubleshoot the error.

Now you have created multiple copies of the virtual machine. You can change the preferred server and other configurations of the cloned virtual machines. See Section 6.7, "Editing a Virtual Machine".

6.8.3 Saving a Virtual Machine as a Template

You can save a virtual machine as a template, to enable other users to create their new virtual machines based on this template. For more information on this, refer to Section 6.3.1, "Creating Virtual Machine From a Template".

Note:

Make sure the status of the virtual machine is Powered Off before you save the virtual machine as a template.

To save a virtual machine as a template:

1. Click the Virtual Machines tab.

2. Select the virtual machine you want to deploy as a template. In the More Actions list, select Save As Template, and click Go. You can only save one virtual machine at a time.

3. Enter the template name, and click Confirm.

4. The status of the original virtual machine changes from Powered Off to Saving.
This process may take some time. When the status returns to Powered Off, click the Resources tab, and then click the Virtual Machine Templates tab. Refresh the virtual machine periodically until the status changes from Creating to Active. You can see the new virtual machine template.

Now you can use the new template to create virtual machines.

6.9 Migrating a Virtual Machine

Live migration is a process to migrate a running virtual machine from one Virtual Machine Server to another, while applications on the existing virtual machine continue to run. Live migration ensures high availability of virtual machines. This feature is important, and useful, when the existing Virtual Machine Server may be out of commission, or on a planned shutdown for maintenance purposes.

Cross-server-pool live migration is not allowed. You can only migrate virtual machines from one Virtual Machine Server to another within the same server pool. You must use identical computers to perform live migrations, that is, the computer make and model number of both the source computer and the destination computer must be identical.

You must create a shared virtual disk before migrating the virtual machine.

To migrate a virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the running virtual machine. In the More Actions list, select Live Migration, and click Go.

3. Select the Virtual Machine Server to which you want to migrate the virtual machine. Click Next.

4. Check the virtual machine information, and click Confirm.

The virtual machine is migrated.

6.10 Deleting a Virtual Machine

When you delete a virtual machine, all the files and data associated with this virtual machine will be removed from Oracle VM Manager. Before deleting a virtual machine, make sure you do not need it any longer.

Note:

Delete the virtual machine only when the virtual machine status is Powered Off or Error.

The process of deleting a normal virtual machine is different from that of deleting a virtual machine stuck in a certain status.

- Deleting a Virtual Machine in Powered Off or Error Status

- Deleting a Stuck Virtual Machine

6.10.1 Deleting a Virtual Machine in Powered Off or Error Status

To delete a virtual machine in the Powered Off or Error status:

1. On the Virtual Machines page, select the virtual machine you want to delete.

2. In the More Actions list, select Delete, and click Go.

3. Confirm the delete action.

6.10.2 Deleting a Stuck Virtual Machine

If a virtual machine gets stuck in any status such as Shutting Down or Creating, you can reset it, or shut it down, and delete it. To reset a virtual machine, see Section 6.4.5, "Resetting a Virtual Machine".

To delete a stuck virtual machine:

1. Click the Virtual Machines tab.

2. On the Virtual Machines page, select the virtual machine, and then click Power Off.

3. After the status changes to Powered Off, delete the virtual machine.

7 Managing Users and Groups

This Chapter describes how to manage users and groups as an Administrator. It includes the following sections:

- The Default Account

- Managing Users

- Managing Groups

- Viewing Logs

Note:

- Functions described in this Chapter are only available to Administrators.

- A small mistake made by an Administrator may cause serious damage to the entire Oracle VM Manager environment. Please minimize the number of administrators when creating the accounts.

7.1 The Default Account

Oracle VM Manager provides a default account. The default user name is admin (lowercase). The password is set when you install Oracle VM Manager.

7.2 Managing Users

You can create new users, delete obsolete users, change the users' role, and reset the user password. This section includes the following topics:

- Creating a User

- Viewing Details

- Editing a User

- Changing a Role

- Deleting a User

To search for a user, click Show Search and enter the search criteria.

7.2.1 Creating a User

To create a user:

1. On the Administration page, click the User tab and then click the Create button.

2. Enter the following user information:

- Username: An account name for the user. You cannot use manager, or user as the user name.
An account name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) and hyphen (-) characters. The maximum name length is 100 characters.

- Password: The password used by the user to log in to Oracle VM Manager.

- Retype Password: The user password.

- First Name: The first name of the user.

- Last Name: The last name of the user.

- Email: The user's e-mail address. If the user forgets the password, a new password is sent to this e-mail.

- Status: Select the account status. It can be Locked or Unlocked. The account is available only when the status is Unlocked. To lock this account, select Locked.

- Role: Grant the user one of the three roles: User, Manager, or Administrator. For more information about the roles, refer to Section 1.5, "Roles in Oracle VM Manager".

3. Select server pools for the user.

4. Select groups for the user. One user may join multiple groups.

5. Click Confirm.

The user is created.

7.2.2 Viewing Details

To view a user's detailed information:

1. On the Administration page, click the User tab.

2. Click the Show link in the User table to view the server pool(s) the user is allowed to use, and the groups to which the user belongs.

Figure 7-1 Details of a User

7.2.3 Editing a User

Edit the user information when you want to:

- Change the user information, such as e-mail address.

- Change the account status to either lock or unlock the account.

- Change the role.

- Add the user to some groups, or server pools.

- Remove the user from some groups, or server pools.

To edit a user:

1. On the Administration page, search and select the user you want to edit, and click the Edit button.

2. On the Edit page you can update the user information, change the user's role, add the user to groups or server pools, or remove the user from groups or server pools.
The account status can be Locked or Unlocked. By default, the status is Unlocked. If you lock an account, the user cannot use it any more.

3. Click Apply.

7.2.4 Changing a Role

When a user's role has changed, for example, a common user is assigned as an Administrator, you need to change the user's role in Oracle VM Manager.

For more information about roles, refer to Section 1.5, "Roles in Oracle VM Manager".

To change the user role:

1. On the Administration page, select the target user, and click the Edit button.

2. Select the role accordingly, and then click the Apply button.

7.2.5 Deleting a User

To delete a user:

1. On the Administration page, search and then select the users you want to delete. Click the Delete button.

2. Confirm the users you want to delete.

7.3 Managing Groups

There are many users in the Oracle VM Manager system, and it is time-consuming to assign privileges individually to each user. The group function enables you to add some specific users to a group. After you assign some privileges to the group, all members of this group will have the group privileges. This will facilitate the job for administrators.

This section includes the following topics:

- Default Groups

- Creating a Group

- Adding a User to a Group

- Editing a Group

- Deleting a Group

To search for a group, click Show Search and enter the search criteria.

7.3.1 Default Groups

There are two default groups: Public Group and My Workspace.

- The Public Group contains all public virtual machines. All users can deploy and view virtual machines in the Public Group.

- The My Workspace group only contains private virtual machines. Only the virtual machine owner can manage virtual machines in My Workspace.

7.3.2 Creating a Group

When there are a large number of users, you can combine specific users into a group, or groups. For example, you can combine users who belong to the same server pool into one group.

To create a group:

1. On the Administration page, click the Group tab.

2. Click the Create button, enter the group name and description.

3. Select users for the group. Double-click the user name in the Available Users column to add it to the Selected Users column.

4. Click Confirm.

7.3.3 Adding a User to a Group

To add a user to a new group:

1. On the Administration page, click the User tab.

2. Search and select the user you want to add to the group, and click Edit.

3. In the Group area, double-click the group in the Available Groups column to move it to the Selected Groups column.

4. Check the Group section. Make sure the group you have selected shows up in the Selected Groups column.

5. Click Apply.

7.3.4 Editing a Group

To edit a group, select the group you want to update, and click the Edit button to update the group information. You can also add users to the group, or remove users from the group.

7.3.5 Deleting a Group

To delete a group:

1. On the Administration page, select the group you want to delete, and click the Delete button.

2. Confirm the group you want to delete.

After you delete a group, all users in this group will still remain in the system. If you want to delete users along with the group, see Section 7.2.5, "Deleting a User".

7.4 Viewing Logs

You can view all Oracle VM Manager logs at once, rather than going to the log pages for each object (such as virtual machine or server pool). The log includes message logs for:

- Virtual machines

- Resources such as virtual machine templates and ISO files

- Oracle VM Servers

- Server pools

- Administration tasks

To view the logs, go to the Administration page and click the Log tab. The log information includes:

- The time the message was generated.

- The log level of the message:

- INFO denotes a normal operational message and is informational only.

- WARNING denotes a more serious message that may require your attention to resolve.

- ERROR denotes an error occurred.

- The username that initiated the process that generated the log.

- The target type, such as a virtual machine or server pool.

- The target name, such as the virtual machine or server pool name.

- The operation that generated the message.

- The message.

You can select the refresh rate for the log results using the Refresh in field. Logs can be refreshed manually, or every 10 or 30 seconds.

To search for a log, click Show Search and enter the search criteria.

A Preparing Virtual Machines For Importing

If you have prebuilt Oracle VM virtual machines, you can import them into Oracle VM Manager to use as virtual machines, or templates.

Before you import a virtual machine, you must have an Oracle VM Server and store the virtual machine files in the correct directory of the Oracle VM Server, according to your needs. Oracle VM Agent updates the directory information in the vm.cfg file automatically when importing virtual machines.

For information about Oracle VM Servers, refer to Section 1.4, "Configuration of Oracle VM Manager", and Section 3.2, "Creating a Server Pool".

If you want to import a prebuilt virtual machine as a template, copy the virtual machine files to the Oracle VM Server directory:

/OVS/seed_pool/vm_name/

If you want to import a prebuilt virtual machine as a private virtual machine (it is not shared with others), copy the virtual machine files to the Oracle VM Server directory:

/OVS/running_pool/vm_name/

To move the virtual machine to the correct location for importing:

1. Log in to the Oracle VM Server.

2. Download, or copy the virtual machine to the correct directory for your needs. For example, to download the virtual machine XEN_EL4U5_X86_HVM from http://example.com/seeds/ as a template:

- If the virtual machine is compressed, run the wget command to download it:

# cd /OVS/seed_pool
# wget http://example.com/seeds/XEN_EL4U5_X86_HVM.tgz

Uncompress the virtual machine:

# cd /OVS/seed_pool
# tar -xzvf XEN_EL4U5_X86_HVM.tgz

- If the virtual machine is not compressed, run the wget -r command to download it:

# cd /OVS/seed_pool
# wget -r http://example.com/seeds/XEN_EL4U5_X86_HVM/

A directory named XEN_EL4U5_X86_HVM is created under the /OVS/seed_pool/ directory, and the virtual machine files are extracted and ready to be imported as a template in Oracle VM Manager.

B Backing Up and Restoring Oracle VM Manager

Back up Oracle VM Manager before you:

- Uninstall Oracle VM Manager.

- Move the Oracle VM Server from one computer to another.

- Make any major change in Oracle VM Manager.

This Appendix includes the following topics:

- Backing Up Oracle VM Manager

- Restoring Oracle VM Manager

B.1 Backing Up Oracle VM Manager

Before you back up Oracle VM Manager, make sure the status of all Oracle VM Servers in the server pool is Running.

To back up Oracle VM Manager:

1. Log in to an Oracle VM Server in the server pool as the root user.

2. Back up the Oracle VM Manager shared storage resources stored in the following directories:

- /OVS/running_pool for virtual machine images

- /OVS/seed_pool for virtual machine templates

- /OVS/iso_pool for ISO files

Skip this step if you have enabled a shared storage backup mechanism.

3. Log into the Oracle VM Manager host as the root user.

4. Back up the existing Oracle VM Manager data:

# sh /opt/ovs-manager-2.2/bin/backup.sh

Enter 1 to back up the data.

Please enter the choice: [1|2]
1. Back up Oracle VM Manager,
2. Restore Oracle VM Manager

Enter the database information, and the path for the dump and log files.

Back up data now ...
Please enter the password for database account 'OVS':
Please specify the path for dump file?
Please specify the path for log file?

Oracle VM Manager is backed up.

B.2 Restoring Oracle VM Manager

To restore Oracle VM Manager:

1. Log in to an Oracle VM Server in the server pool as the root user.

2. Restore the backed up Oracle VM Manager shared storage resources into the following directories respectively:

- /OVS/running_pool for virtual machine images

- /OVS/seed_pool for virtual machine templates

- /OVS/iso_pool for ISO files

3. Log into the Oracle VM Manager host as the root user.

4. Shut down Oracle VM Manager:

# service oc4j stop

5. Restore the backed up Oracle VM Manager data:

# sh /opt/ovs-manager-2.2/bin/backup.sh

Enter 2 to restore the data.

Please enter the choice: [1|2]
1. Back up Oracle VM Manager,
2. Restore Oracle VM Manager

Enter the database information, and the path for the dump and log files.

Please enter the password for database account 'SYS':Please enter the password for database account 'OVS':Please specify the path for dump file?Please specify the path for log file?

For example, enter:

Please enter the password for database account 'SYS':
Please enter the password for database account 'OVS':
Please specify the path for dump file?/dump
Please specify the path for log file?/log

6. Start up Oracle VM Manager:

# service oc4j start

Oracle VM Manager is restored.

C Web Services API

Oracle VM Manager provides a Web services Application Programming Interface (API) to enable integration of third party products with Oracle VM Manager. You can use the API to perform any of the operations in Oracle VM Manager, for example, to create a server pool, add servers, and create virtual machines. You can use any language that supports Web services to access the API, for example Java or Python.

This Appendix describes the Oracle VM Manager Web services API and contains:

- Web Services API

- Creating a Web Service Client

- Authentication and Security

- Web Service Locations

- Web Services

C.1 Web Services API

Oracle VM Manager acts as an administration platform for Oracle VM Servers connected on a network to direct actions to the virtual machines, virtual servers and the server pool. Oracle VM Manager provides the management environment for Oracle VM. A Web services API is available for Oracle VM Manager. The Oracle VM Manager Web services API architecture is shown in Figure C-1, "Oracle VM Manager Web Services API Architecture".

Figure C-1 Oracle VM Manager Web Services API Architecture

The Oracle VM Manager API provides a complete set of interfaces to Oracle VM Manager. The Oracle VM Manager API is accessed through the Oracle VM Manager Web services API using the SOAP protocol.

The Oracle VM Manager Web service API provides all the operations necessary, including life-cycle operations, to monitor and manage virtual infrastructure components, like server pools, virtual servers, virtual machines, networks, storage, and so on.

The Oracle VM Manager Web services API is implemented as shown in Figure C-2, "Oracle VM Manager Web Services API Implementation".

Figure C-2 Oracle VM Manager Web Services API Implementation

The Oracle VM Manager API is used by the Oracle VM Manager UI layer, and by the virtualization management component of Oracle Enterprise Manager. The Web services API can be used by Oracle applications as well as third party applications.

C.2 Creating a Web Service Client

You can use any programming language that supports Web services to create a Web services client. Most example code in this Chapter is written in Java and created using Oracle JDeveloper, although you can use the language and development tool of your choice.

To use Web services in Java, you can create SOAP messages directly, or generate proxy classes for each Web service. In Oracle JDeveloper, use the Web service WSDL URL to automatically generate proxy classes.

If you create an object that exists in multiple web services, for example, a VirtualServer object in both ServerPoolService and VirtualMachineService, you should specify the default package, api.ovs.oracle, or any self defined package name, for all the web services you use. Do not specify the particular package names, for example, api.ovs.oracle.serverPool and api.ovs.oracle.vm, as objects that exist in both packages must then be converted to the respective namespace. In the VirtualServer example, the object sps.ServerPool is not equivalent to vms.ServerPool, and one object must be converted to the other before passing it to the method being invoked.

C.2.1 Creating a Proxy Class in Java

The examples given here use Oracle JDeveloper and the Java wsimport utility to create proxy classes in Java.

C.2.1.1 Using Oracle JDeveloper

To create a proxy class for an Oracle VM Manager Web service in Java using Oracle JDeveloper, use the Web service WSDL URL feature.

Example C-1 Retrieving a Server Pool by Name Using Oracle JDeveloper

An Oracle JDeveloper proxy class for retrieving a server pool using its name might look similar to:

public ServerPool getServerPoolByName(String poolName) throws Exception{
String username = "myuser";
String password = "mypassword";

//ServerPoolServiceSoapHttpPortClient is generated by Jdeveloper.
server.ServerPoolServiceSoapHttpPortClient myPort =
new server.ServerPoolServiceSoapHttpPortClient();
myPort.setMaintainSession(true);
myPort.setUsername(username);
myPort.setPassword(password);
ServerPool thePool = myPort.getServerPoolByName(poolName);
return thePool;
}

Example C-2 Importing a Guest Virtual Machine or Template Using Oracle JDeveloper

An Oracle JDeveloper proxy class for importing a guest virtual machine, or template, might look similar to:

/**
* @param args
*/
public static void main(String[] args) {
try {
oracle.ovs.api.ResourceServiceSoapHttpPortClient myPort = new oracle.ovs.api.ResourceServiceSoapHttpPortClient();
System.out.println("calling " + myPort.getEndpoint());

/* External Template Importing **/
VirtualMachineTemplate vmt = new VirtualMachineTemplate();
/* set template name **/
vmt.setImgName("MyTemplate");
/* set download url **/
vmt.setDownloadURL("http://example.com/OEL5");
/* set proxy url(optional) **/
vmt.setProxyURL("http://proxy.example.com:80");
/* set vm username **/
vmt.setVmUsername("myuser");
/* set vm password **/
vmt.setVmPassword("mypassword");
/* set operating system type **/
vmt.setOsType("Enterprise Linux 5");
/* set description **/
vmt.setDescription("My description.");
/* start importing **/
myPort.registerExternalTemplate("example.com", vmt);

/* Internal Image Importing **/
VirtualMachineImage vmi = new VirtualMachineImage();
/* set vm name **/
DiscoveredVirtualMachineImage[] unregisteredImages = myPort.getAllDiscoverableImages("example.com");
/* find unregistered vm **/
if (unregisteredImages.length > 0) {
vmi.setImgName(unregisteredImages[0].getImgName());
}
else {
return;
}

/* set vm username **/
vmi.setVmUsername("myuser");
/* set vm passwd **/
vmi.setVmPassword("mypassword");
/* set vnc password **/
vmi.setVncPassword("mypassword");
/* set operating system type **/
vmi.setOsType("Enterprise Linux 4 64-bit");
/* set description **/
vmi.setDescription("My description.");
/* start importing **/
myPort.registerInternalImage("example.com", vmi);

} catch (Exception ex) {
ex.printStackTrace();
}
}

Example C-3 Creating a Guest Virtual Machine From a Template Using Oracle JDeveloper

An Oracle JDeveloper proxy class for creating a guest virtual machine from a template might look similar to:

public static void main(String[] args) {
try {
LifecycleServiceSoapHttpPortClient myPort =
new LifecycleServiceSoapHttpPortClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here

myPort.setUsername("myuser");
myPort.setPassword("mypassword");

TemplateVmConfig templateVMConfig= new  TemplateVmConfig();
templateVMConfig.setServerPoolName("example.com");
//your serverpoolName
templateVMConfig.setTemplateName("myTemplate");//your templateName

NICConfig nic = new NICConfig();
nic.setName("VIF0");
nic.setIpAddress("ioemu");

nic.setBridge("xenbr0");
nic.setMacAddress("00:16:xx:xx:xx:xx");
NetworkConfType confType = new NetworkConfType();
confType.setType("Dynamic");
nic.setNetworkConfType(confType);

//nic.set
NICConfig[] vifs = new NICConfig[]{nic};
templateVMConfig.setVif(vifs);

templateVMConfig.setVmName("MyGuestVirtualMachine");

templateVMConfig.setConsolePassword("mypassword");
templateVMConfig.setHaEnable(false);

myPort.createVmBasedOnTemplate(templateVMConfig);
} catch (Exception ex) {
ex.printStackTrace();
}
}

public LifecycleService _port;
public VirtualMachine createVmBasedOnTemplate(TemplateVmConfig templateVMConfig) throws java.rmi.RemoteException{
ServiceFactory factory = ServiceFactory.newInstance();
_port = ((LifecycleService_Service)factory.loadService(LifecycleService_Service.class))
.getLifecycleServiceSoapHttpPort();
return _port.createVmBasedOnTemplate(templateVMConfig);
}

C.2.1.2 Using wsimport

To create a proxy class for an Oracle VM Manager Web service in Java using the wsimport utility:

$ JAVA_HOME/bin/wsimport -d <dir-for-compiled classes> -keep -s <dir-for-generated-source> -p com.oracle.ovm.manager.ws.vms -wsdllocation http://ovm_host:port/OVSWS/nameService.wsdl <path-to-wsdl-file-in-local-host>

For example, to create a proxy class for the ServerPool Web service, you might enter:

$ JAVA_HOME/bin/wsimport -d <dir-for-compiled classes> -keep -s <dir-for-generated-source> -p com.oracle.ovm.manager.ws.vms -wsdllocation http://example.com:8888/OVSWS/ServerPoolService.wsdl <path-to-wsdl-file-in-local-host>

Example C-4 Retrieving a Server Pool by Name Using wsimport

A wsimport proxy class for retrieving a server pool using its name might look similar to:

public ServerPool getServerPoolByName(String poolName) throws Exception{
String url = "http://example.com:8888/";
String contextPath = "OVSWS";
String user = "myuser";
String password = "mypassword";
ServerPoolService_Service sps_service =
new ServerPoolService_Service(new URL(url + contextPath +
"/ServerPoolService.wsdl"),
new QName("http://oracle.ovs.api/", "ServerPoolService"));
sps = sps_service.getServerPoolServiceSoapHttpPort();

BindingProvider bp = (BindingProvider) sps;
Map<String, Object> rc = bp.getRequestContext();
rc.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, url + contextPath +
"/ServerPoolServiceSoapHttpPort");
rc.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, new Boolean(true));
rc.put(BindingProvider.USERNAME_PROPERTY, user);
rc.put(BindingProvider.PASSWORD_PROPERTY, password);

GetServerPoolByNameElement req = new GetServerPoolByNameElement();
req.setPoolName(poolName);
GetServerPoolByNameResponseElement res = sps.getServerPoolByName(req);
ServerPool thePool = res.getResult();
return thePool;
}

C.2.2 Creating a Proxy Class in Python

To create a proxy (stub) class for an Oracle VM Manager Web service using Python:

$ wsdl2py -b http[s]://ovm_host:port/OVSWS/nameService.wsdl

For example, to create a proxy class for the ServerPool Web service, you might enter:

$ wsdl2py -b https://ovm.example.com:4443/OVSWS/ServerPoolService.wsdl

Example C-5 Retrieving a Server Pool by Name using Python

A Python proxy class for retrieving a server pool using its name might look similar to:

import ServerPoolService_client as c

class ServerPoolManagementPort:

def __init__(self, urlbase, auth):
self.wspath = "/ServerPoolServiceSoapHttpPort"
self.loc = c.ServerPoolServiceLocator()
self.srv = self.loc.getServerPoolServiceSoapHttpPort(url = urlbase +
self.wspath, auth = auth)
def getServerPoolByName(self, poolName):
"""
Return instance os a specific server pool managed by the system, by its
name.
@param poolName:
@type poolName: str
@return: ServerPool
"""
request = c.ServerPoolService_getServerPoolByName()
request._poolName = poolName
response = self.srv.getServerPoolByName(request)
return response._result

To call this code, including authentication with the Web service, you might use:

from ServerPoolManagementPort import *
from ZSI.auth import AUTH
auth=(AUTH.httpbasic, 'myuser', 'mypassword')
spm = ServerPoolManagementPort(urlbase = 'https://ovm.example.com:4443/OVSWS/',
auth = auth)
serverpool = spm.getServerPoolByName('myserverpool')

C.3 Authentication and Security

The Oracle VM Manager Web services use HTTP basic authentication to authenticate users and control access. HTTP basic authentication requires that the server requests a username and password from the Web services client, and verifies that the username and password are valid by comparing them against a valid Oracle VM Manager user.

SSL is enabled by default for Web services, and secures the data during transmission at transport level. For each Web service call, the server authenticates the log in credentials for valid Oracle VM Manager users in the basic header.

If you need to set up SSL for Web services after the original Oracle VM Manager installation, you can use the script:

# /opt/ovs-manager-2.2/bin/secure_ws.sh

This script generates the keystore for Oracle VM Manager Web services and configures OC4J.

To perform the authentication with Oracle VM Manager, you must pass the Oracle VM Manager login credentials to the Oracle VM Manager Web service from a Web services client.

Example C-6 Authentication in Java

To perform HTTP basic authentication from a Java Web services client:

1. Change the URL to the Web service from http to https. For example, https://ovm.example.com:4443. This is the URL used to obtain the SOAP HTTP port in step 3.

2. Add the following two system properties to the client-side Java to perform the SSL handshake:

-Djavax.net.ssl.trustStore=/path/ovmm_client_trust.jks    <=== this contains the manager's cert
-Djavax.net.ssl.trustStorePassword=truststorepasswd

3. Obtain the SOAP HTTP port, with code similar to the following:

ServerPoolService_Service sps_service =
new ServerPoolService_Service(new URL(url + contextPath +
"/ServerPoolService.wsdl"),
new QName("http://oracle.ovs.api/", "ServerPoolService"));
//Note, the URL here is the URL mentioned in Step 1. It is the HTTPS URL.
ServerPoolService sps = sps_service.getServerPoolServiceSoapHttpPort();

BindingProvider bp = (BindingProvider) sps;
Map<String, Object> rc = bp.getRequestContext();
rc.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, url + contextPath +
"/ServerPoolServiceSoapHttpPort");
rc.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, new Boolean(true));
rc.put(BindingProvider.USERNAME_PROPERTY, myuser);
rc.put(BindingProvider.PASSWORD_PROPERTY, mypassword);

4. You must also generate a keystore and proxy on the Web services client. For example, you could use:

# java -Djavax.net.ssl.trustStore=/Users/myuser/ssl/client.keystore
-Djavax.net.ssl.keyStore=/Users/myuser/ssl/client.keystore
-Djavax.net.ssl.trustStorePassword=mypassword
-Djavax.net.ssl.keyStorePassword=mypassword
-jar $ORACLE_HOME/webservices/lib/wsa.jar
-genProxy
-wsdl https://ovm.example.com:4443/OVSWS/AdminServiceSoapHttpPort?WSDL

5. To set the login credentials on the Web services client, you could use:

System.setProperty("javax.net.ssl.trustStore", "/Users/myuser/ssl/client.keystore");
System.setProperty("javax.net.ssl.keyStore", "/Users/myuser/ssl/client.keystore");
System.setProperty("javax.net.ssl.trustStorePassword", "mypassword");
System.setProperty("javax.net.ssl.keyStorePassword", "mypassword");
...

Example C-7 Authentication in Python

An Python proxy class to authenticate and retrieve a server pool might look similar to:

import ServerPoolService_client as c
from ZSI.auth import AUTH
loc = c.ServerPoolServiceLocator()
auth = (AUTH.httpbasic, 'myuser', 'mypassword')
srv = loc.getServerPoolServiceSoapHttpPort(auth=auth)
req = c.ServerPoolService_getServerPoolByName()
req._poolName = 'myserverpool'
resp = srv.getServerPoolByName(req)
serverPool = resp._result

C.4 Web Service Locations

Each Oracle VM Manager Web service URL has the syntax:

http[s]://ovm_manager_host:port/OVSWS/WS_name.wsdl

SSL is enabled by default for Web services, and secures the data during transmission at transport level. Although you can access the Web services without using SSL, Oracle recommends you use SSL for increased security.

A test page is available for each Web service that enables you to test a Web service and values for the Web service parameters. The Web service test page URL has the syntax:

http[s]://ovm_manager_host:port/OVSWS/WS_nameSoapHttpPort

When you open a Web service test page in a browser, you must authenticate with the Web service by entering an Oracle VM Manager administrator username and password. When you have authenticated, a form is displayed that enables you to input parameters and invoke different methods in the Web service. This form also contains a link named Service Description that displays the WSDL for the Web service. The following is the syntax for the WSDL URL:

http[s]://ovm_manager_host:port/OVSWS/WS_nameSoapHttpPort?WSDL

or

http[s]://ovm_manager_host:port/OVSWS/WS_name.wsdl

The Web service test page also contains a link to the documentation for the Web service. The syntax for the Web service documentation is:

http[s]://ovm_manager_host:port/OVSWS/WS_nameSoapHttpPort?WS_ nameSoapHttpPortstub.html

For example, if your Oracle VM Manager host is ovm.example.com, and its port is 4443 and SSL is enabled, then the following URL is the location for the LifecycleService:

https://ovm.example.com:4443/OVSWS/LifecycleService.wsdl

And the location of the test page for LifecycleService is:

https://ovm.example.com:4443/OVSWS/LifecycleServiceSoapHttpPort

The corresponding LifecycleService documentation URL is:

https://ovm.example.com:4443/OVSWS/LifecycleServiceSoapHttpPort?LifecycleServiceSoapHttpPortstub.html

C.5 Web Services

The Oracle VM Manager Web services available are:

- LifecycleService: Manages the lifecycle of virtual machines.

- ResourceService: Manages resources.

- PluginService: Manages the plug in.

- ServerPoolService: Manages servers and server pools.

- VirtualMachineService: Manages virtual machines.

- AdminService: Manages users and groups.

C.5.1 LifecycleService

The LifecycleService Web service manages the lifecycle of virtual machines. You can use this Web service to create a virtual machine, enable HA, perform live migration, attach CDs and disks, and so on.

The LifecycleService Web service is located at:

http[s]://ovm_manager_host:port/OVSWS/LifecycleService.wsdl

The methods available in this Web service are:

- addDisk

- addNIC

- attachCDtoVM

- attachSharedVirtualDisk

- changeNetworkType

- clone

- configDisk

- configNIC

- configVMGroup

- createVmBasedOnISO

- createVmBasedOnPXE

- createVmBasedOnTemplate

- deploy

- detachCD

- detachSharedVirtualDisk

- disableHA

- enableHA

- getConsolePassword

- getKeyboardLayoutArray

- getVMGroupByVMId

- liveMigrate

- liveMigrateAll

- removeDisk

- removeNIC

- resetStatus

- setBootPriority

- setConsolePassword

- setCpuCores

- setDynamicMemory

- setGuestCredential

- setMaximumMemory

- setNetworkInsideGuest

- setOperatingSystem

- setPreferredServers

- setVCPUCapByVMID

- setVCPUPriorityByVMID

- setVMConfigParam

- setVMDescription

- setVMKeyboardLayout

More detailed information on the functions available in this web service is available in the Oracle VM Manager Web Services API Reference.

C.5.2 ResourceService

The ResourceService Web service manages resources. You can use this Web service to import and manage ISO files, templates, virtual machines, and shared virtual disks.

The ResourceService Web service is located at:

http[s]://ovm_manager_host:port/OVSWS/ResourceService.wsdl

The methods available in this Web service are:

- ValidateVMConfig

- approveISOResource

- approveImage

- approveTemplate

- deleteISO

- deleteImage

- deleteSharedVirtualDisk

- deleteTemplate

- getAllDiscoverableISO

- getAllDiscoverableImages

- getAllDiscoverableTemplates

- getAllISOResources

- getAllImageResources

- getAllSharedVirtualDisks

- getAllTemplateResources

- getISOResource

- getISOResourceByGroupName

- getISOResourceByGroupNameAndISOName

- getISOResourceByISOName

- getImageResource

- getImageResourceByName

- getRegisteredMultipathDevices

- getRegisteredSharedVirtualDisks

- getSharedDiskResource

- getSharedDiskResourceByName

- getTemplateResource

- getTemplateResourceByName

- getUnregisteredMultipathDevices

- getUnregisteredSharedVirtualDisks

- registerExternalISO

- registerExternalImage

- registerExternalTemplate

- registerISO

- registerInternalISO

- registerInternalImage

- registerInternalSharedVirtualDisk

- registerInternalTemplate

- registerMultipathDevice

- registerSharedVirtualDisk

More detailed information on the functions available in this web service is available in the Oracle VM Manager Web Services API Reference.

C.5.3 PluginService

The PluginService Web service manages the plug in. You can use this Web service to set or get plug in scope properties.

The PluginService Web service is located at:

http[s]://ovm_manager_host:port/OVSWS/PluginService.wsdl

The methods available in this Web service are:

- disposePlugin

- getDaemonManager

- preparePlugin

More detailed information on the functions available in this web service is available in the Oracle VM Manager Web Services API Reference.

C.5.4 ServerPoolService

The ServerPoolService Web service manages servers and server pools. You can use this Web service to create and manage servers and server pools.

The ServerPoolService Web service is located at:

http[s]://ovm_manager_host:port/OVSWS/ServerPoolService.wsdl

The methods available in this Web service are:

- addMembers

- blackoutServer

- checkHAAbility4ServerPoolById

- checkServerConnection

- checkVirtualServerCompatibility

- createServerPool

- deleteServerPool

- endBlackoutServer

- getAgentVersion

- getAllHVMServerPools

- getAllHVMServerPoolsByUserId

- getAllMembers

- getAllServerPools

- getClusterRootByServerPoolId

- getMasterAgentStatus

- getMasterServer

- getMinSupportedOVSAgentVersion

- getMinimumAgentVersion

- getNetworkBridges

- getNetworkBridgesByServerIP

- getServer

- getServerByName

- getServerPool

- getServerPoolById

- getServerPoolByName

- getServerPoolMetricsByServerPoolId

- getServerPools

- get StorageResositoriesByServerPoolId

- getVirtualServerById

- getVirtualServerByName

- getVirtualServerByServerPool

- getVirtualServerMetrics

- getVirtualServers

- rebootServer

- refreshServerPool

- removeMember

- restoreVirtualServerPoolByManagerData

- shutdownServer

- updateServerPool

- updateUserList4ServerPool

- updateUtilityServerPassword

- updateVirtualServer

- updateVirtualServerAgentPassword

- updateVirtualServerById

- validateAddMembers

- validateBlackoutServer

- validateCreateServerPool

- validateDeleteServerPool

- valicateRebootServer

- validateRemoveMember

- validateShutdownServer

- validateUpdateUtilityServerPassword

- validateUpdateVSAgentPassword

More detailed information on the functions available in this web service is available in the Oracle VM Manager Web Services API Reference.

C.5.5 VirtualMachineService

The VirtualMachineService Web service manages virtual machines. You can use this Web service to create and manage virtual machines.

The VirtualMachineService Web service is located at:

http[s]://ovm_manager_host:port/OVSWS/VirtualMachineService.wsdl

The methods available in this Web service are:

- createPropertiesFileOnVirtualMachine

- deleteVMByVMId

- getAllAlertAssociatedWithImg

- getAllOperatingSystemArray

- getAllVMs

- getAssociatedPool

- getAssociatedServer

- getLastAlertAssociatedWithDisk

- getLastAlertAssociatedWithImg

- getRealPath

- getVM

- getVMByName

- getVncPassword

- pauseVMByVMId

- powerOffVMByVMId

- powerOnVMByVMId

- queryCdromArray

- queryLocalDiskInfo

- queryLocalDisks

- queryNetworkInterfaceCardArray

- queryPreferredServer

- queryPreferredServerArray

- querySharedDiskInfo

- querySharedDisks

- querySharedVirtualDiskArray

- queryVMMetricArrayVyVMIds

- queryVMMetricByVMId

- queryVMStatusArrayByVMIds

- queryVMStatusByVMId

- rebootVMByVMId

- resumeVMByVMId

- saveAsTemplate

- saveAsTemplateAsync

- setVMName

- suspendVMByVMId

- unpauseVMByVMId

- unregisterVMByVMId

- update

- uploadVirtualMachine

More detailed information on the functions available in this web service is available in the Oracle VM Manager Web Services API Reference.

C.5.6 AdminService

The AdminService Web service manages users and groups. You can use this Web service to create and manage users and groups.

The AdminService Web service is located at:

http[s]://ovm_manager_host:port/OVSWS/AdminService.wsdl

The methods available in this Web service are:

- createGroup

- createUser

- createUserGroup

- createUserSite

- findAllOVMGroup

- findAllOVMRole

- finalAllOVMUser

- findAllOVMUserGroup

- findAllOVMUserRole

- findAllOVMUserSite

- findUserById

- getOVMVersion

- isAdminUser

- login

- logout

- searchUsers

More detailed information on the functions available in this web service is available in the Oracle VM Manager Web Services API Reference.

D Troubleshooting

This Appendix describes some problems you may encounter when using Oracle VM Manager, and explains how to resolve them. It includes the following topics:

- Log Files

- Cannot Log In to Oracle VM Manager

- Cannot Create a Virtual Machine from Installation Media

- Insufficient Space in Repository for Creating a Virtual Machine

- The Virtual Machine Stuck in a Status

- The Status of the Virtual Machine Is Error

- Cannot Access Virtual Machine Console

- Cannot Perform Live Migration

- Cannot Change CD in the Virtual Machine

- Cannot Import External Resources

- Remote Host Identification Error in Server Pool

Find additional information on the following Oracle support-oriented Web sites:

- Oracle MetaLink, available at http://metalink.oracle.com

- Oracle Virtualization Forum, available at http://forums.oracle.com/forums/forum.jspa?forumID=482

D.1 Log Files

Oracle VM Manager log files are stored in the directory:

/var/log/ovm-manager/

Table D-1, "Log Files" lists the log files it contains.

Table D-1 Log Files

Log File

Description

ovm-manager.log

The Oracle VM Manager installation log.

db.log

The Oracle Database log. When you install Oracle VM Manager on an existing database, the log information is stored here.

oc4j.log

The Oracle Containers for J2EE (OC4J) installation log.

When oc4j.log exceeds 10 MB, a new log file oc4j.log.1. is generated to store the logs in oc4j.log. Subsequently, the oc4j.log is cleared to record new log information.

upgrade_oldversion_newversion.log.log

The Oracle VM Manager upgrading log.

D.2 Cannot Log In to Oracle VM Manager

It may take a very long time to log in, or it is stuck in the Login page. This may be caused by lack of memory for OC4J.

To solve this problem:

1. Log in to the computer where Oracle VM Manager is installed, and run the following command to check the log information:

# cat  /var/log/ovm-manager/oc4j.log | grep "heap"

If OC4J runs out of memory, the following information is displayed:

Internal Exception: java.lang.OutOfMemoryError: Java heap space

2. Run the following command to restart OC4J:

# service oc4j stop
# service oc4j start

If OC4J runs out of memory, you need to increase the OC4J memory size. Follow these steps to do it:

1. View the OC4J configuration information:

# vi /opt/oc4j/bin/oc4j

2. Locate the following line, and increase the memory size to an appropriate value, such as 512:

OC4J_JVM_ARGS="-XX:PermSize=256m -XX:MaxPermSize=512m"

3. Restart OC4J:

# service oc4j stop
# service oc4j start

D.3 Cannot Create a Virtual Machine from Installation Media

The following message is displayed: "Error: There is no server supporting hardware virtualization in the selected server pool."

To solve this problem, make sure the Virtual Machine Server supports hardware virtualization.

Follow these steps to check:

1. Run the following command to check if hardware virtualization is supported by the CPU:

# cat /proc/cpuinfo |grep -E 'vmx|smx'

If any information that contains vmx or smx is displayed, it means that the CPU supports hardware virtualization. Here is an example of the returned message:

flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm

2. Ensure that you have enabled hardware virtualization in the BIOS.

3. Run the following command to check if the operating system supports hardware virtualization:

# xm info |grep hvm

The following is an example of the returned message:

xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x

If the CPU does not support hardware virtualization, use the paravirtualized method to create the virtual machine. See Section 6.3.2, "Creating a Virtual Machine From Installation Media".

D.4 Insufficient Space in Repository for Creating a Virtual Machine

A message similar to the following is displayed: "Error: The largest virtual disk that can be allocated is: 4815 MB."

To solve this problem, decrease the disk size of the virtual machine, or add a new repository. See Oracle VM Server User's Guide for information on creating a storage repository.

D.5 The Virtual Machine Stuck in a Status

For Oracle VM Manager Release 2.1.1 and Release 2.1.2 Users

To solve this problem, set the status to Powered Off, and delete the virtual machine directly. See Section 6.10.2, "Deleting a Stuck Virtual Machine" for more information.

For Oracle VM Manager Release 2.1 Users

To solve this problem, change the status manually as follows:

1. Make sure that the virtual machine in the target server has been shut down. Use xm list or virsh list to check the virtual machine name and ID.

2. If the virtual machine is running, use xm shutdown vm_id or virsh shutdown vm_id to shut it down, where vm_id refers to the virtual machine name or ID.

3. Use xm list or virsh list to check if the virtual machine has been shut down. If it is still running, use xm destroy vm_id, or virsh destroy vm_id to shut it down.

4. Log in as oracle (or root first, then su - oracle) to the computer where Oracle VM Manager is installed, and run the following commands to change the virtual machine status to Powered off in the Oracle XE database:

export ORACLE_HOME='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server'
export ORACLE_SID=XE
$ORACLE_HOME/bin/sqlplus / as sysdba
SQL> update ovs.ovs_vm_img t set t.status='Powered Off' where t.img_name like 'vm_name';
SQL> commit;
SQL> quit

vm_name refers to the virtual machine name.

5. Retry your operation, or delete the virtual machine directly.

For Oracle VM Manager Release 2.2 Users

Reset the virtual machine. See Section 6.4.5, "Resetting a Virtual Machine".

D.6 The Status of the Virtual Machine Is Error

To view more details, click the Virtual Machines tab, and then click the Show link of the virtual machine. Click the number after the Log item to display the error log. The error log information includes: time, log level, target, operation, and message. Alternatively, view the error log in the Administration tab. See Section 7.4, "Viewing Logs".

The following are some error log items and solutions:

- HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS?

- Cannot find host server for vm('/OVS/running_pool/vm_name')

- Could not find '/OVS/running_pool/vm_name' in any storage repository

- /opt/ovs-agent-version/utils/rcp.py /OVS/running_pool/vm_name/ root@example.com:/OVS/running_pool/vm_name password=>encounter 'permission denied'!

- xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Domain 'vm_name' already exists with ID 'number'

- vm('/OVS/running_pool/vm_name') status ('RUNNING') not in ('DOWN', 'ERROR')

- No server selected to run vm('/OVS/running_pool/vm_name') memory=number

- xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Device number (vif) could not be connected. Could not find bridge device null

- No pxe bootable vif found

- virt-install options=>mount: can't get address for host umount: /var/lib/xen/xennfs.mkvX0Q: not mounted ERROR: Unable to mount NFS location!

- winxp_build failed: global name 'xen_handle_vif_qos' is not defined

D.6.1 HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS?

Possible Cause

The Virtual Machine Server does not support hardware virtualization.

Solution

Verify that the Virtual Machine Server supports hardware virtualization, and has hardware virtualization enabled in the BIOS. See Appendix D, "Cannot Create a Virtual Machine from Installation Media".

If the Virtual Machine Server does not support hardware virtualization, you can create the virtual machine from installation media.

D.6.2 Cannot find host server for vm('/OVS/running_pool/vm_name')

Possible Cause

- No Virtual Machine Server available to run the virtual machine.

- Insufficient memory on the Virtual Machine Server.

Solution

1. Make sure at least one Virtual Machine Server is available to run the virtual machine.

2. Make sure the Virtual Machine Server has sufficient memory to run the virtual machine. To release server memory:

- Shut down other running virtual machines.

- Decrease the virtual machine memory, and restart the virtual machine. See Section 6.7, "Editing a Virtual Machine".

D.6.3 Could not find '/OVS/running_pool/vm_name' in any storage repository

Possible Cause

The virtual machine has been removed from the Virtual Machine Server.

Solution

Remove the virtual machine in Oracle VM Manager, and create a new one.

D.6.4 /opt/ovs-agent-version/utils/rcp.py /OVS/running_pool/vm_name/ root@example.com:/OVS/running_pool/vm_name password=>encounter 'permission denied'!

Possible Cause

You have entered an incorrect user name or password when creating the Utility Server.

Solution

Enter correct user name and password for the Utility Server. See Section 3.2, "Creating a Server Pool".

D.6.5 xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Domain 'vm_name' already exists with ID 'number'

Possible Cause

The virtual machine is already started.

Solution

Use the command xm list to check the virtual machine status. Refresh the virtual machine periodically.

D.6.6 vm('/OVS/running_pool/vm_name') status ('RUNNING') not in ('DOWN', 'ERROR')

Possible Cause

The status in Oracle VM Manager has not been synchronized with the status data in the database.

Solution

Shut down the virtual machine, and then restart it.

D.6.7 No server selected to run vm('/OVS/running_pool/vm_name') memory=number

Possible Cause

There is insufficient memory on this Virtual Machine Server.

Solution

Decrease the virtual machine memory, and then restart the virtual machine. Or shut down other running virtual machines to release more memory.

D.6.8 xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Device number (vif) could not be connected. Could not find bridge device null

Possible Cause

No bridge for this virtual machine.

Solution

Select a bridge for the virtual machine. See Section 6.7.2, "Network".

D.6.9 No pxe bootable vif found

Possible Cause

Invalid VIF type for the virtual machine.

Solution

When starting a hardware virtualized machine through PXE, the VIF type must be Fully Virtualized (ioemu). Select a valid VIF type for the virtual machine. See Section 6.7.2, "Network".

D.6.10 virt-install options=>mount: can't get address for host umount: /var/lib/xen/xennfs.mkvX0Q: not mounted ERROR: Unable to mount NFS location!

Possible Cause

The resource location you entered is incorrect.

Solution

Delete the virtual machine, and create a new one. Make sure you enter a correct resource location when creating a paravirtualized machine.

D.6.11 winxp_build failed: global name 'xen_handle_vif_qos' is not defined

Possible Cause

Oracle VM Manager fails to detect the API xen_handle_vif_qos.

Solution

Upgrade both Oracle VM Manager and Oracle VM Server to Release 2.1.2 or above to support this feature.

D.7 Cannot Access Virtual Machine Console

If your operating system is Linux, and you are using Mozilla Firefox to access the virtual machine, download and install the Console Plug-in. See Section 6.5.1, "Installing the Console Plug-In".

If Oracle VM Manager is upgraded from the Release 2.1, rather than a fresh installation, you may encounter the following error when accessing the virtual machine console:

java.lang.ClassNotFoundException: VncViewer.class

This is caused by the delay in cache refresh. To solve this problem, shut down all the Web pages, and open a new one to access the virtual machine console.

D.8 Cannot Perform Live Migration

The following message is displayed: "Error: Server is not ready for live migration."

To solve this problem, you must use identical computers to perform live migration, that is, the computer make and model number must be identical.

D.9 Cannot Change CD in the Virtual Machine

To change the CD in a virtual machine:

1. Unmount the first CD:

# umount mount-point

2. Select the second ISO file, and click Change CD.

3. Mount the second CD:

# mount /dev/cdrom mount-point

D.10 Cannot Import External Resources

Cannot Import Due to Invalid URL

The following information is displayed: "The URL is invalid", or "The proxy URL is invalid".

To solve this problem, log in to the Virtual Machine Server, and run the following command to test the network connection:

# wget url

Here, url refers to the link for downloading the resource.

If the resource is on the Internet, you may need a proxy before running the wget command. Contact your network administrator to get the proxy, an then run the following commands to configure the proxy:

# export http_proxy=http://host:port/
# export ftp_proxy=http://host:port/

Here, host refers to the host name or IP address of the proxy server, and port refers to the port number of the proxy.

Cannot Import Due to NFS Disk

The following information is displayed: "Cannot obtain memory size from vm.cfg."

This error may occur when there are two or more Utility Servers in a server pool, and the disk is shared by the Network File System (NFS) mode.

To solve this problem, click the Next button periodically.

D.11 Remote Host Identification Error in Server Pool

If you reinstall the Oracle VM Server software, or change the root user's password of an Oracle VM Server in a server pool, communication from the server pool to that server may fail.

If you reinstall the Oracle VM Server software (not upgraded), the RSA key is likely to change, even if you use the same IP address and host name. You may see an error similar to:

REMOTE HOST IDENTIFICATION HAS CHANGED

or

Host key verification failed

Workaround: Remove the Oracle VM Server from the server pool, and add the Oracle VM Server again.

E Third Party Licenses

This Appendix includes the Third Party License for all the third-party products included with Oracle VM Manager.

E.1 Apache XML-RPC

Under the terms of the Apache xml-rpc license, Oracle is required to provide the following notices. However, the Oracle program license that accompanied this product determines your right to use the Oracle program, including the Apache software, and the terms contained in the following notices do not change those rights. Notwithstanding anything to the contrary in the Oracle program license, the Apache software is provided by Oracle "AS IS" and without warranty or support of any kind from Oracle or Apache.

E.1.1 Apache XML-RPC Software License

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

5. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

6. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

7. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

8. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

9. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

10. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

E.2 Third-Party Products Included with Sun Microsystems Products

Sun Microsystems has indicated that the following materials may be included in the Java Development Kit and/or JRE materials that are included in the Oracle product. Sun Microsystems currently provides the following notices as part of the Sun distribution:

E.2.1 CS CodeViewer v1.0

Use of any of this software is governed by the terms of the license below:

Copyright 1999 by CoolServlets.com.

Any errors or suggested improvements to this class can be reported as instructed on CoolServlets.com. We hope you enjoy this program... your comments will encourage further development! This software is distributed under the terms of the BSD License. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.      Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2.      Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Neither name of CoolServlets.com nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

"THIS SOFTWARE IS PROVIDED BY COOLSERVLETS.COM AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."

E.2.2 DES and 3xDES

Use of any of this software is governed by the terms of the license below:

"Copyright 2000 by Jef Poskanzer <jef@acme.com>. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.       Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2.       Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."

E.2.3 Crimson v1.1.1

Use of any of this software is governed by the terms of the license below:

The Apache Software License, Version 1.1

Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.       Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2.       Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3.       The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation

http://www.apache.org/

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4.       The names "Crimson" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5.       Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
===========================================================

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc.,

http://www.ibm.com

For more information on the Apache Software Foundation, please see

http://www.apache.org/.

E.2.4 NSIS 1.0j

Use of any of this software is governed by the terms of the license below:

Copyright (C) 1999-2000 Nullsoft, Inc.

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1.       The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2.       Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3.       This notice may not be removed or altered from any source distribution. Justin Frankel justin@nullsoft.com"

E.2.5 Some Portions licensed from IBM

Some Portions licensed from IBM are available at: http://oss.software.ibm.com/icu4j/

E.2.6 Portions Copyright Eastman Kodak Company 1992

E.2.7 Lucida

Lucida is a registered trademark or trademark of Bigelow & Holmes in the U.S. and other countries.

E.2.8 Portions licensed from Taligent, Inc.

E.2.9 Additionally for JRE/JDK 1.5 / 5.0

The following software may be included in this product:

A. IAIK PKCS Wrapper

Use of any of this software is governed by the terms of the license below:

Copyright (c) 2002 Graz University of Technology. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.      Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2.      Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3.      The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by IAIK of Graz University of Technology."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4.      The names "Graz University of Technology" and "IAIK of Graz University of Technology" must not be used to endorse or promote products derived from this software without prior written permission.
5.      Products derived from this software may not be called "IAIK PKCS Wrapper", nor may "IAIK" appear in their name, without prior written permission of Graz University of Technology.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Document Object Model (DOM) v. Level 3

The following software may be included in this product:

W3C SOFTWARE NOTICE AND LICENSE

http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231

This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.

Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications:

1.      The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2.      Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code.
3.      Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
____________________________________

This formulation of W3C's notice and license became active on December 31 2002. This version removes the copyright ownership notice such that this license can be used with materials other than those owned by the W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license, and removes the ambiguous grant of "use". Otherwise, this version is the same as the previous version and is written so as to preserve the Free Software Foundation's assessment of GPL compatibility and OSI's certification under the Open Source Definition. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org.

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

____________________________________
This formulation of W3C's notice and license became active on August 14 1998 so as to improve compatibility with GPL. This version ensures that W3C software licensing terms are no more restrictive than GPL and consequently W3C software may be distributed in GPL packages. See the older formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org.

W3C XML Schema Test Collection v. 1.16.2

Use of any of this software is governed by the terms of the license below:

W3C DOCUMENT NOTICE AND LICENSE

Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.

http://www.w3.org/Consortium/Legal/

Public documents on the W3C site are provided by the copyright holders under the following license. The software or Document Type Definitions (DTDs) associated with W3C specifications are governed by the Software Notice. By using and/or copying this document, or the W3C document from which this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that you use:

1.       A link or URL to the original W3C document.
2.       The pre-existing copyright notice of the original author, or if it doesn't exist, a notice of the form: "Copyright Å0ã5Å0ã5Å0ã5Å0ã5 [$date-of-document] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but a textual representation is permitted.)
3.       If it exists, the STATUS of the W3C document.

When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.

No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional requirements (documented in the Copyright FAQ) are satisfied, the right to create modifications or derivatives is sometimes granted by the W3C to individuals complying with those requirements.

THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders.

----------------------------------------------------------------------------

This formulation of W3C's notice and license became active on April 05 1999 so as to account for the treatment of DTDs, schema's and bindings. See the older formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org. webmaster (last updated by reagle on 1999/04/99.)

Mesa 3-D graphics library v. 5

Use of any of this software is governed by the terms of the license below:

core Mesa code include/GL/gl.h Brian Paul Mesa

GLX driver include/GL/glx.h Brian Paul Mesa

Ext registry include/GL/glext.h SGI SGI Free B

include/GL/glxext.h

Mesa license:

The Mesa distribution consists of several components. Different copyrights and licenses apply to different components. For example, GLUT is copyrighted by Mark Kilgard, some demo programs are copyrighted by SGI, some of the Mesa device drivers are copyrighted by their authors. See below for a list of Mesa's components and the copyright/license for each.

The core Mesa library is licensed according to the terms of the XFree86 copyright (an MIT-style license). This allows integration with the XFree86/DRI project. Unless otherwise stated, the Mesa source code and documentation is licensed as follows:

Copyright (C) 1999-2003 Brian Paul All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL BRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Byte Code Engineering Library (BCEL) v. 5

Use of any of this software is governed by the terms of the license below:

Apache Software License

===========================================================

The Apache Software License, Version 1.1

Copyright (c) 2001 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.       Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2.       Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3.       The end-user documentation included with the redistribution, if any, must include the following acknowledgment:

"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4.       The names "Apache" and "Apache Software Foundation" and "Apache BCEL" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5.       Products derived from this software may not be called "Apache", "Apache BCEL", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

===========================================================
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation.

Regexp, Regular Expression Package v. 1.2

Use of any of this software is governed by the terms of the license below:

Use of any of this software is governed by the terms of Apache Software License, Version 1.1.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org.

CUP Parser Generator for Java v. 0.10k; Use of any of this software is governed by the terms of the license below:

CUP Parser Generator Copyright Notice, License, and Disclaimer

Copyright 1996-1999 by Scott Hudson, Frank Flannery, C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the names of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.

JLex: A Lexical Analyzer Generator for Java v. 1.2.5

Use of any of this software is governed by the terms of the license below:

JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.

Copyright 1996-2003 by Elliot Joel Berk and C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the name of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.

Java is a trademark of Sun Microsystems, Inc. References to the Java programming language in relation to JLex are not meant to imply that Sun endorses this product.

SAX v. 2.0.1

Use of any of this software is governed by the terms of the license below:

Copyright Status

SAX is free!

In fact, it's not possible to own a license to SAX, since it's been placed in the public domain.

No Warranty

Because SAX is released to the public domain, there is no warranty for the design or for the software implementation, to the extent permitted by applicable law. Except when otherwise stated in writing the copyright holders and/or other parties provide SAX "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of SAX is with you.

Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.

In no event unless required by applicable law or agreed to in writing will any copyright holder, or any other party who may modify and/or redistribute SAX, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use SAX (including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the SAX to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.

Copyright Disclaimers

This page includes statements to that effect by David Megginson, who would have been able to claim copyright for the original work.

SAX 1.0

Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of the XML-DEV mailing list, is hereby released into the public domain.

No one owns SAX: you may use it freely in both commercial and non-commercial applications, bundle it with your software distribution, include it on a CD-ROM, list the source code in a book, mirror the documentation at your own web site, or use it in any other way you see fit.

David Megginson, sax@megginson.com

1998-05-11

SAX 2.0

I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.

David Megginson, david@megginson.com

2000-05-05

Cryptix

Use of any of this software is governed by the terms of the license below:

Cryptix General License

Copyright 1995-2003 The Cryptix Foundation Limited. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.       Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2.       Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Glossary

Domain

A configurable set of resources, including memory, virtual CPUs, network devices and disk devices, in which virtual machines run. A domain is granted virtual resources and can be started, stopped and rebooted independently.

See also dom0 and domU.

dom0

An abbreviation for domain zero. The management domain with privileged access to the hardware and device drivers. Dom0 is the first domain started by the Oracle VM Server at boot time. Dom0 has more privileges than domU. It can access the hardware directly and can manage the device drivers for other domains. It can also start new domains.

domU

An unprivileged domain with no direct access to the hardware or device drivers. Each domU is started by Oracle VM Server in dom0. The xm command-line tool is used to interact with each domU.

Guest

A guest operating system that runs within a domain in Oracle VM Server. A guest may be paravirtualized or hardware virtualized. Multiple guests can run on the same Oracle VM Server.

Hardware virtualized machine

A virtual machine with an unmodified guest operating system. It is not recompiled for the virtual environment. There may be substantial performance penalties running as a hardware virtualized guest. Enables Microsoft Windows™ operating system to be run, as well as legacy operating systems. Hardware virtualization is only available on Intel VT or AMD SVM CPUs.

Host computer

The physical computer on which Oracle VM Server is installed.

Hypervisor

The hypervisor, monitor, or Virtual Machine Manager (VMM). It is the only fully privileged entity in the system. It controls only the most basic resources of the system, including CPU and memory usage, privilege checks, and hardware interrupts.

Management domain

See dom0.

Oracle VM Agent

An application installed with Oracle VM Server. It communicates with Oracle VM Manager for management of virtual machines. Oracle VM Manager manages the virtual machines running on Oracle VM Server by communicating with Oracle VM Agent. It contains three components: Server Pool Master, Utility Server, and Virtual Machine Server.

Oracle VM Server

A self-contained virtualization environment designed to provide a lightweight, secure, server-based platform for running virtual machines. Oracle VM Server is based upon an updated version of the Xen hypervisor technology. Includes Oracle VM Agent to enable communication with Oracle VM Manager.

Oracle VM Manager

Provides the user interface, which is a standard ADF (Application Development Framework) web application, to manage Oracle VM Server pools. Manages virtual machine lifecycle, including creating virtual machines from templates or from installation media, deleting, powering off, uploading, deployment and live migration of virtual machines. Manages resources including ISO files, templates and shared virtual disks. Also provides an API via a web service to Oracle VM Server.

Paravirtualized machine

A virtual machine with a kernel that is recompiled to be made aware of the virtual environment. Runs at near native speed, with memory, disk and network access optimized for maximum performance.

Preferred Server

A Virtual Machine Server that provides resources such as memory, CPU, network interface cards (NICs), and disk to the virtual machine. If you select only one Virtual Machine Server as the preferred server, the virtual machine always starts from and runs on this server. If you select multiple preferred servers, each time the virtual machine starts, it runs on the machine with the maximum available resources.

QEMU

Also referred to as qemu-dm, which is the process name. The virtualization process which allows full virtualization of a PC system within another PC system.

Server Pool

Logically an autonomous region that contains one or more physical Oracle VM Servers. Presents a unified view of the storage where the virtual machines reside, and groups the users of these virtual machines into a single community called a group, in which each user is a server pool member.

Server Pool Master

A component of Oracle VM Agent. An application that acts as the contact point to Oracle VM Manager, and to other Oracle VM Agents. Provides virtual machine host load-balancing, and local persistency for Oracle VM Server.

There is only one Server Pool Master in a server pool. A physical server can perform as the Server Pool Master, Utility Server and Virtual Machine Server simultaneously.

Utility Server

A component of Oracle VM Agent. An application that handles I/O intensive operations for virtual machines, server pools and servers, for example, copying, moving and renaming files.

There can be more than one Utility Server in a server pool. A physical server can perform as the Server Pool Master, Utility Server and Virtual Machine Server simultaneously.

vif

A virtual network interface for bridging network interfaces between domUs and dom0. When a domU is started it is assigned a number. This number is used to bridge the network interface from ethn to vifn.0.

Virtual disk

A file or set of files, usually on the host file system although it may also be a remote file system, that appears as a physical disk drive to the guest operating system.

Virtual Machine (VM)

A guest operating system and the associated application software that runs within Oracle VM Server. May be paravirtualized or hardware virtualized machines. Multiple virtual machines can run on the same Oracle VM Server.

Virtual Machine Manager (VMM)

See Hypervisor.

Virtual Machine Server

A component of Oracle VM Agent. An application which runs Oracle VM Server virtual machines. It can start and stop virtual machines, and collect performance data for the host and guest operating systems. Enables communication between the Server Pool Master, Utility Server and Virtual Machine Servers.

There can be more than one Virtual Machine Server in a server pool. A physical server can perform as the Server Pool Master, Utility Server and Virtual Machine Server simultaneously.

Virtual Machine Template

A template of a virtual machine. Contains basic configuration information such as the number of CPUs, memory size, hard disk size, and network interface card (NIC). Create virtual machines based on a virtual machine template using Oracle VM Manager.

VMM

See Virtual Machine Manager (VMM).

Xen™

The Xen hypervisor is a small, lightweight, software virtual machine monitor, for x86-compatible computers. The Xen hypervisor securely executes multiple virtual machines on one physical system. Each virtual machine has its own guest operating system with almost native performance. The Xen hypervisor was originally created by researchers at Cambridge University, and derived from work done on the Linux kernel.

Index

A  C  D  E  G  H  I  L  M  N  O  P  Q  R  S  T  U  V  W  X

A

adding utility or virtual machine servers, 4.1

AdminService, C.5.6

approving ISO files, 5.3.5

approving resources, 5

architecture of Oracle VM Manager, 1.4

C

changing password, 2.2

configurations of virtual machines, 6.7

conversion

Hyper-V images, 5.2

P2V image, 5.2.1.3

P2V template, 5.1.1.3

V2V, 5.2

VMware images, 5.2

XenServer images, 5.2, 5.2

creating groups, 7.3.2

creating server pools, 3.2

creating users, 7.2.1

creating virtual machines, 6.3

D

default account, 7.1

default group, 7.3.1

details of virtual machine, 6.6

dom0, Glossary

Domain, Glossary

domU, Glossary

E

editing groups, 7.3.4

editing server pools, 3.4

editing servers, 4.3, 4.4

editing users, 7.2.3

enhancements, Preface

error log and troubleshooting, D.6

G

groups

adding users, 7.3.3

creating, 7.3.2

deleting, 7.3.5

editing users, 7.3.4

groups advantages, 7.3

Guest, Glossary

Guest operating system, Glossary

H

Hardware virtualized machine, Glossary

high availability

for virtual machines created based on template, 6.3.1

for virtual machines created from installation media, 6.3.2, 6.3.3

overview, 3.5

Host computer, Glossary

Hypervisor, Glossary

I

importing

Oracle VM images, 5.2

vhd images, 5.2

vmdk images, 5.2

importing ISO files, 5.3.1

importing virtual machine templates, 5.1.1

importing virtual machines, 5.2.1

ISO file

searching, 5.3.3

ISO files

approving, 5.3.5, 5.3.5

importing, 5.3.1

reimporting, 5.3.4

status, 5.3.2

ISO files status, 5.3.6

L

LifecycleService, C.5.1

log information and troubleshooting, D.6

logging in to Oracle VM Manager, 2.2

Logs, 7.4

Server, 4.9

Server Pool, 3.8

Virtual Machine, 6.1.4

M

Management domain, Glossary

N

new features, Preface

O

Oracle VM, 1.3, 1.3

Overview, 1.3

Oracle VM Agent, 1.3, Glossary

Oracle VM Manager, 1.3, Glossary

architecture, 1.4

main features, 1.6

user roles, 1.5

Oracle VM Server, Glossary

P

P2V conversion

image, 5.2.1.3

template, 5.1.1.3

Paravirtualized machine, Glossary

Password

Change for Oracle VM Agent, 4.4.2

Change for Utility Server, 4.4.3

PluginService, C.5.3

Preferred Server, Glossary

preferred server, 6.3.1, 6.7.4.2

profile information, 2.2

Q

QEMU, Glossary

QoS, 6.7.3.1

Quality of Service, 6.7.3.1

R

registering users, 2.1

reimporting ISO files, 5.3.4

reimporting virtual machine templates, 5.1.4

reimporting virtual machines, 5.2.4

reset virtual machine, 6.4.5

ResourceService, C.5.2

restarting servers, 4.6

roles changing, 7.2.1

roles of users in Oracle VM Manager, 1.5

S

server log, 4.9

Server Pool, Glossary

server pool configurations, 3.1

server pool log, 3.8

Server Pool Master, Glossary

server pool master, 1.4

server pools

creating, 3.2

server type, 3.2

testing connection, 3.2

deleting, 3.6

how to design, 3.1

restoring, 3.7

searching, 3.3, 4.2

ServerPoolService, C.5.4

servers

adding, 4.1

deleting, 4.8

editing, 4.3, 4.4

restarting, 4.6

shutting down, 4.5

servers concept, 1.4

shared virtual disk

searching, 5.4.3

Shared virtual disks

status, 5.4.2

shared virtual disks

creating, 5.4.1

deleting, 5.4.5

status of virtual machines, 6.1.2

storage, 1.4

T

troubleshooting, D

U

users

changing roles, 7.2.4

creating, 7.2.1

deleting, 7.2.5

editing, 7.2.3

viewing details, 7.2.2

users status, 7.2.3

Utility Server, Glossary

utility server, 1.4

V

vhd image

importing, 5.2

vif, Glossary

Virtual disk, Glossary

Virtual Machine, Glossary

virtual machine

reset, 6.4.5

virtual machine creating

based on virtual machine template, 6.3.1

basic steps, 6.3

from installation media, 6.3.2

PXE boot, 6.3.3

virtual machine image

searching, 5.2.3

virtual machine log, 6.1.4

Virtual Machine Manager, Glossary, Glossary

Virtual Machine Server, Glossary

virtual machine server, 1.4

virtual machine status mechanism, 6.1.2.9

Virtual machine template, Glossary

virtual machine template

searching, 5.1.3

virtual machine templates

approving, 5.1.5

deleting, 5.1.7

editing, 5.1.6

importing, 5.1.1

reimporting, 5.1.4

status, 5.1.2

virtual machine types, 6.1.1

virtual machines

approving, 5.2.5

cloning, 6.8.2

console, 6.5

deleting, 6.10

deleting in certain status, 6.10.2

deploying, 6.8.1

importing, 5.2.1

logs, 6.1.4

pausing and unpausing, 6.4.3

reimporting, 5.2.4

saving as virtual machine template, 6.8.3

shutting down, 6.4.2

starting, 6.4.1

suspending and resuming, 6.4.4

viewing details, 6.1.4

virtual machines configuring, 6.7

virtual machines editing

general information, 6.7.1

network, 6.7.2

preferred server, 6.7.4.2

profile, 6.7.5

storage, 6.7.3

Virtual Network Interface, Glossary

VirtualMachineService, C.5.5

VM, Glossary

VM Server, Glossary

vmdk images

importing, 5.2

VMM, Glossary, Glossary

VNC port, 6.6

W

Wizard to create a server pool, 2.3

X

Xen, Glossary

Xen hypervisor, Glossary

Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved.