HP Integrity Virtual Machines 4.3: Installation, Configuration, and Administration HP Part Number: T2767-91006 Published: March 2011 Edition: 9.
© Copyright 2011 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.....................................................................
2.8 Troubleshooting Installation Problems...........................................................................................44 2.8.1 Error Messages During Installation........................................................................................44 2.8.2 Warning During Startup if HP SIM is Installed......................................................................45 3 Creating Virtual Machines..........................................................................................
6.1.1.1 Storage Utilization...........................................................................................................83 6.1.1.2 Storage Availability.........................................................................................................83 6.1.1.3 Storage Performance.......................................................................................................83 6.1.1.4 Storage Security..................................................................................
.3.2.3 Modifying VM Storage Devices....................................................................................118 7 Creating Virtual Networks........................................................................................123 7.1 Introduction to Virtual Network Configuration...........................................................................123 7.2 Creating and Managing vswitches................................................................................................124 7.2.
8.7 Using the Virtual Console.............................................................................................................155 8.8 Using the virtual iLO Remote Console..........................................................................................157 8.8.1 Configuring, Deleting, and Obtaining Status of a virtual iLO Remote Console..................157 8.8.2 Integrity VM virtual iLO Remote Console Limitations........................................................158 8.
9.3.2.4 Using NTP on VM Hosts...............................................................................................190 9.3.3 SSH Setup Between the VM Hosts........................................................................................190 9.3.3.1 Troubleshooting SSH Key Setup...................................................................................190 9.3.3.2 Using a Third-Party SSH...............................................................................................191 9.
11 Reporting Problems with Integrity VM....................................................................223 11.1 Collecting Integrity VM Data......................................................................................................223 11.1.1 Using the hpvmcollect Command on the VM Host............................................................223 11.1.2 Using the hpvmcollect Command on Guests..................................................................226 11.
List of Figures 1-1 2-1 6-1 6-2 6-3 6-4 6-5 7-1 7-2 8-1 9-1 9-2 10-1 10-2 10-3 10-4 10 Hardware Consolidation Using Integrity VM..............................................................................17 Upgrade Procedure.......................................................................................................................34 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 7-1 7-2 8-1 8-2 8-3 8-4 8-5 8-6 8-7 9-1 9-2 9-3 9-4 11-1 11-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.3: 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.
• • Manpages: “Integrity VM Manpages” (page 237) lists the HP-UX manpages provided with the HP Integrity VM software. Glossary : “Glossary” (page 365) defines important terms used in the Integrity VM documentation. Related Information You can download the latest version of this document from Business Support Center Manuals.
HP Care Pack Service or HP contractual support agreement. HP Insight Remote Support supplements your monitoring, 24x7 to ensure maximum system availability by providing intelligent event diagnosis, and automatic, secure submission of hardware event notifications to HP, which will initiate a fast and accurate resolution, based on your product’s service level. Notifications may be sent to your authorized HP Channel Partner for on-site service, if configured and available in your country.
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.
• • • • • • Multiple Accelerated Virtual Input/Output (AVIO) LAN localnet support — Allows the creation of multiple instances of localnet 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. See Section 6.2.2.4 (page 112). Hyperthreading no longer needs to be turned off in the Integrity VM Host before installing or using Integrity VM.
[Storage Interface Details] Guest Device type Guest Adaptor type Bus Device Function Target Lun Physical Storage type Physical device :disk :avio_stor :0 :0 :0 :3 :0 :disk :/dev/rdisk/disk2 [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-
• • Burner Changer Null for non-DVD devices is not supported. NOTE: In general, AVIO devices (that is, avio_lan, aviolan, avio_stor, or aviostor) are configured and managed the same as VIO devices (that is lan and scsi). However, some additional Integrity VM command options and limitations on backing devices are noted throughout this document.
• • • • • System performance monitoring tools (GlancePlus, Measureware, OpenView Operations Agent) Utility pricing tools (Instant Capacity, Pay per use) Hardware management tools (nPartition Manager, storage and network management tools) Multipath storage solutions HP Serviceguard (which can be run on HP-UX guests as well). Regardless of whether guests are running, do not run other applications on the VM Host system.
supported versions. Install the backup (client) agents on the VM Host and the guests. HP highly recommends that the /var and /opt directories, in addition to the standard locations, be backed up regularly on the VM Host system. Do not use the VM Host system as a backup server. For more information, see the HP-UX 11i v2 Installation and Update Guide. • Using HP GlancePlus/iX to monitor guests You can use Glance on the VM Host to monitor guest data, but recorded measurements can be misleading.
— HP System Management Homepage (SMH). For more information about using Integrity Virtual Machines Manager under SMH, see the HP Integrity Virtual Machines Manager Version 4.0 Getting Started Guide. — HP Insight Dynamics — VSE Management Software environment in the HP Systems Insight Manager (SIM) on the Central Management Server (CMS). For more information about Insight Dynamics — VSE, see the HP Insight Dynamics 6.0 Getting Start Guide on the BSC website: http://bizsupport2.austin.hp.
storage tab. Persistent device files and LUN hardware paths are displayed in the physical storage device representations (boxes). • Using HP Instant Capacity with Integrity VM You can use HP Instant Capacity solutions on the VM Host system as you would on any other HP-UX system. 1.7 Attributes That Can Be Changed Dynamically A dynamic change does not require a reboot of the guest in question. The following attributes can be changed dynamically: • CPU — Adding or removing guest vCPU entitlement.
• • • • 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. HP Integrity VM Providers — To manage Integrity VM guests with VM Manager, gWLM, or any ID-VSE components, install the appropriate provider software from the operating system media or the Integrity VM guest management software kit.
• • • • • • • • • hpvmsar(1M) — Displays performance information about one or several guests on the same host. hpvmsg_move(1M) — Describes how to initiate an online migration (move) of a virtual machine that has been associated with a Serviceguard package. 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.
Table 1-1 Chapters in this Manual (continued) Chapter Read if... Chapter 7: “Creating Virtual Networks” (page 123) 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 8: “Managing Guests” (page 143) You need to manage existing virtual machines and resources. Chapter 9: “Migrating Virtual Machines” (page 175) You need to move virtual machines or active guests from one system to another.
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.3” “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.3 (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.
• • • • • • • VMGuestSW — B.04.30 Integrity VM Guest Support Software VMProvider — B.04.30 WBEM Provider for Integrity VM, which allows you to use the HP Integrity VM Manager to manage the VM Host VMVirtProvider — B.04.30 Integrity VM Virtualization Provider, which provides support for logical servers to manage Integrity VM Hosts and guests. VMKernelSW — B.04.
NOTE: Installing the Integrity VM software requires the system to reboot. Therefore, the swinstall command line installation includes the autoreboot=true parameter. To install the HP Integrity VM software, follow these steps: 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.
are running or not. Table 2-2 lists the kernel parameters that are modified when you install Integrity VM. Table 2-2 Kernel Parameters Parameter Default Value Modified Value 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 and later support both 4KB (default) and 64KB settings for the base_pagesize tunable.
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 7.
NOTE: If you plan to perform a cold install, follow these steps: 1. Offline migrate all virtual machines to another VM Host, for example, system X (which has shared access to the storage). 2. Remove all virtual machines using the hpvmremove command. 3. Back up the /var/opt/hpvm directory. 4. Perform the cold install of HP-UX only, restarting the system. (Step 6 in the flowchart) 5. Restore the /var/opt/hpvm directory. 6. Install the Integrity VM. (Step 7 in the flowchart) 7.
NOTE: Dynamic Root Disk (DRD), an HP-UX system administration toolset, is available to clone an HP-UX system image to an inactive disk for software maintenance or recovery. The bundle name is DynRootDisk and the product name is DRD. Administrators can use DRD to reduce downtime for system maintenance by creating an inactive clone of the booted system, then applying patches and products to the clone. The modified clone can then be booted at a convenient time.
/var/adm/msv2v3check/mmddyy_hhmm is the full log file that contains all notes, warnings, and error messages from an invocation of msv2v3check, where mmddyy_hhmm represents the month, day, year, hours and minutes at the time the msv2v3check utility was started.
1. 2. When your 11i v2 Integrity VM server is running at peak load, use the Integrity VM hpvmstatus –s command to display the available memory. If the available memory is less than 1 GB, then it is highly likely that your server requires additional memory to run the same load with 11i v3 and Integrity VM V4.3. Before upgrading, add the appropriate amount of memory to ensure that there is at least 1 GB of memory available during peak loading.
Table 2-3 lists the HP-UX 11i v2 to HP-UX 11i v3 supported OE server upgrades. Table 2-3 Supported Operating Environments Original 11i v2 Operating Environments New 11i v3 Operating Environments Foundation OE Base OE Technical Computing OE Base OE Enterprise OE Virtual Server OE Mission Critical OE Data Center OE 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.
2.3.4 Perform Required Hardware and Firmware Upgrades Perform all hardware and firmware upgrades that are supported on 11i v2 and that are needed for 11i v3 while still running on 11i v2. This allows the administrator to verify that all guests are fully functional with the changes before upgrading to 11i v3. Read the following information: • Hardware Specific Information • System Firmware Support Matrix • Ethernet System Driver Support Matrix • HP 9000 and HP Integrity Server Connectivity/ 2.3.
12. Install all 11i v3 compatible layered products that are required for equivalent functionality to the 11i v2 VM Host. 13. Install Integrity VM Version 4.3 to the 11i v3 VM Host. NOTE: See Section 2.1.2 (page 30) for a list of products that block the Integrity VM installation. 14. Stop Integrity VM using /sbin/init.d/hpvm stop. 15. Using the appropriate recovery tool, restore the 11i v2 /var/opt/hpvm directory over the existing 11i v3 /var/opt/hpvm directory on the 11i v3 VM Host. 16.
1. 2. 3. 4. 5. Use the hpvmupgrade utility to see whether any guests have configuration problems. Start and stop each guest, one at a time, and make sure that they boot to their OS. Use the guest troubleshooting section, Chapter 11 (page 223), to resolve guest booting problems. Upgrade each guest with the new guest kit. If the guest OS is no longer supported, upgrade the guest OS. NOTE: When Integrity VM is stopped either with the /sbin/init.
Once you have read the product release notes and verified that you have met the system requirements as described in Section 2.1.1, install the Integrity VM software as described in this section. NOTE: Installing the Integrity VM software requires the system to reboot. Therefore, the swinstall command line installation includes the autoreboot=true parameter. To install the HP Integrity VM software, follow these steps: 1. If you have the installation media, mount it.
VMGuestSW VMKernelSW B.04.30 B.04.30 Integrity VM Guest Support Software Integrity VM Kernel Software When you install Integrity VM, the file /etc/rc.config.d/hpvmconf is created to record the product configuration. Note, HPVMNETINTVL has been removed from this file. 2.
2.8.2 Warning During Startup if HP SIM is Installed Integrity VM generates a warning during startup if HP SIM is installed, but Integrity VM continues to start. The HP SIM product consumes memory and CPU resources that would otherwise be available for running virtual machines. The amount of memory and CPU consumed varies depending on the specific system configuration. On systems that are already tight on memory or CPU resources, this might cause virtual machines to fail to start. 2.
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.
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 may not have the desired effect. You can change the number of enabled CPUs in HP-UX guests, using the hpvmmgmt –c num command.
virtual machine. This allows you to create virtual machines for future configurations. When the virtual machine is started, the VM Host checks memory resources, including those allocated to running guests, and makes sure that there is sufficient memory to run the virtual machine. In 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.
Each guest can have two different types of LAN network devices, VIO and AVIO. For VIO guest networks, a vswitch functions just like a physical network interface card (pNIC), accepting network traffic from one or more virtual machines and directing network traffic to all of its ports. A vswitch without the backing of a host physical network card can be used by VIO guest devices for communication among VIO guest devices registered with the same vswitch.
NOTE: If the guest is configured with a number of VLAN devices, but it does not have sufficient memory, some of the devices might be missing after the guest is booted. To resolve this issue, increase the size of the guest memory with the hpvmmodify -r command. If you configure an HP-UX guest and an OpenVMS guest with the same vswitch, the network communication between these guests fail. This problem will be fixed in a future version of OpenVMS.
— — null attach And location is a VM Host system file. For complete information about constructing storage specifications for virtual machines, see Section 6.2.2.1 (page 101). The type of VM Host backing store can affect the performance of the virtual machine. Use the ioscan command to obtain information about the current device configuration on the VM Host system, and try to distribute the workload of the virtual machines across the physical backing stores.
0xe000000200024588 0xe000000200043570 0xe0000000012ef860 cec_cfg_inX+0xd0 0xe000000200024560 0xe000000200043570 0xe000000001306650 cec_cfg_in16+0x30 0xe000000200024538 0xe000000200043570 0xe00000000158d0a0 gh2p_rd_cfg_w+0x60 0xe000000200024508 0xe000000200043570 0xe0000000021d3f10 wsio_cfg_in16+0x70 BSP SP IP 0xe000000200024460 0xe000000200043570 0xe00000012f7313a0 mpt:mpt_handle_chip_fault+0xe0 0xe0000002000243e8 0xe000000200043580 0xe00000012f730fe0 mpt:mpt_ch_task_mgmt+0x540 0xe0000002000243a8 0xe0000002
A rough estimate of the processor weight calculation is: (minimum guest cpu entitlement * number of virtual processors) / (100 * number of host processors) Guests are expected to start in order of highest weight to lowest. You can adjust the order by setting the sched_preference attribute (Section 3.2.6). If a guest fails to start for any reason, the sequence continues with the next guest.
Table 3-3 Configuration Limits (continued) Description Support Memory per VM — Maximum (HP-UX) 128 GB # virtual SCSI devices / VM — Maximum 256 AVIO + 30 VIO # virtual NICs / VM — Maximum 62 # virtual switches — Maximum 50 # virtual NICs / vswitch 511 # virtual AVIO storage devices / VM — Maximum 128 # file backing store devices / VM — Maximum 30 # virtual AVIO storage devices VM Maximum 256 # file backing store devices VM Maximum 30 Maximum size of backing store for VIO (disk, lvol, fil
1 The minimum memory requirement for HP-UX 11i v2 is 512 MB. The minimum memory requirement for HP-UX 11i v3 is 1 GB (see "System Requirements" section in the HP-UX 11i v3 Installation and Update Guide); however, the HP-UX 11i v3 Installation and Update Guide warns that cold installations with 1 GB or less memory might fail or take a long time to complete. Therefore, 2 GB is recommended for cold installations of HP-UX 11i v3.
Table 3-5 Options to the hpvmcreate Command (continued) Option -x keyword=parameter Description Specifies values for dynamic memory setting associated with the guest, including: • dynamic_memory_control • ram_dyn_type • ram_dyn_min • ram_dyn_max • ram_dyn_target_start • ram_dyn_entitlement=amount • amr_enable={0|1} • amr_chunk_size=amount • sched_preference • graceful_stop_timeout For more information about dynamic memory, see Section 8.10 (page 159).
Table 3-5 Options to the hpvmcreate Command (continued) Option Description -K console_IP_Addr Specifies the IP address used to connect to the guest's virtual iLO Remote Console. The address must be specified in IPv4 dot notation or 0. If 0 is entered, then the guest will no longer have virtual iLO Remote Console access using IP.
Table 3-6 Options to the hpvmstart Command (continued) Option Description -F Suppresses all resource conflict checks and associated warning messages (force mode). Use force mode for troubleshooting purposes only. NOTE: The -F option is deprecated in Integrity VM commands; this option should be used only at the direction of HP Support. -s Sanity-checks the virtual machine configuration and returns warnings or errors, but doesn't start the virtual machine. -Q Quietly performs the command.
NOTE: When configuring or starting Integrity VM guests, the following warning message might be displayed if storage associated with the guest appears to be performing very poorly. hpvmcreate: WARNING (host): Device /dev/rdsk/c6t9d0 took 32 seconds to open. 3.5 Changing Virtual Machine Configurations You can create a virtual machine with characteristics that the VM Host cannot supply at the time of creation. This allows you to create virtual machines to run after system configuration changes.
Table 3-7 Options to the hpvmmodify Command (continued) Option Description -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 (—). -l vm_label Modifies the descriptive label for this virtual machine.
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.
Opening minor device and creating guest machine container Creation of VM, minor device 2 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 -K console_IP_Addr Specifies the IP address used to connect to the guest's virtual iLO Remote Console. The address must be specified in IPv4 dot notation or 0. If 0 is entered, then the guest will no longer have virtual iLO Remote Console access using IP.
Table 3-8 Options to the hpvmclone Command (continued) Option Description -m rsrc Modifies a virtual device that is defined on the existing virtual machine in the clone virtual machine configuration. Specify the virtual and physical device information for rsrc . For information about forming a virtual storage device specification, see Chapter 6. For information about forming a virtual network device specification, see Chapter 7. -b rsrc Specifies the boot disk for the new virtual machine.
Table 3-8 Options to the hpvmclone Command (continued) Option Description -x keyword=parameter Specifies values for dynamic memory setting associated with the guest, including: • dynamic_memory_control • ram_dyn_type • ram_dyn_min • ram_dyn_max • ram_dyn_target_start • ram_dyn_entitlement=amount • amr_enable={0|1} • amr_chunk_size=amount • graceful_stop_timeout • mac_address • sched_preference • serial_number • tunables • suspend={enable | disable} • suspend_file=delete For Online VM Migration: • • • • •
device to be physically duplicated in the cloning process. 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 guest1 5 host1 12 OS Type ======= HPUX HPUX OPENVMS 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 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. NOTE: The -F option is deprecated in Integrity VM commands; this option should be used only at the direction of HP Support. -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.
SL: VM: HE: X: 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.
EFI Boot Maintenance Manager ver 1.10 [14.62] Add a Boot Option. Select a Volume Removable Media Boot [Acpi(PNP0604,0)] Load File [Acpi(PNP0A03,0)/Pci(1|0)/Mac(763AE48F393F)] Load File [EFI Shell [Built-in]] Legacy Boot Exit The installation process continues just as if the virtual machine were an Ignite-UX client. When the basic installation process is complete, the software is copied from the distribution media to the guest's disk. Then the operating system reboots.
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 1103 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 HP OpenVMS Guests The following sections contain the release notes specific to OpenVMS guests. For information about installing OpenVMS guests, see the HP OpenVMS V8.4 for Integrity Servers Upgrade and Installation Guide at the following website: OpenVMS Documentation. 5.1 Minimum Processor Requirement for OpenVMS Guests OpenVMS guests are supported on Integrity VM Host systems with Intel® Itanium® 2 9000/9100 Series processors or later processors that OpenVMS supports natively.
************************************************************** * Exception Frame Display: * … Crash dump information follows this output. Use one of the following solutions to fix either of these issues: • Set the VM Host base_pagesize = 64K (See the base_pagesize(5) manpage for details of determining and setting the VM Host’s base_pagesize.) • Set the guest preferred pagesize to 8K: # hpvmmodify -P vm-name -x tunables=ptsz=13 5.
$! Format and print a UUID $uuid = f$getsyi("system_uuid") $len=f$len(uuid) $if (len .eq.
6 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” 6.1 Introduction to Integrity VM Storage The way you configure and manage Integrity VM storage affects the way virtual machines perform.
6.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.
6.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.
tape|changer|burner:avio_stor:bus,device,target:attach_path:new style lunpath hardware path of the attached device The following example shows the resource specifier with the avio_stor adapter: tape:avio_stor:0,4,0:attach_path:0/7/1/1.0x500104f00048b29e.0x0 In contrast, the resource specifier for the same case with the scsi adapter looks like this: tape:scsi:0,4,0:attach:/dev/pt/pt_tape1 To find the lunpath hardware path of a device, see Section 6.1.3.2.
6.1.3.3 Sharing an Attached Device Attached devices can be shared among multiple guests in a VM Host using a single physical HBA port (initiator) or multiple physical HBA ports (initiators) in the VM Host. This section describes how to share attached devices. To share a tape device, do the following: 1.
# hpvmdevmgmt -l gdev:0/4/1/1.0x500104f0004732d9.0x0 0/4/1/1.0x500104f0004732d9.0x0,lunpath4:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACHPATHLUN,AGILE_DSF= /dev/rtape/tape6_BESTn:guest2:0x01.0x00.0x03.0x500104f0004732d8_lunpath4 c. List the attributes of the parent tape DSF: # hpvmdevmgmt -l gdev:/dev/rtape/tape6_BESTn /dev/rtape/tape6_BESTn:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=NO: lunpath3,lunpath6,lunpath5,lunpath4:0x01.0x00.0x03.0x500104f0004732d8 d.
The following example shows that the second guest cannot be started: # hpvmstart -P guest2 hpvmstart: ERROR (host): Device: '0/4/1/0.0x500104f0004732da.0x0' associated with guest: 'guest2' conflicts with device: '0/4/1/0.0x500104f0004732d9.0x0' associated with guest: 'guest1'. Both guests cannot be booted at the same time because both devices use the same initiator, even though SHARE_LUNPATHS is set to YES. HPVM guest guest2 configuration problems: Warning 1 on item 0/4/1/0.0x500104f0004732da.
disk:scsi:0,4,2:lv:/dev/vg01/rlvol2 disk:scsi:0,4,3:lv:/dev/vg01/rlvol3 disk:scsi:0,4,4:disk:/dev/rdisk/disk20 dvd:scsi:0,4,5:file:/fdev/0x500000e012afb8d2/file2 : # hpvmmodify -P guest1 –d tape:scsi:0,4,0:attach:/dev/pt/pt_tape1 # hpvmmodify -P guest1 -m hba:avio_stor:0,4 # ioscan -m lun /dev/pt/pt_tape1 Class I Lun H/W Path Driver S/W State H/W Type Health Description ====================================================================== tape 1 64000/0xfa00/0x0 estape CLAIMED DEVICE online STK 0/1/1/1.
real user sys 0m30.26s 0m0.00s 0m0.01s This delay is caused by the retry of failed commands from the nonresponding backing store. There is currently no workaround. • Devices configured under AVIO Stor HBA for a guest cannot be deleted (using the hpvmmodify command) if the guest is at EFI. Stop the guest using the hpvmstop command and retry the hpvmmodify command. Devices configured under AVIO Stor HBA for an HP-UX 11i v3 guest cannot be deleted (using the hpvmmodify command) if the guest is online.
• • • PciBus PciDev Addr (Target Id) Addr (Target Id) is encoded as an HP-UX tgt ID and an HP-UX lun ID in the HP-UX hardware path.
An HP-UX 11iv3 Lun Path hardware path displayed by the ioscan utility can be mapped to an hpvmstatus utility output as follows: PciDev | PCIFtn | | Addr(Target Id) PciBus | | | Lun | | | | | V V V V V 0/0/2/0.0x16.0x0 6.1.3.7 Multi-Guest Boot Conflict with DVDs When one guest has a DVD device configured as a VIO DVD and another guest has the DVD configured as an AVIO burner, both guests should not boot at the same time, but under certain circumstances, the boot-block check fails.
Table 6-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. 6.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 AVIO documentation for details. 6.1.4.2 Sample Script for Adding Multiple Devices at Once To add 256 AVIO storage devices to a guest, HP recommends that you use the hpvmcreate and hpvmmodify commands to add multiple devices at a time using multiple -a options.
the attached physical device must be provided by the guest OS. An attached device can be attached to only one virtual machine at a time. Attached devices include: • CD/DVD burners • Media changers • Tape devices The maximum transfer size can be 1 MB for any guest operating system. 6.2 Configuring Integrity VM Storage This section describes how to plan and set up Integrity VM storage, including the following topics: • “Integrity VM Storage Considerations” • “Setting Up Virtual Storage” 6.2.
Figure 6-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.3: Release Notes. 6.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 6-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.
to the attached device, like changing a tape, can be done physically without detaching the device from the guest. However, such changes might need to be coordinated with the VM Host administrator, especially if the guest administrator has no physical access to the device attached to the virtual machine. All types of virtual storage devices can be added and removed dynamically from virtual machines. That is, virtual disks, virtual DVDs, tapes, media changers, and CD/DVD burners are all hot-swappable.
adapter, simply called scsi, is an emulated single-ported parallel SCSI MPT storage adapter that can be used to connect 15 SCSI target devices to a guest. An AVIO storage adapter is also supported. The AVIO storage adapter supports up to 128 devices per adapter (and host) and provides higher performance and guest storage manageability.
A VM Host storage entity can only be used for one VM device type at a time. For example, a VM Host CD/DVD drive cannot be used for a Virtual DVD and an attached burner at the same time. • location is a VM Host system file. The file permissions on the VM Host system file are not honored by Integrity VM. VM device types that support write operations can still do so using a VM Host system file marked read only.
6.2.2.3.1 Virtual Disks A Virtual Disk is an emulated SCSI disk whose virtual media comes from a VM Host disk LUN. The VM Host disk LUN is specified using a character device file. The character device file is owned by the HP-UX esdisk or sdisk driver. Virtual Disk resources cannot be shared simultaneously across active virtual machines (except in certain cluster configurations, as indicated in this manual). Only one active virtual machine at time can be given a particular Virtual Disk resource.
volume groups to prevent media conflicts. For information about tracking virtual media allocation, see Section 6.2.1.4 (page 99). If you are using LVM, the Virtual LvDisk resource statement takes the following form: disk:scsi::lv:/dev/vg_name/rlvol_name Where /dev/vg_name/rlvol_name is an LVM character device file for rlvol_name on vg_name.
In this example, the Virtual LvDisk resource statement is disk:scsi::lv:/dev/lvrackA/rdisk2. To use VxVM, the Virtual LvDisk resource statement takes the following form: disk:scsi::lv:/dev/vx/rdsk/dg_name/v_name where /dev/vx/rdsk/dg_name/v_name is a VxVM character device file for volume v_name on disk group dg_name.
logical volumes or whole disks to make the accounting even easier. For more information, see Section 6.2.1.4 (page 99). The Virtual FileDisk resource statement takes the following form: disk:scsi::file:/pathname/file where the /pathname/file specifies the VM Host file used as virtual media. A VxFS file system can be created on top of a whole disk or logical volume. For files over 2 GB, VxFS requires the file system be marked with a largefiles option.
vendor: product id: type: size: bytes per sector: TEAC DW-224E CD-ROM 4300800 Kbytes 2048 In this example, the Virtual DVD resource statement is dvd:scsi::disk:/dev/rdisk/disk7. For a virtual machine to recognize a Virtual DVD, physical media must be present inside the VM Host CD/DVD drive. If media is not added at virtual machine start time, it can be inserted into the VM Host CD/DVD drive after the virtual machine is already up.
To prevent media conflicts, you must manage Virtual FileDVDs carefully (see Section 6.2.1.4 (page 99)). You can see where the file system directory where the ISO file resides using the guest's virtual console. To simplify accounting, allocate file directories from complete logical volumes or whole disks. A Virtual FileDVD reverts to its original resource statement when the guest shuts down or reboots.
If the VM Host administrator does not want to give access to the VM Host CD/DVD drive to the guest administrator, you can set up a Virtual NullDVD to a file system directory containing the ISO files that the guest administrator wants to access. This resource statement would take the following form: dvd:scsi::null:/pathname where /pathname is the file system directory where the ISO files are located. This is the same as setting up a Virtual FileDVD (see Section 6.2.2.3.
where /dev/pt/pt_* files are HP-UX esctl device files. Attachable devices can be specified as scsi or avio_stor. To create an HP-UX esctl device file, follow these steps: 1. Run ioscan to pick up any new devices that were connected: # ioscan 2. Locate the device designated for attachment. a. Install any device special files for these new devices: # insf -e b.
Agile = /dev/rchgr/autoch1 ESCTL = /dev/pt/pt_autoch1 The following are examples of CD/DVD burner device: Agile = /dev/rdisk/disk7 ESCTL = /dev/pt/pt_disk7 Attached devices cannot be shared simultaneously across active virtual machines. Only one active virtual machine can be given a particular attached device at a time. However, like virtual devices, attached devices can be attached and detached dynamically across active virtual machines (see Section 6.3 (page 113)).
The following limitations apply to this release of the NFS-mounted backing stores feature in Integrity VM V4.3: • • • • Integrity VM guests configured with NFS-mounted backing stores cannot be integrated with Serviceguard as either a package (VM-as-an-SG-Package) or node (VM-as-an-SG-Node). The use of symbolic links on the NFS server to redirect the location of a guest's backing-store files is not allowed. However, symbolic links are still allowed inside the guest booted with an NFS backing store.
The VM Host administrator uses the following commands to manage virtual machine storage devices: Management Function Integrity VM Command Add, delete, manage, and modify virtual machine storage hpvmmodify (see Section 3.5 (page 62)) devices. Display information about the storage devices for a virtual hpvmstatus (see Section 8.3 (page 149)) machine. Once a resource is added or attached to a virtual machine and the virtual machine is powered on, the storage resource is owned by the guest administrator.
# passwd testme2 ... # passwd testme3 ... Because of the way the useradd command works, an attempt to create an additional account might result in an error. For example, the following command attempts and fails to add the testme4 user account: # useradd -r no -g users -s /opt/hpvm/bin/hpvmconsole \ > -c "Console access to guest 'testme'" \ > -d /var/opt/hpvm/guests/testme \ > testme4 '/var/opt/hpvm/guests/testme' is not a valid directory To enter the command correctly, include the entire directory path.
NOTE: If a guest hangs, attach to the guest's virtual console using the hpvmconsole command, then use Ctrl/B to enter the virtual console. Enter the tc command to reset the guest. The guest captures a memory dump of the machine state, which can be used later for offline diagnosis. Do not kill the guest from the VM Host or use the virtual console to power down a hung guest. Doing so can corrupt the guest file system. Management Function Integrity VM Command Eject a virtual DVD.
6.3.2.1 Adding Virtual Storage Devices A VM Host administrator adds or attaches Integrity VM storage using the hpvmstatus and hpvmmodify commands. Virtual storage devices can be added or attached while the virtual 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.
... disk scsi 0 1 0 0 0 disk /dev/rdisk/disk5 disk scsi 0 1 0 1 0 disk /dev/rdisk/disk7 disk scsi 0 1 0 2 0 disk /dev/rdisk/disk9 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 6.3.2.
To complete a DVD ejection and insertion, follow the virtual console menus. However, new media selections might require the help of the VM Host administrator. Changes through the virtual console are not saved across guest OS reboots 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.
# diskinfo /dev/rdisk/disk7 SCSI describe of /dev/rdisk/disk7: vendor: HP product id: Virtual DVD 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.
7 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 APA can be configured on the VM Host to provide a highly available LAN for the vswitch (APA in active/passive mode) or to increase the bandwidth of the vswitch LAN (APA active/active mode). Before you stop APA, use the hpvmnet -h command to halt the vswitch. If you do not halt the vswitch first, the hpvmnet command reports an incorrect MAC address for the vswitch.
Table 7-1 Options to the hpvmnet Command (continued) Option Description -h Halts one or all vswitches. You are asked to confirm this action. -F Omits the confirmation dialog before halting, deleting, or rebooting the vswitch. This option is intended for use by scripts and other noninteractive applications (Force mode). NOTE: The -F option is deprecated in Integrity VM commands; this option should be used only at the direction of HP Support. -d Deletes a virtual switch.
Table 7-1 Options to the hpvmnet Command (continued) Option Description -C Changes the specified vswitch. If used with the -N option, the changes are made to the cloned vswitch. You must include either the -S or -s option. -N new-vswitch-name Creates a new vswitch based on the existing vswitch. For new_vswitch_name, specify the unique name of the new virtual switch. The name of the vswitch is limited to eight characters. You must include either the -S or -s option.
NOTE: The Cisco switch for HP BladeSystem c-Class Server Blades has a protocol error that causes it to respond to every MAC address. Because MAC addresses are unique, Integrity VM checks that the generated guest virtual MAC address is unique. If one of these bad switches is on your network, Integrity VM's check will fail. The hpvmcreate command might fail with messages like the following: hpvmcreate: hpvmcreate: WARNING (host): Failed after 3 attempts. WARNING (host): Unable to create Ethernet MAC Address.
======== ====== ======= ========= ======== ============== =============== localnet 1 Up Shared N/A N/A hostnet 296 Up Shared lan0 0x00306e4a93e6 If lan0 goes down, enter the following command to swap to use lan1: # hpvmnet -C -S # hpvmnet Name Number ======== ====== localnet 1 hostnet 296 hostnet -n 1 State ======= Up Up Mode NamePPA ========= ======== Shared Shared lan1 MAC Address IP Address ============== =============== N/A N/A 0x00306e4a92ef 7.2.
# hpvmnet -S clan1 -d hpvmnet: Remove the vswitch 'clan1'? [n/y] y The default command function (if you press Enter) is to not perform the function of the command. To perform the command function, enter y. In the case of commands where a confirmation is required, such as the hpvmnet -h command, you can include the —Q option to override the confirmation process. This is useful in scripts and processes that are not interactive.
7.2.7 Halting vswitches Use the hpvmnet -h command to halt a vswitch. For example: # hpvmnet -S clan1 -h hpvmnet: Halt the vswitch 'clan1'? [n]: y Auto Port Aggregation (APA) can be configured on the VM Host to provide a highly available LAN for the vswitch (APA in active/passive mode) or to increase the bandwidth of the vswitch LAN (APA active/active mode). Before you stop APA, halt the vswitches associated with it.
NOTE: If you modify a vNIC from lan to avio_lan, or avio_lan to lan, you must restart the vswitch. As with virtual storage devices, use the -a rsrc option to associate a guest virtual network device with a vswitch. Before you use this option to associate the virtual network device with a vswitch, create the vswitch using the hpvmnet command.
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. The virtual network entry in the guest configuration file includes the guest information on the left side of the equal sign (=), and VM Host information on the right.
The following sections describe the Port-based VLANs, Guest-based VLANs, and VLAN-backed vswitch features. NOTE: All three features are supported on the accelerated virtual I/O (AVIO) network. Only the Port-Based VLAN feature is supported in virtual I/O and AVIO networks. 7.4.1 Port-Based VLANs Figure 7-2 illustrates a basic virtual machine VLAN that allows guests on different VM Host systems to communicate.
Using HP-UX VLANs manual. Do not use the hpvmnet command to create a virtual switch that is associated with a VLAN port on the VM Host (that is, a LAN created with lanadmin -V). This “nested VLAN” configuration is not supported. Frames arriving at the vswitch from a guest can be “tagged” by the vswitch. Tagging consists of inserting the VLAN ID information into the MAC header before forwarding the frame on.
• • The number of virtual machines that have access to the VLAN The names of virtual machines that are up and that have access to the VLAN 7.4.1.1 Cloning Guests with VLAN Information If you use the hpvmclone command to clone guests, the operation automatically assigns new port numbers for new guests.
Configured Ports Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlandID 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 Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlanID : : : : : : : : : 4 1 Active vm1 none vm1 avio_lan none 2 : : : : : : : Active vm1 100 vm1 avio_lan none : 3 : : : : : : 4 : : : : : : Active vm2 none
NOTE: Guest VLANs and VLAN-backed vswitches are not supported with VIO. OpenVMS guests that are created (hpvmcreate) or modified (hpvmmodify) to add and use a non-physical vswitch must use the same vswitch by name for each OpenVMS guest. The following scenarios fail: • Attempting to start an OpenVMS guest that is using two different localnet vswitches on the same guest. • Using a different localnet vswitch than an already active OpenVMS guest is using.
2 3 Reserved Active avio_lan none avio_lan none 1 1 u03 none none To enable the VLAN-backed vswitch (VBVsw) feature, HP-UX PHNE_40215 or a superseding patch is required on the VM Host. This patch is available as an individual patch or as part of "FEATURE11i" bundle. To verify that the patch is installed, enter the following: # swlist -l product | grep PHNE_40215 PHNE_40215 1.0 LAN cumulative patch The dlpi_max_ub_promisc kernel tunable needs to be set to when using a VBVsw type vswitch.
NOTE: The lanadmin command is deprecated and will be removed in a future HP-UX release. HP recommends that you use the nwmgr command to perform all network interface-related tasks. The following table shows the comparable nwmgr command to use to replace the lanadmin command: Task • Legacy Command nwmgr Command Verify whether TSO is turned on. n # lanadmin -x vmtu n is the VM Host interface, as displayed by the hpvmnet command. # nwmgr -g -A vmtu -c lann Verify that TSO is on for lan0.
# /sbin/rc2.d/S340net stop # ch_rc -a -p "INTERFACE_NAME[0] = "lan3" # /sbin/rc2.d/S340net start The guest network begins to function. 7.5.2 Troubleshooting VLAN Problems When VLANs are configured on the vswitch, the partitioned LAN must have its own set of network servers to service requests on the VLAN. For example, the VLAN's DNS server or a router setup on the VLAN should be set up on the VLAN.
NOTE: The lanadmin command is deprecated and will be removed in a future HP-UX release. HP recommends that you use the nwmgr command to perform all network interface-related tasks. The following table shows the nwmgr command that performs the same task as the lanadmin command: Task Legacy Command Check the status of the transmit CKO. # lanadmin -x cko 4 Hardware TCP/UDP (IPv4) transmit checksum offload is currently enabled. Hardware TCP/UDP (IPv4) receive checksum offload is currently disabled.
• 142 or VLAN must match, whether they are physical systems or guests. The VM Host does not check for MTU mismatches for its guests. The lanadmin card specific options that are supported on igssn on the guest are: — -x:speed,fctrl,cko,type,card_info,stats drv,vmtu,and drv_pr.
8 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, including the use of ID-VSE Logical Server Management (LSM).
NOTE: The SLVM volume groups must be in the activated mode before running the hpvmhostrdev script. For information about deactivated volume groups, see Section 8.1.2 (page 144). 4. Execute the Integrity VM hpvmhostgdev -a command to ensure that all devices are populated in the gdev database. The hpvmhostgdev command analyzes disklist and lvlist output and adds unused gdevs to the Integrity VM device database. NOTE: If you add new devices in the future, run the hpvmhostgdev -a script again.
• • If the volume group is to remain deactivated, the VM Host administrator can manually add the physical volume as a restricted device with the hpvmdevmgmt command. Or, after activating the volume group, execute the hpvmhostrdev command, so that the VM Host storage management database is updated accordingly. An HP-UX system administrator can deactivate a volume group using the vgchange command.
The following examples show how to add various device types to the storage pool: • File: # hpvmdevmgmt -a gdev:/var/opt/hpmv/ISO-images/hpux/112350GOLD.ISO:attr:PRESERVE=YES • VxVM volume: # hpvmdevmgmt -a gdev:/dev/vx/rdsk/guestdg/vxvm_g2:attr:PRESERVE=YES To remove a device from the storage pool, used the following command: # hpvmdevmgmt -d gdev:/dev/rdisk/disk23 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.
CAUTION: HP does not recommend using the -x register_status option. Integrity VM commands ensure that the VM is registered only on one VM Host at a time. Registering a VM on more than one VM Host can lead to accidentally booting the VM on more than one VM Host and could cause inconsistencies with the display of graphical tools. However, if you find that VM is not registered on any VM Host, you can manually register it with the hpvmmodify command. For information on this command, see Section 9.1.3. 8.2.
the hpvmmigrate command sets the guest to be runnable, it now also sets the modify_status=enabled and visible_status=enabled attributes. 8.2.4 Cannot Distinguish Between JBOD and Remote SAN with Device Check If your Integrity VM server has local JBOD disks configured, they appear as disks that are SAN-resident in the Virtualization Provider making them available for guests.
8.3 Monitoring Guests To display information about all the virtual machines configured on the VM Host, enter the hpvmstatus command.
For example, to see detailed information about the host1 virtual machine, enter the following command: # hpvmstatus -V -P host1 [Virtual Machine Details] Virtual Machine Name : Virtual Machine UUID : Virtual Machine ID : Virtual Machine Label : VM's Model Name : VM's Serial Number : VM's Config Version : VM's Config Label : 41m04s PST Operating System : OS Version Number : State : Start type : Console type : Guest's hostname : Guest's IP address : EFI location : Pattern File location : Guest revision : Runn
Target Lun Physical Storage type Physical Device : : : : 0 0 disk /dev/rdisk/disk0 [Network Interface Details] Physical Storage type : vswitch Guest Adaptor type : lan Backing : vswitch1 Vswitch Port : 1 Ioscan format : 0/0/0/0 Bus : 0 Device : 0 Function : 0 Mac Address : f6-92-cf-35-86-78 [Misc Interface Details] Guest Device type : Guest Adaptor type : Physical Storage type : Physical Device : serial com1 tty console To display the VM Host system resource, use the -s option to the hpvmstatus comman
Table 8-2 Options to the hpvmsar Command (continued) Option Display Description -I Guest Interrupt Display -N Guest AVIO Network traffic by vswitch Display -S Vswitch AVIO Network traffic by Port Display 8.5 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.
# useradd -d /var/opt/hpvm/guests/host1 \ -c 'host1 console' -s /opt/hpvm/bin/hpvmconsole host1 This example uses the following options: • The -d option specifies the home directory for the host1 account. • The -c option specifies a comment text string that describes the account. • The -s option specifies the path for the shell of the new account. 2. Use the passwd command to set a password for the account. For example: # passwd host1 3.
the associated guest with the usermod command. This allows multiple accounts to map to the guest, and requires the account names to be valid HP-UX login strings. Authorization of access to the virtual console is determined by the guest configuration file (set using the -u and -g options to the hpvmcreate, hpvmmodify, and hpvmclone commands). This controlled access allows you to temporarily block access by using the hpvmmodify command to change the virtual console administrator account name. 8.5.
# cd /opt/hpvm/guest-images # ls common hpux openvms To install guest management software on an HP-UX guest, select the appropriate version of HP-UX: • 11iv2 indicates HP-UX 11.23. For HP-UX 11i v2 guests, the guest depot file: /opt/hpvm/guest-images/hp-ux/11iv2/hpvm_guest_depot.11iv2.sd • 11iv3 indicates HP-UX 11.31. For HP-UX 11i v3 guests, the guest depot file is: /opt/hpvm/guest-images/hpux/11iv3/hpvm_guest_depot.11iv3.
[host1] vMP> co You can pass a command to the virtual machine console using the —c option to the hpvmconsole command. For example, to start a virtual machine named host1, enter the following command: # hpvmconsole -P host1 -c "pc -on" Table 8-3 lists the options to the hpvmconsole command. Table 8-3 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.
For more information about using the hpvmconsole command, see hpvmconsole(1M). 8.8 Using the virtual iLO Remote Console The Integrity VM virtual iLO Remote Console feature allows you access to the guest console by logging into a specific IP address. You can assign each guest a virtual iLO Remote Console IP Address with which the end user can connect using either telnet or Secure Shell (SSH). After login authentication, the guest console is immediately available.
To obtain the virtual iLO Remote Console settings of a guest, use the hpvmstatus command. For example: # hpvmstatus -P guestname .... [Remote Console] Remote Console Ip Address: Remote Console Net Mask: .92.81.68 255.255.252.0 When users connect to the virtual iLO Remote Console IP Address, they must log in using the standard telnet or ssh system authentication. After authenticating, they receive immediate access to the guest console: # ssh -l guest1admin .92.81.
— — • PHCO_41595 PHNE-41452 The virtual iLO Remote Console's SSH server host keys can change. When an SSH client connects to an SSH server, the client downloads the server's host keys and keeps a local copy (usually in a file such as ~/.ssh/known_hosts). On subsequent connections, the SSH client verifies that the host key sent by the server matches the local copy. If the keys does not match, the SSH client prints an error message. The virtual iLO Remote Console uses the host system's SSH server host keys.
Table 8-4 Dynamic Memory Control Command Options Keyword Value Pair Description dynamic_memory_control={1|0} Specifies whether a sufficiently privileged user on the guest (such as root) can change the dynamic memory values while the guest is running. To disable guest-side dynamic memory control, specify 0 (zero). If the guest is not active, the only effect is the modification of the guest configuration file. On the running guest, the change takes effect immediately.
8.10.1.1 Configuring a Virtual Machine to Use Dynamic Memory By default, dynamic memory is not enabled. To configure a virtual machine to use dynamic memory, enter the hpvmcreate, hpvmmodify, or hpvmclone command.
Table 8-5 Dynamic Memory Characteristics 162 Characteristic Setting Description Type none No dynamic memory support any Dynamic memory is configured on the host, but the dynamic memory subsystem on the guest has not started and reported the implementation type. driver Dynamic memory is implemented in a driver and does not use Guest OS Online Add/Delete features. OLAD Dynamic memory is implemented using Guest OS Online Add/Delete features.
Table 8-5 Dynamic Memory Characteristics (continued) Characteristic Setting Description enabled Control that overrides started. guestctl Guest-side control is enabled. The following example displays active usage of the VM Host and guest(s) dynamic memory usage values, along with the guest memory utilization. The guest's current swapping and paging and translation address memory misses per second are included. For a description of each column displayed, see the hpvmsar manpage.
Table 8-6 Options to the hpvmmgmt Command (continued) -cnum Specifies the number of virtual CPUs to enable on the guest. -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.
8.10.3 Troubleshooting Dynamic Memory Problems This section describes how to solve problems in the use of dynamic memory. 8.10.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 the guest hangs, on the VM Host, use the hpvmstatus command to check the memory statistics on the guest. For example: # 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 : 27 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 . . .
# hpvmmgmt -V -l ram Dynamic memory driver not found on guest. 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 76). 8.10.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.
HPVMAMRCHUNKSIZE=256 HPVMAMRWAITTIME=60 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 8.10.1 (page 159).
8.10.4.3 Viewing Automatic Memory Reallocation Automatic memory reallocation parameters and status are displayed for each VM using the standard Integrity VM commands.
The guest should be able to boot if the logical volume is reverted (using lvreduce in case of LVM) to its original size. If this fails, the guest root device has been corrupted, and the guest operating system must be reinstalled. An AVIO logical volume backing store not used as a root disk can be extended while the guest is online.
Table 8-7 Options to the hpvmdevmgmt Command (continued) Option Description -I Creates passthrough device files (for example, /dev/rscsi). Passthrough devices are used by attached devices, such as tape devices, media changers, and CD/DVD burners. Modifies an existing attribute or adds the attribute -m {server|rdev|gdev}:entry_name[:attr:attr_name=attr_value] if it does not already exist. Adds an entry.
8.12.2.2 Replacing Devices If a backing storage device malfunctions, replace it by using the hpvmdevmgmt -n option. The -n option works for only guest devices. It replaces the existing device entry with the new device entry while keeping all the current guest dependents. Thus, each guest dependent is modified to replace the old device with the new one.
8.13 HP AVIO Stor EFI Driver Enumeration Policy The default enumeration policy of the “HP AVIO Stor EFI Driver” is to enumerate boot LUNs. Use the drvcfg EFI utility to change the enumeration policy to do the following: • Enumerate boot LUNs only. • Enumerate all LUNs.
9 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 9-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 9-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) 9.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.
9.2 Command Line Interface for Online and Offline Migration To migrate a virtual machine to another VM Host, perform the following steps: 1. 2. 3. Set up SSH keys on both the source and target hosts, as described in Section 9.3.3 (page 190). Present all SAN storage assigned to the virtual machine to the target VM Host (if it is not already there). If using offline migration and the guest is booted, stop the guest on the source host, using the hpvmstop or hpvmconsole command.
a problem, it is reported, and the virtual machine is not migrated. You can specify the -F option (force) to suppress the errors and force the virtual machine migration to the target VM Host. CAUTION: Use the -F option with caution, because some errors can prevent a virtual machine from working properly on the target VM Host.
Table 9-3 Options to the hpvmmigrate Command (continued) Option Description -C For offline migrations, physically copies the storage device specified with the -m option to the target VM Host during the migration process. If specified before the first -m option, it applies to all -m options that specify an appropriate type of storage. This might take a long time to complete if a large amount of storage needs to be copied.
Table 9-3 Options to the hpvmmigrate Command (continued) Option Description -k Creates the virtual machine configuration on the target VM Host and marks it Not Runnable, but does not change the virtual machine on the source VM Host. This is used primarily to distribute virtual machine configurations for Serviceguard. -l new-vm-label Specifies a descriptive label for the virtual machine, which can be useful in identifying a specific virtual machine in the hpvmstatus command verbose display.
Table 9-3 Options to the hpvmmigrate Command (continued) Option Description -s Indicates that the migration should not occur, but the hpvmmigrate command should check whether or not the migration is possible. Because virtual machines and their hosts are dynamic, a successful -s trial does not always guarantee a subsequent successful migration.
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 hpvmmigrate command does not check that you are using a private network to migrate your guest. Using a private network is important for security and to maintain the performance of your site's public network.
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 A transient network error might cause the hpvmmigrate command's vswitch connectivity check to report a failure. If the connectivity check fails, retry the migration by re-issuing the hpvmmigrate command.
A vswitch of the same name, connected to the same network must be available on the source and target VM Host servers. The hpvmmigrate command does connectivity checking before migration. You can use the hpvmmigrate -w option to bypass the vswitch connectivity checks, but only use -w if you are certain that the source and target vswitches are connected to the same subnet. Otherwise, your guest will lose network connectivity after migrating.
be allowed to deliver time (allow guests to be a time consumers). Because a VM guest never delivers time, you do not need to configure the local clock (server 127.127.1.0) or an ntp.drift file. So, the ntp.conf file on a VM guest should be as simple as the single line: server minpoll 4 maxpoll 6 After configuring the guest's /etc/ntp.conf file, assuming NTP is already enabled (that is, the XNTPD variable in /etc/rc.config.
# hostname host19 # machinfo -v CPU info: 12 Intel(R) Itanium 2 9000 series processors (1.6 GHz, 24 MB) 533 MT/s bus, CPU version C2 24 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 -byte atomic operations . . . # hostname host20 # machinfo -v CPU info: 4 Intel(R) Itanium 2 9000 series processors (1.
hosts: ipnodes: files dns files dns Excerpt from /etc/rc.config.d/netconf on the host2 system: INTERFACE_NAME[3]=lan3 IP_ADDRESS[3]=10.3.81.142 SUBNET_MASK[3]=255.255.252.0 BROADCAST_ADDRESS[3]="" INTERFACE_STATE[3]="" DHCP_ENABLE[3]=0 INTERFACE_MODULES[3]="" Example output from netstat on the host2 VM Host system: # netstat -in Name Mtu lan3 1500 lan0 1500 lo0 32808 Network 10.3.80.0 .17.80.0 127.0.0.0 Address Ipkts ... 10.3.81.142 1022313379 ... .17.81.142 2420913 ... 127.0.0.1 123762 ...
• • • hpvmmigrate -h host39 — Look up host39-hpvm-migr first, and if not found, look up host39. hpvmmigrate -h host39-hpvm-migr — Look up host39–hpvm-migr. hpvmmigrate -h host39.atl — Look up host39.atl. Of course, target.fully.qualified.domain-name will not be modified.
obsolete keys from the known_hosts file, and then use the secsetup command again to configure new keys. If you set up SSH security between VM Hosts before adding the conventional —hpvm-migr host alias to the /etc/hosts file and you do not run secsetup on the host-alias addresses, the hpvmmigrate command fails with the message, Host key verification failed, when it attempts to use the conventional host alias.
For example, if a guest stops I/O to storage for too long, it could experience I/O errors and applications could fail or the operating system could crash. If a guest is frozen for too long, external network connections to the guest can time out and network connections can be dropped. Network time-outs are especially troublesome for certain UDP applications that are not resilient enough to tolerate packets being delayed and dropped.
Do not mark disks SHARE=YES for devices assigned to virtual machiness that will migrate (unless more than one virtual machine will share the storage on the same VM Host). Marking a device SHARE=YES can lead to more than one virtual machine using the device at the same time and can lead to disk corruption. 9.3.4.4 Using NTP on the VM Guests Using NTP is strongly recommended for Online VM Migration environments. Each guest should include all potential VM Hosts as servers in its ntp.
Online migration support among Integrity servers is limited by the processor architecture. Online migration among servers with processor family 31 is supported regardless of the model number within that family. Migration among servers with processor family 32 and model numbers 0 or 1 is supported. Otherwise, online migration is supported among servers with identical processor family and model number. To check if a guest can be migrated to the target VM Host, use the -s option to the hpvmmigrate command.
9.5.2 Using the p2vassist Utility The p2vassist utility is structured as a tree of menus, each of which can execute a function or give access to a deeper-level menu. Use the p2vassist command on the VM Host system. For example: # p2vassist P2V Assistant Manager ====================================== 1 ) General Configurations 2 ) Manage Applications 3 ) Manage O.S.
Depots source (type 'q' to return): depsrv.hp.com:/release/1123.0706/ic054 2. List the applications available in the source host. Select menu 2, option 1 (Manage Applications - List Applications). Note the names of the products to be selected. For example: P2V Assistant Manager ====================================== 1 ) General Configurations 2 ) Manage Applications 3 ) Manage O.S.
Manage Applications ====================================== 1 ) List Applications 2 ) Select Applications 3 ) Add Data Directories/Files 4 ) Consolidate Applications ----0 ) Return Enter Option Number: 2 Select Applications ============================== Please enter the list of depots to be installed on the target system, separated by spaces. You can list the applications using the first option of this menu. Depots list (type 'q' to return): hpuxwsAPACHE hpuxwsTOMCAT hpuxwsWEBMIN hpuxwsXML 4.
1 ) List Applications 2 ) Select Applications 3 ) Add Data Directories/Files 4 ) Consolidate Applications ----0 ) Return Enter Option Number: 4 Consolidate Applications ============================== This option will consolidate application(s) installed on the current system and then migrate into another a suitable target system. The target system is the machine which will host the consolidated application(s).
The P2V assistant prompts you either to continue or to stop the installation. If you choose to continue, the P2V assistant first uninstalls the application on the target host, then installs the selected one. Do not continue the installation if older versions can break dependencies on another applications. In addition, install older versions of applications might overwrite updated libraries that were installed by patches. 9.
10 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 10-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.
10.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. 10.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. 10.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.
node, it might not be possible to failover a virtual machine package running on a Serviceguard node with a large amount of physical memory to a Serviceguard node with less available memory. 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.
the Cluster Volumes Manager (CVM) as well as files on a Cluster Files System can be configured to be active and available on multiple Serviceguard nodes simultaneously. Additional care and planning should be taken when configuring VMs as Serviceguard Packages to insure that no more then one guest on one node can access these backing store types.
Depending on the system configuration, you might see an error similar to the following when running cmcheckconf or cmapplyconf to the virtual machine packages: # cmapplyconf -P /etc/cmcluster/hpvm-sg1-g4/hpvm-sg1-g4.conf Incorrect permissions for /etc/cmcluster/hpvm-sg1-g4 (40777). Directory must be executable for owner, and not writable by group and others on node hpvm-sg1-h1. cmapplyconf: Error found in package file: /etc/cmcluster/hpvm-sg1-g4/hpvm-sg1-g4.conf.
a. b. c. d. e. f. g. Run the hpvmcreate command to create the virtual machine. Run the hpvmstart command to start the virtual machine. Install and configure the guest operating system. Install the guests kits and optionally the cmappserver software. Optionally configure any guest applications and their associated application monitor run commands. Run the hpvmstop command to stop the virtual machine. Unmount, export and deactivate storage. 5. On the secondary nodes, perform the following step: a.
NOTE: The following situation might occur when you are using Insight Dynamics — VSE to manage distributed guests (guests that are configured as Serviceguard packages): • There is a guest configuration file for each guest on each VM Host. Therefore, when you modify a distributed guest you must modify the guest on each VM Host that is a cluster node. 10.3.
10.3.10 Maintenance Mode Using the Integrity VM commands, you can make changes to the VM configuration, disable maintenance mode and then distribute the VM configuration using the hpvmmigrate command. If the changes made to the VM configuration impact the Serviceguard Package configuration, the package should be repacked using the hpvmsg_package command, and then re-applied using the cmapplyconf files as previously outlined.
max_reformation_duration value of the VM Host cluster. To determine this value, use the following command: cmviewcl -v -f line | grep max_reformation_duration NOTE: With Serviceguard and Integrity VM running, you might see the following types of messages in the syslog file: Syslog entries - cmcld[XXXX]: Warning: cmcld process was unable to run for the last X.XX seconds These messages can be ignored. 10.
Volume Group configuration for /dev/vgsharedA has been saved in /etc/lvmconf/vgsharedA.conf # e. Create the logical volumes: # lvcreate -L 18748m -n lvdisk0 /dev/vgsharedA Logical volume "/dev/vgsharedA/lvdisk0" has been successfully created with character device "/dev/vgsharedA/rlvdisk0". Logical volume "/dev/vgsharedA/lvdisk0" has been successfully extended. Volume Group configuration for /dev/vgsharedA has been saved in /etc/lvmconf/vgsharedA.conf # ... 2.
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100% Found 2 volume groups on node creek1 Found 2 volume groups on node creek2 ... Writing cluster data to /etc/cmcluster/creekQuorumRiver.cfg. # e. Edit the configuration file and change the entry for each of the SLVM volume groups, so that they are listed as an HPVM_VOLUME_GROUP. If each entry is already listed as aVOLUME_GROUP, replace each line so that each entry is listed as an HPVM_VOLUME_GROUP.
This node is the Server. Volume group "/dev/vgsharedA" has been successfully changed. # b. Check the VG Status line of the vgdisplay —v /dev/vgname output to make sure that it is shared: # vgdisplay -v /dev/vgsharedA | grep "VG Status" VG Status available, shared, client If the VG is not listed as shared, deactivate it and reactivate it with vgdisplay —v /dev/vgname. 5. Install HostAVIOStor bundle.
10.5.2 Creating and Configuring VMs as Serviceguard Packages Having SLVM Backing Storage Deploying virtual machines as Serviceguard packages is a common occurrence. Multiple virtual machines can have virtual disks mapped to logical volumes in a single SLVM volume group. In the event that one of those virtual machines is moved to another node (VM Host) in the Serviceguard cluster, the other virtual machines need to have continued access to logical volumes in that volume group.
dependency_name dependency_condition dependency_location c. hpvm_vgsharedA hpvm_vgsharedA = up same_node Check the configuration of the package: # cmcheckconf -P /etc/cmcluster/slvmtest/slvmtest2.conf Attempting to validate slvmtest. ... cmcheckconf: Verification completed with no errors found. d. Save the original configuration file and use the modified configuration in its place to apply the package configuration to the cluster: # cp slvmtest.conf slvmtest.conf.orig # mv slvmtest2.conf slvmtest.
4. 5. Ensure that the VM package is running on the desired node. Verify failover and online migration function as expected prior to placing systems into production. 10.6 Troubleshooting Network Problems When Using Serviceguard If the guest has network problems after failover: • Make sure the vswitches are configured on the adoptive node. If you are using the VLAN feature of Integrity VM vswitches, make sure that appropriate VLAN IDs are assigned to each port.
11 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 11-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 I/O configuration info ................................... OK Collecting filesystem info .......................................... OK Collecting system info .............................................. OK Collecting lan info ................................................. OK Running lanshow ..................................................... NO Collecting installed sw info ........................................ OK Collecting command logs .............................................
11.1.2 Using the hpvmcollect Command on Guests To use the hpvmcollect command on the guest, you must first install the guest management software on the guest as described in Section 8.6 (page 154). Table 11-2 describes the options to the hpvmcollect command on the guest. Table 11-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.
11.2 Managing the Size of the VMM Driver Log File The monitor log file (/var/opt/hpvm/common/hpvm_mon_log) is limited in size to 1024 KB. When the log file grows larger than this, it is copied to a new file (hpvm_mon_log.$time), and 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.
A Rolling Back to the Previously Installed Version of Integrity VM In the unlikely event that you need to roll back to a previous version of Integrity VM, this appendix provides the information needed to perform the rollback. The preferred method for rolling back to a previously installed version of Integrity VM is to restore the system image that was backed up before installing the current version of Integrity VM on the VM Host.
B Sample Script for Adding Multiple Devices The following example provides a script that enables you to specify multiple storage devices at once for a guest. #!/bin/ksh # --------------------------------------------------------------------------------------# HP Integrity VM example script. # # SUMMARY: # # Add disks to an Integrity VM (guest) in 'batch mode' with hpvmmodify, using AVIO. # # SYNOPSIS # # ./thisscript [-a] -P guestname -f disklistfile [-N #] [-n #] [-t #] [-qT] [-F flags] # or # .
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # -q Quite mode - no display of hpvmmodify command that will run -t targetmax Max target value to use for -a disk:avio_stor:[b,d,targetmax]... Valid values: 0 - special case: script will use full 0-127 range 15...127 - script will use specified max 1... 14 - not valid for this script, since 0-14 is the normal default range for target values if -t is not specified.
# setup BUS,DEV,TGT for next call TGT=$TGT+1 if [ $TGT -gt $WRKTGT ] then TGT=0 DEV=$DEV+1 fi # Skip b,d of 0,3 if [ $BUS -eq 0 ] && [ $DEV -eq $DEVSKIP ] then DEV=$DEV+1 fi if [ $DEV -gt $DEVMAX ] then DEV=0 BUS=$BUS+1 fi if [ $BUS -gt $BUSMAX ] then # NOTE: should not be here, but error out just in case. echo "ERROR: Max supported bus value exceeded, no more room for another adaptor.
typeset -i XN ADDFLAG=0 AUTOBDT=0 QUIET=0 USERDISKCNT=0 USERTGT=0 XN=$XNDEFAULT # # Get cmd line options # while getopts :aF:f:HhN:n:P:qTt: option do case $option in a) # add flag - do actual call to hpvmmodify ADDFLAG=1 a=$a+1 ;; F) # hpvmmodify flags FLAGS=$OPTARG F=$F+1 ;; f) # disklist file DISKLISTFILE=$OPTARG f=$f+1 ;; H) # Help usage exit 0 ;; h) # help usage exit 0 ;; N) # number of disks to add from the disklistfile USERDISKCNT=$OPTARG N=$N+1 ;; n) # number of disks to add at a time XN=$OPTARG n=$
exit 1 fi if [ ! -s "$DISKLISTFILE" ] then echo "ERROR: Disklist file: $DISKLISTFILE is a zero-length file." exit 1 fi GUESTSTATUS="`hpvmstatus -P $GUESTNAME -M 2> /dev/null`" if [ -z "$GUESTSTATUS" ] then echo "ERROR: Could not find guest: $GUESTNAME" exit 1 fi if [ $t -eq 1 ] then if [ $USERTGT -gt 0 ] && [ $USERTGT -lt 15 ] then echo "ERROR: User specified target max (-t $USERTGT) must be 0 or in range 15...127.
ADDRSRC="-a disk:avio_stor:$BDT:disk:$DISK" ADDCMD="$ADDCMD $ADDRSRC" DISKIDX=$DISKIDX+1 CMDIDX=$CMDIDX+1 # Run hpvmmodify if at the add multiplier (-n) or at the last disk if [ $CMDIDX -eq $XN ] || [ $DISKIDX -eq $DISKCNT ] then # Do the hpvmmodify if [ $QUIET -eq 0 ] then echo "Calling: $TIMECMD $ADDCMD" fi if [ $ADDFLAG -eq 1 ] # check for -a flag then $TIMECMD $ADDCMD RETVAL=$? if [ $RETVAL -ne 0 ] then typeset -i FINALCNT FINALCNT=$DISKIDX-$XN echo "ERROR - hpvmmodify failed.
Integrity VM Manpages 237
hpvm(5) NAME hpvm -- HP Integrity Virtual Machines (Integrity VM). SYNOPSIS Virtualization technology DESCRIPTION HP Integrity Virtual Machines allows the creation and management of virtual machines, in which unmodified operating systems designed for HP Integrity servers can run. Integrity VM provides a VM Host, which manages the physical machine and allocates system resources, such as memory, CPU time, and I/O devices to virtual machines.
• • • • • • hpvmstart: Starts a virtual machine. Runs on the VM Host. hpvmstatus: Displays status of one or more virtual machines. Runs on the VM Host. hpvmsuspend: Suspends a virtual machine. hpvmstop: Stops a virtual machine. Runs on the VM Host. hpvmupgrade: Assists an Integrity VM upgrade. p2vassist: Moves a system workload from a discreet server to a virtual machine. Runs on the VM Host. All commands except hpvmconsole require superuser privileges.
hpvmclone(1M) NAME hpvmclone -- Create a new virtual machine that is a copy of an existing virtual machine. SYNOPSIS hpvmclone { -P vm_name | -p vm_number } [-K console_IP_Addr] [-L console_IP_Addr_Netmask] -N clone_VM_name [ -F | -s ] [-l vm_label] [-B start_attr] [-O os-type [:version]] [-c number_vcpus] [ -e percent[:max_percent] | -E cycles[:max_cycles] ] [-r amount] [-S] [-g user] [-g [+]group[: {admin |oper}]] [-u user] [-u [+]user[: {admin| oper}]] [-a rsrc]... [-m rsrc]... [-d rsrc]...
using telnet or ssh using this IP address. Accessing the virtual iLO Remote Console will automatically run the command hpvmconsole for this guest. To facilitate virtual iLO Remote Console access, an IP alias interface will be created using this IP address and the netmask specified in the option. If the IP address specified is 0, the IP alias interface for this guest will be removed. If this option is not specified, then the new guest being created will have no virtual iLO Remote Console set up.
replaced in the new virtual machine by the new value in CPU clock cycles. The -e and the -E options are mutually exclusive. -l vm_label Specifies a descriptive text string for the new virtual machine. This option can be useful in identifying a specific virtual machine in the hpvmstatus -V display. The label can be up to 256 alphanumeric characters, including A-Z, a-z, 0-9, the dash (—), the underscore (_), and the period (.). To specify white space, the label must be quoted (" ").
NOTE: You can specify the os_type here manually, but when the guest boots, the os_type is set to whatever operating system was last booted. The operating system version is only set manually with the -O option. -a rsrc Adds an I/O resource to the new virtual machine. The resource specification (rsrc) is described in hpvmresources(5). This option can be specified more than once. -d rsrc Deletes an I/O resource from the new virtual machine.
-r amount Specifies the amount of memory available to the new virtual machine at boot time. The sizes are expressed as integers, optionally followed by one of these units: • • M (megabytes) G (gigabytes) If the letter is left off, the unit type defaults to megabytes. If the -r option is omitted, the amount of memory is that of the existing virtual machine. -S Specifies that the cloned guest must share the same virtual LAN (VLAN) ports as the source guest.
• -x amr_enable={0|1} Enables or disables AMR monitoring for a guest, where 1 enables and 0 disables. The monitor (amr daemon) adjusts the guest size and take its entitlement into account. • - x amr_chunk_size=amount Specifies the increment amount of changes in memory size (default is 256 MB). Larger values result in faster memory size growth. • -x mac_address={new|same} • -x serial_number={new|same} • -x sched_preference={none|cell|ilm} where: — — — • none — The default preference.
RETURN VALUES The hpvmclone command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmclone command displays error messages on stderr for any of the following conditions: • • • • • • • • • An invalid option is specified. An invalid value is specified for an option. A value was omitted for an argument that requires one, or a value was supplied for an argument that does not take one.
3 4 Active Active avio_lan lan 100 none 1 1 vm2 vm2 OBSOLESCENCE The -F option is deprecated in Integrity Virtual Machines commands. This flag might be removed in a future release of Integrity Virtual Machines. HP recommends use of the command with the -s option, then resolving any errors or warnings that result before executing the command without the -s option and without the -F option. AUTHORS The hpvmclone command was developed by HP.
hpvmcollect(1M) NAME hpvmcollect -- Collects crash dumps, logs, system status, and configuration on the VM Host and guests for post-mortem analysis.
-c Includes the latest crash dump directory in the archive. This option is used if the guest or the VM Host crashes or hangs. Valid on both the VM Host and the guest. -d directory Specifies a target directory in which to create the hpvmcollect_archive directory. Valid on both the VM Host and the guest. -f Forces an archive to be overwritten, if it exists, rather than renamed with an appended timestamp. Valid on both the VM Host and the guest.
Gathering info for post-mortem analysis of guest 'myguest' on host Copying host's device database ...................................... Collecting I/O configuration info ................................... Collecting filesystem info .......................................... Collecting system info .............................................. Collecting lan info ................................................. Running lanshow .....................................................
Collecting system info .............................................. Collecting lan info ................................................. Running lanshow ..................................................... Collecting installed sw info ........................................ Collecting crash dump ............................................... Running crashinfo ................................................... Collecting tombstone ................................................
hpvmconsole(1M) NAME hpvmconsole -- Connect to the console of a virtual machine. SYNOPSIS hpvmconsole { -P vm-name | -p vm-number } [-c command] [-e echar] [-f] [-i] [-q] DESCRIPTION An Integrity VM virtual machine console is similar in appearance to the maintenance processor of an Integrity system. Each virtual machine has its own virtual console from which you can manage the virtual machine and the guest operating system.
2: All other program failures (operational error). DIAGNOSTICS The hpvmconsole command displays error messages on stderr for any of the following conditions: • • • An invalid option is specified. The hpvmconsole command and Integrity VM are at different revision levels. An operational error occurred. EXAMPLES To use the console interactively: # hpvmconsole -p guestname To collect the guest console log in the correct order: # hpvmconsole -P "$GUEST" -q -c cl > $GUEST.
hpvmcreate(1M) NAME hpvmcreate -- Create a new Integrity VM virtual machine. SYNOPSIS hpvmcreate -P vm-name [-K console_IP_Addr] [-L console_IP_Addr_Netmask] [ -F | -s ] [-l vm-label] [-B start-attr] [-O os-type [:version]] [-c number-vcpus ] [ -e percent[:max_percent] | -E cycles[:max_cycles] ] [-r amount] [-g [+] group [: {admin |oper}]] [-u [+] user[: {admin |oper}]] [-a rsrc]...
virtual iLO Remote Console for this guest. The address is entered in dot notation form. -L console_IP_Addr_Netmask During a migration the virtual iLO Remote Console addressing will follow the migration. -e percent[:max_percent] Specifies the percentage of CPU resources to which each of the guest's virtual CPUs is entitled. During peak system CPU load, the entitlement is the guaranteed minimum allocation of CPU resources for this virtual machine.
volumes, and so forth) are collectively referred to as "backing stores." Integrity VM recognizes the following types of guest virtual devices: • • • • • Virtual DVDs, which can be backed by files in a VM Host file system or by physical DVD drives. Virtual disks, which can be backed by files in a VM Host file system, by logical volumes or by whole disks. Attached I/O devices (DVD, tape, changer, and other peripheral device types). Attached AVIO devices (tape, changer, and burner).
initialized on the VM Host. This is the default behavior. The virtual machine can then be started manually with the hpvmstart command or through its virtual console. This option does not set the virtual machine's console to enable booting when the virtual machine is started. This function must be set with the virtual machine's console. -O os-type[:version] Specifies the type and version of the operating system running on the virtual machine.
name. The argument specifies the privilege level available at the virtual console: either admin or oper (the default). This option can be specified more than once. -s Verifies the virtual machine configuration and returns warnings or errors but does not create the virtual machine. This option is used to start the hpvmcreate command's resource checking for a virtual machine configuration without actually creating the virtual machine.
— • scheduler then optimizes where the guest runs, so that it can be closest to its memory. ilm — Indicates that guests that are larger than any single cell and contain highly threaded applications. -x graceful_stop_timeout={0 | number} Specifies the amount of time in seconds to allow a graceful stop when hpvmstop —g is specified. The default is 30 seconds. NOTE: If the graceful stop does not finish within the time frame specified, a hard stop is then executed.
• • A value was omitted for an argument that requires one, or a value was supplied for an argument that does not take one. The hpvmcreate command and the Integrity VM software are at different version levels.
hpvm(5), hpvmclone(1M), hpvmcollect(1M), hpvmconsole(1M), hpvmdevinfo(1M), hpvmdevmgmt(1M), hpvmdevtranslate(1M), hpvmhostgdev(1M), hpvmhostrdev(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmmove_suspend(1M), hpvmnet(1M), hpvmnvram(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmresume(1M), hpvmsar(1M), hpvmsg_move(1M), hpvmsg_package(1M), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), hpvmsuspend(1M), hpvmupgrade(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M),
hpvmdevinfo(1M) NAME hpvmdevinfo -- Report about storage for a virtual machine. SYNOPSIS On the VM Host: hpvmdevinfo [ -P vm-name | -p vm-number ] [ -M | -S | -V ] On the guest: hpvmdevinfo [ -M | -S | -V | -Q ] DESCRIPTION The hpvmdevinfo command displays the available information about the storage devices assigned to a virtual machine. When run on the VM Host, hpvmdevinfo displays information about selected guests or all guests and their assigned storage.
1: One or more error conditions occurred. EXAMPLES The following example, specified on a VM Host, displays information about all guests, in a format suitable for loading into a spreadsheet. # hpvmdevinfo -S The following example, specified on a guest, displays information matching guest devices with VM Host resources: # hpvmdevinfo AUTHOR The hpvmdevinfo command was developed by HP.
hpvmdevmgmt(1M) NAME hpvmdevmgmt -- Manage the devices that are associated with the VM Host and the guests.
Restrict everything in and under a specified directory that is also in the same file system that the specified restricted directory is in. # hpvmdevmgmt -a rdev:/some-directory:attr:RECURSIVE=FS Restrict everything in and under a specified directory, even if sub-paths to the specified restricted directory contain mount points to other file systems.
NOTE: HP recommends that you do not use IGNOREWWID=YES on a multipath device, or use it only on one path of a multipath device, because serious device or guest conflicts could arise. The UUID and PHYSUUID are set up in the Virtual Connect profile. Only superusers can execute the hpvmdevmgmt command. A set of Integrity VM servers can be grouped into an Integrity VM multiserver environment, MSE. This grouping is required when a set of Integrity VM servers is also configured as a Serviceguard cluster.
To restrict the vswitch named myswitch so that it is no longer shareable, enter the following command: # hpvmdevmgmt -m gdev:myswitch:attr:SHARE=NO This command restricts the vswitch called myswitch to use by one guest only. The PRESERVE attribute has the values {YES|NO}. When set to YES, it preserves the existence of a device database entry if, and when, the last guest listed as a dependency on that device is deleted.
• List all devices with a specific dependency: hpvmdevmgmt -V -l {all|server|rdev|gdev}:depend:dependent-name • List a single entry by name: hpvmdevmgmt -V -l {all|server|rdev|gdev}:entry-name -v Displays the version number of the hpvmdevmgmt output format. The version number is displayed first, followed by the display specified by other options. -V Increases the amount of information displayed (verbose mode). -S size filename Creates a file for use as a virtual device.
• Delete an attribute from an entry: -d {server | rdev | gdev}:entry-name:attr:attr-name • Delete one alias if a device has multiple aliases defined. -d gdev_alias:/dev/rdisk/disknn The following limitations apply: — Valid to delete only guest device aliases. — More than one alias must be defined, so that the alias delete does not attempt to delete the only alias.
# hpvmdevmgmt -l gdev:/dev/rdisk/disk2 List all the restricted devices: # hpvmdevmgmt -l rdev List all the guest devices used by the guest phantom: # hpvmdevmgmt -l gdev:depend:phantom List all shareable guest devices (those with the attribute SHARE=YES): # hpvmdevmgmt -l gdev,SHARE=YES Allocate a 4 GB file: # hpvmdevmgmt -S 4G /var/opt/hpvm/guests/mirage/disk_4G_file Create attached (passthrough/esctl) devices: # hpvmdevmgmt -I Modify a guest device attribute on an ISO file from not shared to shared:
3. List the attributes of the parent tape DSF: # hpvmdevmgmt -l gdev:/dev/rtape/tape6_BESTn /dev/rtape/tape6_BESTn:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=NO: lunpath3,lunpath6,lunpath5,lunpath4:0x01.0x00.0x03.0x500104f0004732d8 4. Modify the SHARE_LUNPATHS attribute: # hpvmdevmgmt -m gdev:/dev/rtape/tape6_BESTn:attr:SHARE_LUNPATHS=YES NOTE: The SHARE_LUNPATHS and SHARE attributes take effect only after an hpvmstop command. 5.
hpvmdevtranslate(1M) NAME hpvmdevtranslate -- Translate Integrity VM guest devices into HP-UX 11i v3 agile devices. SYNOPSIS hpvmdevtranslate [-v] -a hpvm_mgmtdb hpvmdevtranslate [-v] -a hpvmdevtranslate [-v] -P guestname hpvmdevtranslate [-v] -u hpvmdevtranslate [-v] DESCRIPTION The primary purpose of this program is to help Integrity VM administrators upgrade an Integrity VM host from HP-UX 11i v2 to HP-UX 11i v3.
To convert a single guest, use the following command: # hpvmdevtranslate -P guestname You can use the hpvmdevtranslate command to undo the previous translation if the translation is not more than five days old. The undo operation is run with the following command: # hpvmdevtranslate -u Options The following options can be specified only once. The hpvmdevtranslate command recognizes the following command-line options and arguments: -v Displays the version number of the hpvmdevtranslate command.
hpvm(5), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevinfo(1M), hpvmdevmgmt(1M), hpvmhostgdev(1M), hpvmhostrdev(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmmove_suspend(1M), hpvmnet(1M), hpvmnvram(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmresume(1M), hpvmsar(1M), hpvmsg_move(1M), hpvmsg_package(1M), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), hpvmsuspend(1M), hpvmupgrade(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M), hpvmmgmt(1M), hpvmpu
hpvmhostgdev(1M) NAME hpvmhostgdev -- Manages Integrity VM Host devices available for virtual machine access. SYNOPSIS hpvmhostgdev [-H | -u | { -a | -c {disklist|lvlist} | -l [>devlistfile] } | -d | -f devlistfile| -r | -v { all|assigned|unassigned }] DESCRIPTION The hpvmhostgdev command analyzes disklist and lvlist output searching for unused disks and logical volumes (LVs). It uses its results to add unused devices to the Integrity VM device database as guest devices (gdevs).
-f Uses specified device-list file to add devices for guest use. -l Lists unused devices that can be added for guest use. (For example, pipe —l output to a file for use with —f.) -r Recovers the Integrity VM device management database. -u Uses disklist device cache (Do not force hardware scan.). NOTE: This option is used to speed up the disklist command to obtain unused disks.
hpvm(5), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevinfo(1M), hpvmdevmgmt(1M), hpvmdevtranslate(1M), hpvmhostrdev(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmmove_suspend(1M), hpvmnet(1M), hpvmnvram(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmresume(1M), hpvmsar(1M), hpvmsg_move(1M), hpvmsg_package(1M), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), hpvmsuspend(1M), hpvmupgrade(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvmmgmt(1M), hpvmpubapi(3) 2
hpvmhostrdev(1M) NAME hpvmhostrdev -- Manages virtual machine access to devices used by the Integrity VM Host system. SYNOPSIS hpvmhostrdev [-D | -E | -d | -h | -r | -u] DESCRIPTION The hpvmhostrdev command manages virtual machine access to devices — disks and volumes — used by the VM host system. The Integrity VM device-management database (hpvmdevmgmt (1M) provides the capability to restrict virtual machine access to devices used by the VM Host.
-E Enables automatic execution of hpvmhostrdev during startup of the Integrity VM software. Subsequent startup of the Integrity VM system (that is, /sbin/init.d/hpvm start), automatically identifies, updates, and restricts use of the VM Host system's storage devices. Note that execution of hpvmhostrdev -E does not — by itself — add restricted device entries to the Integrity VM device database.
hpvm(5), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevinfo(1M), hpvmdevmgmt(1M), hpvmdevtranslate(1M), hpvmhostgdev(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmmove_suspend(1M), hpvmnet(1M), hpvmnvram(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmresume(1M), hpvmsar(1M), hpvmsg_move(1M), hpvmsg_package(1M), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), hpvmsuspend(1M), hpvmupgrade(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvmmgmt(1M), hpvmpubapi(3) 2
hpvminfo(1M) NAME hpvminfo -- Display information about the Integrity VM environment. SYNOPSIS hpvminfo [ -V | -M | -X ] [ -v | -S ] DESCRIPTION Allows you to determine whether you are running in a guest or on the VM Host. When run in a guest, this command returns information to identify the VM Host as well as the guest. Information can be presented in several formats. The -M option displays in a machine-readable format, while the -X option displays in the XML format.
# hpvminfo hpvminfo: Running on an HPVM host. The following example demonstrates the command running inside a guest. # hpvminfo hpvminfo: Running inside an HPVM guest. The following example shows detailed information about the VM Host from within a guest. # hpvminfo -V hpvminfo: Running inside an HPVM guest.
hpvmmgmt(1M) NAME hpvmmgmt -- Manage dynamic data within the Integrity VM guest environment. SYNOPSIS hpvmmgmt [-l type] [ -V | -M | -X ] [-v] hpvmmgmt [-l type] [-t interval] [-V] [-v] hpvmmgmt [-c num] [-v] hpvmmgmt [-v] [-x keyword=value ] | [-x keyword=value [:keyword=value]] DESCRIPTION The hpvmmgmt command allows you to view and potentially manage dynamic guest data. To manage the data, the VM Host must have configured the guest to do so.
The -V, -M, and -X options are mutually exclusive. Displays verbose attribute and resource information in the XML format. -X The -V, -M, and -X options are mutually exclusive. -x keyword=value Specifies virtual machine characteristics.
Target memory Comfortable minimum Minimum memory Maximum memory Boot memory Free memory Available memory Memory pressure Memory chunksize Driver Mode(s): STARTED : 2103 MB : 2423 MB : 1222 MB : 6144 MB : 6135 MB : 124 MB : 286 MB : 12 : 65536 KB ENABLED GUESTCTL The following example sets the dynamic RAM target to the original boot amount: # hpvmmgmt -x Attempting to Successfully # hpvmmgmt -x Attempting to Successfully ram_target=0 decrease memory from 2039 MB to 745 MB.
hpvmmigrate(1M) NAME hpvmmigrate -- Migrate an active guest or an offline virtual machine to a specified VM Host. SYNOPSIS hpvmmigrate { -P vm-name | -p vm-number } -h target-host-alias-or-IP-addr [-l new-vm-label ] [-N new-vm-name] [-D] [-n] [-s] [-F] [-q] [ -e percent [:max_percent] | -E cycles[:max_cycles] ] [-c number-vcpus ] [-r amount] [-m rsrc-with-absolute-path [-C] [-t]]...
hpvmmodify command, if necessary, to mark the guest Runnable on only one single VM Host, and Not Runnable on all other VM Hosts that have the virtual machine configured. When hpvmmigrate sets the guest to Not Runnable state (runnable_status=disabled) , it also sets modify_status=disabled and visible_status=disabled. Likewise, when hpvmmigrate sets the guest to a Runnable state, it also sets modify_status=enabled and visible_status=enabled.
is allocated the minimum percentage of 5%. The default is 10%. Integrity VM reserves processing power for essential system functions such as logging, networking, and file system daemons. The -e and the -E options are mutually exclusive. -E cycles[:max-cycles] For offline migration, specifies the virtual machine's CPU entitlement in CPU cycles. The cycles are expressed as an integer, followed by one of these units: • • M (megahertz) G (gigahertz) If no letter is specified, the default unit is megahertz.
the dash (—), the underscore (_), and the period (.). To specify white space, the label must be quoted (" "). -m rsrc-with-absolute-path For offline migration, specifies a resource of a virtual machine for copying, translation, and so on. For a network specification, use the following syntax: -m network:lan::vswitch:OLD:network:lan::vswitch:NEW This option can be specified more than once. For information about specifying virtual machine storage and network resources for guests, see hpvmresources(5).
• • M (megabytes) G (gigabytes) If the letter is omitted, the default unit is megabytes. -s Indicates that the migration should not occur, but the hpvmmigrate command should check whether or not the migration is possible. Because guests and their VM Hosts are dynamic, a successful -s trial does not always guarantee a subsequent successful migration. The hpvmmigrate command with the -o, -s, and -h options (but without a -p or -P option) checks host connectivity and CPU compatibility for online migration.
HPVM_OVMM_ENCRYPT_BY_DEFAULT variable to 0, changes this default behavior. Requires encryption negotiation and sends guest memory data with protection. -y You can modify the default behavior by setting variables in the /etc/rc.config.d/hpvmconf file using the ch_rc command. The variable HPVM_OVMM_ENCRYPT_BY_DEFAULT controls whether any attempt at encryption negotiation is done. The default setting of 1 attempts an encryption negotiation.
• • • • • Invalid virtual machine configuration. Remote execution error. Virtual machine resource validation error. A remote vswitch is not present or not active. The version of the hpvmmigrate command is incompatible with the version on the target VM Host. EXAMPLES Display the version number of the hpvmmigrate command. # hpvmmigrate -v hpvmmigrate: Version B.04.30 Migrate the offline virtual machine named host1, to the host abc.def.com. # hpvmmigrate -P host1 -h abc.def.
hpvmmodify(1M) NAME hpvmmodify -- Rename a virtual machine or modify the attributes of a virtual machine. SYNOPSIS hpvmmodify { -P vm-name | -p vm-number } [-K console_IP_Addr] [-L console_IP_Addr_Netmask] [ -F | -s ] [-N new-vm-name] [-l vm-label] [-B start-attr] [-O os-type [:version]] [-c number-vcpus] [-r amount] [ -e percent[:max_percent] | -E cycles[:max_cycles] ] [-g -group]... [-g [+]group[: {admin | oper}]]... [-u -user]... [-u [+]user:[ {admin | oper}]]...
Options The hpvmmodify command recognizes the following command-line options and arguments. -P vm-name Specifies the name of the virtual machine to be modified. You must specify either the -P or the -p option. -p vm-number Specifies the number of the virtual machine to be modified. The vm-number is displayed by the hpvmstatus command. You must specify either the -P or the -p option. -K console_IP_Addr Specifies the IP address used to connect to the guest's virtual iLO Remote Console.
In addition to the guest calculation, Integrity VM reserves processing power for essential system functions such as logging, networking, and file system daemons. The -e and the -E options are mutually exclusive. NOTE: If you change from -e percent to -E cycles on a guest that previously had a maximum configured and do not specify a maximum, then the default maximum value is chosen.
the dash (—), the underscore (_), and the period (.). To specifiy white space, the label must be quoted (" "). -B start-attr Specifies the startup behavior of the virtual machine. The start_attr argument can have the following (case-insensitive) values: • auto: Automatically start the virtual machine when Integrity VM is initialized on the host. • manual: Manually start the virtual machine. This is the default.
NOTE: When assigning a null device to a resource on a virtual machine, the file name serves as a placeholder. Therefore, if the file does not exist, you do not receive an error. For example, in the following command, if the file XXX.iso does not exist, no error is given. # hpvmmodify -P vm1 -a disk:scsi::null:/opt/XXX.iso The resource is specified as described in hpvmresources(5). This option can be specified more than once. -d rsrc Deletes an I/O resource from a virtual machine.
NOTE: The rmsf -L command should not be executed on an Integrity VM server until all guest devices names have been changed to agile device names. The following commands are helpful for reconfiguring guests to use agile device names: • insf By default, creates both persistent and legacy DSFs for new devices. • insf -L Restores legacy DSFs and legacy configuration information. • rmsf -L Aids in migration by removing all legacy DSFs and legacy configuration information.
maximum equal to the maximum vCPUs supported for the specific guest operating system type. Integrity VM Version 4.3 supports up to 16 vCPUS for all guest types. For example, to set a guest with four vCPUs with no range, use the following command: # hpvmmodify -P guestname -c 4 To set a quest with four vCPUs with a range of two to six vCPUs, use the following command: # hpvmmodify -P guestname -c 4:2:6 -r amount Specifies the amount of memory available to this virtual machine.
• -x ram_dyn_max=amount • -x ram_dyn_target_start=amount Specifies whether the virtual machine's dynamic memory settings are automatically adjusted. The ram_dyn_entitlement and amr_enable options must be set to enable adjustments. • -x ram_dyn_entitlement=amount Specifies the minimum guaranteed amount of memory. • -x amr_enable={0|1} Enables or disables AMR monitoring for a guest, where 1 enables and 0 disables. The monitor (amr daemon) adjusts the guest size and take its entitlement into account.
• -x runnable_status={disabled|enabled} Specifying runnable_status=disabled prevents the guest from being started. It also prevents other guests from booting if they share devices with a disabled guest whose devices are marked SHARE=NO. Specifying enabled allows guest to be started again. Set -x runnable_status=disabled only with the hpvmmodify command. An error message is printed if it is specified with the hpvmcreate or the hpvmclone commands.
NOTE: HP does not recommend using -x runnable_status, -x modify_status, or -x visible_status except with extreme caution. 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. If modify_status is disabled, the VM is most likely running on another VM Host. Any modification made to this VM's configuration will be lost when it is migrated back to this VM Host.
• number of seconds the migration spends during the quiesce stage. The default is 15 seconds. -x online_migration= {enabled | disabled} RETURN VALUES The hpvmmodify command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmmodify command displays error messages on stderr for any of the following conditions: • • • • • • • • • • • An invalid option is specified. An invalid value is specified for an option, or a value is omitted.
# hpvmmodify -P myguest2 -e 10:20 Temporarily change the CPU entitlement to 50% until virtual machine myguest2 is rebooted: # hpvmmodify -A -P myguest2 -e 50 The following are sample warning messages returned when the hpvmmodify command is executed with various configuration problems on the guest myguest1: HPVM guest myguest1 configuration problems: Warning 1: Guest needs more vcpus than server supports. Warning 2: Insufficient free memory for guest. Warning 3: Insufficient swap resource for guest.
hpvmmove_suspend(1M) NAME hpvmmove_suspend -- Move suspend files to a different directory. SYNOPSIS hpvmmove_suspend { -d | -D directory } [-q] DESCRIPTION The hpvmmove_suspend command changes the directory where suspend files are stored and moves all existing suspend files to the new directory. Suspend files can be very large, up to the size of guest memory for each suspended guest. If there is insufficient space in /var to accommodate them, this command can be used to move them to a larger disk.
AUTHOR The hpvmmove_suspend command was developed by HP.
hpvmnet(1M) NAME hpvmnet -- Create and control an Integrity Virtual Machines virtual network switch (vswitch).
By default, Integrity VM creates a vswitch named localnet that is not associated with a physical interface. It is used only for communication between the guests running on the same VM Host; the VM Host itself does not participate in a localnet. There is no nameserver or router configured on a localnet, unless one of the guests performs this function. Only superusers can execute the hpvmnet command. Two classes of virtual network interface are supported in Integrity VM: lan and avio_lan.
Inbound Non-Unicast Pkts (local) Inbound Discards Outbound Octets 3557451342b Outbound Unicast Pkts (wire) : 36 : : 20000 Outbound Unicast Pkts (local) : 300000 Outbound Non-Unicast Pkts : 400000 Outbound Discards -M : 30000 : 0 Displays verbose resource information in a machine-readable format. Individual fields are separated by one of the following delimiters: • • • The colon (:) separates each field and resource type. The semicolon (;) separates subfields of a resource type.
Specifies the VLAN identifier for the specific vswitch and -u portid:portnum:vlanid:{vlanid port. Configure VLANs by specifying the number of the port on the vswitch (portnum) to use for VLAN | none} communication, and the VLAN identifier (vlanid). Virtual machines that are configured to use the VLAN can communicate with one another. To disable a VLAN, specify none for the VLAN identifier.
• • A value was omitted for an argument that requires one, or a value was supplied for an argument that does not take one. The hpvmnet command and Integrity Virtual Machines are at different revision levels.
Delete the vswitch named switch2: # hpvmnet -d -S switch2 hpvmnet: Remove the vswitch 'switch2'? [n/y]: y Delete the vswitch with the vswitch ID of 6, and omit the confirmation dialog: # hpvmnet -d -s 6 -F Start the vswitch named switch1: # hpvmnet -b -S switch1 Stop the vswitch named switch1: # hpvmnet -h -S switch1 hpvmnet: Halt the vswitch 'switch1'? [n/y]: y Configure port 2 on vswitch switch1 with VLAN identifier 100: # hpvmnet -S switch1 -u portid:2:vlanid:100 Display information about VLAN ports
[Port Configuration Details] Port Port Port Untagged Number of Active VM Tagged Number state Adaptor VLANID Reserved VMs VLANIDs ======= ============ ======== ======== ============ ============ ============ 2 Available avio_lan 20 0 AUTHORS The hpvmnet command was developed by HP. OBSOLESCENCE The -F option is deprecated in Integrity Virtual Machines commands. This flag might be removed in a future release of Integrity Virtual Machines.
hpvmnvram(1M) NAME hpvmnvram -- Display, create, edit and remove EFI variables in NVRAM files from a VM Host.
to obtain a list of virtual disk devices currently assigned to the virtual machine. • boot_order Specifies the entry where the new boot option is to be placed in the EFI BootOrder ordered list. If boot_order is not specified, a default value of "1" is assigned as the boot order. • efi_file_path Specifies the path of an EFI application, such as an EFI OS loader, to be used with the new boot option.
—Q Quietly performs the command. When used with the -a, -d, -m, -S, or -R options, the reminder to back up the NVRAM file is suppressed. -P vm-name Specifies the name of the virtual machine whose current NVRAM file is used. -p vm-number Specifies the number of the virtual machine whose current NVRAM file is used. The vm_number is assigned when a virtual machine is created and is displayed by the hpvmstatus command.
2 3 Boot0002 Boot0000 Guest Device: Bus 0, Dev 1, Ftn 0, Tgt 2, Lun 0 EFI Shell [Built-in] Move the second boot option to be the first boot option in the virtual machine named guest3: # hpvmnvram -P guest3 -m 2:1 You should make a backup copy of this nvram file before proceeding with changes.
# hpvmnvram -G Timeout -P guest3 Variable NV+RT+BS '61DFE48B-CA93-D211-AA0D00E098032B8C:Timeout' DataSize = 2 0000 | 0x 00 00 Remove the variable panicinfo for 3CC469BA-5744-11D4-868E7F7F00000000 GUID of the virtual machine named guest3: # hpvmnvram -R 3CC469BA-5744-11D4-868E7F7F00000000:panicinfo -P guest3 AUTHOR The hpvmnvram command was developed by the HP.
hpvmpubapi(3) NAME hpvmpubapi -- Integrity VM public application interface descriptions. SYNOPSIS #include
DIAGNOSTICS There are no error returns for the hpvm_api_server_check and hpvm_api_virtmach_check routines. If an error occurs on the hpvm_api_version_get, hpvm_api_my_uuid_get, hpvm_api_server_uuid_get, or hpvm_api_server_hostname_get routine, one of the following error codes defined in hpvm_api_public.h is returned: • HPVMAPINOMEMORY — Inadequate memory resources. • HPVMAPIINVALARG — Invalid argument. • HPVMAPIBADFORMAT — Retrieved uuid was formatted badly.
hpvmremove(1M) NAME hpvmremove -- Remove an Integrity VM virtual machine. SYNOPSIS hpvmremove { -P vm_name | -p vm_number } [-F] [-Q] DESCRIPTION The hpvmremove command deletes a virtual machine's configuration information and frees any resources associated with it. Once the virtual machine has been removed all resources associated with the virtual machine become available for allocation to other virtual machines.
• • The vm_name argument is in some state other than Off. The hpvmremove command and Integrity VM are at different revision levels. EXAMPLES Delete the virtual machine myguest: # hpvmremove -P myguest hpvmremove: Remove the virtual machine myguest? [n/y]: y Delete a virtual machine using its unique identifier using the force option: # hpvmremove -F -p 333 Remove a running guest: # hpvmremove -P hpux1 hpvmremove: The guest is currently running, not able to remove. hpvmremove: Unable to continue.
hpvmresources(5) NAME hpvmresources -- Specifying virtual storage and virtual network devices. SYNOPSIS Virtual resource specification DESCRIPTION Use the hpvmcreate, hpvmclone, and hpvmmodify commands to specify storage devices and vswitches for guests. To specify the name of the storage device or vswitch, use the syntax described here. The resource specification contains the virtual device information and the backing store information, separated by a colon (:).
• null. Specify an empty storage unit. Do not specify a world-writable directory such as tmp. (This is useful for removable media, such as DVDs.) NOTE: When assigning a null device to a resource on a virtual machine, the file name serves as a placeholder. Therefore, you do not receive an error if the file does not exist. For example, in the following command, if the file XXX.iso does not exist, no error is given. # hpvmmodify -P vm1 -a disk:scsi::null:/opt/XXX.iso • • attach.
network:adaptertype:bus,device,mac-addr:vswitch:vswitch-name:portid:portnumber If you omit any portion of the network resource specification, use the colon character (:) as a field delimiter.
• • The physical network device type is vswitch. The vswitch name is net1. AUTHORS The hpvmresources command was developed by HP.
hpvmresume(1M) NAME hpvmresume -- Resume a virtual machine. SYNOPSIS hpvmresume { -P vm-name | -p vm-number } [-F] [-s] [-Q] DESCRIPTION The hpvmresume command causes the specified virtual machine to resume. The virtual machine must exist and be in the suspended state. The hpvmresume command verifies that the virtual machine can be allocated all of the required resources defined by its configuration file. If this is not possible, the virtual machine is not resumed.
RETURN VALUES The command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmresume command displays error messages on stderr for any of the following conditions: • An invalid option is specified. • The vm-name or vm-number does not exist, cannot be accessed, is not a virtual machine, or is corrupt. • The virtual machine is in a state other than suspended and cannot be resumed.
hpvmsar(1M) NAME hpvmsar -- Integrity VM system activity reporter. SYNOPSIS hpvmsar { -a | -A | vm-name[...] } [-M] [-s rate ] [-n count ] [-h rate] hpvmsar -I { -a | -A | vm-name[...] } [-M] [-m mode] [-s rate ] [-n count ] [-h rate] hpvmsar -H [-s rate ] [-n count ] [-h rate] hpvmsar -F { -a | -A | vm-name[...] } [-M] [-s rate ] [-n count ] [-h rate] hpvmsar -G { -a | -A | vm-name[...] } [-s rate ] [-n count ] [-h rate] hpvmsar -N { -a | -A | vm-name[...
• • • • [-a | -A | vm-name [...]] 0: Stacked up values — Stacks up busy time, idle time, and wait time vertically. Busy time is on the bottom and wait time is on the top of the column. 1: Cumulative view — Stacks the busy time of multiple guests from the left of the window and the wait time of multiple guests from the right of the window. This mode makes it possible to see how multiple guest share the total available host time.
NOTE: • • • • • • • • • • • • • • -F This option is for HP-UX guests only. GDISK — Name of the guest disk in persistent dsf format. G%BUSY – As seen from the guest, this is the percentage of time, over the interval, that the disk device was busy servicing an I/O request. GAVQUE —Average number of I/O requests outstanding for this guest disk as seen from the guests point of view. GR+W/s — This is the number of read and write I/O transfers performed per second as seen from the guest.
• • • • • • -G SET_RR — Number of time the RR was reset during guest execution. TPA — Number of TPAs completed for the guest. ITLB — Number of instruction TLB entries needed by guest access were missing and had to be inserted. ITC_D — Number of va/pa address inserts into translation cache. PTC_GA — Number of PTC in guest vCpu. PTC_GA is similar to PTC_G. DKEYMISS — Number of Data Key Misses for the guest. Display the Guest Dynamic Memory, Swapping, and Paging Activity for the sample interval.
• • • • -I HADDRTMISS/s — Number of address translation faults per second on the VM Host. VADDRTMISS — Number of address translation faults per second for Integrity VM kernel module (vmm). HDYNRCLM(MB) — Unused memory reclaimed from all booted guests for use by dynamic memory. This memory is able to be distributed to guests and VM Host by dynamic memory based upon memory utilization of host and guests and dynamic memory settings. If AMR is enabled, this distribution is done automatically.
• • • • TX — Transmit rate in megabytes/second for named guest/vswitch/port over interval specified. RX Mb/s — Receive rate in megabytes/second for named guest/vswitch/port over interval specified. TXDROPS — Number network transmit packet dropped by the port over interval specified. RXDROPS — Number network receive packet dropped by the port over interval specified. NOTE: The Integrity VM guest kit for HP-UX guests must be installed to receive output with the -G or -D options.
HBLKS/s HAVWAIT HAVSERV 17:43:43 ux1 disk1 134 0.00 0.98 17:43:43 ux1 disk8 0 0.00 0.00 17:43:44 ux1 disk1 0.00 0.12 17:43:44 ux1 disk8 0 0.00 0.00 17:43:45 ux1 disk1 0 0.00 0.00 2.00 0.50 13 134 0.00 1.11 disk12 1.00 0.50 13 0.00 0.00 0 0 0.00 0.00 disk14 0.00 0.00 0 0.00 0.50 2 0.00 0.00 0 0 0.00 0.00 disk14 0.00 0.00 0 0.00 0.00 0 0 0.00 0.00 disk12 0.00 0.00 0 0.00 0.28 disk12 0.00 0.
hpvmsg_move(1M) NAME hpvmsg_move -- Initiate an online migration of a virtual machine that has previously been associated with a Serviceguard package. SYNOPSIS hpvmsg_move [-v] [-h target-node | -n target-node] [-P vm-name] DESCRIPTION The hpvmsg_move command initiates an online migration (move) of a virtual machine that has previously been associated with a Serviceguard package.
6: The target node is not up and running. 7: The backing storage is not compatible with online migration. 8: The package is not running on the local node. 9: Attempt to re-enable package on local node failed. DIAGNOSTICS The hpvmsg_move command displays error messages on stderr for errors and warnings encountered during execution. EXAMPLE The following example moves a Serviceguard package online from one node to another.
hpvmsg_package(1M) NAME hpvmsg_package -- Assist the user who is developing and managing a set of Serviceguard package configurations. SYNOPSIS hpvmsg_package [ -V | -Q | -L | -s | -U ] [-m { 0 | 1 }] [ -x {file | name= [value]} ]... [ -n node [, node]... ]... [-P vm-name] DESCRIPTION The hpvmsg_package command assists the user who is developing and managing a set of Serviceguard package configurations and associated toolkit files.
— service-restart — An application monitor restart value (service_restart). service-halt-timeout — An application monitor halt timeout value in seconds (service_halt). module-attribute-custom-value — A Serviceguard module attributes and values. For example, logging_level=5 file — A file containing any of the above attributes, one per line. — — — RETURN VALUES The hpvmsg_package command returns the following values: 0: Successful completion. 1: Inappropriate command line or configuration error.
disk scsi 0 0 0 disk scsi 0 0 0 disk scsi 0 0 0 disk scsi 0 0 0 disk scsi 0 0 0 disk scsi 0 0 0 [Network Interface Details] Interface Adaptor Name/Num ========= ========== ========== vswitch lan intl100 vswitch lan igelan 2 3 4 5 6 7 0 0 0 0 0 0 disk file lv file lv file /dev/rdisk/disk978 /guest/g1-N-DF-SCRATCH/file /dev/g1-N-L-SCRATCH/rlvol1 /guest/g1-N-LF-SCRATCH/file /dev/vx/rdsk/g1-N-V-SCRATCH/g1-N-V-SCRATCH_lv /guest/g1-N-VF-SCRATCH/file PortNum Bus Dev Ftn Mac Address ======= === === === =======
hpvm(5), hpvmclone(1M), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevinfo(1M), hpvmdevmgmt(1M), hpvmdevtranslate(1M), hpvmhostgdev(1M), hpvmhostrdev(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmmove_suspend(1M), hpvmnet(1M), hpvmnvram(1M), hpvmpubapi(3), hpvmresources(5), hpvmresume(1M), hpvmsar(1M), hpvmsg_move(1M) , hpvmstop(1M), hpvmsuspend(1M),hpvmupgrade(1M)p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M), hpvmmgmt(1M), hpvmpubapi(3) 341
hpvmstart(1M) NAME hpvmstart -- Start a virtual machine. SYNOPSIS hpvmstart { -P vm-name | -p vm-number } [ -F | -s ] [-Q] DESCRIPTION The hpvmstart command causes the specified virtual machine to start. The virtual machine must exist and be in the off state. The hpvmstart command verifies that the starting virtual machine can be allocated all of the required resources defined by its configuration file. If not, the virtual machine is not started.
RETURN VALUES The command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmstart command displays error messages on stderr for any of the following conditions: • • • • • An invalid option is specified. The vm-name or vm-number does not exist, cannot be accessed, is not a virtual machine, or is corrupt. The virtual machine is in a state other than off and cannot be started. Use the hpvmstop command to stop the virtual machine.
hpvmstatus(1M) NAME hpvmstatus -- Display status information about one or more virtual machines.
The hpvmstatus command displays the active configuration for guests that are on, including the resource assignments that are currently in effect. For guests with a status of off, the command displays the configuration to be used when the guest in next booted. The hpvmstatus command displays variety of information: • • • • • • To list all the virtual machines that are on the VM Host, enter the hpvmstatus command without the -P, -p, -e, or -r option.
• State: — Off => guest is not started — Off (NR) => guest is not started and is not runnable — On => guest is started — On (EFI) => guest is started and running in EFI — On (OS) => guest is started and running in the operating system — On (RMT) => guest is started and running as a Serviceguard-packaged VM on another member of the cluster. See Runsysid.
-X Displays verbose information about attribute and resource in XML format, including information on migrating virtual machines. The -V, -M, and -X options are mutually exclusive. -P vm-name Specifies the name of the virtual machine for which information is to be displayed. The -P and -p options are mutually exclusive. -p vm-number Specifies the number of the virtual machine for which information is to be displayed.
• • • • • • • • • • • • • DynMem Min: The minimum memory that can be dynamically allocated to this virtual machine with the dynamic memory allocation capability or automatic memory reallocation (AMR). Memory Entitle: The value of the desired memory allocation for the virtual machine. It may be set manually or automatically (by AMR). : The amount of memory entitlement this virtual machine is guaranteed to have allocated to it, provided it has memory demand.
Prefer column for guests that are not started. Once started, the cell number, or ilm is displayed. Displays the guest configuration differences between the next start and the last start guest configurations. If there are no differences, the following messages is printed and the next start configuration replaces the current configuration: -A No differences were found. Copy has been removed. If only the last configuration is present, the following message is returned: No next start configuration found.
EFI Location Pattern File location ... : /opt/hpvm/guest-images/common/efi : /opt/hpvm/guest-images/common/patterns.
====== =========== ======= ======= ================ 0 108MHz 1300MHz 1.
[Guest Cell Local Memory Usage] Cell MB MB MB Virtual Machine Name VM # Prefer Interleave Home Cell Other Cell ==================== ===== ====== ========== ========== ========== lp0 1 none 0 0 0 lp1 2 1 15 12371 2 lp2 3 cell 0 0 0 lp3 4 ilm 15 0 32783 AUTHORS The hpvmstatus command was developed by the HP.
hpvmstop(1M) NAME hpvmstop -- Stop a virtual machine. SYNOPSIS hpvmstop { -P vm-name | -p vm-number | -a } [ -h | -g ] [-F] [-q] [-Q] DESCRIPTION The hpvmstop command stops a running virtual machine by simulating the operations performed at the system console on a physical system. The command can perform a hard stop, which functions like a power failure, or a graceful stop, in which the guest operating system receives notification and time to perform cleanup operations before the stop.
NOTE: If neither -g nor -h are specified, a hard stop is performed. The -h and -g options are mutually exclusive. Specifies the force option. Omits the confirmation dialog before resetting the virtual machine. This option is intended for use by scripts and other noninteractive applications. -F The -F option is deprecated in Integrity Virtual Machines commands. -q Makes certain scripted operations less verbose (quiet mode). -Q Quietly performs the command.
SEE ALSO On the VM Host: hpvm(5), hpvmclone(1M), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevinfo(1M), hpvmdevmgmt(1M), hpvmhostgdev(1M), hpvmhostrdev(1M), hpvminfo(5), hpvmmigrate(1M), hpvmmodify(1M), hpvmmove_suspend(1M), hpvmnet(1M), hpvmnvram(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmresume(1M), hpvmsg_move(1M), hpvmsg_package(1M), hpvmstart(1M), hpvmstatus(1M), hpvmsuspend(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M), hpvmmgmt(1M), hpvmpubapi(
hpvmsuspend(1M) NAME hpvmsuspend -- Suspend a virtual machine. SYNOPSIS hpvmsuspend { -P vm-name | -p vm-number } [-F] [-n] [-q] [-Q] [-s] hpvmsuspend -A { -P vm-name | -p vm-number } hpvmsuspend -v hpvmsuspend -H DESCRIPTION The hpvmsuspend command suspends a virtual machine. A virtual machine that is suspended does not use CPU or memory resources. The resources that are defined in the virtual machine's configuration file are checked to determine whether the migrated virtual machine can be suspended.
0: Successful completion. 1: One or more error conditions occurred when parsing the command. 2: One or more error conditions occurred during the suspension. DIAGNOSTICS The hpvmsuspend command displays error messages on stderr for any of the following conditions: • An invalid option is specified. • An invalid value is specified for an option. • A value is omitted for an argument that requires one, or a value is supplied for an argument that does not take one.
hpvmupgrade(1M) NAME hpvmupgrade -- Assist an Integrity VM upgrade. SYNOPSIS hpvmupgrade -e [-v] DESCRIPTION The hpvmupgrade command performs operations specific to an Integrity VM version upgrade. The -e option 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. The hpvmupgrade command produces the following log file: /var/opt/hpvm/common/hpvmupgrade.current_date_and_time.
p2vassist(1M) NAME p2vassist -- Physical to virtual migration assistant. SYNOPSIS p2vassist function-number DESCRIPTION The p2vassist command is a menu-driven application that helps migrate applications from a running physical or virtual machine to another. To start the script, enter the p2vassist command: # p2vassist P2V Assistant Manager ====================================== 1 ) General Configurations 2 ) Manage Applications 3 ) Manage O.S.
----0 ) Return • List Applications This option lists the products installed on the server. You can obtain the names of the depots to consolidate from this listing. The list returned does not contain Operational Environment related packages. The list of packages to exclude is stored in a configuration file (see the Add Data Directories/Files item in this list).
system-level directories are rejected by default (such as ./, /var, and /usr). If you specify a software depot, p2vassist reads the data directories from the depot definition. These directories appear as a suggestion to the user.
3 Manage Operating System Images This option is not supported in the current version of Integrity VM. RETURN VALUES Upon completion, the p2vassist command returns with one of the following values: 0: Successful completion. The application was successfully consolidated. 1: An error occurred. EXAMPLES The following example shows how to consolidate applications: # p2vassist P2V Assistant Manager ====================================== 1 ) General Configurations 2 ) Manage Applications 3 ) Manage O.S.
gdbm . . hpuxwsAPACHE hpuxwsTOMCAT hpuxwsWEBMIN hpuxwsXML . . vim xpm zlib 1.8.3 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 This example shows the correct names of the depots that can be obtained. In this example, consolidates the web server suite (hpuxwsAPACHE, hpuxwsTOMCAT, hpuxwsWEBMIN and hpuxwsXML).
4 ) Consolidate Applications ----0 ) Return Enter Option Number: 4 Consolidate Applications ============================== This option will consolidate application(s) installed on the current system and then migrate into another a suitable target system. The target system is the machine which will host the consolidated application(s). This wizard requires that non-interactive Secure Shell (ssh) access be set up between this system and the target server.
Glossary This glossary defines the terms and abbreviations as they are used in the Integrity VM product documentation. Accelerated Virtual Input/Output See AVIO adoptive node The cluster member where the package starts after it fails over. APA Auto Port Aggregation. An HP-UX software product that creates link aggregates, often called “trunks,” which provide a logical grouping of two or more physical ports into a single “fat pipe”.
its entitlement, depending on the virtual machine's demand for processor resources and the overall system processor load. event log Information about system events. An event log indicates what event has occurred, when and where it happened, and its severity (alert level). Event logs do not rely on normal I/O operation. extensible firmware interface See EFI.
online VM migration Enables a running guest and its applications to be moved from one VM Host to another without service interruption. OVMM Online VM migration. See online VM migration. package configuration script A script that is customized for each virtual machine Serviceguard package and that contains specific variables and parameters, including logical volume definitions, for that virtual machine. package control script A script containing parameters that control how Serviceguard operates.
virtual machine migration Migration of a virtual machine from one VM Host system to another by using the Integrity VM command hpvmmigrate. Do not use this command for virtual machine packages. virtual machine package A virtual machine that is configured as a Serviceguard package. virtual network A LAN that is shared by the virtual machines running on the same VM Host or in the same Serviceguard cluster. virtual switch See vswitch. VM See Virtual machine. VM Host The virtual machine host system.
Index A adapters virtual storage, 94 adding virtual storage, 117 admin privileges, 152 Administrator guest, 115 VM Host, 113 Agile device names, 47 APA, using, 124 applications running on guests, 21 running on VM Host, 21 attachable devices specifying, 110 attached devices, 95 attached I/O, 85 Auto Port Aggregation (see APA) autoboot, 66 Automatic cell balancing, 51 automatic memory reallocation, 167 AVIO using, 19 B bundle names, 30 C CD/DVD burner, virtual, 85 characteristics of virtual machines, 48 clo
hpvminfo command, 43 hpvmmigrate command, 179 hpvmmodify command, 62 hpvmnet command, 124 hpvmremove command using, 70 hpvmstart command options, 60 hpvmstatus command, 149 displaying VLANs with, 135 hpvmstop command, 69 I installing guest management software , 154 installing HP-UX guest management software, 76 installing HP-UX guests, 73 installing Integrity VM, 29, 31 Integrity Virtual Machines (see Integrity VM) Integrity VM installation requirements, 29 installing, 29 problems installing, 44 removing,
configuring, 138 symmetric configuration for virtual machine migration, 176 system requirements (see Hardware requirements) T tagged frames, 134 tape, virtual, 85 troubleshooting dynamic memory problems, 165 HP-UX guest creation problems, 77 Integrity VM installation problems, 44 network problems, 138 P2V problems, 198 virtual machine creation, 71 VLAN problems, 140 U Update-UX, 39 upgrading guests, 38 Integrity VM, 33 user guest, 116 Using virtual console, 155 using virtual storage, 113 examples of, 116
commands, 113 VM Manager, 23 requirements for using, 31 VMM driver log file, 227 VMProvider, 23 VMs as Serviceguard Nodes configuration procedure, 206 vNICs, 124 managing, 130 removing, 132 vswitches creating, 124 deleting, 128 re-creating, 129 starting, 129 W WBEM Services, 31 372 Index
