HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration HP Part Number: T2767-90206 Published: March 2010, Edition 8.
© Copyright 2010 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.......................................................................................................13 Intended Audience................................................................................................................................13 New and Changed Information in This Edition...................................................................................13 Typographic Conventions.....................................................................
3 Creating Virtual Machines..........................................................................................43 3.1 Legacy and Agile Device Names.....................................................................................................43 3.2 Specifying Virtual Machine Characteristics....................................................................................44 3.2.1 Virtual Machine Name................................................................................................
6.1.3 Linux Guest Installation Media...............................................................................................82 6.2 Installing Red Hat Enterprise Linux Guests from ISO Images.......................................................82 6.3 Installing Red Hat Enterprise Linux Guests from a Boot Disk and Network Server.....................86 6.4 Installing SUSE Linux Guests from ISO Images.............................................................................88 6.
7.3.1 Integrity VM Storage Roles...................................................................................................119 7.3.1.1 VM Host Administrator................................................................................................119 7.3.1.2 Guest Administrator......................................................................................................119 7.3.1.3 Guest User.................................................................................................
9.7.3 Troubleshooting Dynamic Memory Problems......................................................................156 9.7.3.1 Dynamic Memory Restrictions......................................................................................157 9.7.3.2 VM Host Resource Considerations...............................................................................157 9.7.3.3 Guest Resource Considerations.....................................................................................157 9.7.3.
10.5.1 Requirements for Migrating a Workload............................................................................182 10.5.2 Using the p2vassist Utility...................................................................................................182 10.5.3 Troubleshooting P2V Problems...........................................................................................186 11 Using HP Serviceguard with Integrity VM.............................................................187 11.
hpvmclone(1M)...................................................................................................................................222 hpvmcollect(1M).................................................................................................................................229 hpvmconsole(1M)...............................................................................................................................233 hpvmcreate(1M)........................................................
List of Figures 1-1 2-1 7-1 7-2 7-3 7-4 7-5 8-1 8-2 9-1 10-1 10-2 11-1 11-2 11-3 11-4 10 Hardware Consolidation Using Integrity VM..............................................................................17 Upgrade Procedure.......................................................................................................................32 Integrity VM Storage I/O Stack...................................................................................................
List of Tables 1 2 1-1 2-1 2-2 2-3 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 6-1 6-2 6-3 7-1 7-2 8-1 8-2 9-1 9-2 9-3 9-4 9-5 9-6 10-1 10-2 12-1 12-2 HP-UX Versions.............................................................................................................................14 Integrity VM Versions...................................................................................................................14 Chapters in this Manual...........................................................
About This Document This document describes how to install and configure the HP Integrity Virtual Machines (Integrity VM) product, and how to create and install virtual machines and guest operating systems. For recent updates to the product documentation, see the HP Integrity Virtual Machines 4.2: Release Notes. Intended Audience This document is intended for system and network administrators responsible for installing, configuring, and managing Integrity VM and virtual machines.
Table 1 HP-UX Versions Version Number Version Name HP-UX 11i v2 HP-UX 11.23 HP-UX 11i v2 (0505) HP-UX 11i v2 May 2005 release HP-UX 11i v2 (0609) HP-UX 11i v2 September 2006 release HP-UX 11i v3 HP-UX 11.31 Table 2 defines the naming conventions for the versions of the Integrity VM product. Table 2 Integrity VM Versions Version Number Version Name Integrity VM A.01.20 HP Integrity Virtual Machines version 1.2 Integrity VM A.02.00 HP Integrity Virtual Machines version 2.0 Integrity VM A.03.
• • Integrity VM Manpages lists the HP-UX manpages provided with the HP Integrity VM software. Glossary : “Glossary” (page 325) defines important terms used in the Integrity VM documentation. Related Information You can download the latest version of this document from docs.hp.com.
HP Encourages Your Comments HP encourages your comments concerning this document. We are truly committed to providing documentation that meets your needs. Your comments and suggestions regarding product features will help us develop future versions of the ID-VSE Management Software. Use the following e-mail address to send feedback directly to the Insight Dynamics — VSE (ID-VSE) for Integrity development team: vse@hpuxweb.fc.hp.com. NOTE: HP cannot provide product support through this e-mail address.
1 Introduction This chapter describes the Integrity VM product, including the following topics: • • • • • • • “About HP Integrity Virtual Machines” “New Features and Enhancements in This Release” “Using AVIO with Integrity VM” “Running Applications in the Integrity VM Environment” “Related Products” “Using the Integrity VM Documentation” “Using This Manual” 1.
Guests are fully loaded, operational systems, complete with operating system, applications, system management utilities, and networks, all running in the virtual machine environment that you set up for them. You boot and manage guests using the same storage media and procedures that you would if the guest operating system were running on its own dedicated physical hardware platform. Even the system administration privileges can be allocated to specific virtual machine administrators.
• • • Inclusion of the Online VM Migration feature into the VSE-OE and DC-OE. Improvement of migration performance on heavily loaded host systems. Guest-based VLAN support. The features in the following list have been rolled-into Integrity VM V4.2 from the patch kits that were provided after Integrity V4.1 was released. • Windows Server 2008 (also know as Windows Server 2008 SP1) guests. • Support for enabling or disabling vCPUs online.
[Network Interface Details] Physical Storage type Guest Adaptor type Backing Vswitch Port Bus Device Function Mac Address :vswitch :avio_lan :swlan1 :5 :0 :1 :0 :2a-2e-5a-05-0a-ba Physical Storage type Guest Adaptor type Backing Vswitch port Bus Device Function Mac Address :vswitch :avio_lan :swlan2 :9 :0 :2 :0 :2a-2e-5a-05-0a-bc NOTE: The CLI accepts either avio_lan or aviolan and either avio_stor or aviostor.
The asynchronous event generation occurs in addition to any notifications issued using the SCSI programming model, such as CHECK CONDITION on a subsequent I/O. When the AVIO storage driver on the guest detects the events, it takes the appropriate actions, such as discovering the new targets. For example, if new targets are added using the hpvmmodify -a command, then the guest driver automatically detects the new device without the manual scan.
A guest running on a virtual machine runs the way it does on a physical system. By allocating virtual resources, you provide the guest operating system and applications with access to memory, CPUs, network devices, and storage devices as if they were part of a dedicated system.
• • • • • HP Integrity Virtual Machines Manager — A graphical user interface for creating and managing HP Integrity virtual machines. Runs under either HP System Management Homepage (HP SMH) or HP Systems Insight Manager (HP SIM) as part of the HP Insight Dynamics — VSE (ID-VSE) Integrity. For more information, see the HP Integrity Virtual Machines Manager 4.1 Software: User Guide.
• • • • • • hpvmsg_package(1M) — Assists the user with developing and managing Serviceguard package configurations. hpvmstart(1M) — Describes how to start virtual machines. hpvmstatus(1M) — Describes how to get statistics about the guests. hpvmstop(1M) — Describes how to stop a virtual machine. hpvmupgrade(1M) — Examines the current Integrity VM server system to determine whether any virtual machines will have difficulty booting after the upgrade to the next Integrity VM version.
Table 1-1 Chapters in this Manual (continued) Chapter Read if... Chapter 7: “Creating Virtual Storage Devices” (page 93) You need to make changes to the storage devices used by the VM Host or virtual machines. Chapter 8: “Creating Virtual Networks” (page 127) You need to make changes to the network devices on the VM Host system or to the virtual network devices used by the virtual machines. Chapter 9: “Managing Guests” (page 141) You need to manage existing virtual machines and resources.
2 Installing Integrity VM This chapter describes how to install the Integrity VM software and how to prepare the VM Host environment for guests. It includes the following topics: • • • • • • • “Installation Requirements” “Installation Procedure for New Installations” “Upgrading the VM Host from Previous Versions of Integrity VM V3.X to Integrity VM V4.2” “Verifying the Installation of Integrity VM” “Removing Integrity VM” “Reserving VM Host Devices” “Troubleshooting Installation Problems” 2.
Table 2-1 Requirements for Installing Integrity VM V4.2 (continued) Resource Description Disk storage Sufficient disk space for the following: • The VM Host operating system (see the HP-UX 11i v3 Installation and Update Guide) • The VM Host software (50 MB) • Disk space for each guest operating system, including swap space NOTE: The VM Host requires swap space only as recommended by HP-UX 11i v3. Otherwise, no swap space is required for Integrity VM.
• • • • • • VMProvider — B.04.20 WBEM Provider for Integrity VM, which allows you to use the HP Integrity VM Manager to manage the VM Host VMVirtProvider — B.04.20 Integrity VM Virtualization Provider, which provides support for logical servers to manage Integrity VM Hosts and guests. VMKernelSW — B.04.
1. If you have the installation media, mount it. If you are installing from the network, identify the VM Host and path name that correspond to the software distribution depot that contains the T2767CC bundle (for example, my.server.foo.com:/depot/path). 2. Use the swinstall command to install Integrity VM and specify the path to the depot. For example, the following command installs Integrity VM and online VM migration bundle: # swinstall -x autoreboot=true -s my.server.foo.
Table 2-2 Kernel Parameters Parameter Default Value Modified Value base_pagesize 4 64 filecache_max 50% 1% filecache_min 5% 1% lcpu_attr 0 0 lockable_mem_pct 90% 99% maxdsiz_64bit 4294967296 34359738368 NOTE: Integrity VM Version 4.2 does not support hyperthreading. Specify the following command to turn off hyperthreading; otherwise, Integrity VM will not start: /usr/sbin/setboot -m off 2.3 Upgrading the VM Host from Previous Versions of Integrity VM V3.X to Integrity VM V4.
Figure 2-1 Upgrade Procedure 1. Study current 11i v2 to 11i v3 upgrade documentation. 2. Analyze the HP-UX 11i v2 based Integrity VM server using tools. 3. Decide whether to perform a cold install or update_ux. 4. Update hardware requiring new firmware or replace obsolete adapters. 5. Final check - assure all guests boot and then backup both server and guests. 6. Perform cold install or update_ux. ...cold install update_ux... 7.
2.3.1 Study the Current HP-UX 11i v2 to HP-UX 11i v3 Update Documentation The first stage of upgrading an Integrity VM V3.0 or V3.5 server to an Integrity VM V4.
require waiting until after the upgrade, such as substituting agile devices for an 11i v2 multipath solution. Another area of particular concern is the layered products running on your 11i v2 based Integrity VM server. Analyze each layered product to determine its upgrade impact: • No change - Layered product is compatible. • Delete/reinstall - Layered product requires a new version to work on 11i v3. • Delay upgrade – Layered product needs a new version that has not yet released.
It produces the following log file: /var/opt/hpvm/common/hpvmupgrade.current_date_and_time This log file contains a section for each guest configured on the server and displays the following message types: • Warning messages indicate problems that can cause a guest booting problem. • Error messages indicate problems that can cause a guest problem.
requires has changed its OE packaging. For information about the new 11i v3 OEs, see these documents: • • Customer Support Letter Describing OE Licensing New HP-UX 11i v3 Operating Environments The following are the new HP-UX OEs: • HP-UX 11i v3 Base OE (BOE) The BOE provides and integrated HP-UX operating environment for customers who require less complex installations.
NOTE: Many software subsystems require upgrades on the 11i v2 Integrity VM server before updating to HP–UX 11i v3. The most obvious of these is that Integrity VM must be upgraded to V3.0 or V3.5 before beginning the HP-UX upgrade. Other layered products, such as Serviceguard, require version upgrades before updating the operating system to 11i v3. Analyze each layered product for required upgrades. Remove HP Integrity Virtual Machines Manager (vmmgr) Version 3.
2.3.5 Perform Either a Cold-Install or an Update If the cold-install upgrade path is chosen, the administrator is taking the responsibility for fully configuring the 11i v3 Integrity VM Host to be functionally equivalent to the 11i v2 Integrity VM Host configuration. Integrity VM V4.2 provides the hpvmdevtranslate utility to assist in mapping the legacy devices used by guests on the 11i v2 VM Host to the new 11i v3 agile devices.
# hpvmdevtranslate -a /var/opt/hpvm/common/hpvm_mgmtdb_pre1131 18. Edit the script, /var/opt/hpvm/common/hpvm_dev_convert, taking note of ERROR lines and commenting out the exit line that prevents the running of the script. 19. Continue with the remaining 11i v3 Integrity VM Host configuration until the host is functionally equivalent to the former 11i v2 Integrity VM Host. If you choose the update path, follow these steps: 1. Create a recovery image. 2.
• Mass storage issues The Integrity VM V4.2 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.
The VM Host and guest configuration files are stored at /var/opt/hpvm. The new configuration files are not compatible with those of previous versions of Integrity VM. Therefore, if you are upgrading to the current version, the guest configuration files (except the /ISO-Images/ and /backup directories) are saved to the /var/opt/hpvmbackup directory. If you revert to the older version of Integrity VM, you can use the backup configuration files to restore your VM Host and guest configurations.
Guests are not affected by this procedure. To remove guests, see the procedures in Section 3.8 (page 63). 2.7 Reserving VM Host Devices You can protect the storage and network resources used by the VM Host against usage and corruption by virtual machines by marking the VM Host devices as restricted devices. For example, you can reserve the disk storage on which the VM Host operating system and swap space reside, which prevents guests from being able to access the same disk storage devices.
3 Creating Virtual Machines After you install Integrity VM, you can create guests and virtual resources for the guests to use. This chapter includes the following topics: • • • • • • • • • “Legacy and Agile Device Names” “Specifying Virtual Machine Characteristics” “Using the hpvmcreate Command” “Starting Virtual Machines” “Changing Virtual Machine Configurations” “Cloning Virtual Machines” “Stopping Virtual Machines” “Removing Virtual Machines” “Troubleshooting Virtual Machine Creation Problems” 3.
3.2 Specifying Virtual Machine Characteristics When you create a new virtual machine, you specify its characteristics. Later, you can change the virtual machine characteristics. You can set the characteristics of a virtual machine using the following commands: • hpvmcreate, which creates new virtual machines. • hpvmclone, which creates new virtual machines based on existing virtual machines. • hpvmmigrate, which moves virtual machines from one system to another.
3.2.1 Virtual Machine Name Use the -P vm-name option to specify the name of the new virtual machine. This option is required for the hpvmcreate command. In the following example, the new virtual machine is named host1. On the VM Host, enter the following command: # hpvmcreate -P host1 The virtual machine name can be up to 256 alphanumeric characters, including A-Z, a-z, 0-9, the dash (—), the underscore (_), and period (.). The virtual machine name must not start with a dash. 3.2.
The default minimum and maximum boundary values are a minimum of one (1) virtual CPU, and a maximum of eight (8) virtual CPUs. NOTE: HP Integrity VM does not support real-time applications running in the guest. Scheduling and precise timing properties that can be relied upon on physical hardware are not guaranteed to be preserved in a virtual machine. In particular, changing the hires_timeout_enable(5) HP-UX tunable or the tick rate (HZ) on Linux may not have the desired effect. 3.2.
addition to the amount of memory you specify for the virtual machine, the VM Host requires a certain amount of overhead for booting the guest operating system. The amount of memory allocated to all the running guests cannot exceed the amount of physical memory minus the amount used by the VM Host for its operating system and its administrative functions. For more information about the memory requirements of the VM Host, see Section 2.1 (page 27).
for communication among VIO guest devices registered with the same vswitch. This type of vswitch is typically referred to as localnet. For more information, see Section 8.2.1.1 (page 130). Unlike VIO guest networks, traffic from an AVIO guest LAN network device is directed to the pNIC directly by a separate host module rather than by the vswitch. In addition, AVIO does not support localnet type vswitch, because each AVIO guest device must have a backing of the host physical device.
stores). The VM Host system must have sufficient physical storage for the VM Host and for all of the virtual machines. Use the -a option to create and allocate the virtual device to the virtual machine. For example: # hpvmcreate -a VM-guest-storage-specification:VM-Host-storage-specification where: • VM-guest-storage-specification defines where and what storage is seen in the virtual machine.
Integrity VM checks the current physical configuration when you create a virtual machine using the hpvmcreate command. If the virtual machine uses backing stores that are not available, the virtual machine is created, and warning messages provide details. If you use the hpvmstart command to start a virtual machine that requires physical resources that are not available on the VM Host system, the virtual machine is not allowed to start, and error messages provide detailed information about the problem.
NOTE: If the start_attr attribute is set to Auto, the virtual machine also starts after you install or upgrade Integrity VM. In addition to automatically starting guests when Integrity VM starts, this feature also determines a startup order to best utilize VM Host processor and memory resources. On cellular systems with cell local memory (CLM) configured, the goal is to start the guests so that CLM is utilized first.
Table 3-3 Configuration Limits Description Support # vCPUs/VM — Maximum (Integrity VM V3.5 Max vCPU min (#pCPUs, Max vCPU) = 4, Integrity VM V4.2 Max vCPU = 8) # vCPUs/pCPU — Maximum 20 # VMs per VM Host — Maximum 256 # pCPUs in VM Host HP-UX limit Memory per VM — Minimum (11i v2 HP-UX) 1 GB Memory per VM — Minimum (11i v3 HP-UX) 1.
Table 3-4 Guest Default Settings HP-UX Guest Default Settings Windows Guest Default Settings Linux Guest Default Settings Unknown Guest Operating System Default Settings Maximum CPUs 8 8 8 8 Default CPUs 1 1 1 1 Default memory 2 GB 2 GB 2 GB 2 GB Minimum memory 512 MB1 512 MB 512 MB 32 MB Maximum memory 64 GB 64 GB 64 GB 128 GB Default reserved memory 64 MB 64 MB 64 MB 64 MB Minimum reserved memory 32 MB 64 MB 32 MB 32 MB Maximum reserved memory 64 GB 64 GB 64GB 12
Table 3-5 Options to the hpvmcreate Command (continued) Option Description -B start_attribute The startup behavior of the virtual machine (auto or manual).
winguest1 winguest2 host1 5 WINDOWS On (OS) 9 WINDOWS Off 12 UNKNOWN Off 1 1 1 5 3 0 1 1 0 1 GB 2 GB 2 GB 0 0 0 The host1 virtual machine has been assigned virtual machine number 12, has been created with an UNKNOWN operating system type, one vCPU, no storage devices, no network devices, and 2 GB of memory. The Runsysid column indicates the VM Host that runs the virtual machine in a Serviceguard cluster.
Daemonizing.... hpvmstart: Successful start initiation of guest 'host1' The hpvmstatus command displays the allocation of memory and devices. After you start the virtual machine, the hpvmstatus command displays the virtual machine status as On (EFI), because the virtual machine is powered on but the guest operating system is not running. Because the operating system has not been installed, the guest OS type is listed as UNKNOWN.
Table 3-7 Options to the hpvmmodify Command (continued) Option Description -s Sanity-checks the virtual machine configuration and returns warnings or errors, but does not start the virtual machine. -N new-vm-name Specifies a new name for the virtual machine. The name can consist of up to 256 alphanumeric characters including A-Z, a-z, 0-9, the dash (-), the underscore character (_), and the period (.). The virtual machine name cannot start with a dash (—).
Table 3-7 Options to the hpvmmodify Command (continued) Option Description -i package-name Specifies whether the virtual machine is managed by Serviceguard or gWLM (or both). For the argument, specify one or more of the following parameters: • SG indicates that the VM Host is a Serviceguard cluster node. • SG-pkgname indicates that the VM Host is a Serviceguard package. • GWLM indicates that the VM Host is managed by gWLM. • NONE indicates there are no external managers.
Allocating guest memory: 2048MB allocating low RAM (0-40000000, 2048MB) /opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ba249f2-3399-11db-aacc-00306ef392e0 /vmm_config.next): Allocated 1073741824 bytes at 0x6000000100000000 locking memory: 0-40000000 allocating firmware RAM (ffaa0000-ffab5000, 84KB) /opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ba249f2-3399-11db-aacc-00306ef392e0 /vmm_config.
Table 3-8 Options to the hpvmclone Command (continued) Option Description -B start_attr Specifies the startup behavior of the virtual machine. For start_attr, enter one of the following keywords: auto: Automatically starts the virtual machine when the VM Host is started (autoboot). manual: The virtual machine is not started automatically. Use the hpvmstart command to start the virtual machine manually.
Table 3-8 Options to the hpvmclone Command (continued) Option Description -u user[:{admin|oper}] Specifies a user authorization. The specified administrative level (admin or oper) is applied to the specified user group.
the actual data and software associated with the guest. The clone_vm_name must not already exist on the same VM Host. The new virtual machine's configuration information can be modified from the original configuration file by using command options. If no options are specified, all original parameters are retained. This will cause resource conflicts if both the original and clone virtual machines are booted together.
[Virtual Machines] Virtual Machine Name VM # ==================== ===== config1 1 config2 2 winguest1 5 winguest2 9 host1 12 OS Type ======= HPUX HPUX WINDOWS WINDOWS UNKNOWN State #VCPUs #Devs #Nets Memory Runsysid ========= ====== ===== ===== ======= ======== Off 1 5 1 512 MB 0 Off 1 7 1 1 GB 0 On (OS) 1 5 1 1 GB 0 Off 1 3 1 2 GB 0 Off 1 0 0 2 GB 0 The default action of this command (if you press Enter) is to not perform the command operation. To continue the operation, you must enter y.
Table 3-10 Options to the hpvmremove Command (continued) Option Description -F Forces the command to act regardless of errors. -Q Performs the command without requiring user input to confirm. For example, the following command removes the virtual machine named host1.
4 Creating HP-UX Guests To create HP-UX guests, install the HP-UX operating system on the virtual machine. To install the HP-UX guest operating system, follow the procedures in the following sections: • “Installing the HP-UX Guest Operating System” • “Installing HP-UX Guest Management Software” • “Troubleshooting HP-UX Guest Creation” 4.
CL: SL: VM: HE: X: Console Log Show Event Logs Virtual Machine Menu Main Help Menu Exit Connection [host1] vMP> The hpvmconsole command opens the virtual machine console. From the virtual console, you can control the virtual machine just as if it were a physical Integrity server. 3. In response to the virtual machine prompt, enter the co command: [host1] vMP> co EFI Boot Manager ver 1.10 [14.
Save changes to NVRAM [Y-Yes N-No]: 6. Y Exit the EFI Boot Maintenance Management screen to return to the EFI Boot Manager screen. Boot from the new boot entry, indicated by the virtual machine's MAC address:. EFI Boot Maintenance Manager ver 1.10 [14.62] Add a Boot Option.
NOTE: You might receive a warning message during the guest installation process indicating that the AVIO bundles are not installed. The installation will continue and complete successfully. The AVIO bundles are optional and install by default. If they do not, and if you want to install them with the Integrity VM bundle T2767CC, go to the HP-UX 11i v3 0903 media and look for the following bundles to install on the HP-UX guest, GuestAVIOStor and GuestAvioLan.
• 11iv2 indicates HP-UX 11.23. For HP-UX 11.23 guests, the guest depot file is: /opt/hpvm/guest-images/hpux/11iv2/hpvm_guest_depot.11iv2.sd • 11iv3 indicates HP-UX 11.31. For HP-UX 11.31guests, the guest depot file is: /opt/hpvm/guest-images/hpux/11iv3/hpvm_guest_depot.11iv3.sd Complete instructions for installing the guest management software are in the README.txt file in /opt/hpvm/guest-images/hpux directory. HP-UX guests reboot as part of the guest management software installation process. 4.
5 Creating Windows Guests You can install HP Integrity Windows Server 2008 on your virtual machines. These Windows guests can be managed like a Windows server running on an independent Integrity server, nPartition, or Integrity server blade by either the VM Host administrator or the Windows system administrator. This chapter includes the following topics: • “Windows Guest Requirements” • “Installing Windows Server 2008 Guests” • “Managing Windows Guests” • “Troubleshooting Windows Guest Installation” 5.
3. Select the DVD by typing fsX: at the EFI shell, where X should be zero (0) if the disk is not bootable otherwise, X should be 2. 4. At the fsX: prompt, type bootia64 to start the Windows installer. 5. After the SAC> is displayed, and the CMD event becomes available, type cmd. 6. Type Esc + Tab and press return to enter the newly-created cmd channel. 7. At the X:\windows\system32> prompt, type txtrestore. 8.
17. A window, named Server Manager Window, opens. Optionally, click the Do not show me this console at logon checkbox and close the window. 18. After installing the operating system, perform these tasks: a. Install the Integrity Support Pack (ISP). b. Activate the operating system. c. Apply operating system updates using the Smart Update Media. d. Enable Windows components. e. Verify system device drivers and register for updates. f. Install and configure the Simple Network Management Protocol (SNMP). g.
# hpvmmodify -P win2 -d disk:scsi::file:/var/opt/hpvm/ISO-images/windows/unattend_xml.iso This .iso file can be used on this VM Host or copied from this VM Host to another on which the Windows guest is to be installed using any standard HP-UX techniques (for example, FTP, scp, and so on). NOTE: Do any copying in binary mode to preserve the exact contents of the file, which will look like a formatted disk to the Windows guest.
EFI Boot Manager ver 1.10 [14.62] [Build: Sun Jun 8 12:30:44 2008] Please select a boot option EFI Shell [Built-in] Boot option maintenance menu Use ^ and v to change option(s). Use Enter to select an option Boot option maintenance menu b. Typically, the EFI shell is automatically selected upon startup. If not, choose EFI Shell [Built-in] from the menu. Loading.: EFI Shell [Built-in] EFI Shell version 1.10 [14.
12. Go back to the root of drive X:\ and start the automated installation by typing the following command: X:\ setup.exe /unattend:e:\unattend.xml 13. Press Esc Tab to make sure there are no errors. The installation should complete in about 15 minutes and reboot. 14. At this point, you should be able to log into the Windows guest as Administrator using the Remote Desktop from a Windows PC (Start > Programs > Accessories > Communications > Remote Windows Desktop).
5.3 Managing Windows Guests Use the Windows Remote Desktop to manage the Windows guest: Log in as Administrator and configure Windows TCP/IP using the same networking information supplied earlier at the SAC> prompt. Install SNMP from the Windows Management and Monitoring Tools and configure it. SNMP is required for the HP Systems Insight Manager (SIM), which provides the ID-VSE environment.
2. 78 Create an opening in the firewall for the ID-VSE providers. Select Add Port… Set the name to wbem-https. Set the port number to 5989, and select TCP.
You can now monitor and manage the Windows guest using VM Manager and HP SMH. For more information, see the HP Integrity Virtual Machines Manager 4.1 Software: User Guide manual. To shut down a Windows guest, use the Windows system management procedures. The Integrity VM commands for stopping guests do not shut down the Windows software properly and can lead to problems when the Windows guest is rebooted. 5.
6 Creating Linux Guests You can install the Linux operating system on your virtual machines. Linux guests can be managed like a discreet Integrity server or nPartition, by either the VM Host administrator or the Linux system administrator.
Table 6-1 Linux TUI Control Keys tab Moves to next field alt Moves to the previous field space Selects the item from a list arrow Scroll lists that are too long for a single screen enter Activates the action 6.1.3 Linux Guest Installation Media You can install Linux guests using any one of the following types of installation media: • Images (*.iso files) of the Red Hat Installation DVDs (recommended) (described in Section 6.2 (page 82)).
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids /eaccd6e4-b004-11db-bd1f-00306ef4693e/vmm_config.next): Allocated 86016 bytes at 0x6000000180000000 Loading boot image Image initial IP=102000 GP=62E000 Initialize guest memory mapping tables Starting event polling thread Starting thread initialization Daemonizing.... hpvmstart: Successful start initiation of guest 'linux1' Use the hpvmconsole command to connect to the guest. 4. Boot the guest.
NOTE: Failure to add this option results in an apparent guest hang, where the guest is trying to run a graphical installation program without a display. If this happens, reset the virtual machine. Press Ctrl/B to reach the virtual console. Enter the RS command to restart the virtual machine. Then resume the installation procedure. The installation process continues: Uncompressing Linux... done Loading initrd initrd.img...done Linux version 2.6.9-42.EL (bhcompile@altix2.build.redhat.com) (gcc version 3.4.
Table 6-2 Linux Installation Screens (continued) Screen Typical Response Language Support Select your primary language plus any additional languages, then enter OK. Time Zone Selection Select a city in your time zone from the list, then enter OK. Root Password Type the guest's root password in each entry, then enter OK. Package Defaults Select Customize software selection and then enter OK. Package Group Selection Scroll to the bottom, select Everything, and then enter OK.
6.3 Installing Red Hat Enterprise Linux Guests from a Boot Disk and Network Server This section describes how obtain the Linux Installation (Boot) image from a boot disk and then obtain the Linux packages to be installed from a network server. This procedure assumes the Linux installation directory tree has been created from the ISO images on a network server.
• • From the EFI shell From the File menu To boot from the EFI shell: a. Go to the EFI shell. For example: fs0 fs1 fs2 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig5D1D1134-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part2,Sig5DB58D88-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0)/CDROM(Entry0) EFI lists devices with filesystems detected as fs{n}. In the preceding example, fs0 and fs1 are older filesystems that are present on the disk.
. Welcome to Red Hat Enterprise Linux 6. The boot program presents a few screens that allow you to specify the network parameters of the guest (IP address, netmask, gateway, DNS), the network name of the server, and the directory path to the installation tree on the server. Respond to the screens as described in Table 6-3. Table 6-3 Linux Guest Network Installation Screens Screen Title Response Language Selection Select your language and enter OK. Select Installation Method NFS or FTP and enter OK.
=== from "dmesg" command === ipmi_si: Error clearing flags: cl You can ignore this error message. • SLES 10 requires the media to be in the first optical drive present to the guest; otherwise, the installation fails with the following error: Failed to initialize the catalog. Try again? The following steps install SUSE Linux Enterprise Server (SLES) for HP Integrity servers SLES 10 update 2 guests: 1. On the VM Host system, load the *.
fs0 fs1 fs2 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig5D1D1134-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part2,Sig5DB58D88-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0)/CDROM(Entry0) EFI lists devices with file systems detected as fs{n}. In this example, fs0 and fs1 are older file systems that are present on the disk.
6.5 Installing Integrity VM Linux Guest Management Software After you install the Linux guest operating system, you must install the Integrity VM Linux guest management kit from the VM Host system. When you install Integrity VM, the Linux guest management kit is loaded into the following directory: /opt/hpvm/guest-images/linux This directory contains a README.txt file that contains instructions for installing the Linux guest management kit on the Linux guest.
7 Creating Virtual Storage Devices This chapter describes what Integrity VM storage is, how to configure it, and how to use it. The topics included in this chapter are: • “Introduction to Integrity VM Storage” • “Configuring Integrity VM Storage” • “Using Integrity VM Storage” 7.1 Introduction to Integrity VM Storage The way you configure and manage Integrity VM storage affects the way virtual machines perform.
7.1.1.4 Storage Security To avoid problems while supporting multiple virtual machines on one physical machine, Integrity VM isolates each virtual machine. Using Integrity VM commands, the VM Host administrator determines the physical storage resources that each virtual machine can access. This storage isolation is maintained by the Integrity VM storage subsystem through DMA boundary checks on each virtual machine I/O operation, thereby ensuring that one virtual machine does not access the memory of another.
7.1.2.2 Attached I/O Attached I/O allows a virtual machine to access to a VM Host LUN directly. In this architecture, the Integrity VM storage subsystem attaches a LUN on the VM Host to a virtualized storage adapter. A LUN can be a disk, DVD, tape, media changer, or other peripheral device types. Because attached I/O does not require device virtualization, the performance of attached I/O might be better than shared I/O.
Add # hpvmmodify -P guest1 -a tape:avio_stor:0,5,0:attach_path:0/1/1/0.0x50060b0000332254.0x0 # hpvmmodify -P guest1 -a changer:avio_stor:0,5,1:attach_path:0/1/1/0.0x50060b0000332253.0x0 # hpvmmodify -P guest1 -a burner:avio_stor:0,5,2:attach_path:0/1/1/0.0x50060b0000332252.0x0 Delete # hpvmmodify -P guest1 -d tape:avio_stor:0,5,0:attach_path:0/1/1/0.0x50060b0000332254.0x0 # hpvmmodify -P guest1 -d changer:avio_stor:0,5,1:attach_path:0/1/1/0.0x50060b0000332253.
0/5/0/0/0/0.0x500110a0008b9de2.0x0 /dev/rtape/tape5_BEST /dev/rtape/tape5_BESTn /dev/rtape/tape5_BESTb /dev/rtape/tape5_BESTnb # ioscan -m lun /dev/rtape/tape6_BEST Class I Lun H/W Path Driver S/W State H/W Type Health Description ====================================================================== tape 6 64000/0xfa00/0x3 estape CLAIMED DEVICE online STK 0/4/1/0.0x500104f0004732d9.0x0 0/4/1/1.0x500104f0004732d9.0x0 0/4/1/0.0x500104f0004732da.0x0 0/4/1/1.0x500104f0004732da.
/dev/rtape/tape6_BESTn:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=YES: lunpath3,lunpath6,lunpath5,lunpath4:0x01.0x00.0x03.0x500104f0004732d8 7.1.3.3.1 Sharing Conflicts You cannot share a device when a mixture of VIO and AVIO usage is specified; however, you can configure two guests with one guest using a device with VIO access and the other guest using a device with AVIO access.
NOTE: After the user adds more than one attached lunpath to a particular device to one or more guests, each device database lunpath entry has an AGILE_DSF attribute that points to the agile-named parent DSF. If the user wants to allow guests to boot at the same time when they use different lunpaths to the same device, SHARE_LUNPATHS=YES is set on the entry to which that AGILE_DSF points.
================================================================== lunpath 21 0/7/1/1.0x500104f00048b29e.0x0 eslpt CLAIMED LUN_PATH # hpvmmodify -P guest1 -a tape:scsi:0,4:attach:/dev/pt/pt_tape1 LUN path for tape1 7.1.3.5 Limitations The AVIO attached devices feature has the following limitations: • Integrity VM does not support the hpvmmodify -m hba option when attached devices are present under the adapter.
Table 7-2 Patch Dependencies for AVIO Attached Devices Patch Number HP-UX Version VM Host Guest Notes PHKL_38604 11i v3 Yes Yes Hard1 dependency for guest, and soft2 dependency for VM Host. PHKL_38605 11i v3 Yes No Soft dependency on VM Host. PHKL_38750 11i v3 Yes Yes Recommended patch. 1 2 Enforced during swinstall. Required only if attached devices are configured. No enforcement using swinstall. 7.1.3.
AVIO backing store. HP recommends the use of AVIO for the supported guest operating systems, guest devices and host backing stores. See the HP Integrity Virtual Machines 4.2: Release Notes and AVIO documentation for details. 7.1.4.2 Integrity VM Storage Devices Integrity VM supports a variety of virtual and attachable devices. Disk and DVD-ROM devices support several virtual media types (see Section 7.1.4.2.1 (page 102)).
7.2.1 Integrity VM Storage Considerations When you configure storage for a virtual machine, consider the following: • VM storage supportability • Storage performance • VM storage multipath solutions • VM storage management • VM storage changes • Virtual storage setup time The following sections explain each of these considerations. 7.2.1.1 VM Storage Supportability Before you configure virtual machine storage, make sure the VM Host storage can be supported by the virtual machine.
Figure 7-1 Integrity VM Storage I/O Stack Virtual File Disk File Systems Layer Virtual LvDisk Logical Volume Managers Layer Virtual Disk Attached Devices Disk Drivers Layer Integrity Vm Passthrough Drivers Layer VM Host Driver Services HP-UX Interface Driver HP-UX Interface Driver HP-UX Interface Driver Physical Adapter Physical Adapter Physical Adapter Physical Media Physical Media Physical Media For a virtual I/O operation to be completed, it has to travel round trip between the virtual sto
It is important to know exactly where the virtual media is located on physical storage devices. With Integrity VM, a single physical disk might be sliced into logical volumes or files. Slicing up physical disks increases utilization, but it can affect the performance of the physical device. The guest OS treats the virtual disk as a whole disk, not as a part of a physical one. Over-slicing physical storage can overload a physical device's ability to handle virtual I/O that is meant for whole disks.
For supported multipathing configurations, see the HP Integrity Virtual Machines 4.2: Release Notes. 7.2.1.4 VM Storage Management Before you decide how to divide VM Host storage, consider the impact on the management of the storage subsystem. A VM Host administrator manages VM storage to make sure virtual media is allocated safely. This begins with understanding the VM Host I/O stack and knowing from where the virtual media is being allocated.
Figure 7-5 Bad Virtual Device Allocation Guest A Guest B Virtual LvDisk As these examples illustrate, it is important to know where storage is allocated from to avoid data corruption with virtual machines or even the VM Host. Management utilities such as the HP System Management Homepage (HP SMH) utility allow you to track disk devices, volume groups, logical volumes, and file systems.
Logical volume creation is relatively simple. Logical volumes are used widely on HP-UX systems. The Veritas Enterprise Administrator can be used to create logical volumes. With experience, you can use logical volume commands more quickly. Creating files for virtual devices is not hard, but takes time. Files are usually placed on top of logical volumes, so you might have to create a logical volume first. To create empty files for virtual disks, use the hpvmdevmgmt command (see Section 9.9 (page 161)).
• pcislot is an integer from 0-7. A PCI function number is not specified. It is implicitly zero because the virtual MPT storage adapter supports only a single channel. • scsitgt is an integer from 0-14 for virtual SCSI (15 is reserved for the virtual SCSI adapter) and 0–127 for AVIO. All supported storage device types can share the same virtual SCSI MPT or AVIO adapter by specifying the same PCI bus and slot numbers.
resource can only be specified once to a given virtual machine. Therefore, only one VM Host system file per VM Host storage entity can be provided to a virtual machine (see Section 7.2.1.4 (page 106)). Not all virtual device types support all VM Host storage types (see Section 7.1.4 (page 101)). Complete VM storage resource statements are discussed in the next section. 7.2.2.
where /dev/rdsk/diskX is an HP-UX esdisk character device file. The legacy Virtual Disk resource statement takes the form: disk:scsi::disk:/dev/rdsk/cXtYdZ where /dev/rdsk/cXtYdZ is an HP-UX sdisk character device file. Use of agile device names for configuring storage devices is highly recommended as it provides multipathing benefits. These device files can be located for a VM Host LUN using the ioscan command. These system files are installed and removed using the insf and rmsf commands, respectively.
VGDA PE Size (Mbytes) Total PE Alloc PE Free PE Total PVG Total Spare PVs Total Spare PVs in use 2 4 8681 8192 489 0 0 0 --- Logical volumes --LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV /dev/lvrackA/disk1 available/syncd 8192 2048 2048 1 LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV /dev/lvrackA/disk2 available/syncd 8192 2048 2048 1 LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV /dev/lvrackA/disk3 available/syncd 8192 2048 2048 1 LV N
TY NAME PUTIL0 dg VxvmTest1 ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 VxvmTest1 - - - - - - dm disk01 c5t8d0 - 71680564 - - - - v vxvm_1 pl vxvm_1-01 sd disk01-01 fsgen vxvm_1 vxvm_1-01 ENABLED ENABLED ENABLED 2048000 2048000 2048000 0 ACTIVE ACTIVE - - - v vxvm_2 pl vxvm_2-01 sd disk01-02 fsgen vxvm_2 vxvm_2-01 ENABLED ENABLED ENABLED 2048000 2048000 2048000 0 ACTIVE ACTIVE - - - v vxvm_3 pl vxvm_3-01 sd disk01-03 fsgen vxvm_3 vxvm_3-01 ENABLED ENABLED ENABLED 2048000
Multipath options for a Virtual FileDisk device are discussed in Section 7.2.1.3 (page 105). NOTE: Each Integrity VM guest can support a maximum of 30 Virtual FileDisks (combined limit for both AVIO and VIO). 7.2.2.3.4 Virtual DVDs A Virtual DVD is an emulated SCSI DVD-ROM with virtual media that comes from a disc inside of a CD/DVD drive on the VM Host. The VM Host CD/DVD drive is specified using an HP-UX sdisk character device file.
eject command. Once ejected, the Virtual DVD turns into a Virtual NullDVD and the VM Host CD/DVD drive unlocks. After you place physical media in the VM Host's CD/DVD drive, use the virtual console's insert command to turn a Virtual NullDVD back to a Virtual DVD, relocking the VM Host CD/DVD drive. Most physical VM Host CD/DVD devices on HP Integrity servers have only one path to them. As such, no multipath software is available on the VM Host for them. 7.2.2.3.
If the VM Host administrator gives access to the guest administrator to load and unload physical media on the VM Host CD/DVD drive, the Virtual NullDVD can be set up with the following form of the resource specification: dvd:scsi::null:/dev/rdisk/disk# where /dev/rdisk/disk# is an HP-UX esdisk character device file that points to the VM Host CD/DVD drive. The legacy sdisk device file, /dev/rdsk/cXtYdZ, may also be used. This is the same as setting up a Virtual DVD (see Section 7.2.2.3.
Virtual NullDVDs require no additional management beyond that required for the Virtual DVD (see Section 7.2.2.3.4 (page 114)) or Virtual FileDVD (see Section 7.2.2.3.5 (page 115)) types they become. 7.2.2.3.7 Attachable Devices Integrity VM allows you to attach physical VM Host backup device types to virtual machines. The VM Host backup device types are tapes, media changers, and CD/DVD burners. These devices are specified on the VM Host using HP-UX agile esctl or legacy sctl device files.
If the device is not seen, there is a hardware problem or SCSI ID conflict. Consult the documentation for the particular device to resolve this issue before proceeding. If the device is seen but not claimed, this is a result of missing drivers in the VM Host. Integrity VM does not require the drivers to be loaded on the VM Host for the devices to be attached. The HP-UX tape (stape) and changer (schgr) drivers are not loaded by default unless those devices are connected at install time.
7.3.1 Integrity VM Storage Roles This section describes the roles that individuals play in working with Integrity VM storage. Each role has different responsibilities in using Integrity VM storage. The roles might be played by one or more individuals depending on security requirements and skill sets. The three roles are: • “VM Host Administrator” (page 119) • “Guest Administrator” (page 119) • “Guest User” (page 120) 7.3.1.
for displaying devices that are removable. Selecting options through the submenus completes the ejection/insertion process. Management Function Integrity VM Command Eject a virtual DVD. vMP> ej Insert a virtual DVD vMP> in NOTE: When a DVD without a disk in the drive is added to a guest, specify the backing store type of null, for example: # hpvmmodify -P guest -a dvd:scsi::null:/dev/rdisk/disk# Run ioscan on the booted guest if the guest if running HP-UX.
machine is powered on or off. A new virtual storage adapter can be added only when the virtual machine is off. The virtual storage adapter can have up to 30 VIO storage devices or up to 128 AVIO devices total (the number of virtual and attached devices.) The process to add or attach a virtual storage device to a guest is as follows: 1. Based on the all Integrity VM storage considerations, choose a storage device to add. 2.
disk avio_stor 0 5 0 0 0 disk /dev/rdisk/disk11 # hpvmmodify -P myvmm -d disk:scsi::disk:/dev/rdisk/disk7 # hpvmstatus -P myvmm ... [Storage Interface Details] disk scsi 0 1 0 0 0 disk /dev/rdisk/disk5 disk scsi 0 1 0 2 0 disk /dev/rdsk/disk9 To delete an AVIO storage device, specify the following: host# hpvmmodify -P guest1 -d disk:avio_stor:0,5,0:disk:/dev/rdisk/disk11 7.3.2.3 Modifying VM Storage Devices The VM Host administrator or the guest administrator can modify an Integrity VM storage device.
If the VM Host administrator sets up a Virtual DVD for the virtual machine, the virtual console eject and insert command unlock and lock the physical VM Host CD/DVD drive. The eject command changes the Virtual DVD into a Virtual NullDVD in the VM, unlocking the VM Host CD/DVD drive in the process. The physical media in the VM Host CD/DVD drive can then be changed by the VM Host administrator or the guest administrator if access is permitted.
type: CD-ROM size: 4300800 Kbytes bytes per sector: 2048 To modify an existing AVIO storage backing store, specify the following: host# hpvmmodify -P guest1 -m disk:avio_stor:0,5,0:disk/dev/rdisk/disk11 In this command, avio_stor indicates the “from” adapter and the “bus,dev” specification indicates the bus and device list of storage targets to convert.
NOTE: Guest operating systems, applications, or configuration files sensitive to device names or hardware paths need to be repaired after the move. Because HP-UX 11i v3 supports the agile device naming model, 11i v3 guest applications using agile device names are not affected as long as they are configured with disk backing stores. HP recommends the use of agile device names for guest configurations to avoid problems when VM Hosts are reconfigured.
product id: type: size: bytes per sector: Virtual FileDVD CD-ROM 3686144 Kbytes 2048 For attached devices, modifications are made physically on the device. The guest OS supplies commands for loading and unloading tapes using media changers. But loading new media into the media changer, changing tapes in standalone drives, and changing discs with CD/DVD burners are accomplished manually. This process requires cooperation between the VM Host administrator and the guest administrator.
8 Creating Virtual Networks You can allocate virtual network devices or virtual network interface cards (vNICs) to the guest when you create the guest with the hpvmcreate command or when you modify an existing guest using the hpvmmodify command, as described in Chapter 3. Virtual network interface cards 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.
NOTE: guest. • • Trunking software such as APA is supported only on the VM Host, not on the Guest virtual network interface card (vNIC) — the virtual network adapter, as recognized by the guest operating system. Virtual switch (vswitch) — the virtual network switch maintained by the VM Host that is associated with a pNIC and can be allocated to one or more guests.
Table 8-1 Options to the hpvmnet Command (continued) Option Description -n nic-id Specifies the network interface on the VM Host that the new vswitch will use. For example, to associate a vswitch to lan0, enter -n 0. -p n Specifies the port number. To display information about all ports, enter —p all. -Q Specifies the command function should proceed without asking for confirmation. By default, the command requires confirmation, and does not proceed without it. -r Restarts the vswitch information.
Note that clan1 is associated with the network interface on the VM Host that has MAC address 0x00306e3977ab (this is not the MAC address of any virtual machine connected to this vswitch). For information about connecting vswitches to guests, see Chapter 3. For information about modifying virtual networks, see Section 8.3.1 (page 133). You can create multiple vswitches associated with the same host physical NIC. However, you cannot boot (hpvmnet —b) more than one of them at the same time. 8.2.1.
[Port Configuration Details] Port Port Untagged Number of Number state VLANID Reserved VMs ======= ============ ======== ============ 1 Reserved none 1 2 Reserved 20 1 3 Reserved none 1 # hpvmnet -C -S vmvlan -n 1 -N clnvlan # hpvmnet -S clnvlan Name Number State Mode NamePPA ======== ====== ======= ========= ======== clnvlan 320 Down Shared lan1 [Port Configuration Details] Port Port Untagged Number state VLANID ======= ============ ======== 2 Available 20 Active VM ============ MAC Address IP Address ==
When an active vswitch is deleted, the VM Host automatically determines that the vswitch is gone. When the vswitch is recreated, the guest network automatically becomes functional again. 8.2.5 Recreating vswitches To change the vswitch to use another pNIC on the VM Host (for example, to change from lan0 to lan1), follow this procedure: 1. Delete the vswitch that was associated with lan0. For example: # hpvmnet -S myswitch -h -Q # hpvmnet -S myswitch -d 2. Create a new vswitch associated with lan1.
# hpvmclone –P vm-name -N clone-vm-name —a network:adapter-type:[hardware-address]:vswitch:vswitch-name The vNIC specified with this command is added to the new virtual machine. • To modify an existing virtual machine: # hpvmmodify –P vm-name —a network:adapter-type:[hardware-address]:vswitch:vswitch-name The —a option adds the specified vNIC to the virtual machine. NOTE: If you modify a vNIC from lan to avio_lan, or avio_lan to lan, you must restart the vswitch.
The localnet vswitch can be used as a local network ,and vNICs can be specified for a guest. For example: # hpvmmodify -P host1 -a network:lan::vswitch:clan0 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.
• • • Enhanced security through traffic isolation within nodes that are VLAN members Bandwidth preservation, limiting the broadcast domain to a VLAN instead of the entire LAN Enhanced manageability for node migrations and network topology changes Figure 8-2 illustrates a basic virtual machine VLAN that allows guests on different VM Host systems to communicate.
# hpvmnet -c -S vmlan4 -n 1 # hpvmnet -b -S vmlan4 2. Use the hpvmnet command with the —u option to create the port and assign it a VLAN ID. For example, to create ports 1 and 2 for VLAN 100, enter the following command: # hpvmnet -S vmlan4 -u portid:1:vlanid:100 # hpvmnet -S vmlan4 -u portid:2:vlanid:100 3. Add the vswitch ports to the guest configuration using the hpvmmodify command.
8.4.2 Displaying VLAN Information 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 vm1, enter the following command: # hpvmstatus -P vm1 . . . [Network Interface Details] Interface Adaptor Name/Num ========= ========== ========== vswitch lan localnet vswitch lan localnet vswitch lan vmlan4 vswitch lan vmlan4 vswitch lan vmlan900 vswitch lan vmlan900 . . .
Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlanId Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlanID : : 3 : : : : : : 4 : : : : : : Active vm2 none vm2 avio_lan none Active vm2 100 vm2 avio_lan none 8.4.3 Configuring VLANs on Physical Switches When communicating with a remote VM Host or guest over the network, you might need to configure VLANs on the physical switches.
# lanscan Hardware Station Path Address 0/0/5/0 0x02636C6E3030 Crd Hdw Net-Interface In# State NamePPA 1 UP lan3 snap3 NM ID 1 MAC Type ETHER HP-DLPI DLPI Support Mjr# Yes 119 In the preceding example, before the modification, the LAN PPA was 0. The new LAN PPA on the first boot after the modification is 3. Therefore, you must first bring the guest network down, then you must change the INTERFACE_NAME[0] from lan0 to lan3. You can then use /sbin/ rc2.d/S340net to restart the guest network.
9 Managing Guests To manage a guest, connect to the guest using a remote connection and use the operating system administration procedures appropriate to the guest OS. Integrity VM provides utilities for managing virtual machines from the VM Host and from inside the guest. This chapter describes how to manage guests using Integrity VM commands and utilities.
NOTE: Adding devices to the storage pool does not prevent them from being used by the HP-UX operating system or other Integrity VM commands. The storage pool does not fully support lunpaths or directories. In addition, Virtual Machine Management (VMM), a layer between Integrity VM and LSM, has no way to insert or eject a DVD, because this is done from the virtual console. 9.1.2 Registering and Unregistering a VM A VM is registered when it is runnable, modifiable, and visible.
CAUTION: HP does not recommend using the -x runnable_status option. Integrity VM ensures that the VM is runnable only on one VM Host at a time. Marking a VM runnable on more than one VM Host can lead to accidentally booting the VM on more than one VM Host. • The modify_status option of a VM is listed in the hpvmstatus -V output. If modify_status=disabled, you cannot modify a VM except to set modify_status=enabled.
The following example shows the output of the hpvmstatus command: # hpvmstatus [Virtual Machines] Virtual Machine Name VM # ==================== ===== vm1 1 vm2 2 vm3 3 vm4 4 vm5 5 vm6 6 vm7 7 OS Type ======= HPUX WINDOWS WINDOWS LINUX HPUX LINUX HPUX State #VCPUs #Devs #Nets Memory Rmt Host ========= ====== ===== ===== ======= ======== Off 2 2 2 6 GB On (RMT) 4 1 1 2 GB 3 On (RMT) 2 1 1 1 GB 2 On (OS) 4 1 1 2 GB 1 On (RMT) 4 9 1 2 GB 3 On (OS) 4 1 1 4 GB 1 On (RMT) 4 1 1 2048 MB 3 The hpvmstatus -V opti
Table 9-1 Options to the hpvmstatus Command (continued) Option Description -p vm-number Specifies the number of the virtual machine for which to display information. -D Displays the resource allocation of the specified virtual machine. You must include either the -p option or the -P option. -e Displays the event log for the VM Host or the specified virtual machine. The event log records all changes to virtual machine configurations.
Maximum memory limit Reserved memory Minimum reserved limit Maximum reserved limit VHPT Size : : : : : 64 GB 64 MB 32 MB 64 GB 1 MB [Dynamic Memory Information] Type : driver Minimum memory : 1024 MB Target memory : 2039 MB Maximum memory : 2048 MB Current memory : 2039 MB Comfortable minimum : 759 MB Boot memory : 2039 MB Free memory : 1148 MB Available memory : 215 MB Memory pressure : 0 Memory chunksize : 65536 KB Driver Mode(s) : STARTED ENABLED GUESTCTL [Storage Interface Details] Guest Device type
9.3 Creating Guest Administrators and Operators Integrity VM provides secure access to guest machine consoles. When you create the virtual machine, you can specify groups and user accounts to have administration or operator privileges on that guest. These users are allowed to log in to the VM Host under their own user accounts and to use the hpvmconsole command to perform system administration tasks on the guest virtual machine.
# passwd host1 3. Use the hpvmmodify command to provide the user with guest administration privileges: #hpvmmodify -P winguest1 -u host1:admin A guest administrator can now access the host1 virtual console by using the ssh command or telnet command on the VM Host and logging in to the host1 account. The guest administrator cannot use the su command. NOTE: For security reasons, HP strongly recommends that you do not include /opt/hpvm/ bin/hpvmconsole, the virtual console image, in /etc/shells.
Figure 9-1 Installing Guest Management Software HP-UX VM Guest HP-UX Windows Software Software Installation Media HP-UX Guest Software Windows VM Guest Windows Guest Software Guest Management Software Repository Real VM Host The guest management software is required on each guest. The guest management software ensures that guests have the required patches for optimum performance and manageability. It also enables the hpvmmgmt, hpvmcollect, and hpvminfo commands on the guests, as appropriate.
software updates that you should also install on your guests, see the HP Integrity Virtual Machines 4.2: Release Notes. 9.5 Using the Virtual Console Each virtual machine has its own virtual console from which to power on or off the virtual machine, boot the guest operating system or shut it down, and so on. The hpvmconsole command connects to the virtual console of a specified virtual machine.
Table 9-2 Options to the hpvmconsole Command Option Description -P vm-name Specifies the name of the virtual machine console to open. -p vm-number Specifies the number of the virtual machine console to open. -c command Specifies a machine console command to run on the virtual machine. -e echar Specifies an alternate interrupt character. The default interrupt character is Ctrl/B. -f Follows the console output after reaching EOF on standard input. Used for scripting. -i Interacts with the console.
9.7.1 Managing Dynamic Memory from the VM Host On the VM Host, the dynamic memory software is included with Integrity VM. Manage dynamic memory on the VM Host using the -x option with the hpvmcreate, hpvmmodify, or hpvmclone command. The -x option associates a variety of configuration parameters with the guest, including dynamic memory and network management for the guests. Table 9-3 provides a complete list of -x keywords used for dynamic memory.
Table 9-3 Dynamic Memory Control Command Options (continued) Keyword Value Pair Description amr_chunk_size=amount Specifies the increment amount for changes in memory size (default is 256 MB). Larger values result in faster memory size growth. ram_target={0|start|amount} Sets the current memory size for the guest. The ram_target keyword is valid on the hpvmmodify and hpvmmgmt commands only.
Maximum memory Current memory Comfortable minimum Boot memory Free memory Available memory Memory pressure Memory chunksize Driver Mode(s) : : : : : : : : : 6144 MB 2103 MB 2167 MB 6135 MB 125 MB 286 MB 0 65536 KB STARTED ENABLED . . . Table 9-4 describes the dynamic memory characteristics displayed by the hpvmstatus and hpvmmgmt commands.
Table 9-4 Dynamic Memory Characteristics (continued) Characteristic Setting Description Available memory valueM (for megabytes) or valueG (for gigabytes) Amount of memory in the guest allocated by user processes but not locked. This memory is available for paging. Memory pressure value A value between 0 and 100 used as an indicator of memory deficit and paging. The higher the number the longer the system has been in a memory deficit.
Table 9-5 Options to the hpvmmgmt Command (continued) -v Displays the version number of the hpvmmgmt command. -V Displays detailed information (verbose mode) about the virtual machines. -M Displays verbose attribute and resource information in a machine-readable format. -X Displays verbose attribute and resource information in the XML format.
9.7.3.1 Dynamic Memory Restrictions Use of dynamic memory is subject to the following restrictions: • • • • The size of a virtual machine cannot be increased above its original boot size (as specified with the -r option). If the virtual machine memory has become fragmented , attempting to reduce the size of the virtual machine might fail or might take a very long time. If you cannot reduce the size of the virtual machine to the desired size, abort the operation by setting a new target size.
# hpvmstatus -V -P host1 . . . [Dynamic Memory Information] Type : driver Minimum memory : 1222 MB Target memory : 2103 MB Maximum memory : 6144 MB Current memory : 2103 MB Comfortable minimum : 2167 MB Boot memory : 6135 MB Free memory : 0 MB Available memory : 286 MB Memory pressure : 100 Memory chunksize : 65536 KB Driver Mode(s) : STARTED ENABLED . . . An indication of this problem is a small or zero amount of free memory and a large memory pressure value (100).
hpvmmgmt: Unable to continue. # hpvmmgmt -x ram_target=2048 Failed to open dynamic memory driver, error: No such device. Failed to set dynamic value error: No such device hpvmmgmt: Unable to continue. For information about installing the guest management software, see Section 4.4 (page 68). 9.7.3.7 Upgrade the Guest Kit When Upgrading Integrity VM The dynamic memory software has two components: the VM Host support and the HP-UX guest support.
The value of HPVMAMRCHUNKSIZE is the default number of MB by which the guest attempts to grow when it encounters memory pressure. The higher this value is, the more quickly a VM attempts to grow when it encounters memory pressure. HP recommends that chunk-size values be a multiple of the dynamic memory chunk size. For a description of dynamic memory chunk size, see Section 9.7.1 (page 152).
Percent Cumulative Virtual Machine Name VM # #VCPUs Entitlement Maximum Usage Usage ==================== ===== ====== =========== ======= ======= ================ guest0 1 2 10.0% 100.0% 2.0% 21637 guest1 2 2 10.0% 100.0% 2.5% 28863 linux0 4 2 10.0% 100.0% 0.8% 10318 win0 6 2 10.0% 100.0% 0.
9.9.2 Using the hpvmdevmgmt Command To list and modify the devices used by the VM Host and the virtual machines, use the hpvmdevmgmt command. Table 9-6 describes the options to the hpvmdevmgmt command. Table 9-6 Options to the hpvmdevmgmt Command Option Description Lists an entry. To list all entries, enter the following -l {server|rdev|gdev}:entry_name:attr:attr_name=attr_value command: # hpvmdevmgmt -l all -v Displays the version number of the hpvmdevmgmt output format.
For example, to make the HP-UX iso.* images shareable so that two virtual machines (host1 and host2) can use them to install at the same time, enter the following commands: # hpvmdevmgmt -m gdev:/var/opt/hpvm/ISO-images/hpux/:attr:SHARE=YES # hpvmmodify -P host1 -a dvd:scsi::null:/var/opt/hpvm/ISO-images/hpux/ # hpvmmodify -P host2 -a dvd:scsi::null:/var/opt/hpvm/ISO-images/hpux/ Virtual DVDs and virtual network devices can be shared. DVDs are not shareable unless you specify otherwise.
9.9.3 Inspect and Edit the Repair Script The hpvmdevmgmt -r report and repair-script function might identify one or more new pathnames for disks whose old pathnames no longer exist. The repair-script performs that reassignment using the hpvmdevmgmt -n command. In general, you should inspect and edit the script before running it for the following reasons: • All replace commands, hpvmdevmgmt —n, in the script are commented out.
10 Migrating Virtual Machines There are several different forms of Virtual Machine migration. With the hpvmmigrate command, you can move either an offline virtual machine or a live, online virtual machine running a guest operating system and applications from a source VM Host system to a target VM Host system. For offline migration, the hpvmmigrate command has been available with HP Integrity Virtual Machines Version 1.2 and later.
Figure 10-1 Symmetric Hosts Configured for Guest Migration The basic virtual machine migration environment includes a source machine and a target machine. Both must be running Integrity VM and must be able to run the guests. Both machines must conform to their operating system requirements and restrictions, and both must be able to provide the allocated resources to the guest. If the guest uses 2 GB of memory on one machine, it must be able to use that amount on the other machine.
Figure 10-2 Online Guest Migration from Source to Target Guest continues to operate on source host while migration begins app1 Guest is briefly suspended as final resident memory image transfers Guest continues operation on target server after transfer completes app1 app2 app2 Guest OS Guest OS Guest OS with unique: Kernel Parameters Patch levels Layered software SAN Source Host (Intergrity VM and HP-UX) - Target Host (Intergrity VM and HP-UX) 10.1.
You might want to segregate guests to balance the workload on VM Hosts workloads. For example, you might want to separate guests whose workloads peak simultaneously. Or, perhaps you want to group workloads together that have similar special resource requirements. For example, you would usually run your multi-threaded applications on a VM Host that has several CPUs in order to maximize the effectiveness of multi-way virtual machines.
5. 6. If migrating the guest offline, restart the guest on the target host using the hpvmstart or hpvmconsole command. You can also use the hpvmmigrate -b option with an offline migration to automatically restart the guest on the target. If you do not use the hpvmmigrate -D option to remove the virtual machine configuration on the source VM Host, it is marked Not Runnable, and it is configured with all its devices. This protects the storage from unintended use by Integrity VM commands.
Specify the guest using one of the following options: • • -P source-vm-name to specify the guest name -p source-vm_number to specify the virtual machine number Specify the target host by including the –h option and specifying one of the following: • • Target host alias for the private, high-speed network connection Target host IP address of the private, high-speed network connection NOTE: If you migrate a virtual machine that is being managed by ID-VSE, use Capacity Advisor to collect utilization data b
Table 10-1 Options to the hpvmmigrate Command (continued) Option Description -F Forces the migration of a virtual machine, whether or not there are resource validation errors (such as resource conflict, resource nonexistence, and so forth). . Use the -F option rarely and with caution. This option ignores all resource validation errors, including oversubscribing of resources. NOTE: These errors can prevent the virtual machine from booting on the target VM Host.
Table 10-1 Options to the hpvmmigrate Command (continued) Option Description -p source-vm-number Specifies the unique number of the virtual machine to be migrated. To display the source-vm-number, enter the hpvmstatus command. Most forms of the hpvmmigrate command require either the -p option or the -P option. -P source-vm-name Specifies the unique name of the virtual machine to be migrated. Most forms of the hpvmmigrate command require either the -p option or the -P option.
This example specifies: • • The name of the guest (-P VM1) The name of the target host (-h HostB) Online Migration Example The Online VM Migration feature is initiated with the -o option to the hpvmmigrate command. The following example migrates a guest to another VM Host. The guest name is vm3. The target VM Host is called host2, and the target VM Host's private network is called host2–hpvm-migr (that is, host2–hpvm-migr is an alias for the private network defined in /etc/hosts).
NOTE: The Online VM Migration feature is not supported for a guest running as a Serviceguard node. Therefore, disable online migration for all guests that are Serviceguard nodes. For example: # hpvmmodify -P sg_node1 -x online_migration=disabled The Online VM Migration feature is supported with Serviceguard packaged guests. For more details, see Section 10.4 (page 181). 10.2.
synchronization is strongly recommended on all VM Hosts and guests to maintain consistent time accuracy. 10.3.1 VM Host Requirements and Setup The VM Hosts must be configured with Integrity VM Version 4.2 or later. All the latest HP-UX patches required by Integrity VM, as well as any required Integrity VM patches for Integrity VM, should be installed. Consult the most recent HP Integrity Virtual Machines Release Notes, available from http://docs.hp.com/en/vse.
8 logical processors (2 per socket) Vendor identification: GenuineIntel Processor version info: 0x0000000020000704 Family 32, model 0, stepping 7 Processor capabilities: 0x0000000000000005 Implements long branch Implements 16-byte atomic operations . . . 10.3.1.2 Private Network Setup Source and target VM Host systems should be connected with a dedicated, high-speed private network.
security. Also, a high-speed, private network helps ensure efficient online migrations and preserves the bandwidth and performance of the site network. You can also use the nwmgr command to help verify the connection.
10.3.1.4 Using NTP on VM Hosts Using NTP to synchronize clocks is strongly recommended for Online VM Migration environments. In addition to a typical NTP configuration, all the potential VM Hosts should use each other as mutual peer NTP servers to help maintain time consistency between hosts. 10.3.2 SSH Setup Between the VM Hosts Only superusers can execute the hpvmmigrate command. The migration of a guest is controlled by a set of secure remote operations that must be enabled on both systems.
10.3.2.2 Using a Third-Party SSH The HP-UX native SSH is assumed. To use an incompatible SSH command with the hpvmmigrate command, make sure your version of SSH is set up for host-based authentication without requiring interactive passwords. Then set the SSHEXECPATH environment variable (in /etc/rc.config.d/hpvmconf) to invoke a command or shell script similar to the one provided in alt_ssh_example.
• • • • migrate_init_phase_timeout — Specifies the maximum number of seconds the online migration spends during the initialize phase of the migration. The default is 10 seconds. migrate_copy_phase_timeout — Specifies the maximum number of seconds the online migration spends during the full-copy phase. The default is infinite. migrate_io_quiesce_phase_timeout — Specifies the maximum number of seconds the migration spends during the quiesce phase. The default is 15 seconds.
10.3.3.5 Marking a Guest Not Runnable On all VM Hosts that have a virtual machine configured, the virtual machine should be marked Runnable on only one VM Host at a time. While migrating online guests, unexpected errors or guest resets or aborts should not cause your guest to be marked Runnable or Not Runnable incorrectly. To verify the Runnable state of a virtual machine, use the hpvmstatus command to see that the guest is Runnable on only one VM Host and Not Runnable on all other VM Hosts.
# hpvmsg_move -n node2 ogmlin The Integrity VM V4.2 hpvmsg_move command disables the package before migrating the guest and re-runs the package after migration is finished. Therefore, the packaged guest is not protected by Serviceguard while migration is in progress. A guest configured as a Serviceguard package is not protected by Serviceguard while the migration is in progress.
0 ) Return 3 - Manage O.S. Images ====================================== Function not implemented yet To migrate a workload, follow these steps: 1. Set the location of the depots to use in installing the application. Select menu 1, option 1 and then enter the fully qualified depot path in either the form accepted by the SD products or as alocal directory. The location must be a registered depot source. For example, to specify depsrv.hp.com:/release/1123.
gcc gdbm . . . hpuxwsAPACHE hpuxwsTOMCAT hpuxwsWEBMIN hpuxwsXML . . . vim xpm zlib 3. 4.2.0 1.8.3 gcc gdbm B.2.0.55.03 B.5.5.9.04 A.1.070.07 A.2.00 HP-UX HP-UX HP-UX HP-UX 7.0 3.4k 1.2.3 vim xpm zlib Apache-based Web Server Tomcat-based Servlet Engine Webmin-based Admin XML Web Server Tools Enter the applications to be migrated. Select menu 2, option 2 (Manage Applications - Select Applications). Enter the application names noted in the previous step, as a space-separated list.
1 ) List Applications 2 ) Select Applications 3 ) Add Data Directories/Files 4 ) Consolidate Applications ----0 ) Return Enter Option Number: 3 Please enter the list of directories/files to be transferred to the target system, separated by spaces.
Transferring Configuration files... Checking application disk space... Transferring /opt/hpws/apache directory Transferring /opt/hpws/tomcat directory Transferring /opt/hpws/webmin directory Application Sucessfully consolidated on to vmp2v, please wait... to vmp2v, please wait... to vmp2v, please wait... host: vmp2v Press to return to menu: 10.5.
11 Using HP Serviceguard with Integrity VM After you install Integrity VM and create the guest, you can install HP Serviceguard on either the VM Host system (to provide failover for the guest), or on the guest (to provide failover for applications running on the guest). This chapter describes how to configure Serviceguard with Integrity VM and assumes you are familiar with HP Serviceguard. The procedures in this chapter use the HP Serviceguard commands to accomplish Serviceguard tasks.
VMs as Nodes), HP-UX virtual machines are used as actual Serviceguard cluster nodes to provide the same HA failover capabilities found in traditional Serviceguard cluster configurations. Essentially, you can use Integrity VM to consolidate Serviceguard clusters on to virtual machines.
Figure 11-2 Guest Application Failover to Another Guest on the Same VM Host Guest VM1 Serviceguard Cluster Serviceguard Package Failover Guest VM2 Physical Node 1 VM Host 1 In this configuration, the primary node and the adoptive node are guests running on the same VM Host system. This cluster does not provide protection against single point of failure (SPOF), because both the primary cluster member and the adoptive cluster member are guests on the same physical machine.
11.2.4 Usage Considerations VMs as Serviceguard Nodes configurations should be considered whenever there is a need for consolidating systems in Serviceguard clusters, and the applications require full HA monitoring and failover functionality that is provided by Serviceguard. These configurations allow for a reduction in the total number of physical systems required for clusters by moving cluster nodes from individual physical systems to multiple VMs running on single systems.
memory, in addition to storage and network I/O connections, to handle their workloads. Any initial performance problems with a virtual machine can be compounded when application workloads are failed over to it by Serviceguard in response to a failure in one of the other cluster members. 11.2.6 Availability Integrity VM instances are not highly available in VMs as Nodes configurations. A failure of a VM is similar to a node failure in a Serviceguard cluster.
• • Guest OS boot disks can be of any backing-store type; however, shared storage, the storage used by the application on the guest that is accessed from more than one virtual machine, can be only whole disk or SLVM. DVD and tapes devices can be defined on one or more VM and are typically ignored by Serviceguard. For additional information about excluding a Device from probing, see the Managing Serviceguard manual. 11.2.
NOTE: APA is not supported in the VM guest, and primary and secondary LAN failover is not provided in the VM Host. 2. 3. On each of the VM Hosts, use the hpvmnet command to create vswitches. Create the storage configuration on each of the VM Hosts and physical Serviceguard Nodes. • System disk storage for physical nodes, as well as VM nodes, can be of any type support by Serviceguard and Integrity VM.
Serviceguard and all of its processes, packages, and applications are running as a cluster in the guest, just as Serviceguard considers the virtual machine environment as an alternative platform type. Even with its independent management focus, you should consider certain interaction between the virtual machine and Serviceguard environment.
• • • • In the case of LAN failure, Serviceguard switches to a standby LAN or moves affected packages to a standby node. In the case of SPU failure, your application is transferred from a failed SPU to a functioning SPU automatically and in a minimal amount of time. For failure of other monitored resources, such as disk interfaces, a package can be moved to another node. For software failures, an application can be restarted on the same node or another node with minimum disruption.
Dynamic memory is an optional feature of Integrity VM that allows you to change the amount of physical memory in use by a virtual machine without rebooting the virtual machine. In VMs as Serviceguard Package configurations, the virtual machines can be configured with differing dynamic memory configurations on different Serviceguard nodes. If you plan to use the dynamic memory feature, you should understand how it might impact your virtual machine configurations and failover strategy.
The Integrity VM toolkit script, hpvmsg_package, is used to create Serviceguard package configuration file and control script templates for the VMs to be protected by Serviceguard packages. This script is designed to determine the cluster-shared backing store and application data storage used by the VM guest to be packaged and adds the appropriate logical volume and mount point entries into the package control script for guest failover. 11.3.
d. e. Configure the lock disk or quorum server. Configure storage: LVM, shared LVM, VxVM, and file systems. 2. On the primary node, perform the following steps: a. Run the cmquerycl command to create Serviceguard ASCII configuration file. b. Edit configuration file to insure that the cluster name, networks usage, LVM devices, and lockdisk or quorum server are correct. c. Run the Serviceguard command cmcheckconf to check the configuration and cmapplconf command to apply the configuration file. d.
11.3.8 Managing the Package with Serviceguard Commands After the virtual machine has been packaged, it is managed as a Serviceguard package using Serviceguard comamnds. Many of the Integrity VM commands are aware of this packaging and no longer function in the same manner as they did prior packaging. You can use any of the available Serviceguard tools the Serviceguard Manager or the command-line tools to manage basic package functionality.
the package should be repacked using the hpvmsg_package command, and then re-applied using the cmapplyconf files as previously outlined. Maintenance Mode is enabled only on the local node, and when enabled, will periodically note that it is enabled for each VM in the system syslog file. In the event that the Serviceguard node on which the VM is running fails during maintenance mode, the VM package will be failed over to a secondary node.
11.5 Migrating VMs That are Using Logical Volume Backing Stores Integrity VM now supports the migration of virtual machines that are using LVM logical volume (lvol) backing stores configured with avio_stor, also known as shared LVM (SLVM). To enable SLVM functionality, Serviceguard A.11.19 and patch PHSS_40152 must be installed on the VM Host systems. In addition, for virtual machines using avio_stor adapters, version B.11.31.0910.01 of the HostAVIOStor software bundle must be installed.
a. On the initial VM Host, deactivate the VG: # vgchange -a n /dev/vgsharedA b. Export the LVM definition for the VG: # vgexport -v -p -s -m /tmp/vgsharedA.map /dev/vgsharedA Beginning the export process on Volume Group "/dev/vgsharedA". /dev/disk/disk15 vgexport: Preview of vgexport on volume group "/dev/vgsharedA" succeeded. c. d. Copy (for example, with ftp or rcp) the map file to all the other VM Hosts.
HPVM_VOLUME_GROUP HPVM_VOLUME_GROUP # NOTE: f. /dev/vgmobileG /dev/vgsharedA Each SLVM volume group being used by Integrity VM must have an entry. Check the cluster: # cmcheckconf -k -v -C /etc/cmcluster/creekQuorumRiver.cfg Begin cluster verification... Checking cluster file: /etc/cmcluster/creekQuorumRiver.cfg Defaulting MAX_CONFIGURED_PACKAGES to 300. Checking nodes ...
5. Install HostAVIOStor bundle. If you plan to migrate VMs using logical volumes with avio_stor adapter, install a new HostAVIOStor bundle on all VM Hosts. You do not need to install this bundle if your VMs use the legacy VIO scsi adapters. # swinstall -s depot-location HostAVIOStor 6. Troubleshooting The following problems might occur: • The hpvmmigrate fails with a message “Online migration requires only disk or null backing stores.
# ls # cmmakepkg -m sg/multi_node -m sg/volume_group > hpvm_vgsharedA.conf Package template is created. This file must be edited before it can be used. # 2. Edit the configuration file, making the following modifications: a. Provide the package with a name (for example, hpvm_vgshareA). b. Change the vgname_cmd to vgchange -a s. c. Add the vg name for the SLVM volume group.
... Modify the package configuration ([y]/n)? y Completed the cluster update e.
— of the HEARTBEAT_INTERVAL parameter is entered in microseconds; the default value is 1,000,000 microseconds. Setting the value of this parameter to less than the default is not recommended. The default should be used where possible. The maximum value recommended is 15 seconds, and the maximum value supported is 30 seconds. This value should be at least half the value of the NODE_TIMEOUT parameter.
12 Reporting Problems with Integrity VM Report Integrity VM defects through your support channel. Follow these instructions to collect data to submit with your problem report. 1. Run the hpvmcollect command to gather information about the guest before modifying any guest. Preserve the state of the VM Host and Integrity VM to best match the environment when the VM Host failed. If multiple guests are running, run the hpvmcollect command for guest that was running at the time. 2. 3. 4.
Table 12-1 Options to the hpvmcollect Command on the VM Host (continued) Option Description -f Forces an archive to be overwritten, if it exists, rather than renamed with an appended time stamp. -h Displays the help message for the hpvmcollect command. -l Leaves the collected information in a directory rather than in an archive file. The directory name follows the same naming convention as the archive name. -g Deletes old guest memory dump data as part of data collection.
Collecting command logs ............................................. OK Collecting messages from vmm ........................................ OK Collecting lv info .................................................. N/A Collecting vgdisplay info ........................................... OK Collecting vxprint info ............................................. OK Collecting disk info ................................................ N/A Collecting passthru disk info .......................................
Table 12-2 Options to the hpvmcollect Command on Guests Option Description -c Includes the latest crash dump directory in the archive. This option is used if the guest or the VM Host fails or hangs. -f Forces an archive to be overwritten, if it exists, rather than renamed with an appended time stamp. -g Deletes old guest memory dump data as part of data collection. -h Displays the help message for the hpvmcollect command.
an empty one is created for the new log. To allow this log file to increase to 102400 KB, include the following line in the /etc/rc.config.d/hpvmconf file: VMMLOGSIZE=102400 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 5052 # kill -HUP 5052 12.
A Sample Unattend.xml File The following example contains an unattend.xml template for use when installing the Microsoft Windows Server 2008 guest using RTM media. PAGE 216 *MachineName* Administrator Abcdef12 WORKGROUP
