Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Integrity Virtual Machines Installation, Configuration, and Administration > Chapter 2 Planning Your Virtual Machines

Allocating Resources to Guests

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

The way you allocate the physical resources to the guests determines the ultimate success of your configuration. For both performance and safety, spread the workload across devices. The VM Host reads the guest configuration from the guest configuration file at /var/opt/hpvm/guests/guestname. You can check the current configuration against your plans, adjusting the configuration for better performance and easier management.

The guests must all share the same physical system with the VM Host. Therefore, it is useful to look at the resource requirements of all guests that will be running at the same time. Table 2–3 lists the types of information you need in order to create a guest, with space to enter your own guest information. Use the information from Table 2–1, VM Host System Resources Information to help you assess the resource requirements for your Integrity VM environment.

Table 2-3 Guest Planning Worksheet

Guest name 
Operating system 
Virtual CPUs 
CPU entitlement 
Memory 
Network adapters 
Network device hardware address 
IP address 
Vswitch name 
Boot device 
Startup behavior 
Admin account name 
Applications 
Application (virtual) storage device 
Virtual storage device hardware address 
Physical backing store 

 

Note that this table reflects Table 2–2. Use the information from Table 2–2 to help you fill out your planning worksheet for each guest.

The following sections present three example guests designed to run on the VM Host named compass, which is presented in Table 2-1. The three example guests are:

  • compass1, a software distribution server with high network and disk storage requirements.

  • compass2, a research and development system. For security purposes, it can access only the local network. This guest is a heavy CPU and memory user.

  • compass3, an operations server. It has high disk-storage requirements, requires network access, and has regular spikes of high CPU and memory usage.

In the following sections, each guest is added to the planning chart, allowing you to assess the total requirements of all the guests running at the same time on the same VM Host system.

The Distribution Server (compass1)

The first example guest, compass1, has one virtual CPU, two virtual network devices, one of which is a dedicated network device. This distribution server requires both virtual disk storage (a logical volume) and a virtual DVD storage device. Table 2-4 shows the planning worksheet with the data for the first guest included.

Table 2-4 Planning Worksheet for compass1

Guest namecompass1  
Operating systemHP-UX 11i v2 May 2005  
Virtual CPUs1  
CPU entitlement5%  
Memory1 GB  
Network adapters2  
Network device hardware addresslan(0,1)  
IP addressDHCP served  
Vswitch nameclan1 (shared)

clan2

(dedicated)
  
Boot device/dev/rdsk/c0t1d0  
Startup behaviorautomatic  
Admin account nameguest1  
ApplicationsOracle 10g  
Application (virtual) storage devicedisk (/dev/rdsk/c1t1d0)

DVD

  
Virtual storage device hardware address

disk: default hardware address

DVD:

PCI bus: 0

PCI slot: 0

SCSI target: 1

  
Physical backing storedisk: /dev/vg01/rlv022

DVD: /null:/root

  

 

If the guest runs multiple applications with specific requirements for virtual devices, you might need to expand this chart.

The R&D System (compass2)

Information about the second guest, compass2, is entered into the next blank column in the worksheet, as shown in Table 2–5. This guest is a research and development system. It runs a multiprocessing operating system and has large memory requirements. It is a highly secure environment, and network usage is restricted to local machines. This virtual machine is an isolated environment for patching, upgrading, and testing software changes.

Table 2-5 Planning Worksheet for compass2

Guest namecompass1compass2 
Operating systemHP-UX 11i v2 May 2005HP-UX 11i v2 May 2005 
Virtual CPUs12 
CPU entitlement5%50% 
Memory1 GB5 GB 
Network adapters21 
Network device hardware addresslan(0,1)none 
IP addressDHCP servednone 
Vswitch nameclan1 (shared)

clan2

(dedicated)
localnet 
Boot device/dev/rdsk/c0t1d0/dev/rsk/c0t2d0 
Startup behaviorautomaticmanual 
Admin account nameguest1guest2 
ApplicationsOracle 9C++ 
Application (virtual) storage devicedisk (/dev/rdsk/c1t1d0)

DVD

disk (/dev/rdsk/c1t2d0) 
Virtual storage device hardware address

disk: default hardware address

DVD:

PCI bus: 0

PCI slot: 0

SCSI target: 1

disk: default hardware address 
Physical backing storedisk: /dev/vg01/rlv022

DVD: /null:/root

disk:/dev/vg02/rlv023 

 

Make sure that dedicated virtual devices (like the boot disk) are not the same on any other guests, and that the number of virtual CPUs and the amount of memory you specify do not exceed the amount that is available on the VM Host system when the guest is created. Note that the storage device for the compass2 guest is different from the compass1 guest, making it easier to manage the VM Host system when both guests are running at the same time, as well as providing a balanced workload.

The Operations Server (compass3)

The third guest, compass3, is the system used by management and corporate operations. The application demands on this virtual machine vary greatly and the resource demands spike frequently. Network access is required and there are high I/O performance requirements. Table 2–6 shows the information for compass3 in the last column of the worksheet.

Table 2-6 Planning Worksheet for compass3

Guest namecompass1compass2compass3
Operating systemHP-UX 11i v2 May 2005HP-UX 11i v2 May 2005 UpdateHP-UX 11i v2 May 2005
Virtual CPUs121
CPU entitlement5%50%5%
Memory1 GB3 GB2GB
Network adapters211
Network device hardware addresslan(0,1)nonelan(0,1)
IP addressDHCPnone17.22.3.6
Startup behaviorautomaticmanualautomatic
Vswitch nameclan1 (shared)

clan2

(dedicated)
localnetclan1 (shared)
Boot device/dev/rdsk/c0t01d0/dev/rdsk/c0t2d0/dev/rdsk/c0t3d0
Startup behaviorautomaticmanualautomatic
Admin account nameguest1guest2guest3
ApplicationsOracle 9C++DeskMgr
Application (virtual) storage devicedisk: /dev/rdsk/c1t1d0

dvd

disk: /dev/rdsk/c1t2d0disk: /dev/rdsk/c1t3d0
Virtual storage device hardware address

disk: default hardware address

DVD:

PCI bus: 0

PCI slot: 0

SCSI target: 1

disk: default hardware addressdisk: default hardware address
Physical backing storedisk: /dev/vg01/rlv022

DVD: /null:/root

disk: /dev/vg02/rlv023disk: /dev/vg03/rlv024

 

The planning worksheet now shows all three guests side by side. Use the parameters from the VM Host system (Table 2–1) and those you record in the guest planning worksheet (Table 2–6) to assess the total requirements of the guests on the system. Total memory and disk space requirements include the guest requirements and the VM Host requirements. For more information about the total memory and disk space requirements, refer to “Installation Requirements” in Chapter 3.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2005 Hewlett-Packard Development Company, L.P.