Oracle VM, User Manual

Page: 94 / 112

Oracle VM Agent Deployment
D-2 Oracle VM Server User's Guide
D.2 Oracle VM Agent Deployment
Oracle VM’s deployment architecture utilizes server pools, with shared access to
storage across Oracle VM Servers in the server pool. Guest virtual machines are stored
on the shared storage and placed on one of the Oracle VM Servers in one of two ways
to balance the workloads of the server pool:
■
Auto: Selects the Oracle VM Server in the pool with most available resources (for
example, memory) to start the guest virtual machine.
■
Manual: Allows the user to designate a pool of Oracle VM Servers as preferred
servers where the guest virtual machine is allowed to start and run.
Since the guest virtual machines are not bound to any specific physical Oracle VM
Server in the server pool, unless preferred servers are explicitly specified in Oracle VM
Manager, guest virtual machines are not prevented from powering-on simply because
an individual Oracle VM Server happens to be down for maintenance or otherwise
unavailable at the time. Further, since the load-balancing algorithm assures that a
guest virtual machine is placed on the Oracle VM Server with the most resources
available, it also helps assure the maximum aggregate performance from the server
pool.
Oracle VM Manager communicates with Oracle VM Agent to perform the
management of guest virtual machines and Oracle VM Servers in server pools. There
are a number of configuration options you can use when deploying Oracle VM.
■
The Server Pool Master, Utility Server and Virtual Machine Server can be on the
same computer.
■
The Server Pool Master and Utility Server can be on the same computer, and the
Virtual Machine Server can be on another computer.
■
All three Oracle VM Server agent components can be on separate computers.
Figure D–2, "Oracle VM deployment" shows the deployment options for managing
Oracle VM Servers.