Configure and Manage HP Virtual Machines

Configure and Manage HP Virtual
Machines
Lab Guide
Lab Guide
Contents
Introduction.............................................................................................. 3
New features and enhancements.............................................................4
Lab objectives.......................................................................................... 5
Resources................................................................................................. 7
Using the HP Virtual Labs.........................................................................8
What is HPVL?.............................................................................. 8
Verifying prerequisites.......................................................................8
Hardware and software requirements..........................................8
Testing lab access..............................................................................9
Accessing lab equipment...........................................................11
Exiting the lab............................................................................11
Getting help...............................................................................12
Notes for this lab.......................................................................12
Lab — Virtual Machine Overview

Virtual Machine Overview......................................................................13
Objectives........................................................................................ 13
Identifying hardware & software requirements (Host).....................14
System requirements:................................................................14
Integrity VM Host requirements:................................................14
Hardware & software requirements (for each virtual machine).......14
Requirements for each VM:........................................................14
Software:................................................................................... 14
Installing and checking Integrity VM................................................15
Task 1: Installing Integrity VM....................................................15
Task 2: Installation sanity check................................................17
Lab 2 — Resource Management

Resource Management...........................................................................18
Objectives........................................................................................ 18
Managing resources in HPVM...........................................................18
Networking................................................................................18
Mass storage.............................................................................. 18
Memory...................................................................................... 19
CPU............................................................................................ 19
Lab 3 — Virtual Switch

Virtual Switch......................................................................................... 20
Objectives........................................................................................ 20
Creating, starting, shutting down and removing a vswitch..............20
Task 1: Creating a Virtual Switch...............................................20
Task 2: Starting a Virtual Switch................................................21
Task 3: Shutting and removing a vSwitch..................................22
14.21
Configure and Manage HP Virtual Machines Virtual Lab
Lab 4 — Virtual Machine

Virtual Machine...................................................................................... 23
Objectives........................................................................................ 23
Creating and checking the status of a VM........................................23
Task 1: Creating a VM................................................................23
Task 2: Checking the status of VMs............................................24
Lab 5 — Virtual NIC

Virtual NIC.............................................................................................. 25
Objectives........................................................................................ 25
Adding and checking the status of a network device.......................25
Task 1: Adding a virtual network device.....................................25
Task 2: Checking the status of a network device.......................26
Lab 6 — Virtual Storage Device

Virtual Storage Device........................................................................... 27
Objectives........................................................................................ 27
Adding and checking the status of a virtual storage device.............27
Task 1: Adding a virtual storage device.....................................27
Task 2: Checking the status of a storage device........................28
Lab 7 — VM Access
VM Access.............................................................................................. 29
VM Access.............................................................................................. 29
Objectives........................................................................................ 29
Virtual Machine console...................................................................29
Task 1: Starting a VM using the console.....................................29
Task 2: Using Virtual MP shortcuts.............................................30
Lab 8 — Installing an Operating System Using a Virtual DVD

Installing an Operating System Using a Virtual DVD..............................32
Virtual DVD............................................................................................ 32
Objectives........................................................................................ 32
OS Installation on VM – Scenarios....................................................32
Installing an operating system on the VM........................................33
Installing an operating system using virtual DVD............................35
Task 1: Locating and attaching an iso image.............................35
Task 2: Continuing Virtual DVD installation................................37
ii 14.21
Lab Guide
Lab 9 — Virtual Machine Monitoring

Virtual Machine Monitoring....................................................................53
Objectives........................................................................................ 53
Monitoring and using tools in VMs...................................................53
Task 1: Monitoring VMs from the Host........................................54
Task 2: Monitoring VM activity...................................................54
Task 3: Using tools available in a VM.........................................55
Lab 10 — Troubleshooting Issues in a VM

Troubleshooting Issues in a VM..............................................................58
Objectives........................................................................................ 58
Troubleshooting VM issues...............................................................58
Task 1: Troubleshooting VM storage device configuration &
specification problems...............................................................59
Task 2: Troubleshooting VM network device configuration &
specification problems...............................................................61
Task 3: Troubleshooting VM commands in HPVM’s command log
.................................................................................................. 62
Task 4: Troubleshooting the VM monitor log file.........................63
Appendix A....................................................................................... 64
Overview of changes in VMs......................................................64
For further study..............................................................................64
12.41 3
Introduction
HP Integrity Virtual Machines (VM) is a soft partitioning and virtualization
technology that provides operating system isolation, with sub-CPU
allocation granularity and shared I/O. Integrity VM can be installed on an
Integrity server, Integrity server blade, or hardware partition (nPartition)
running HP-UX. The Integrity VM environment consists of following two
types of components:
 VM Host
 Virtual machines (also called guests)
The VM Host virtualizes physical processors, memory, and I/O devices. It
allows you to allocate them as virtual resources to each VM.
VM are abstractions of real, physical machines. The guest operating
system runs on the VM just as it would run on a physical Integrity
server, with no special modification.
Integrity VM provides a small guest software package that aids in local
management of the guest's VM.
14.21 [Module, #], –4

Lab Guide
New features and enhancements

Following new features and enhancements are available in the latest
version of Integrity VM:
 HP-UX 11i v3 VM Host — HP-UX 11i v3 1103
 HP-UX 11i v3 guests — HP-UX 11i v3 1003 through 1103 (all
Integrity servers)
 HP-UX 11i v2 guests — HP-UX 11i v2 0712 to 0806 (all Integrity
servers)
 HP OpenVMS V8.4 guests
 NVRAM Edit Utility — Displays, creates, edits and removes EFI
variables in NVRAM files from a VM Host
 Integrity VM virtual iLO Remote Console — Allows access to the
guest console by logging into a specific IP address
 hpvmhostgdev script utility
 Serviceguard 11.20
 16 virtual CPUs
 128 GB guest memory
 Multiple Accelerated Virtual Input/Output (AVIO) LAN localnet
support — allows the creation of multiple instances of localnet
virtual switches (vswitches)
 Guest VLAN support for AVIO localnet
 256 virtual AVIO storage devices
 hpvmsar enhancements
 Support for NFS guest back stores for root, swap, and dump
 Hyperthreading no longer needs to be turned off in the Integrity VM
Host before installing or using Integrity VM. It is no longer necessary
to specify /usr/sbin/setboot -m off
 Support for Fibre Channel over Ethernet (FCoE) using the next
generation converged infrastructure (CNA) hardware
 Support for networking HBA's AM225A, AM232A, and AM233A
 Support for ID-VSE Logical Server Management 6.2
 Support for HP OpenVMS V8.4 guests
14.21 [Module, #], –5

Lab objectives
After completing the labs, you should be able to:
 Describe Integrity VM overview
 Identify hardware & software requirements for VM Host
 Identify hardware & software requirements for each VM
 Verify Integrity VM installation
 Apply installation sanity check

 Define resource management
 Describe basic networking allocation for a VM
 Identify mass storage entities in a VM
 Define memory resource management
 Outline CPU resource management and planning

 Define a virtual switch
 Understand what are vswitches
 Create a vswitch
 Start a vswitch
 Stop and remove a vswitch

 Define a virtual machine
 Create a virtual machine
 Check status of a virtual machine

 Define a virtual NIC
 Add a virtual network device
 Check the status of network device

 Define a virtual hard disk
 Add a virtual storage device
 Check the status of virtual storage device

 Outline Integrity VM Access
 Start a virtual machine using console
 Apply virtual MP shortcuts
6 14.21
Lab Guide
 Install an operating system using a virtual DVD
 Identify scenarios for operation system installation on a VM
 Attach an ISO image using a virtual DVD
 Apply continuing DVD installation

 Monitor virtual machines
 Monitor virtual machines from the Host
 Monitor virtual machine activity
 Use tools available in a VM

 Troubleshooting Techniques
 Troubleshoot VM storage device configuration & specification

problems
 Troubleshoot VM network device configuration & specification

problems
 Troubleshoot Integrity VM commands in HPVM’s command log
 Troubleshoot the Integrity VM monitor log file
14.21 [Module, #], –7

Resources
You can download the following related documents from Business
Support Center Manuals.
 HP Integrity Virtual Machines 4.3 System Administrator's Guide:
Installation, Configuration, and Administration
 HP Integrity Virtual Machines 4.3: Release Notes
 Ignite-UX Reference
 Ignite-UX Installation Booting White Paper
 Using Ignite-UX with Integrity VM White Paper
 HP-UX Installation and Update Guide
 HP-UX Reference
 Managing Serviceguard
 HP Auto Port Aggregation (APA) Support Guide
 Using HP-UX VLANS
 HP Integrity Virtual Machines Manager 4.1 Software: User Guide
 HP Integrity Virtual Machines Manager 4.1 Software: Release Notes
 HP Insight Dynamics —VSE 6.2: Integrity CMS Installation and
Configuration Guide
 HP Insight Global Workload Manager 6.2 Software: User Guide
 HP Insight Virtualization Manager 6.2 With Logical Server
Management: User Guide
 HP Insight Capacity Advisor 6.2 Software: User Guide
 HP Integrity Essentials Global Workload Manager: Workload
Management for HP Integrity Virtual Machines (a white paper)
The website Business Support Center Manuals also includes technical
papers about using virtual machines.
For a time-limited evaluation version of Integrity VM, search HP Business
Support Center (BSC).
8 14.21
Lab Guide
Using the HP Virtual Labs

What is HPVL?
HPVL provides pools of computers controlled by a reservation system. It
allows you to reserve a computer or group of computers to complete
course labs, or experiment on your own. HPVL installs the appropriate
operating system and application software on your machine. It also
provides you with login information and a set of buttons that connect to
your system.
Systems can be reserved for several days at a time. During the
reservation period, you will have sole access to the setup, and all
changes you make will remain untouched.
The HPVL web site is http://hpvl.usa.hp.com/

There you can find instructions and lists of labs available.
Follow the links to the Internal Program Site and Self-Paced Labs. This
lab has been moved to the External HPVL, so use the External HPVL
Scheduler to make a system reservation. The lab is also available for a
while longer on the Internal HPVL.
Verifying prerequisites
Verify that the PC you are using to access HPVL meets the following
requirements:
Hardware and software requirements

You require any PC with access to the Internet allowing https secured
transactions. The connection can be direct or through your company’s
firewall via a web proxy server.
Supported operating systems

Following are the supported operating systems:
 Windows XP (Home or Professional) SP1 or SP2
Note
Windows patch KB884020 required for XP SP2—available at
http://support.microsoft.com/?id=884020
 Windows 2000
 Windows ME
 Windows 98
Note
14.21 [Module, #], –9

Microsoft Dial-Up Networking 1.4 is required—available at
http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q285189
Supported browsers
Following are the supported browsers:
 Microsoft Internet Explorer 6.x, 7.x, or 8.0 with Java enabled
 Select menu item Tools  Internet Options  Advanced.
 Under Microsoft VIM, the JIT compiler for Virtual machine

enabled check box should be selected.
 Mozilla Firefox 3.x.x with Java enabled
 Select Options  Web Features.
 The Enable Java check box should be selected.
Additional requirements
As an additional requirement:
 You must have network access to the public Internet and specifically
to https://hpvl.usa.hp.com/
If you are behind a firewall (or accessing the Internet via a web
proxy gateway), you have permission to access SSL-protected sites
from outside your Intranet.
 For Windows 7, Windows Vista, and Windows XP operating systems,
local administrative privileges are required to install ActiveX
components. ActiveX components are installed the first time you
connect to the HPVL.
Known incompatibilities
Following are the known incompatibilities:
 Norton Firewall 2003 might be needed to be disabled
Windows XP Service Pack 2 requires Windows patch KB884020. This is
available at http://support.microsoft.com/?id=884020
Testing lab access

You will now verify that you are successfully connected to the HPVL.
1. Use Microsoft Internet Explorer to connect to http://labs.usa.hp.com
2. At the Login screen, enter the student's username and password as
provided to you by your instructor.
10 14.21
Lab Guide
14.21 [Module, #], –11

3. Under the Terminal Servers section, click the HPVL Access link.
4. The F5 Application Access Webtop window displays. Next, a Remote

Desktop Protocol (RDP) session opens which will automatically
display your assigned HPVL labgroup. All lab activities (telnet, RDP
access, web management of lab devices) will take place within the
F5 Application Access Webtop.
5. When Webtop is used for the first time, it will automatically install
the ActiveX networking component on your PC.
Note
For Windows 7, Windows Vista, and Windows XP operating
systems, local administrative privileges are required to install
the software. Non-privileged users then can use the TS Webtop
too. If your login has no administrator rights, you will
encounter an error message like this one: “Sorry, ActiveX
control is required to view this page”.
Note
You may be required to reboot after the installation on
Win95/98/ME and Win NT 4.0 systems. Installation on Win2K
and Win XP computers is completely transparent.
6. You are successfully connected once you see the F5 Application

Access Webtop window. This connection will take 20–60 seconds.
Your course-specific labgroup will be displayed inside an Internet
Explorer browser on your Webtop. Your labgroup might differ from
the one shown below.
7. Select the labgroup and click the assigned labgroup.
12 14.21
Lab Guide
8. Next, you can view the details and other equipment access
information.
Accessing lab equipment

To access the lab equipment, open a Telnet to Host to the system
console of an Integrity server
There are two steps:
 First, you must login to the MP with its username and password.
 Then, to login to the server, choose “Console” menu and then use
your root username and password.
You can also access the server console using VNC to Host button.
Exiting the lab

1. Once you complete the HPVL lab, close any open RDP or iLO
connection windows on your Webtop. Next, open the HPVL lab
window, scroll down to the bottom of the page, and click the Exit
Lab button.
14.21 [Module, #], –13

2. Once you have exited from the lab, close the browser on your
Webtop. This will automatically log you out of the Webtop and leave
the system ready for your next access.
3. Press F5 or click Logout at the top-right to close the window.
Your session is now finished.
Getting help
HPVL Help Desk
To get assistance, please use the form at:
http://hpvl.usa.hp.com/ticket.htm
Notes for this lab

In this lab, you should use the Telnet to Host button to open a telnet
connection and window to the HP-UX system. This will let you enter
commands.
Some exercises may ask you to reboot the system and interrupt the
boot process. For this, you should click Telnet to MP to get to the System
Console.
Caution
Do not copy-paste commands.
14 14.21
Lab Guide
Virtual Machine Overview

Lab 1
Objectives
After completing this lab, you should be able to:
 Identify hardware & software requirements (Host)
 Identify hardware & software requirements (for each virtual
machine)
 Verify Integrity VM installation
 Apply installation sanity check
14.21 [Module, #], –15

Identifying hardware & software

requirements (Host)
System requirements:
 Any Integrity server
 HP-UX 11iv3 March 2013
 Host dedicated to Integrity VM
 Total of Host and all virtual machine requirements
Integrity VM Host requirements:

 750 MB physical memory plus 7.5% of additional physical memory
 Swap space 1.5x physical memory size
 Roughly 16 GB disk space plus guest disk requirements
Hardware & software requirements (for each

virtual machine)
Requirements for each VM:
 Install Integrity VM 4.3 software on a system that is running HP-UX
11i v3.
 You can install Integrity VM on a hard partition (nPar) running HP-UX,
but do not attempt to install Integrity VM on a virtual partition
(vPar). Integrity VM cannot be installed on a system that has HP-UX
Virtual Partitions (vPars) software installed.
 The resources on the VM Host system (such as disks, network
bandwidth, memory, and processing power), are shared by the VM
Host and all the running guests.
 Guests running simultaneously share the remaining memory and
processing power. By default, network devices are also sharable
among guests. Some resources must be made exclusive to the VM
Host, such as the VM Host operating system boot disk.
Software:
 Integrity VM SW (T2767CC)
 Product includes HPUX 11i v3 (0505), Foundation OE for Host system
 VMs run off-the-shelf HPUX 11i v3
 Patch levels required:
PHSS_42973 1.0 HPVM B.04.30 CORE PATCH
16 14.21
Lab Guide
PHSS_42974 1.0 HPVM B.04.30 HPVM-VMSGTK
Installing and checking Integrity VM

Task 1: Installing Integrity VM
To install Integrity VM, perform the following steps:
1. Check for HP-UX Virtual Partitions bundle using the following
command:
# swlist -l bundle | grep OE
9. Use the following command to view or verify currently running HPVM

Host:
# hpvminfo -v
10. Use the following command to find and verify if HPVM bundle is
installed:
# swlist -l bundle | grep T2767CC
11. Use the following command to find and verify if HPVM product
patches are installed:
# swlist -l product | egrep '42973|42974'
12. Alternatively, you can use the bdf command to list the mounted file
systems:
# bdf
14.21 [Module, #], –17

18 14.21
Lab Guide
13. HPVM installation has several dependencies. To install these
dependencies, use the following command.
For example, while installing T2767CC, dependencies have to be
installed.
# swlist -l product -d @
10.99.0.251:/hpvl_depot/ignite/Rel_B.11.31VM43
14. To install dependencies like vmGuestSW, AVIO-HVSD, vmKernel, and

AVIO-HSSN etc., use the following command. These are HP-UX 11i v3
based dependencies of the B.06.20 version.
# swlist -l product | egrep -i 'vmGuestSW|AVIO-HVSD|vmKernel|
AVIO-HSSN'
Note
Because of pre-installed packages, actual installation has not been
shown. The steps show how to check and verify the installed
packages which are needed for HPVM 4.3.
14.21 [Module, #], –19

Task 2: Installation sanity check

To perform sanity checks on the installed packages/bundles, perform the
following steps:
Verify SD installation
1. Use the verify command to verify SD installation.
# swverify T2767CC
2. Use the hpvminfo command to check if any VM is running on the

host. The VMs should now be in /etc/PATH.
# hpvminfo
20 14.21
Lab Guide
Resource Management
Lab 2
Objectives
 Describe basic networking allocation for a virtual machine
 Identify mass storage entities in a virtual machine
 Define memory resource management
 Outline CPU resource management and planning
Managing resources in HPVM

Managing resources in HPVM includes Networking, Mass Storage,
Memory, and CPU.
Networking
 You can allocate virtual network devices or virtual network interface
cards (vNICs) to the guest when you create the guest using the
hpvmcreate command or when you modify an existing guest using
the hpvmmodify command.
 vNICs are added using the same option that is used to add storage
devices, but the format of the argument to the command option is
different. To add a vNIC to a guest, use the following command
option:
-a network:adaptertype:bus,device,mac-addr:vswitch:vswitch-
name:portid:portnumber
 However, before you can allocate a virtual switch (vswitch) to the

guest, you must create a vswitch using the hpvmnet command.
Mass storage
Several entities may be used for virtual SCSI device(s).
 File on the Host – flexible deployment
 Logical Volume – better performance
 Disk (Partition) – best performance, least flexible
 LUN/SAN – flexibility & SAN features
 Any virtual SCSI may be ‘boot disk’
 Independent of target entity it maps to
14.21 [Module, #], –21
 Target entities may not be modified after starting VM
Memory
Memory Resources Management:
 Each VM has physical memory allocated when it starts
 Memory is locked down, and isolated from other VMs on the Host
 Cannot be paged out – paging done by VM
 Nearly all virtual memory access operations performed by VM’s
operating system
 Special memory actions (e.g., TLB miss) assisted by Host
CPU
CPU Resource Management & Planning:
 A VM may have multiple virtual CPUs
 Each VM has a CPU entitlement
 Default is 5% (also the minimum)
 May be specified in increments of 1%

 Each VM is guaranteed access to its entitlement
 Actual allocation may differ from entitlement depending on its
demand and aggregate demand of other VMs
22 14.21
Lab Guide
Virtual Switch
Lab 3
Objectives
After completing this lab, you should be able to create, start, shut down,
and remove a Virtual Switch (vswitch).
Creating, starting, shutting down and

removing a vswitch
For VMs to communicate either with other VMs or outside the VM Host
system, each VM’s virtual network must be associated with a virtual
switch (vswitch). If you start a VM without a vswitch, the virtual machine
has no network communication channel.
A vswitch can be associated with at most one physical NIC.
To view operational Virtual LAN (vLAN) or vswitches on the Host, enter
the following command:
# hpvmnet
Task 1: Creating a Virtual Switch

To allow guests to access network devices, you must create vswitches
on the VM Host. This section describes how to create a vswitch and
verify that it has started.
To create vswitches, use the hpvmnet command.
1. The hpvmnet CLI creates and manages vswitches.
15. To create a vswitch named vswA that is associated with the Integrity
VM Host’s lan0, use the command below:
# hpvmnet –c –S vswA –n 0
Note
14.21 [Module, #], –23

You may get following output : # hpvmnet: The vswitch name
already exists.
Continue to the next command.
24 14.21
Lab Guide
2. The hpvmnet CLI also displays state of vswitches on the Integrity VM
Host.
# hpvmnet
Task 2: Starting a Virtual Switch

Verify that a vswitch has started using the process described below:
1. Once created, you can start the vswitch vswA using the –b option.
# hpvmnet –b –S vswA
16. The vswitch is now running. Use the hpvmnet command to display its
new state along with the MAC address of the physical device.
# hpvmnet
17. Use the following command to scan the LAN:

# lanscan
14.21 [Module, #], –25

Task 3: Shutting and removing a vSwitch

After you have verified that the vswitch is running, using the following
steps you can shut down or remove the vswitch.
1. A vswitch may be shut down/halted using the following command:
# hpvmnet -h -S localnet
18. The vswitch is now halted and not available. Use the hpvmnet
command to confirm:
# hpvmnet
19. The vswitch may be completely deleted if so desired. Use the

following command to delete a vswitch:
# hpvmnet -d -S localnet –F
26 14.21
Lab Guide
Virtual Machine
Lab 4
Objectives
 Create a Virtual Machine (VM)
 Check the status of a VM
Creating and checking the status of a VM

In this section, you will learn about key hpvmcreate, hpvmmodify options.
Following are the commonly used options for hpvmcreate and hpvmmodify:
-P <name> Name of virtual machine (for use with other CLIs)
-a <resdef> Define new resource/device (multiple specifications OK)
-e <alloc> CPU entitlement in percent of physical CPU(s)
-E <alloc> CPU entitlement in clock cycles
-r <bytes> Memory allocation for VM
-c <#CPUs> Number of virtual CPUs for the VM
Task 1: Creating a VM
Use the following command to create a basic VM.
# hpvmcreate –P vm01 –e 17
14.21 [Module, #], –27

Task 2: Checking the status of VMs

1. Once Integrity VM software is installed and running, the VM Host
gets available. Enter the following command to get information
about the status of the guests:
# hpvmstatus
20. Use the following command to examine detailed information for the
new VM:
# hpvmstatus –P vm01
28 14.21
Lab Guide
Virtual NIC
Lab 5
Objectives
After completing this lab, you should be able to add a virtual network
device and check its status.
Adding and checking the status of a network

device
You can define a vNIC for a guest using the hpvmmodify command. For
example, the following command adds a vNIC to the guest named host1.
# hpvmmodify -P host1 -a
network:lan:0,0,0x00306E39F70B:vswitch:clan1
The guest configuration file

/var/opt/hpvm/guests/guestname/vmm_config.current contains an entry
for each guest virtual network device. When the guest is booted
(through the hpvmstart or hpvmconsole command), the guest LAN is
configured as specified in the LAN entry in the guest configuration file.
The localnet vswitch can be used as a local network, and vNICs can be
specified for a guest.
Note
Never modify the guest configuration files directly. Always use
the Integrity VM commands to modify virtual devices and
virtual machines. Failure to follow this procedure can result in
unexpected problems when guests are started.
Task 1: Adding a virtual network device

The following command adds a vNIC to the guest vm01, which can be used
to communicate with any virtual machine connected to the vswA vswitch.
# hpvmmodify –P vm01 –a network:aviolan::vswitch:vswA.
14.21 [Module, #], –29

Task 2: Checking the status of a network device

1. You can display the vswitches and ports on a vswitch used by a guest
using the hpvmstatus command. For example, to display the network
information about the guest named vm01, enter the following
command:
2. Use the following command for LAN scan:

# lanscan
30 14.21
Lab Guide
Virtual Storage Device

Lab 6
Objectives
 Add a virtual storage device
 Check the status of virtual storage device
Adding and checking the status of a virtual

storage device
When you create a virtual machine (VM), you need to specify the virtual
storage devices that the VM uses. Virtual storage devices are backed by
physical devices on the VM Host system (backing stores). The VM Host
system must have sufficient physical storage for the VM Host and for all
of the other VMs.
After you create a VM, you can use the hpvmmodify command to add,
remove, or modify storage devices for the VM. To add a device to an
existing virtual machine, include the -a option as you did with the
hpvmcreate command.
Task 1: Adding a virtual storage device

Add a hard disk to a virtual machine using the following command:
# hpvmmodify -P vm01 -a disk:aviostor::disk:/dev/rdsk/c2t0d0
14.21 [Module, #], –31

Task 2: Checking the status of a storage device

Use the following command to examine the new state of the storage
device:
32 14.21
Lab Guide
VM Access
Lab 7
Objectives
 Start the virtual machine (VM) using the console
 Apply Virtual MP Shortcuts
Virtual Machine console

An Integrity VM virtual machine console is similar in appearance to the
maintenance processor of an Integrity system. Each VM has its own
virtual console from which you can manage the VM and the guest
operating system. The hpvmconsole command connects to the virtual
console of a specified VM.
If you have logged into the physical console of a VM Host and has run
hpvmconsole interactively, then:
 To return to the physical console, press Ctrl+B.
 To return to the virtual console main menu, press Ctrl+X.
Task 1: Starting a VM using the console

Use the hpvmconsole command when accessing the VM console from the
host (Integrity VM Host) console – Control characters (e.g., ^B) will be
caught by the host console:
# hpvmconsole –P vm01
14.21 [Module, #], –33

Task 2: Using Virtual MP shortcuts

1. Shortcut 1: Use the PC command for system power control. It can be
issued directly from the CM and vMP level as well.
# PC
2. Shortcut 2: The Enter menu item or [Q] to Quit option allows you to
start the server. Type ON to start the server/VM.
3. Shortcut 3: For confirming the powering up of the system, type Y for

the System will be powered on. Confirm? (Y/N) option.
34 14.21
Lab Guide
14.21 [Module, #], –35

4. Shortcut 4: To return to the vMP main menu, use Ctrl+B.
36 14.21
Lab Guide
Installing an Operating System Using a

Virtual DVD
Lab 8
Objectives
 Identify scenarios for operating system installation on a virtual
machine (VM)
 Attach an ISO image using a virtual DVD
 Apply continuing DVD installation
OS Installation on VM – Scenarios
Scenarios vary based on installation sources:
1. Ignite-UX Server
21. Virtual DVD (iso file)
22. Virtual DVD (physical DVD)
Now that you have some background, you can now go through the guest
operating system installation for virtual DVD (iso file) scenario.
14.21 [Module, #], –37

Installing an operating system on the VM

You can install either HP-UX 11i v2 operating system or the HP-UX 11i v3
operating system as a guest OS.
See the table below for the list of supported versions of the HP-UX
operating system.
Type of Integrity VM Integrity VM Integrity Integrity Integrity
Guest OS Version Version VM B.04.20 VM VM B.04.30
Support A.03.50 B.04.10 B.04.20.05
HP-UX 11i v2
HP Integrity HP-UX 11i v2 HP-UX 11i v2 HP-UX 11i HP-UX 11i HP-UX 11i
Servers May 2005 September v2 v2 v2
through 2006 December December December
December through 2007 2007 2007
2007 December
2007
HP Integrity HP-UX 11i v2 HP-UX 11i v2 HP-UX 11i HP-UX 11i HP-UX 11i
server May 2005 September v2 v2 v2
blades through 2006 December December December
December through 2007 2007 2007
2007 December
2007
HP Integrity Not Not HP-UX 11i HP-UX 11i HP-UX 11i
server supported supported v2 v2 v2
blades (i2– December December December
based)1 20072 2007 2007
HP Integrity Not Not Not HP-UX 11i HP-UX 11i
Superdome supported supported supported v2 v2
21 December December
2007 2007
rx2800 i2 supported supported supported v2 v2
Servers December December
2007 2007
HP-UX 11i v3
HP Integrity HP-UX 11i v3 HP-UX 11i HP-UX 11i HP-UX 11i HP-UX 11i
Servers March 2007 v3 March v3 v3 March v3 March
through 2007 September 2008 2010
September through 2007 through through
2008 September through Septembe Septembe
2009 March r 2010 r 2011
2010
HP Integrity Not HP-UX 11i HP-UX 11i HP-UX 11i HP-UX 11i
server supported v3 March v3 v3 March v3 March
blades 2007 September 2008 2010
through 2007 through through
September through Septembe Septembe
38 14.21
Lab Guide
2009 March r 2010 r 2011
2010
14.21 [Module, #], –39

HP Integrity Not Not HP-UX 11i HP-UX 11i HP-UX 11i
server supported supported v3 March v3 March v3 March
blades (i2– 2009 2009 2010
based)1 through through through
March Septembe Septembe
20102 r 2010 r 2011
Superdome supported supported supported v3 v3 March
21 Septembe 2010
r 2010 through
Septembe
r 2011
rx2800 i2 supported supported supported v3 v3 March
Servers Septembe 2010
r 2010 through
Septembe
r 2011
1
Support for the latest Intel® Itanium® Processor 9300 series
2
Requires V4.2 with the following VM Host patches:
PHSS_40875 1.0 HPVM B.04.20 CORE PATCH
PHSS_40876 1.0 HPVM B.04.20 VMAGENT
PHSS_40901 1.0 HPVM B.04.20 VMMIGRATE PATCH
40 14.21
Lab Guide
Installing an operating system using virtual

DVD
Virtual DVD is added to a VM in the same way as virtual hard drive.
Virtual DVD is specified in two basic ways:
 Using ISO image as target
 Using physical DVD drive as target
Following are few examples of virtual device specification using
hpvmmodify, hpvmcreate, or hpvmclone.
 Virtual DVD mapped to physical DVD:

-a dvd:scsi::disk:/dev/rdsk/c0t0d0
 Virtual DVD mapped to file:

-a dvd:scsi::file:/wherever/hpux_11.31.iso
 Virtual disk mapped to file:

-a disk:scsi::file:/hpvm/storage/VHDA
 Virtual disk mapped to physical disk, LUN:

-a disk:scsi::disk:/dev/rdsk/c0t0d0
 Virtual disk, with virtual bus (0), dev(1), target(2) explicitly specified
and mapped to logical volume:
-a disk:scsi:0,1,2:lv:/dev/vg01/rlvol2
Note
Target storage must not be modified on host or the store
system while the VM is on.
Task 1: Locating and attaching an iso image
A Virtual File DVD is an emulated SCSI DVD with virtual media that
comes from a VM Host ISO file. The VM Host ISO file is specified using
the absolute pathname to the ISO file. The file can be on a VxFS file
systems locally mounted on the VM Host.
To locate and attach an iso image, perform the following steps:
1. Use the ls command to view files and directories:
# ls
14.21 [Module, #], –41

2. To change the directory, use the cd command:
# cd /ISO_IMAGES/
3. Use the ls command to view files and directories in the iso images:
# ls
23. Use the hpvmmodify command to attach a virtual DVD:

# hpvmmodify –P vm01 –a
dvd:avio_stor::file:/ISO_IMAGES/B.11.31.iso
24. To check the status of the VM, use the following command:
#hpvmstatus –P vm01
Note
42 14.21
Lab Guide
Defining virtual DVD using physical DVD option is not
available.
14.21 [Module, #], –43

Task 2: Continuing Virtual DVD installation

To install the HP-UX operating system on the VM, follow this procedure:
1. To boot the guest from the virtual console, enter the following
command:
# hpvmconsole –P vm01
2. In response to the virtual machine prompt, enter the pc command.
Note
If virtual machine is already ON, you need to reboot it using
reset command or using PC-> OFF -> y and pressing Enter in
Console menu.
3. To switch on the VM, enter on for the Enter menu item or [Q] to Quit
option.
4. To power up the system, enter Y for the System will be powered on.
Confirm? (Y/N) option.
44 14.21
Lab Guide
14.21 [Module, #], –45

5. To enter the EFI shell, enter the co command at the VM console
prompt and press Enter.
# co
6. In the Please select a boot option, select EFI Shell [Built-in]. The
details are displayed.
Note
Use ^ and v to change the option(s). Press Enter to select an
option.
Note
If the above screen comes after starting the Virtual Machine
without interruption, then skip step 7 to 9.
7. Enter the cls command to clear the screen:

# cls
46 14.21
Lab Guide
14.21 [Module, #], –47

8. In the displayed Shell prompt, enter fs1: to enter file system 1.
9. Next, type install.efi and press Enter to start the booting process.
The processing screens are displayed.
10.Once the booting process is completed, you will need to change the
terminal window dimensions as suggested to 80x24.
48 14.21
Lab Guide
14.21 [Module, #], –49

11.To change the terminal window dimensions, right-click your mouse
on the CLI window and click Properties.
12.The following window is displayed. Change the window size width

and height as suggested or as per your comfort and click OK.
50 14.21
Lab Guide
13.In the HP-UX installation menu, select Install HP-UX and press Enter
to continue with the typical HP-UX installation process.
14.The User Interface and Media Options screen is displayed. Select OK

and press Enter.
15.The Basic tab is displayed by default in the loaded screen.
14.21 [Module, #], –51

16.Click the Configuration drop-down menu and select HP-UX Data
Center Operating Environment. Select Go and press Enter.
17.The itool Confirmation screen appears. Select the appropriate virtual

storage if you see multiple storage devices. Next, select Go and
press Enter.
52 14.21
Lab Guide
18.The Configuration screen loads with the relevant details displayed in
the correct sequence.
14.21 [Module, #], –53

54 14.21
Lab Guide
19.Once the configuration is completed, the Installation screen displays
details of the installation packages.
14.21 [Module, #], –55

20.The completed Installation packages screen is displayed.
21.The Booting screen appears displaying details of VM reboot in the

process of installation.
56 14.21
Lab Guide
22.Once the VM is re-booted, the operating system installation is
completed and displayed.
23.The Welcome to HP-UX screen appears. For Are you ready to link this
system to a network, type n and press Enter.
24.The DHCP (Dynamic Host Configuration Protocol) screen is displayed.

For the Do you wish to use DHCP to obtain networking information?
option, type y and press Enter.
14.21 [Module, #], –57

58 14.21
Lab Guide
25.Next, the System name screen appears. Type the system name and
press Enter.
26.The confirmation screen is displayed. Type y and press Enter.
27.Next, the time zone enabler screen is displayed. For the Enter the
number for your location <1-7> then press [Enter] option, select
your preferred time zone and press Enter.
14.21 [Module, #], –59

60 14.21
Lab Guide
28.In the Select your time zone from the following list: option, select
accordingly, type y, and press Enter.
29.Once you have selected your preference, type y and press Enter in
the displayed screen.
30.In the next screen, type y to set the root password and then press
Enter.
31.Next, type your selected password and re-enter for verification. Next,
press Enter.
32.For networking to operate correctly, you must assign the system a

unique Internet Protocol (IP) address. Select the default IP in the
displayed screen and press Enter.
14.21 [Module, #], –61

62 14.21
Lab Guide
33.In the confirmation screen, type y and press Enter.
34.To maintain the default subnetwork mask, simply press Enter.
35.Next, set the local language by typing the number assigned to your
preferred language and press Enter.
36.Select your preference from the displayed options by typing the

number assigned to your preferred option and press Enter.
14.21 [Module, #], –63

64 14.21
Lab Guide
37.Next, simply press Enter to continue.
38.Your system is now configured as a standalone system with the

system name you have selected. Press Enter to continue.
39.The Console Login screen is displayed with the system readiness

message, The system is ready.
14.21 [Module, #], –65

40.Finally, the System Login and password screen is displayed. You are
ready to begin.
66 14.21
Lab Guide
Virtual Machine Monitoring

Lab 9
Objectives
 Monitor virtual machines (VMs) from the Host
 Monitor VM activity
 Use tools available in a VM
Monitoring and using tools in VMs

Since each VM is manifested as a UNIX process running on the VM Host,
the physical resources – including CPU, I/O, etc. – consumed by a given
VM can be identified by monitoring the process associated with that VM.
These processes have the executable name hpvmapp and typically have
the option –d whose argument name is the name of the VM. For
example, the process with command hpvmapp –d vm01 corresponds to
the virtual machine named ‘vm01.’
Simple tools such as ps and top can be used on the VM Host to monitor
a VM by identifying the process ID for a given VM. For example, the PID
for some VM can be identified from the output of ps –fu root | grep
hpvmap and then used with top to identify the resources being consumed
by that VM. Use any system monitoring tool you prefer.
14.21 [Module, #], –67

Task 1: Monitoring VMs from the Host

For generically monitoring a process enter the following command:
# ps -fu root
Task 2: Monitoring VM activity

For details on current CPU utilization, use the following command:
# hpvmstatus -r
68 14.21
Lab Guide
Task 3: Using tools available in a VM

Integrity VM provides tools (HPVM-Guest bundle) to be used in a VM.
Use the following commands to use the provided tools:
1. To enter into the console mode, use the following command:
#hpvmconsole –P vm01
2. You can use the -C option to change the physical network interface
card (pNIC) the guest has in use. To login to the VM and examine the
output, use the following command:
# lanscan
3. Use the following command to identify a disk that is at least as large

as the existing boot disk:
# ioscan –funC disk
4. Use the command getconf to see the machine configuration.

# getconf MACHINE_MODEL
5. Use the following command to see machine model number:

# mode1
14.21 [Module, #], –69

70 14.21
Lab Guide
6. Use the following command to see the CPU utilization:
# top
7. Use the foolowing command to view and monitor log file:

# cat var/opt/hpvm/common/hpvm_mon_log
14.21 [Module, #], –71

8. Use the following command to increase or decrease the log file:
# vi /etc/rc.config.d/hpvmconf
9. After you make this change to the hpvmconf file, enter the following
commands to determine the PID for the monitor log daemon and to
kill it:
# cat /var/run/hpvmmonlogd.pid
# kill -HUP 5052
72 14.21
Lab Guide
Troubleshooting Issues in a VM
Lab10
Objectives
 Troubleshoot virtual machine (VM) storage device configuration &
specification problems
 Troubleshoot VM network device configuration & specification
problems
 Troubleshoot VM commands in HPVM’s command log
 Troubleshoot the VM monitor log file
Troubleshooting VM issues
The Integrity VM V4.3 release supports the use of both legacy and agile
devices in guests. It is not necessary to convert guests to use strictly
agile devices. If, however, problems occur with guests using multipath
solutions that are based on legacy devices, change the backing device
to use the equivalent agile device. Make sure there are no
incompatibilities at this time.
You can use the hpvmcollect command on the VM Host or on the guest
to collect Integrity VM information that is useful in analyzing system
problems. The options available for the hpvmcollect command on the
VM Host are different from those available on guests.
The hpvmcollect command creates a directory called
hpvmcollect_archive in your current directory (if it does not already
exist) and then collects information about the VM Host crash dump. The
information is then put into a tar file format (if there is a crash dump) or
tar.gz file format (if there is no crash dump). Do not modify the guest
configuration before running the hpvmcollect command.
The table below describes the options for the hpvmcollect command on
the VM Host.
Option Description
-P vm-name Specifies the virtual machine name, where vm-name is
the name of the virtual machine.
-p vm-number Specifies the virtual machine number, where vm-number
is the number of the virtual machine.
-s host Specifies a host name to receive the archive, which is
14.21 [Module, #], –73

copied using the scp command. Verify that you can log
into the host without a password.
-n crash-dump Specifies the number of crash dumps to copy to the
archive. By default, the hpvmcollect command copies
the latest crash dump directory (based on the bounds
file). This option can be used only with the -c option.
-d dir Specifies a target directory in which to create the
hpvmcollect_archive directory.
-b report-number Specifies the archive name with the specified label. If an

archive with the same name exists, it is renamed by
appending a time stamp to the original name before the
new archive is created.
Task 1: Troubleshooting VM storage device configuration

& specification problems
To troubleshoot issues relating to VM storage device configuration &
specifications, perform the following steps:
1. By default, the hpvmcollect command creates a directory called
hpvmcollect_archive in your current directory, and copies and
collects all the Integrity VM and VM Host information. For example, to
gather information for a guest named host1 on the VM Host, enter
the following command:
# hpvmcollect –P vm01
74 14.21
Lab Guide
14.21 [Module, #], –75

2. When you create a VM and attach backing storage path, virtual disk
devices will be defined even if they don’t exist. An error message will
be displayed if there is an error (e.g., a typo in the path). The
following command creates a VM with attached backing storage
path:
# hpvmcreate –P bogusvm –a disk:aviostor::file:/bogus-path
3. Virtual disk devices defined with storage that does not exist, may not
start. Use the following command to view status of such devices.
# hpvmstart –P bogusvm
76 14.21
Lab Guide
Task 2: Troubleshooting VM network device

configuration & specification problems
1. When you create a VM and attach a virtual switch, virtual network
devices will be defined even if they don’t exist. An error message will
be displayed if there is an error (e.g., a typo in the path). The
following command creates a VM with attached networking path.
# hpvmcreate –P bogusvm1 –a network:aviolan::vswitch:vswitch1
2. Virtual machines with disabled or non-existent virtual switches will

start (and HP-UX will boot just as with disabled NIC, just slowly). Use
the following command to view status of such devices:
# hpvmstart –P bogusvm1
14.21 [Module, #], –77

Task 3: Troubleshooting VM commands in HPVM’s

command log
To troubleshoot issues relating to VM commands in HPVM’s command
log, perform the following steps.
1. Use the following command to see log files:
# vi /var/opt/hpvm/guests/bogusvm1/log
78 14.21
Lab Guide
Task 4: Troubleshooting the VM monitor log file

To troubleshoot issues related to VM commands in HPVM’s command
log, perform the following steps:
1. Use the following command to see VM monitor log files:
# vi /var/opt/hpvm/common/hpvm_non_log
14.21 [Module, #], –79

Appendix A
Overview of changes in VMs
The following list contains changes in support in future releases of
Integrity VM:
 VIO is deprecated in v4.3.
 VIO support is deprecated in v4.3 and will be dropped in the next
major release of Integrity VM, so you should begin planning to
convert from VIO to AVIO at your earliest opportunity.
 To determine if your VMs are using VIO, run hpvmstatus -d for all
your guests. Look for storage devices that use scsi and look for
network devices that use LAN:
# hpvmstatus -P guestname -d | grep -w scsi
# hpvmstatus -P guestname -d | grep -w lan
 Use of hpvmupgrade and p2vassist commands is deprecated starting

in V4.3 and will be dropped in the next Integrity VM release.
 Integrity VM V4.3 does not support Microsoft Windows and Linux
guests. Version 4.2.5 was the last version to support Microsoft
Windows and Linux guests. For information about V4.2.5 support,
see the HP Integrity Virtual Machines 4.2.5: Release Notes on the
BSC website at: http://www.hp.com/go/hpux-hpvm-docs
 Use of legacy device special files (DSFs) to define virtual storage is
deprecated starting in Version 4.3.
 Support for the use of legacy DSFs to define virtual storage
(including virtual disks and DVDs) are deprecated. Customers should
begin planning to use persistent (agile) DSFs when defining their
virtual storage devices. HP recommends the use of persistent DSFs
(for example, those with pathnames such as /dev/rdisk/disk##) for
better storage availability and reliability.
 To check about the use of legacy DSFs, use the following command:
# hpvmstatus -P guestname -d | grep -w rdsk
For further study

Now that you have become familiar with the basic commands and
functions of a VM, feel free to review the man pages and experiment with
other command options.
80 14.21
Lab Guide
14.21 [Module, #], –81

Configure and Manage HP Virtual Machines

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Configure and Manage HP Virtual Machines

Transféré par

Droits d'auteur :

Formats disponibles

Configure and Manage HP Virtual

Lab — Virtual Machine Overview

Lab 2 — Resource Management

Lab 3 — Virtual Switch

Lab 4 — Virtual Machine

Lab 5 — Virtual NIC

Lab 6 — Virtual Storage Device

Lab 8 — Installing an Operating System Using a Virtual DVD

Lab 9 — Virtual Machine Monitoring

Lab 10 — Troubleshooting Issues in a VM

14.21 [Module, #], –4

New features and enhancements

14.21 [Module, #], –5

 Identify hardware & software requirements for VM Host

 Identify hardware & software requirements for each VM

 Verify Integrity VM installation

 Apply installation sanity check

 Describe basic networking allocation for a VM

 Identify mass storage entities in a VM

 Define memory resource management

 Outline CPU resource management and planning

 Understand what are vswitches

 Stop and remove a vswitch

 Create a virtual machine

 Check status of a virtual machine

 Add a virtual network device

 Check the status of network device

 Add a virtual storage device

 Check the status of virtual storage device

 Start a virtual machine using console

 Apply virtual MP shortcuts

 Identify scenarios for operation system installation on a VM

 Attach an ISO image using a virtual DVD

 Apply continuing DVD installation

 Monitor virtual machines from the Host

 Monitor virtual machine activity

 Use tools available in a VM

 Troubleshoot VM storage device configuration & specification

 Troubleshoot VM network device configuration & specification

 Troubleshoot Integrity VM commands in HPVM’s command log

 Troubleshoot the Integrity VM monitor log file

14.21 [Module, #], –7

Using the HP Virtual Labs

The HPVL web site is http://hpvl.usa.hp.com/

Hardware and software requirements

Supported operating systems

14.21 [Module, #], –9

 Select menu item Tools  Internet Options  Advanced.

 Under Microsoft VIM, the JIT compiler for Virtual machine

 Select Options  Web Features.

 The Enable Java check box should be selected.

Testing lab access

14.21 [Module, #], –11

4. The F5 Application Access Webtop window displays. Next, a Remote

6. You are successfully connected once you see the F5 Application

Accessing lab equipment

Exiting the lab

14.21 [Module, #], –13

3. Press F5 or click Logout at the top-right to close the window.

Your session is now finished.

Notes for this lab

Virtual Machine Overview

14.21 [Module, #], –15