HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.
© Copyright 2007 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.......................................................................................................11 Intended Audience................................................................................................................................11 New and Changed Information in This Edition...................................................................................11 Typographic Conventions.....................................................................
3.2 Using the hpvmcreate Command...................................................................................................38 3.2.1 Example of Virtual Machine Creation.....................................................................................39 3.3 Starting Virtual Machines................................................................................................................40 3.4 Changing Virtual Machine Configurations..............................................................
7.1.3.2.2 Attached Devices.....................................................................................................84 7.2 Configuring Integrity VM Storage..................................................................................................85 7.2.1 Integrity VM Storage Considerations.....................................................................................85 7.2.1.1 VM Storage Supportability...................................................................................
9 Managing Guests......................................................................................................123 9.1 Monitoring Guests.........................................................................................................................123 9.2 Creating Guest Administrators and Operators.............................................................................126 9.3 Installing the Guest Management Software.......................................................................
11.2.3 Virtual-to-Physical Cluster..................................................................................................156 11.2.4 Configuring VMs as Serviceguard Nodes...........................................................................156 11.3 Serviceguard in VM Host Configuration....................................................................................157 11.3.1 Configuring the Integrity VM Multiserver Environment...................................................158 11.3.
hpvminfo(1M).....................................................................................................................................208 hpvmmigrate(1M)...............................................................................................................................210 hpvmmgmt(1M)..................................................................................................................................214 hpvmmodify(1M).........................................................
List of Tables 1 2 1-1 2-1 2-2 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 6-1 6-2 6-3 7-1 8-1 8-2 9-1 9-2 9-3 9-4 9-5 9-6 10-1 10-2 11-1 12-1 12-2 HP-UX Versions.............................................................................................................................12 Integrity VM Versions...................................................................................................................12 Chapters of 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 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.
• • • • • • • • • • • • Troubleshooting Ignite-UX Installation Booting White Paper HP-UX Installation and Update Guide HP-UX Reference Managing Serviceguard Windows on Integrity: Smart Setup Guide HP Auto Port Aggregation (APA) Support Guide Using HP-UX VLANS HP Integrity Virtual Machines Manager Getting Started Guide HP Virtual Server Environment Software Installation and Update Guide HP Integrity Essentials Global Workload Manager Administrator's Guide Red Hat Enterprise Linux 4; Installation Guide for x
1 Introduction This chapter describes the Integrity VM product, including: • • • • • • • Section 1.1: “About HP Integrity Virtual Machines” (page 15) Section 1.2: “New Features and Enhancements in This Release” (page 16) Section 1.3: “Using AVIO with Integrity VM” (page 18) Section 1.4: “Running Applications in the Integrity VM Environment” (page 19) Section 1.5: “Related Products” (page 21) Section 1.6: “Using the Integrity VM Documentation” (page 21) Section 1.7: “Using This Manual” (page 22) 1.
Guests are fully loaded, operational systems, complete with operating system, system management utilities, applications, 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.
The following list describes enhancements to Integrity VM for this release: • Guests can run any of the following operating systems: — HP-UX 11i v2 (May 2005 [0505] or later), including HP-UX 11i v2 0712 — HP-UX 11i v3 — Windows 2003 (Enterprise or Datacenter edition) SP1 and SP2 — Red Hat Linux Enterprise Edition Advanced Server Release 4 update 4 and update 5 — SUSE Linux Enterprise Server (SLES) for HP Integrity servers SLES 10 update 1.
VERSION: HPVM A.03.50 clearcase opt Mon Aug 01 2007 13h32m14s EDT MYUUID: 1C57939a-56b1-11dc-a903-0017a4510fc0 SERVER UUID: 58d03fSd-79ed-11d9-b720-17c097e9e0d0 SERVER HOSTNAME: test.case.com • You can now add a server in one step instead of three. Previously, you needed to specify three commands to add an HPVM server. For example, the following three commands add a server whose host name is company: 1. Add the entry: hpvmdevmgmt -a server:company 2.
[Network Interface Details] Physical Storage type Guest Adaptor type Backing Vswitch Port Bus Device Function Mac Address :vswitch :avio_lan :swlan1 :5 :0 :1 :0 :2a-2e-5a-05-0a-ba Physical Storage type Guest Adaptor type Backing Vswitch port Bus Device Function Mac Address :vswitch :avio_lan :swlan2 :9 :0 :2 :0 :2a-2e-5a-05-0a-bc NOTE: The command line interface (CLI) accepts either avio_lan or aviolan and either avio_stor or aviostor.
resources to the virtual machines, do not run end-user applications, such as database software, on the VM Host system. Instead, run them on virtual machines. Typical software you can run on the VM Host system includes the following: • HP-UX 11i V2 Foundation Operating Environment (FOE) NOTE: The HP-UX FOE and license is included with the Integrity VM media so that you can install and run Integrity VM on the VM Host system. For HP-UX guests, you must purchase separate HP-UX FOE licenses.
You must purchase licenses for any software you run on a virtual machine, including the HP-UX operating system and any HP or third-party layered software. You can purchase the licenses for HP software under the HP Virtualization Licensing program. For more information, contact your HP Support representative. Always read the product release notes before installing any software product so that you have the latest information about changes and additions to the documentation.
1.6.1 Integrity VM Manpages For online information about using Integrity VM, see the following manpages on the VM Host system: • • • • • • • • • • • • • • • • • hpvm(5) - describes the Integrity VM environment. hpvmclone(1M) - describes how to create virtual machines based on existing virtual machines. hpvmcollect(1M) - describes how to collect virtual machine statistics. hpvmconsole(1M) - describes how to use the virtual machine console. hpvmcreate(1M) - describes how to create virtual machines.
Table 1-1 Chapters of this Manual Chapter Read if... Chapter 1: “Introduction” (page 15) You are new to HP Integrity Virtual Machines. Chapter 2: “Installing Integrity VM” (page 25) You are installing the HP Integrity Virtual Machines product. Chapter 3: “Creating Virtual Machines” (page 31) You are setting up new virtual machines on your VM Host system. Chapter 4: “Creating HP-UX Guests” (page 51) You are creating virtual machines that will run the HP-UX operating system.
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 sections: • • • • • • • Section 2.1: “Installation Requirements” (page 25) Section 2.2: “Installation Procedure” (page 27) Section 2.3: “Upgrading from Earlier Versions of Integrity VM” (page 28) Section 2.4: “Verifying the Installation of Integrity VM” (page 28) Section 2.5: “Removing Integrity VM” (page 28) Section 2.
Table 2-1 Requirements for Installing Integrity VM (continued) Resource Description Disk storage Sufficient disk space for the following: • The VM Host operating system (see the HP-UX 11i v2 Installation and Upgrade Guide) • The VM Host software (50 MB) • Swap space size should be at least as large as physical memory plus 4 GB (for example, for 16 GB of RAM, swap space should be 20 GB) NOTE: HP-UX uses this space to start up guests, but guests are never swapped out.
2.2 Installation Procedure Once you have read the product release notes and verified that you have met the system requirements as described in Section 2.1.1 (page 25), 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.
Integrity VM installation modifies certain kernel parameters. For this reason, you cannot install any other applications besides Integrity VM on the VM Host system, regardless of whether guests 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 dbc_max_pct 50 1 dbc_min_pct 5 1 maxdsiz_64bit 4294967296 34359738368 swapmem_on 1 0 2.
• • • • HostAvioLan HostAVIOStor GuestAvioLan GuestAVIOStor To remove these bundles, enter the following commands: # swremove -x autoreboot=true T2801AA VMProvider VMMigrate # rm -rf /opt/hpvm # rm -rf /opt/hpvmprovider Guests are not affected by this procedure. To remove guests, see the procedures in Section 3.7 (page 48). 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 sections: • • • • • • • • Section 3.1: “Specifying Virtual Machine Characteristics” (page 31) Section 3.2: “Using the hpvmcreate Command” (page 38) Section 3.3: “Starting Virtual Machines” (page 40) Section 3.4: “Changing Virtual Machine Configurations” (page 41) Section 3.5: “Cloning Virtual Machines” (page 44) Section 3.
Table 3-1 Characteristics of an Integrity Virtual Machine (continued) Virtual Machine Characteristic Default Setting Command Option Where Described Startup behavior If you omit the option, it is set to auto, and the virtual machine starts when Integrity VM is started. -b start_attribute Section 3.1.8: “Specifying the Virtual Machine Boot Attribute” (page 37) Dynamic memory If you omit the option, dynamic memory is not enabled for the guest. -x keyword=parameter Section 3.1.
example, to set the new virtual machine compass1 to have two vCPUs, enter the following command: # hpvmcreate -P compass1 -c 2 Every virtual machine has at least one vCPU. A running virtual machine cannot use more vCPUs than the number of physical CPUs on the VM Host system. (For the purpose of this discussion, the term “physical CPU” refers to a processing entity on which a software thread can be scheduled.
• • The amount of memory required by the guest operating system. For example, the HP-UX 11i v2 operating system requires 1 GB of memory. The amount of memory required by the applications running on the guest. The amount of memory should be at least the total of these two amounts. If there is not enough memory in the current configuration, Integrity VM issues a warning but allows you to create the virtual machine. This allows you to create virtual machines for future configurations.
• • vswitch-name is the name you assign to the vswitch. You must specify the name of the vswitch. nic-id is the pNIC ID on the VM Host. If you omit the nic-id, the vswitch is created for the localnet. To start the vswitch, enter the hpvmnet -b command. For example: # hpvmnet -b -S vswitch-name For more information about using the hpvmnet command, see Section 8.2.1 (page 110). To create the virtual machine and allocate the vswitch to it, use the -a option to the hpvmcreate command.
— — • • changer burner adapter-type can be scsi or avio_stor on an HP-UX 11i v2 guest (0505 or later). hardware-address or scsi:pcibus,pcislot:,scsitgt (optional) specifies the virtual device PCI bus number, PCI slot number, and SCSI target number. If you do not specify this information, it is generated automatically. HP recommends that you allow the hardware address to be generated automatically.
Some devices should be restricted to use by the VM Host and to each guest (for example, boot devices and swap devices). Specify restricted devices using the hpvmdevmgmt command. For more information about sharing and restricting devices, see Section 9.8.2.4 (page 140). Any alternate boot devices should be set with the same care that you would use on a physical system.
3.1.9 Specifying Dynamic Memory Parameters Specifies whether the new virtual machine will use dynamic memory and the values associated with it by including the following keywords: • dynamic_memory_control={0|1} • ram_dyn_type={none|any|driver} • ram_dyn_min=amount • ram_dyn_max=amount • ram_dyn_target_start=amount For more information about using dynamic memory for guests, see Section 9.6 (page 130). 3.1.10 Configuration Limits Table 3-2 lists the configuration limits for Integrity VM Version 3.5.
Table 3-3 Options to the hpvmcreate Command Option Description -P vm-name Virtual machine name. You must specify a name when you create or modify the virtual machine. You cannot modify this characteristic. -O os_type Operating system. If you do not specify the operating system type, it is set to UNKNOWN. -c number_vcpus Virtual CPUs (vCPUs) allocated. If you omit this option when you create the virtual machine, the default is one vCPU. -e percent CPU entitlement allocated.
==================== ===== ======= config1 1 HPUX config2 2 HPUX winguest1 5 WINDOWS winguest2 9 WINDOWS compass1 12 UNKNOWN ========= ====== ===== ===== ======= ======== Off 1 5 1 512 MB 0 Off 1 7 1 1 GB 0 On (OS) 1 5 1 1 GB 0 Off 1 3 1 2 GB 0 Off 1 0 0 2 GB 0 The compass1 virtual machine has been assigned virtual machine number 12, has been created with an UNKNOWN operating system type, one vCPU, no storage devices, no network devices, and 2 GB of memory.
Starting event polling thread Starting thread initialization Daemonizing.... hpvmstart: Successful start initiation of guest 'compass1' The hpvmstatus command displays the allocation of memory and devices. After you start the virtual machine, the hpvmstatus command displays the virtual machine status as On (EFI), because the virtual machine is powered on but the guest operating system is not running. Because the operating system has not been installed, the guest OS type is listed as UNKNOWN.
Table 3-5 Options to the hpvmmodify Command (continued) Option Description -F Suppresses all resource conflict checks and associated warning messages (force mode). Use force mode for troubleshooting purposes only. -s Sanity-checks the virtual machine configuration and returns warnings or errors, but does not create the virtual machine. -N new-vm-name Specifies a new name for the virtual machine.
Table 3-5 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.
Starting event polling thread Starting thread initialization Daemonizing.... hpvmstart: Successful start initiation of guest 'compass1' The virtual machine compass1 is started. Now the guest operating system must be installed. For information about creating HP-UX guests, see Chapter 4 (page 51). For information about creating Windows guests, see Chapter 5 (page 55). 3.
Table 3-6 Options to the hpvmclone Command (continued) Option Description -a rsrc Creates a virtual device for the new virtual machine (clone). Specify the virtual and physical device information for rsrc . For information about forming a virtual storage device specification, see Chapter 7 (page 81). For information about forming a virtual network device specification, see Chapter 8 (page 109).
For example, to clone the virtual machine named compass1, to create a new virtual machine named clone1, enter the following commands.
3.6 Stopping Virtual Machines To stop a running virtual machine, use the hpvmstop command. You must confirm this command. Table 3-7 describes the options to the hpvmstop command: Table 3-7 Options to the hpvmstop Command Option Description -P vm-name Specifies the name of the virtual machine. -p vm_number Specifies the number of the virtual machine. To display the virtual machine number, enter the hpvmstatus command. -a Specifies all the virtual machines that are running.
NOTE: It is important to shut down guests gracefully before stopping Integrity VM by specifying the -g option with the hpvmstop command. The guest operating system is notified of an imminent power failure, which gives it time to perform cleanup operations. Because behavior of guest shutdown can vary, HP recommends stopping virtual machines using their native operating system commands. 3.7 Removing Virtual Machines To remove a virtual machine from the VM Host, use the hpvmremove command.
3.8.1 Configuration Error on Starting the Virtual Machine When you start the virtual machine, the following message is displayed: Configuration error: Device does not show up in guest If you encounter this type of problem: 1. Verify that the path name to the file-backing store is correct and that the physical storage device is mounted. 2. Verify that the size of the physical storage device is divisible by 512 bytes (for a disk device) or 2048 (for a DVD device). 3.
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: • Section 4.1: “Installing the HP-UX Guest Operating System” (page 51) • Section 4.2: “Installing HP-UX Guest Management Software” (page 54) • Section 4.3: “Troubleshooting HP-UX Guest Creation” (page 54) 4.
CM: CL: SL: VM: HE: X: Command Menu Console Log Show Event Logs Virtual Machine Menu Main Help Menu Exit Connection [compass1] 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: [compass1] vMP> co EFI Boot Manager ver 1.10 [14.
Save changes to NVRAM [Y-Yes N-No]: 6. Y Exit the EFI Boot Maintenance Management screen to return to the EFI Boot Manager screen. Boot from the new boot entry, indicated by the virtual machine's MAC address:. EFI Boot Maintenance Manager ver 1.10 [14.62] Add a Boot Option.
NOTE: You may 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 should install by default. If they did not, and you want to install them with the Integrity VM bundle T2767AC, go to the HP-UX 11i v2 0712 media and look for the following bundles to install on the HP-UX guest, GuestAVIOStor and GuestAvioLan.
5 Creating Windows Guests You can install HP Integrity Windows 2003 on your virtual machines. These Windows guests can be managed like a Windows server running on an independent Integrity server or nPartition, by either the VM Host administrator or the Windows system administrator. This chapter describes: • Section 5.1: “Windows Guest Requirements” (page 55) • Section 5.2: “Installing Windows Guests” (page 55) • Section 5.3: “Managing Windows Guests” (page 64) • Section 5.
# hpvmconsole -P win1 -fi -c "pc -on" vMP MAIN MENU CO: CM: CL: SL: VM: HE: X: Console Command Menu Console Log Show Event Logs Virtual Machine Menu Main Help Menu Exit Connection [guest1] vMP> pc -on System will be powered on. -> System is being powered on. Please wait for the guest start sequence to complete. Use of the attention character can prevent the guest from running. (C) Copyright 2000 - 2007 Hewlett-Packard Development Company, L.P.
4. Connect to the CDROM file system (listed in the EFI output) by entering the name of the file system. For example: EFI Shell> fs0: 5. Enter the ls command to make sure you are connected to the right device (look for the setupldr.efi file): Fs0: ls Now that the EFI is ready, you can install the Windows® operating system.
ScriptPath=\IA64\ADDINS Support=X:\Supp IVPQET2373ALABA.PQI ================================================================= Note: Will always exit. ========================== TASK MENU ============================ A B C Q - 16GB 33GB Full Exit Drive Partition Size. Drive Partition size. Drive size. to console.
Cache Enabled. This image MainEntry is at address 0000000000102000 FPSWA.EFI preload successful. FPSWA.EFI start successful. Loading device drivers EFI Boot Manager ver 1.10 [14.62] [Build: Thu Jun 8 12:30:44 2007] Please select a boot option Windows Server 2003, Enterprise EFI Shell [Built-in] Boot option maintenance menu Use ^ and v to change option(s).
11. Obtain the guest's IP address by entering the i command to the SAC> prompt. Use the Remote Desktop Connection from a PC to connect to that IP address and log in as Administrator. The Support Pack completes installation: Computer is booting, SAC started and initialized. Use the "ch -?" command for information about using channels. Use the "?" command for general help. SAC>... EVENT: The CMD command is now available. SAC>i Net: 2, Ip=1.2.3.4 Subnet=255.255.248.0 Gateway=16.116.0.
-> Command successful. [guest1] vMP> 3. From the EFI shell, enter the map command: Shell> map Device mapping table fs0 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0)/CDROM(Entry0) blk0 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0) blk1 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0) blk2 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0)/CDROM(Entry0) Shell> 4. Enter the file system entry for the DVD. For example: Shell> fs0: Fs0: 5. Enter the setupldr command: Fs0:> setupldr The Windows Setup Begins...
9. Accept the Windows license by pressing ESC-8, which emulates F8. 10. Select the partition in which to install Windows: If the disk you are installing to has been cleaned as described in Section 5.2 (page 55), two partitions (EFI and Reserved) are automatically created. The remainder of the disk is unpartioned space. Select the unpartitioned space using the down arrow. Create a new partitiion by entering C.
Choose an NTFS partition. If there is no NTFS partition, format one. The partition is formatted, the files are copied, and the system reboots. 12. Start the Windows installation. In response to the SAC> prompt, press ESC-Tab SAC>...ESC-Tab Setup is being restarted................. EVENT: A new channel has been created. Use "ch -?" for channel help. Channel: Unattended Setup Channel SAC> EVENT: The CMD command is now available The following message is displayed: Name: Unattended Setup Channel Description: .
5.3 Managing Windows Guests Use the Windows Remote Desktop to manage the Windows guest: Log in as Administrator and configure Windows TCP/IP using the same networking information supplied earlier at the SAC> prompt. Install SNMP from the Windows Management and Monitoring Tools and configure it. SNMP is required for the HP Systems Insight Manager (SIM), which provides the Virtual Server Environment (VSE).
start.html file there. This file has information to guide you through installation of SSM. Consult the Smart Setup Guide for more details. After install the Smart Setup, install the components of HP's Smart Update media. This media is available from HP. Insert the Smart Update media into the virtual DVD as described for SSM. You initiate the Smart Update installation the same way you initiated SSM. Open the virtual DVD, then open the start.html file.
You can now monitor and manage the Windows guest using VM Manager and SMH. For more information, see the Getting Started with VM Manager manual. To shut down a Windows guest, use the Windows system management procedures. The Integrity VM commands for stopping guests do not shut down the Windows software properly and can lead to problems when the Windows guest is rebooted. 5.
5.5.1 Remote desktop unable to connect If the Windows guest is installed and on, but the Remote Desktop displays the following error, you might have to set the required Windows Registry parameters: Unable to connect Set the following registry parameters: • fDenyTSConnections should be set to 0. • TSEnabled should be set to 1. 5.
6 Creating Linux Guests You can install the Linux operating system on your virtual machines. Linux guests can be managed like a discreet Integrity server or nPartition, by either the VM Host administrator or the Linux system administrator. This chapter describes: • Section 6.1: “Installing Linux Guests” (page 69) • Section 6.2: “Installing Red Hat Enterprise Linux Guests from ISO Images” (page 70) • Section 6.
Table 6-1 Linux TUI Control Keys tab Moves to next field alt Moves to the previous field space Selects the item from a list arrow Scroll lists that are too long for a single screen enter Activates the action 6.1.3 Linux Guest Installation Media You can install Linux guests using any one of the following types of installation media: • Images (*.iso files) of the Red Hat Installation DVDs (recommended) (described in Section 6.2 (page 70)).
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids /eaccd6e4-b004-11db-bd1f-00306ef4693e/vmm_config.next): Allocated 86016 bytes at 0x6000000180000000 Loading boot image Image initial IP=102000 GP=62E000 Initialize guest memory mapping tables Starting event polling thread Starting thread initialization Daemonizing.... hpvmstart: Successful start initiation of guest 'linux1' Use the hpvmconsole command to connect to the guest. 4. Boot the guest.
NOTE: Failure to add this option results in an apparent guest hang, where the guest is trying to run a graphical installation program without a display. If this happens, reset the virtual machine. Enter Ctrl/B to reach the virtual console. Enter the RS command to restart the virtual machine. Resume the installation procedure. The installation process continues: Uncompressing Linux... done Loading initrd initrd.img...done Linux version 2.6.9-42.EL (bhcompile@altix2.build.redhat.com) (gcc version 3.4.
Table 6-2 Linux Installation Screens (continued) Screen Title Typical Entry Time Zone Selection Select a city in your time zone from the large scroll list, then enter OK. Root Password Type in the guest's root password in each entry, then enter OK. Package Defaults Select Customize software selection and then enter OK. Package Group Selection Scroll to the bottom, select Everything, and then enter OK. Installation to begin Enter OK. Required Install Media Enter Continue.
This procedure assumes the Linux installation directory tree has been created from the ISO images on a network server. For more information, see Red Hat Enterprise Linux 4; Installation Guide for x86, Itanium, AMD64, and Intel Extended Memory Technology 64 (Intel EM64T). Export this directory tree using NFS or make sure it is otherwise accessible to the VM Host system (for example, using FTP). 1. Create the boot disk by copying the boot.
fs0 fs1 fs2 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig5D1D1134-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part2,Sig5DB58D88-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0)/CDROM(Entry0) EFI lists devices with filesystems detected as fs{n}. In the preceding example, fs0 and fs1 are older filesystems that are present on the disk.
Table 6-3 Linux Guest Network Installation Screens Screen Title Response Language Selection Select your language and enter OK. Select Installation Method NFS or FTP and enter OK. Network Configuration for eth0 Type in the guest's IP address and netmask. Enter OK. Request for server parameters Enter the server name, path to theiInstallation tree, and FTP parameters (if any). Complete the installation procedure as described in the previous sections.
1. On the VM Host system, load the *.iso files of SUSE Linux Enterprise Server (SLES) for HP Integrity servers SLES 10 update 1 into the following directory: /var/opt/hpvm/ISO-images/linux/ Use the following file names or any file names you prefer: • SLES-U1-ia64-AS-disc1.iso • SLES-U1-ia64-AS-disc2.iso For security reasons, mark the ISO images as read-only. 2. Create a virtual machine with one disk and one DVD device for the ISO files, as well as one network virtual switch.
shell > fsn: fsn > bootia64 Where n corresponds to the Virtual DVD.
The guest management software provides the following Integrity VM commands on the Linux guest: • hpvmcollect • hpvminfo For online information about using these commands, after you install the guest management software, enter the man command. For example: # man hpvminfo hpvminfo(1M) hpvminfo(1M) NAME hpvminfo - Display information about the Integrity VM environment. . . . 6.
7 Creating Virtual Storage Devices This chapter describes what Integrity VM storage is, how to configure it, and how to use it, including: • Section 7.1: “Introduction to Integrity VM Storage” (page 81) • Section 7.2: “Configuring Integrity VM Storage” (page 85) • Section 7.3: “Using Integrity VM Storage” (page 102) 7.1 Introduction to Integrity VM Storage The way you configure and manage Integrity VM storage affects the way virtual machines perform.
7.1.1.4 Storage Security To avoid problems while supporting multiple virtual machines on one physical machine, Integrity VM isolates each virtual machine. Using Integrity VM commands, the VM Host administrator determines the physical storage resources that each virtual machine can access. This storage isolation is maintained by the Integrity VM storage subsystem through DMA boundary checks on each virtual machine I/O operation, thereby insuring that one virtual machine does not access the memory of another.
7.1.2.2 Attached I/O Attached I/O allows a virtual machine to access to a VM Host LUN directly. In this architecture, the Integrity VM storage subsystem attaches a LUN on the VM Host to a virtualized storage adapter. A LUN can be a disk, DVD, tape, media changer, or other peripheral device types. Because attached I/O does not require device virtualization, the performance of attached I/O might be better than shared I/O.
The following virtual DVD-ROM types are supported: Virtual DVD Type Backing Storage Device Described in ... Virtual DVD Disk in a VM Host physical DVD drive Section 7.2.2.3.4: “Virtual DVDs” (page 97) Virtual FileDVD ISO file on a VM Host VxFS file system Section 7.2.2.3.6: “Virtual NullDVDs” (page 98) Virtual NullDVD (empty) VM Host physical DVD drive or VxFS directory Section 7.2.2.3.3: “Virtual FileDisks” (page 96) 7.1.3.2.
• Smart Array — A9890A — A9891A • Combo — A9782A — A9784A — AB465A — AB290A — AD193A — AD194A NOTE: Only HP-UX guests can use AVIO, and the backing store can be only disk or volume. There is no attached AVIO device support, and guests can be only disk or DVD. 7.2 Configuring Integrity VM Storage This section describes how to plan and set up Integrity VM storage, including: • Section 7.2.1: “Integrity VM Storage Considerations” (page 85) • Section 7.2.2: “Setting up Virtual Storage” (page 91) 7.2.
— — SAS adapters supported by the SASD driver iSCSI adapters supported by the ISCSI driver If the physical storage is not connected with one of above adapter and driver types, it cannot be used by a virtual machine. Use the ioscan command to display the VM Host storage that is connected to adapters and drivers. • Any VM Host attachable devices available for use by a virtual machine must be supported by the guest OS to which it is attached.
is on and the disk drivers that control the whole disk. Therefore, in general, the higher the virtual media is in the VM Host I/O stack, the slower it operates. The simplified I/O stack in Figure 7-1 does not completely illustrate all the choices that can affect the performance: • Performance of different software layers differs. • The interfaces to each software layer are different, allowing Integrity VM different ways to send I/O through the layers.
7.2.1.3 VM Storage Multipath Solutions For load balancing and higher availability for virtual machines, consider using a multipath solution on the VM Host. Currently there are no multipath solutions for the attachable device types of tapes, media changers, and CD/DVD burners. However, there are several VM Host multipath options for virtual devices.
Figure 7-3 shows an example of a VM Host I/O stack as it applies to a single LUN: Figure 7-3 Sub-LUN Storage Allocation Example File File Logical Volume File 2 File Logical Volume 2 1 File File Logical Volume Whole Disk File File Logical Volume 2 The virtual machine is allocated a logical volume from the LUN for a Virtual LvDisk. • The logical volume that has been allocated is marked 1. • The parts of the disk that cannot be allocated are marked 2.
Figure 7-5 Bad Virtual Device Allocation Guest A Guest B Virtual LvDisk As these examples illustrate, it is important to know where storage is allocated from to avoid data corruption with virtual machines or even the VM Host. Management utilities such as HP System Administration Manager (sam) and the System Management Homepage (SMH) utilities allow you to track disk devices, volume groups, logical volumes, and file systems.
Logical volume creation is relatively simple. Logical volumes are used widely on HP-UX systems. The sam utility or the Veritas Enterprise Administrator can be used to create logical volumes. With experience, you can use logical volume commands more quickly. Creating files for virtual devices is not hard, but takes time. Files are usually placed on top of logical volumes, so you might have to create a logical volume first. Use sam to accomplish this.
• pcislot is an integer from 0-7. A PCI function number is not specified. It is implicitly zero because the virtual MPT storage adapter supports only a single channel. • scsitgt is an integer from 0-14 (15 is reserved for the virtual SCSI adapter). Unlike real parallel SCSI bus, there is no arbitration on virtual SCSI buses. The SCSI target IDs for the virtual devices must be unique.The virtual SCSI MPT adapter takes target ID 15 for itself, leaving 0-14 for SCSI targets.
Not all virtual device types support all VM Host storage types (see Section 7.1.3 (page 83)). Complete VM storage resource statements are discussed in the next section. 7.2.2.3 VM Storage Resource Statements This subsection provides information on formulating complete valid resource statements for Integrity VM storage devices. To specify an Integrity VM storage device for a virtual machine, use a complete valid resource statement with the hpvmcreate or hpvmmodify command.
These device files can be located for a VM Host LUN using the ioscan command. These system files are installed and removed using the insf and rmsf commands, respectively. Device files are created automatically by the VM Host for any storage it sees during boot. New devices connected or created after boot time, require the use of ioscan and insf to create the new sdisk device files. Old device files for storage not longer present can be removed with rmsf.
Where /dev/vg_name/rlvol_name is an LVM character device file for rlvol_name on vg_name.
Where /dev/vx/rdsk/dg_name/v_name is a VxVM character device file for volume v_name on disk group dg_name.
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. The mkfs command can be used to create the VxFS file systems directly. Once the file systems are created, mount can be used to mount them onto the VM Host file system.
NullDVD should be specified (see Section 7.2.2.3.6 (page 98)). Physical media can then be inserted into the VM Host CD/DVD drive and become virtual media for a Virtual DVD using the hpvmmodify or the virtual console's insert command (see Section 7.3.1.2 (page 103)). After the Virtual DVD is in the virtual machine, the VM Host CD/DVD drive is locked. The VM Host CD/DVD drive is automatically unlocked when the virtual machine is shut down.
The choice of how to configure a Virtual NullDVD depends on the access that the VM Host administrator gives to the guest administrator. Virtual DVD changes can be initiated from the virtual console (see Section 7.3.1.2 (page 103)). All virtual DVD changes by the guest administrator are constrainted by the actions of the VM Host administrator.
# hpvmdevmgmt -m gdev:/var/opt/hpvm/ISO-images/hpux/:attr:SHARE=YES For more information about using the hpvmdevmgmt command, see Section 9.8 (page 138). Virtual NullDVDs require no additional management beyond that required for the Virtual DVD (see Section 7.2.2.3.4 (page 97)) or Virtual FileDVD (see Section 7.2.2.3.5 (page 98)) types they become. 7.2.2.3.7 Attachable Devices Integrity VM allows you to attach physical VM Host backup device types to virtual machines.
If the device is not seen, there is a hardware problem or SCSI ID conflict. Consult the documentation for the particular device to resolve this issue before proceeding. If the device is seen but not claimed, this is a result of missing drivers in the VM Host. Integrity VM does not require the drivers to be loaded on the VM Host for the devices to be attached. The HP-UX tape (stape) and changer (schgr) drivers are not loaded by default unless those devices are connected at install time.
Where component parts of the minor number are constructed as follows: Minor Number Construction CC Two hexadecimal digits, identifying the controlling interface card by its instance number. The instance value is displayed in ioscan output, under column I for the interface hardware type. T One hexadecimal digit identifying the drive (target) address. L One hexadecimal digit identifying the LUN within the device 0 Hexadecimal digit zero, for reserved portion of the minor number.
7.3.1.1 VM Host Administrator The VM Host administrator role is an individual responsible for the proper configuration and maintenance of the VM Host for running virtual machines. As such, this person needs complete access to the VM Host to install hardware and software. This person also needs to understand how to do HP-UX system maintenance, how to configure hardware properly, and how to set up and use various software applications and tools.
There are no Integrity VM storage commands for application users in the guest OS. The guest users use Integrity VM storage on the guest OS the same way as they normally use storage on an HP Integrity server. Any required Integrity VM storage changes must be directed to the guest administrator or VM Host administrator. 7.3.2 Integrity VM Storage Use Cases This subsection describes ways to use the Integrity VM storage commands. 7.3.2.
disk scsi 0 1 0 1 0 disk /dev/rdsk/c3t2d0 disk scsi 0 1 0 2 0 disk /dev/rdsk/c9t0d0 # hpvmmodify -P myvmm -d disk:scsi::disk:/dev/rdsk/c3t2d0 # hpvmstatus -P myvmm ... [Storage Interface Details] disk scsi 0 1 0 0 0 disk /dev/rdsk/c7t0d0 disk scsi 0 1 0 2 0 disk /dev/rdsk/c9t0d0 To delete an AVIO storage device, specify the following: host# hpvmmodify -P guest1 -d disk:avio_stor:0,5,0 7.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.
vendor: product id: type: size: bytes per sector: HP Virtual DVD CD-ROM 4300800 Kbytes 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/rdsk/c1t1d0 To modify an existing SCSI storage device to be an AVIO storage device, specify the following: host# hpvmmodify -P guest1 -m hba:avio_stor:0,5 NOTE: Only HP-UX guests can use AVIO, and the backing store can be only disk or volume.
directory for the Virtual FileDVD. The eject command changes the Virtual FileDVD into a Virtual NullDVD device. ISO files can be added to or removed from the file system directory for the Virtual FileDVD by the VM Host administrator. Once this ISO file directory is updated, use an insert command to view all the newly available ISO files in the directory and to choose one to be used for a new Virtual FileDVD. It is not necessary to change the file directory between each eject and insert operation.
8 Creating Virtual Networks You can allocate virtual network devices or virtual network interface cards (vNICs) to the guest when you create the guest with the hpvmcreate command or when you modify an existing guest using the hpvmmodify command, as described in Chapter 3 (page 31). Virtual network interface cards are added using the same option that is used to add storage devices, but the format of the argument to the command option is different.
NOTE: guest. • • Trunking software such as APA is supported only on the VM Host, not on the Guest virtual network interface card (vNIC) — the virtual network adapter, as recognized by the guest operating system. Virtual switch (vswitch) — the virtual network switch maintained by the VM Host that is associated with a pNIC and can be allocated to one or more guests.
Table 8-1 Options to the hpvmnet Command (continued) Option Description -Q Specifies the command function should proceed without asking for confirmation. By default, the command requires confirmation, and does not proceed without it. -s Retrieves statistics. -S vswitch_name Specifies the name of the virtual switch. The vswitch name is limited to 8 characters and must be unique on the VM Host.
8.2.1.1 Local Networks Virtual network communication may be limited to virtual machines on the VM Host system through the use of vswitches that are not connected to a physical NIC. A virtual network such as this is called a local virtual network or simply a local network (localnet). To create a local network, a vswitch must first be created using hpvmnet without the -n option so that it is not connected to the physical network.
# lanscan Hardware Path 0/0/3/0 0/1/2/0 0/4/1/0 Station Address 0x00306E39F70B 0x00306E3977AB 0x00306E4CE96E Crd In# 0 1 2 Hdw State UP UP UP Net-Interface NamePPA lan0 snap0 lan1 snap1 lan2 snap2 NM ID 1 2 3 MAC Type ETHER ETHER ETHER HP-DLPI Support Yes Yes Yes DLPI Mjr# 119 119 119 The hardware path from the output of lanscan on the guest matches the path in the guest configuration file.
======= ============ ======== ============ ============ 2 Available 20 0 Note that only the configured VLAN port identification data is copied to the new vswitch. Use this hpvmnet command option when you have a vswitch with numerous VLAN ports. This process makes it unnecessary to reenter all the port data for each new vswitch. 8.2.4 Deleting vswitches To delete a vswitch, first stop the vswitch using the —h option to the hpvmnet command. Then delete the vswitch using the -d option to the hpvmnet command.
# hpvmnet -S myswitch -d 2. Create a new vswitch associated with lan1. For example: # hpvmnet -S myswitch -c -n 1 3. Add a new vNIC to your guest using the new vswitch. For example: # hpvmmodify -P guestname -a network:lan:,,:vswitch:myswitch 8.2.6 Starting vswitches Virtual switches (vswitches) start automatically when the VM Host system is started. You can start the vswitch manually using the —b option to the hpvmnet command.
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.
Figure 8-2 Integrity VM VLAN Configuration Example Guest VM1 VSwitch1 Guest VM2 VSwitch2 VLAN1 Guest VM3 PNIC 1 PNIC 1 PNIC 2 PNIC 2 VM Host VSwitch1 Guest VM4 VSwitch2 VLAN1 VM Host Internet A vNIC on a guest is associated with a port on the vswitch and all network communication to and from the guest passes through this vswitch port. You can configure VLAN rules on the individual ports of the vswitch, similar to most physical switches.
# hpvmmodify -P vm1 -a network:lan::vswitch:vmlan4:portid:1 # hpvmmodify -P vm2 -a network:lan::vswitch:vmlan4:portid:2 The following command shows the resulting configuration: # hpvmnet -S vmlan4 Name Number State Mode PPA MAC Address IP Address ======== ====== ======= ========= ====== ============== =============== vmlan4 2 Up Shared lan4 0x00127942fce3 192.1.2.
. . [Network Interface Details] Interface Adaptor Name/Num ========= ========== ========== vswitch lan localnet vswitch lan localnet vswitch lan vmlan4 vswitch lan vmlan4 vswitch lan vmlan900 vswitch lan vmlan900 . . .
8.4.3 Configuring VLANs on Physical Switches When communicating with a remote VM Host or guest over the network, you might need to configure VLANs on the physical switches. The physical switch ports that are used must be configured specifically to allow the relevant VLANs. If the remote host is VLAN aware, You must configure VLAN interfaces on the host for the relevant VLANs. Use thelanadmin command to configure VLANs on a remote HP-UX host.
• • • • • • • • • • • • • • • • • • A9784A — Combo Add-in AB352 — Core AB545A — Networking Add-in A7011A — Networking Add-in A7012A — Networking Add-in AB290A — Combo Add-in AB287A — Add-in (10 GbE) AD331A — Add-in AD332A — Add-in AD193A — Combo Add-in AD194A — Combo Add-in AD221A — Add-in AD222A — Add-in AD299A — Add-in AD337A — Add-in AD338A — Add-in AD339A — Add-in AD385A — Add-in (10 GbE) NOTE: In this release, AVIO is supported only on HP-UX 11iv2 guests. 8.5.
9 Managing Guests To manage a guest, connect to the guest using a remote connection and use the operating system administration procedures appropriate to the guest OS. Integrity VM provides utilities for managing virtual machines from the VM Host and from inside the guest. This chapter describes how to manage guests using Integrity VM commands and utilities, including: • • • • • • • • Section 9.1: “Monitoring Guests” (page 123) Section 9.
Table 9-1 Options to the hpvmstatus Command (continued) Option Description -D Displays the resource allocation of the specified virtual machine. You must include either the -p option or the -P option. -e Displays the event log for the VM Host or the specified virtual machine. The event log records all changes to virtual machine configurations.
Maximum Entitlement : 100.
9.2 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 that will have administration or operator privileges on that guest. These users are allowed to log in to the VM Host under their own user accounts and to use the hpvmconsole command to perform system administration tasks on the guest virtual machine.
#hpvmmodify -P winguest1 -u compass1:admin A guest administrator can now access the compass1 virtual console by using the ssh command or telnet command on the VM Host and logging in to the compass1 account. The guest administrator cannot use the su command. NOTE: For security reasons, HP strongly recommends that you do not include /opt/hpvm/ bin/hpvmconsole, the virtual console image, in /etc/shells. Doing so opens two security vulnerabilities: • It allows ftp access to the account.
Figure 9-1 Installing Guest Management Software HP-UX VM Guest HP-UX Windows Software Software HP-UX Guest Software Windows VM Guest Windows Guest Software Guest Management Software Repository Installation Media Real VM Host The guest management software is required on each guest. The guest management software ensures that guests have the required patches for optimum performance and managability. It also enables the hpvmmgmt, hpvmcollect, and hpvminfo commands on the guests, as appropriate.
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 compass1, enter the following command: # hpvmconsole -P compass1 -c "pc -on" Table 9-2 lists the options to the hpvmconsole command. Table 9-2 Options to the hpvmconsole Command Option Description -P vm-name Specifies the name of the virtual machine console to open. -p vm-number Specifies the number of the virtual machine console to open.
HElp Q - Display this screen - Quit help For more information about using the hpvmconsole command, see hpvmconsole(1M). 9.5 Guest Configuration Files When the guest is created, the VM Host creates the guest configuration file /var/opt/hpvm/guests/guestname. Integrity VM creates up to three guest configuration files: • • • The vmm_config.current file contains the current guest configuration currently set. The vmm_config.prev file contains the last known guest configuration settings. The vmm_config.
Table 9-3 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.
You can configure a virtual machine to reduce its memory size early in a boot process, making the virtual machine available but maintaining lower memory overhead on the VM Host system. Use the following -x option to enable this feature: -x ram_dyn_target_start - memory size after boot You can supply several dynamic memory keywords on the same command line.
Table 9-4 Dynamic Memory Characteristics (continued) Characteristic Setting Description 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. Minimum memory valueM (for megabytes) or valueG (for gigabytes) The lower bounds for ram_target and ram_dyn_target_start.
9.6.1.3 Modifying a Virtual Machine's Memory Size on the VM Host Once dynamic memory is configured, a virtual machine's memory size can be changed to any value between the minimum size (ram_dyn_min) and the maximum size (ram_dyn_max) in increments of the chunk size (64 MB). Use the following -x option to the hpvmmodify command to change the memory size: # hpvmmodify -P compass1 -x ram_target = new memory size 9.6.
Type Current memory Target memory Comfortable minimum : : : : driver 6135 MB 6135 MB 2167 MB To display more information, include the -V option.
This feature limits the types of software you can run on a VM Host system. If the VM Host system supports an additional workload beyond the virtual machines, the large pages tend to fragment and performance of the newly started virtual machine might degrade. Dynamic memory increases the possibility of VM Host memory becoming fragmented. The current implementation of dynamic memory releases portions of the memory allocated to a virtual machine.
9.6.3.5 Actual Memory Allocations Might Differ If you specify a value for the ram_target or ram_dyn_target_start parameter that results in a change in memory size that is not a multiple of 64 MB, the target value is reset. For example, if you specify 6 GB of memory, the HP-UX guest actually has access to 6135 MB of memory. If you attempt to set the memory size to 2048 MB, the amount of memory actually removed is 4087 MB. This is not a multiple of 64 MB, so the target memory size is reset to 2103 MB. 9.6.3.
Virtual Machine Name VM # ==================== ===== chip 1 dale 5 OS Type ======= HPUX HPUX State #VCPUs #Devs #Nets Memory Runsysid ========= ====== ===== ===== ======= ======== On (OS) 2 1 1 3 GB 0 On (OS) 2 1 1 3 GB 0 For information about installing the HP-UX guest management software, see Section 4.2 (page 54). 9.7 Integrity VM Log Files Each guest has a log file named /var/opt/hpvm/guests/guestname/log. The VM Host log files are stored as /var/opt/hpvm/common/command.log and hpvm_mon_log. 9.
Table 9-6 Options to the hpvmdevmgmt Command Option Description Lists an entry. To list all entries, enter the following -l {server|rdev|gdev}:entry_name:attr:attr_name=attr_value command: # hpvmdevmgmt -l all -v Displays the version number of the hpvmdevmgmt output format. The version number is 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.
To restrict the vswitch named myswitch so that it is no longer sharable, enter the following command: # hpvmdevmgmt -m gdev:myswitch:attr:SHARE=NO This command restricts the vswitch called myswitch to use by one guest only. 9.8.2.2 Replacing Devices If a backing storage device malfunctions, replace it using the hpvmdevmgmt -n option. The -n option works only for guest devices. It replaces the existing device entry with the new device entry while keeping all the current guest dependents.
Here is an example of how to change the enumeration policy to enumerate only boot LUNS: Shell> drvcfg -s HP AVIO Stor Driver Configuration ================================== Enumerate only boot LUNs (Y/N)? [N]:Y Drv[2F] None None Ctrl[ALL] Lang[eng] - Options set.
10 Migrating Virtual Machines The hpvmmigrate command allows you to move a virtual machine from a source VM Host system to a destination VM Host system. The hpvmmigrate command is available with HP Integrity Virtual Machines A.01.20 and later. This chapter includes the following sections: • Section 10.1: “Introduction to Virtual Machine Migration” (page 143) • Section 10.2: “Migration Guests from VM Host to VM Host” (page 144) • Section 10.
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. Similary, if the source machine can provide a guest with four vCPUS, the target machine must also be able to provide them. To modify the virtual devices or network on the target host, use the hpvmmodify command. To enable migration the source and destination hosts must be configured symmetrically.
Table 10-1 Options to the hpvmmigrate Command Option Description -P source-vm-name Specifies the name of the guest to migrate. -p source-vm-name Specifies the virtual machine number of the guest to migrate. To display the virtual machine number, enter the hpvmstatus command. -h dest-hostname | dest-host-IP Specifies the destination VM Host system name or IP address. —v Displays the version of the hpvmmigrate command . —H Displays information about how to use the hpvmmigrate command.
10.3 Network and Storage Migration Considerations Effective migration of VM Host systems depends on proper configuration of the networks and storage used by the source and destination hosts. The hpvmmigrate command verifies that the source and destination hosts provide the guest with symmetric accessibility to network and storage resources. If you set up the configuration properly on both hosts before you migrate the guest, the migration task will be much easier and faster. 10.3.
10.3.3.1 SSH Key Setup HP recommends that you use the HP-UX Distributed Systems Administration Utilities (DSAU) tools to set up the SSH keys on the source and destination hosts, which is installed by default on HP-UX 11.23 (0512 release). The bundle name is DSAUtilities. You use the /opt/dsau/bin/csshsetup command to set up SSH keys between hosts. The csshsetup command simplifies the task of setting up SSH public-key authentication trust relationships between hosts.
The P2V assistant only migrates applications that have software depot (SD) packages. Applications that are not SD-compliant cannot be migrated with the P2V assistant. 10.4.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.
Depots source currently configured: NONE 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).
Type below if you would like to continue ---------------------------------------------------------- The P2V assistant prompts you to choose to continue or 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 would break dependencies on another applications.
11 Using HP Serviceguard with Integrity VM After you have installed Integrity VM and created the guest, you can install 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, including the following topics: • Section 11.1: “Introduction to HP Serviceguard with Integrity VM” (page 153) • Section 11.
• Storage Requirements To make sure the Serviceguard configuration is managable, use identical backing stores on both the primary node and alternate nodes. To use VMs as Serviceguard Nodes configurations, the backing storage units must be whole disks. Integrity VM does not support using other types of backing stores on primary and alternate nodes for applications that are configured as Serviceguard packages.
Serviceguard cluster. Depending on the configuration of the cluster, the application configured as a Serviceguard package can fail over: • From one guest to another guest in the same VM Host system • From one guest to another guest in another VM Host system • From the guest on a VM Host system to a separate physical server or nPar You can even mix and match VMs as Serviceguard Nodes configurations to meet your specific requirements.
Figure 11-2 Guest Application Failover to a Guest on a Different VM Host Serviceguard Package Failover Guest VM2 Guest VM1 Serviceguard Cluster Physical Node 1 Physical Node 2 VM Host VM Host In this configuration, the Serviceguard nodes are guests running on either separate hard partitions (nPars) or HP Integrity servers. Note that Integrity VM does not run on soft partitions (vPars). 11.2.
3. 4. 5. Ensure that each guest has access to a quorum server or cluster lock disk. Use the hpvmstatus command to make sure the guest is running and to verify the guest name. Use the cmquerycl command to specify the nodes to be included in the cluster and to generate a template for the cluster configuration file. For example, to set up a cluster named gcluster that includes nodes host1 and host2, enter the following command: # cmquerycl -v -C /etc/cmcluster/gcluster.
3. 4. Modify the Serviceguard package configuration files to match your guest environment, as described in Section 11.3.3: “Modifying the Package Configuration Files” (page 161). Start the Serviceguard package, as described in Section 11.3.4: “Starting the Distributed Guest” (page 161). NOTE: When using AVIO networking devices for guests that are configured as Serviceguard Packages, be sure that all Service guard standby lans are configured using PPA devices supported by AVIO. 11.3.
2. Verify the registration by entering the following command on each member of the multiserver environment: # hpvmdevmgmt -l server host1:CONFIG=SERVER,SERVERADDR=16.116.9.0,SERVERID=1::WWID_NULL host2:CONFIG=server,EXIST=NO,DEVTYPE=UNKNOWN,SHARE=NO,SERVERADDR=16.116.8.91, SERVERID=2::WWID_NULL The list of servers in the multiserver environment must match the list of nodes in the Serviceguard cluster configuration. 11.3.
Respond to both prompts by entering y. The hpvmsg_package script creates the virtual machine package template files in the etc/cmcluster/guest-name/ directory: • guest-name.config • guest-name • hpvmsg_ctrl • hpvmsg_mon • hpvmsg_start • hpvmsg_stop The hpvmsg_package is a utility that you can use to configure a guest as a Serviceguard package.
Checking for inconsistencies .. Done Cluster cluster1 is an existing cluster Maximum configured packages parameter is 10. Configuring 3 package(s). 7 package(s) can be added to this cluster. 200 access policies can be added to this cluster.
STANDBY STANDBY STANDBY STANDBY up up up up 0/2/1/0/4/0 0/2/1/0/6/0 LinkAgg0 0/0/3/0 PACKAGE compass1 STATUS up STATE running lan2 lan8 lan900 lan0 AUTO_RUN disabled NODE host1 Policy_Parameters: POLICY_NAME CONFIGURED_VALUE Failover configured_node Failback manual Script_Parameters: ITEM STATUS Service up MAX_RESTARTS 0 RESTARTS 0 Node_Switching_Parameters: NODE_TYPE STATUS SWITCHING Primary up enabled Alternate up enabled NODE host 2 STATUS up NAME host1 host2 NAME host1 (current) STATE r
host2# cmrunpkg -n host2 compass1 4. Enable the package: host2# cmmodpkg -e compass1 5. On the adoptive node, verify that the compass1 package has started: host2# cmviewcl -v -p compass1 6. On the adoptive node, verify that the guest named compass1 is on: host2# hpvmstatus -P compass1 11.3.7 Managing Distributed Guests To start, stop, and monitor distributed guests, use the Serviceguard commands described in this section.
1. 2. 3. 4. 5. 6. Move the distributed guest to the adoptive node using the cmhaltpkg and cmrunpkg commands. Remove the toolkit from the VM Host system as described in Section 11.4.1: “Removing the Serviceguard for Integrity VM Toolkit” (page 164). Install the Integrity VM product as described in Chapter 2: “Installing Integrity VM” (page 25). Move the distributed guest back to the VM Host system using the cmhaltpkg and cmrunpkg commands.
1. 2. 3. On the original node where the guest is running, run the hpvmsg_package command. Apply the package configuration using the cmapplyconf command. To provide Serviceguard protection immediately, restart the guest package after repackaging it. For more information about using these commands, see Section 11.3.2 (page 159). 11.5 Troubleshooting Serviceguard with Integrity VM This section describes how to solve some of the problems that can occur using Serviceguard and Integrity VM. 11.5.
• • VxVm - Before starting a package, ServiceGuard requires that all disk groups associated with the package are deported. See the Managing ServiceGuard manual for details. Files - Before starting a package, ServiceGuard requires that filesystems of file backing stores associated with the package are unmounted. If the guest has problems accessing network, make sure the network devices are available on the VM Host system. Packages do not start if any of their defined subnets are unavailable.
11.5.4 Polling Interval for Virtual Machine Serviceguard Nodes Serviceguard failover in Integrity VM can take longer than expected with the default 5-second network polling interval. To reduce the failover time, reduce the value of the HPVMNETINTVL tunable to 2. If your system has Serviceguard installed and you want to make sure that failover of the vswitches used for Serviceguard takes less than 5 seconds, use a text editor to add or change the following line in the /etc/rc.config.
12 Reporting Problems with Integrity VM Report Integrity VM defects through your support channel. Follow these instructions to collect data to submit with your problem report. 1. Run the hpvmcollect command to gather information about the guest before modifying any guest. Preserve the state of the VM Host and Integrity VM to best match the environment when the VM Host failed. If multiple guests are running, run the hpvmcollect command for guest that was running at the time. 2. 3. 4.
Table 12-1 Options to the hpvmcollect Command on the VM Host (continued) Option Description -c Includes the latest crash dump directory in the archive. This option is used if the guest or the VM Host fails or hangs. -f Forces an archive to be overwritten, if it exists, rather than renamed with an appended time stamp. -h Displays the help message for the hpvmcollect command. -l Leaves the collected information in a directory rather than in an archive file.
Collecting lan info ................................................. OK Running lanshow ..................................................... NO Collecting installed sw info ........................................ OK Collecting command logs ............................................. OK Collecting messages from vmm ........................................ OK Collecting lv info .................................................. N/A Collecting vgdisplay info ...........................................
12.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 9.3 (page 127). Table 12-2 describes the options to the hpvmcollect command on the guest. Table 12-2 Options to the hpvmcollect Command on Guests Option Description -c Includes the latest crash dump directory in the archive. This option is used if the guest or the VM Host fails or hangs.
The collection is "//hpvmcollect_archive/compass1_Sep.29.05_122453PST.tar" 12.2 Managing the Size of the VMM Driver Log File The monitor log file (/var/opt/hpvm/common/hpvm_mon_log) is 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 grow up to 102400 KB, include the following line in the /etc/rc.config.
A Integrity VM Support Policy This appendix describes the HP Integrity Virtual Machine support policies and software version requirements for Integrity VM Host and guest operating system environments. A.1 Integrity VM Minimum Support Life Each release, starting in 2007, is supported a minimum of three years. Integrity VM Version Release Date Expected End of Support Date Current Status A.01.00 December 2005 December 2007 Supported A.01.20 March 2006 March 2008 Supported A.02.
A.3 VM Host OS and Server Support Integrity VM Version A.01.20 Version A.02.00 Version A.03.00 VM Host OS Support HP-UX 11i v2 HP-UX 11i v2 HP-UX 11i v2 May 2005 through May 2005 through Sept 2006 September 2006 September 2006 through June 2007 Version A.03.50 Notes HP-UX 11i v2 December 2007 New versions of Integrity VM are guaranteed to support the latest HP-UX OE release on the VM Host. New Integrity VM versions support the latest HP-UX OE release on the VM Host.
A.5 Windows and Linux Guest Support Integrity VM Version A.01.20 Version A.02.00 Version A.03.00 Version A.03.
A.6 Serviceguard Support Integrity VM Version A.01.20 Version A.02.00 Version A.03.00 A.03.50 Notes Serviceguard – Virtual machines as packages (Serviceguard running on VM Host) Serviceguard release • A.11.16 • A.11.17 • A.11.17 w/ SMS A.01.00 Serviceguard release • A.11.16 • A.11.17 • A.11.17 w/ SMS A.01.00 Serviceguard release • A.11.16 • A.11.17 • A.11.17 w/ SMS A.01.00 • A.11.18 • A.11.18 w/ SMS A.01.01 Serviceguard release • A.11.16 • A.11.17 • A.11.17 w/ SMS A.01.00 • A.11.18 • A.11.
A.7 Storage Interface Support Integrity VM Versions A.01.20 Version A.02.
software vendor and the release of the Operating Environment (OE) installed on the VM Host system. Storage Device Version A.01.20 Whole Disk SecurePath A-P LVM Logical Volumes • PVLinks • EMC PowerPath • HP Secure Path A-A / A-P VxVM Logical Volumes • Veritas DMP • EMC PowerPath • HP Secure Path A-A / A-P VxFS Files • • • • Version A.02.00 Version A.03.00 Version A.03.50 • HP Secure Path A-A / A-P • EMC PowerPath PVLinks Veritas DMP EMC PowerPath HP Secure Path A-A / A-P A.7.
card may be configured with Auto Port Aggregation (APA) with the resulting port supported as indicated in the following table: Integrity VM Version A.01.20 Version A.02.00 Version A.03.00 Version A.03.50 Virtual I/O (VIO) All supported Ethernet interfaces network interfaces Accelerated Virtual I/O (AVIO) network interfaces Not supported in versions previous to A.03.50. Notes Virtual I/O network interfaces are those defined using the lan adapter type. (See the hpvmresources manpage.
Integrity VM Manpages 183
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.
hpvmclone(1M), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevmgmt(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmnet(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M), hpvmmgmt(1M), hpvmpubapi(3) 185
hpvmclone(1M) NAME hpvmclone -- Create a new virtual machine that is a copy of an existing virtual machine.
option, the new virtual machine's entitlement will be that of the existing virtual machine. The percentage can be set to an integral value between 0 and 100. If the value specified is less than 5, then the virtual machine will be allocated the minimum percentage of 5%. The default is 10%. The entitled CPU resources inherited from the existing virtual machine, specified in cycles or percentages, will be replaced in the new virtual machine by this percentage. The -e and the -E options are mutually exclusive.
initialized on the VM Host. This is the default. 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.
-F Ignores all virtual machine configuration warnings, including oversubscribing of resources (Force mode). This option is primarily intended for use by scripts and other noninteractive applications. -c number_vcpus -r amount Specifies the number of virtual CPUs visible to the new virtual machine. If unspecified, the number defaults to that of the existing virtual machine. Specifies the amount of memory available to the new virtual machine at boot time.
To specify the serial number of the new virtual machine, enter the following: -x serial_number={new|same} RETURN VALUES The hpvmclone command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS hpvmclone displays error messages on stderr for any of the following conditions: • • • • • • • • • An invalid option is specified. An invalid value is specified for an option.
1 2 3 4 Active Active Active Active lan none lan 100 avio_lan none lan 100 2 2 vm1 vm1 1 1 vm2 vm2 The following example shows how to use the hpvmclone command to create a new Linux guest named linux2 based on the existing guest named linux1. The boot disk is specified. # hpvmclone -P linux1 -N linux2 -b disk:scsi:0,0,0:disk: 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.
-l -s hostname -h -P vm_name Leaves the collected information in the directory rather than an archiving it. Valid on both the VM Host and the guest. Specifies a hostname to receive the archive, which is copied using scp. Verify that you can login to the host without a password. Valid on both the VM Host and the guest. Displays the help message. Valid on both the VM Host and the guest. Specifies the unique name of the virtual machine to be archived. Valid on the VM Host only.
Copying hpvm configuration .......................................... Copying hpvm control script ......................................... Copying guest's config file ......................................... Getting status of the guest ......................................... Getting detailed status of the guest ................................ Getting guest's entitlement ......................................... Copying guest's config file change log ..............................
AUTHORS The hpvmcollect command was developed by HP.
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.
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 was encountered. 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 Virtual Machines virtual machine.
-E cycles Specifies the virtual machine's CPU entitlement in CPU cycles. The cycles are expressed as an integer, followed by one of the following letters to specify units: • • M: megahertz G: gigahertz If no letter is specified, the default unit is megahertz. The -e and -E options are mutually exclusive. -F Suppresses all resource conflict checks and associated warning messages (force mode). This option is primarily intended for use by scripts and other noninteractive applications.
-B start-attr Specifies the startup behavior of the virtual machine. The start_attr attribute 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. If the start-attr attribute is set to auto, the virtual machine is started when Integrity VM is initialized.This is the default.
available at the virtual console: either admin or oper (the default). This option can be specified more than once. -u user[:kind]] Specifies the user authorization. A VM Host user account specified here can use the hpvmconsole command to manage this guest.The user parameter specifies the user name. The kind argument specifies the privilege level available at the virtual console: either admin or oper (the default). This option can be specified more than once.
# hpvmcreate -P myguest1 -c 4 -r 2G -a disk:scsi::disk:/dev/rdsk/c1t2d0 Create a virtual machine named myguest2, specifying two virtual CPUs and a virtual switch named vswitch1. Each virtual CPU has a 50% entitlement.
hpvmdevmgmt(1M) NAME hpvmdevmgmt -- Manage the devices that are associated with the VM Host and the guests.
# # even if sub-paths to the specified restricted directory # # contain mount points to other file systems. # hpvmdevmgmt -a rdev:/some-directory:attr:RECURSIVE=DIR This restricts the ability to later designate anything in or hierarchically below the specified directory for use by a guest.
Options No options can be specified more than once. hpvmdevmgmt recognizes the following command-line options and arguments: -l {server | rdev | gdev} Lists an entry. The option can perform the following actions: • List all entries. To list all entries, use the following command format: hpvmdevmgmt -l all. • List all with the specified attribute or dependency. To list all the devices with a specific attribute, use the following command format: hpvmdevmgmt-V -l {all|server|rdev|gdev}:attr-name=attr-value.
-r Generates a report script that can be used after inspection to fix various device database problems. RETURN VALUES The hpvmdevmgmt command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmdevmgmt command displays error messages for any of the following conditions: • • • • An invalid option is specified. An invalid value is specified for an option.
# hpvmdevmgmt -d gdev:all:depend:mirage Replace a guest device: # hpvmdevmgmt -n gdev:/dev/vgvm/lvol5:/dev/rdsk/c2t1d0s4 AUTHORS The hpvmdevmgmt command was developed by HP.
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: Running on an HPVM host. The following example demonstrates the command run inside a guest. # hpvminfo hpvminfo: Running inside an HPVM guest. The following example shows the detailed information about the VM Host, from within a guest. # hpvminfo -V hpvminfo: Running inside an HPVM guest.
hpvmmigrate(1M) NAME hpvmmigrate -- Migrate a virtual machine to a different VM host. SYNOPSIS hpvmmigrate { -P vm-name | | -p vm-number } -h dest-hostname-or-IP-addr [-l vm-label ] -N new-vm-name [-c number-vcpus] [-r ] [ -e percent | | -E cycles ] [-m storage-resource] [-C] [-b] [-d] [-F] [-q] hpvmmigrate {-v} hpvmmigrate {-H} DESCRIPTION Thehpvmmigrate command moves an existing virtual machine to the destination VM Host.
-N new-vm-name Specifies the new name for the virtual machine being migrated, assuming no virtual machine with that name already exists. The name can consist of up to 256 alphanumeric characters, including A-Z, a-z, 0-9, the dash (-), the underscore character (_), and period (.). The virtual machine name must not start with a dash (-). The virtual machine name can only be changed by using the -N option. The name change takes effect immediately.
Physically copies the single storage device specified with the -m option to the target host during the migration process Causes hpvmmigrate to boot the target guest automatically after the migration process is complete. Causes hpvmmigrate to automatically shut down the target guest before the migration process, after the resource test in the target host.
# hpvmmigrate -P compass1 -h abc.def.com AUTHORS hpvmmigrate was developed by HP.
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, where: type=ram List dynamic memory values.] hpvmmgmt [-v] [-x name=value or] [-x name=value:name=value, where] [-x ram_target= { 0 | start | amount }] DESCRIPTION The hpvmmgmt command allows you to view and potentially manage dynamic guest data.
Specifies virtual machine characteristics. Use the following keywords: • -x ram_target={0 | start | amount} -x keyword=value Specifies the guest RAM target, where the values are as follows: — — — 0 indicates the dynamic memory driver reduces the memory on the guest to what it determines is a comfortable minimum that does not result in guest memory being paged out. start indicates that the guest dynamic memory size is set back to the boot time value. amount is a specific target memory size for the guest.
SEE ALSO On the VM Host: hpvm(5), hpvmclone(1M), hpvmcollect(1M), hpvmconsole(1M), hpvmcreate(1M), hpvmdevmgmt(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmnet(1M), hpvmpubapi(3), hpvmremove(1M), hpvmresources(5), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M), hpvmpubapi(3) 216
hpvmmodify(1M) NAME hpvmmodify -- Rename a virtual machine or modify the attributes of a virtual machine.
-e percent error message indicates the changes that require the virtual machine to be rebooted. 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. The percent can be set to an integral value between 0 and 100. If the value specified is less than 5, the virtual machine will be allocated the minimum percentage of 5%. The default is 10%.
-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. If the start_attr attribute is set to auto, the virtual machine is started when Integrity VM is initialized. This is the default.
The rsrc specifies the mapping of a guest virtual device to a VM Host backing store. Integrity VM guests access virtual devices that are instantiated on physical entities managed by the VM Host. These physical entities (for example, network cards, files, logical volumes, disk partitions, and so forth) are collectively referred to as "backing stores.
of an authorized group can use the hpvmconsole command to manage this guest. {admin|oper} specifies the privilege level available at the hpvmconsole, either admin or oper (the default). Do not specify the privilege level when you are removing a group. This option can be specified more than once. -u [+|-]user[:{admin|oper}] Adds (+ or unspecified) or removes (-) a user authorization. An authorized VM Host user account can use the hpvmconsole command to manage this guest.
DIAGNOSTICS hpvmmodify 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. vm_name or vm_number does not exist, cannot be accessed, is not a virtual machine, or is corrupt. The new_vm_name already exists. One or more options other than -a, -m, -d, -g or -u have been specified more than once. The same resource was allocated more than once.
Warning Warning Warning Warning Warning 7 on item /dev/rdsk/c1t1d3 backing device does not exist. 8 on item /dev/rdsk/c3t1d0: Device file '/dev/rdsk/c3t1d0' in use by another guest. 9 on item hostnet: MAC address in use for switch hostnet. 10 on item offnet: Vswitch offnet is not active. 11 on item badnet: 'badnet' backing device does not exist. These problems will prevent HPVM guest myguest1 from booting.
hpvmnet(1M) NAME hpvmnet -- Create and control an Integrity Virtual Machines virtual network switch (vswitch).
Two classes of virtual network interface are supported in Integrity VM: lan and avio_lan. The lan interface is supported on all underlying HP-UX network interface cards. The avio_lan interface is supported on selected HP-UX network interface cards and provides accelerated performance. For examples of use of the lan and avio_lan keywords, see the hpvmcreate and hpvmmodify manpages. Options No options can be specified more than once.
-M 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. The comma (,) separates individual items in a list of similar items. The -V, -M and -X options are mutually exclusive. -X Displays verbose resource information in the XML format. The -V, -M, and -X options are mutually exclusive.
up VLAN rules on the virtual switch and later create virtual machines referencing the specific port numbers. Specifies the port number on the vswitch. To specify all the ports on the vswitch, enter all. This command displays information about VLAN ports configured for the specified vswitch. Do not use the -p option with the -V option. 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.
MAC Address IP Address Vswitch Port Guest's Name MAC Address IP Address Vswitch Port Guest's Name MAC Address IP Address Vswitch Port Guest's Name MAC Address IP Address Vswitch Port Guest's Name MAC Address IP Address Vswitch Port Guest's Name MAC Address IP Address Vswitch Port Packets in Packets out to stream Packets out to guest Packets dropped Broadcasts Counter 0 Counter 1 Counter 2 Counter 3 Cycles in Cycles out to stream Cycles out to guest Cycles switch packet : : : : : : : : : : : : : : : : : : :
1 2 3 4 Reserved Active Reserved Active lan none lan none avio_lan none lan none # hpvmnet -S myswitch -p 4 Vswitch Name : Max Number of Ports : Port Number : Port State : Active VM : Untagged VlanId : Reserved VMs : Adaptor : 1 1 config2 1 1 winguest2 myswitch 100 4 Active winguest2 none winguest2 avio_lan In order to switch over the lan1 from lan0: # hpvmnet -C -S hostnet -n 0 # hpvmnet -S hostnet Name Number State Mode NamePPA MAC Address IP Address ======== ====== ======= ========= ======== ===
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 the hpvm_api_virtmach_check routines. If an error occurs on the hpvm_api_version_get, hpvm_api_my_uuid_get, the hpvm_api_server_uuid_get, or the hpvm_api_server_hostname_get routine, one of the following error codes defined in hpvm_api_public.
hpvmremove(1M) NAME hpvmremove -- Remove an Integrity Virtual Machines virtual machine. SYNOPSIS hpvmremove { -P vm_name | -p vm_number } [-F] 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.
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. AUTHORS The hpvmremove command was developed by HP.
hpvmresources(5) NAME hpvmresources -- Specifying virtual storage and virtual network devices. SYNOPSIS Virtual resource specification DESCRIPTION The hpvmcreate, hpvmclone, and hpvmmodify commands may be used 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 (:).
• • • file. For the physical device, specify a locally-mounted, non-NFS, VxFS file (for example, /guestfiles/diskfile1). null. Specifies an empty storage unit. This should not be a world-writable directory such as tmp. (This is useful for removable media, such as DVDs.) attach. Specifies an attached device, such as a tape device, media changer, or CD/DVD burner. The physical device names must not contain the following characters: colon (:), semicolon (;), and comma (,).
addresses, and to make sure that the proper bits are set. You can specify the bus and device with the MAC address, or the MAC address without the bus and device, or you can omit the entire hardware address. If you do not specify the virtual network device hardware address, or a portion of it, the missing information will be generated automatically.
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 checks to make sure that the starting virtual machine can be allocated all of the required resources defined by its configuration file. If not, the virtual machine will not be started.
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 some state other than Off, and cannot be started. Use the hpvmstart command to stop the virtual machine. The virtual machine cannot boot at this time because of detected resource complaints.
hpvmstatus(1M) NAME hpvmstatus -- Display status information about one or more virtual machines.
• • To display the virtual machine's resource scheduling information, include the -r option. To display the mode the scheduler is in, include the -S option. To obtain a display in machine-readable format, use the -M or -X option. Only superusers can execute the hpvmstatus command. Options No options can be specified more than once. The hpvmstatus command recognizes the following options and arguments: -v -V Displays the version number of the hpvmstatus command.
When you specify a virtual machine, the hpvmstatus command displays the following information for each virtual CPU: • • • • • Cumulative Usage: The number of cycles this virtual CPU has consumed since the virtual machine was booted. Guest percent: The CPU percentage the guest has consumed. Host percent: The CPU percentage that the VM Host uses on behalf of the guest. Cycles achieved (expressed in MHz). Sampling Interval: The time period between samples.
[Authorized Administrators] Oper Groups: Admin Groups: Oper Users: Admin Users: [Virtual CPU Details] #vCPUs Entitlement Maximum ====== =========== ======= 1 10.0% 100.
Available memory = 2557 Mbytes Available swap space = 1541 Mbytes Maximum vcpus for an HP-UX virtual machine = 2 Maximum vcpus for a Windows virtual machine = 2 Maximum vcpus for a Linux virtual machine = 2 Available entitlement for a 1 way virtual machine = 900 Mhz Available entitlement for a 2 way virtual machine = 810 Mhz Display the Serviceguard server information on the VM Host system: # hpvmstatus -m HPVM Multi-server environment This servers identifier=1 Server_id=1 Server_state=1 Server_ipaddr=1.2.
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. It 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.
RETURN VALUES The hpvmstop command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmstop 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. vm-name or vm-number does not exist, cannot be accessed, is not a virtual machine, or is corrupt.
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. Start the script by entering 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. The name of the depots to consolidate may be obtained from this listing. The list returned does not contain Operational Environment related packages. The list of packages that will be excluded is stored in a configuration file (see Data Directories/FILES section below).
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 perform application consolidation: # p2vassist P2V Assistant Manager ====================================== 1 ) General Configurations 2 ) Manage Applications 3 ) Manage O.
. . hpuxwsAPACHE hpuxwsTOMCAT hpuxwsWEBMIN hpuxwsXML . . vim xpm zlib 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, the web server suite (hpuxwsAPACHE, hpuxwsTOMCAT, hpuxwsWEBMIN and hpuxwsXML) will be consolidated.
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. Depots to be installed: Firefox Dirs/Files list not defined.
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”.
extensible firmware interface See EFI. failover The operation that takes place when a primary service (network, storage, or CPU) fails, and the application continues operation on a secondary unit. In the case of Serviceguard virtual machines, the virtual machine can fail over to another cluster member. In case of a network failure, on a properly configured system the virtual machine can fail over to another LAN on the same cluster node.
PMAN Platform Manager. See VM Host. pNIC Physical network interface card. primary node The cluster member on which a failed-over package was originally running. redundancy A method of providing high availability that uses mltiple copies of storage or network units to ensure services are always available (for example, disk mirroring). restricted device A physical device that can be accessed only by the VM Host system. For example, the VM Host boot device should be a restricted device.
WBEM Web-Based Enterprise Management. A set of Web-based information services standards developed by the Distributed Management Task Force, Inc. A WBEM provider offers access to a resource. WBEM clients send requests to providers to get information about and access to the registered resources. workload The collection of processes in a virtual machine.
Index A adapters virtual storage, 83 adding virtual storage, 104 admin privileges, 126 Administrator guest, 103 VM Host, 103 APA, using, 110 applications running on guests, 19 running on VM Host, 19 attachable devices specifying, 100 attached devices, 84 attached I/O, 83 Auto Port Aggregation (see APA) AVIO using, 18 B bundle names, 26 C CD/DVD burner, virtual, 83 characteristics of virtual machines, 31 cloning guests VLAN information, 118 cloning virtual machines, 44 cluster in a box configuration, 155 c
installing guest management software, 54 hpvmclone command, 44 options, 44 hpvmcollect command, 169, 172 options, 169, 172 hpvmconsole command, 112 options, 127, 129 using, 126 hpvmcreate command, 38 options, 39 hpvmdevmgmt command, 138 hpvminfo command, 28 hpvmmigrate command, 144 hpvmmodify command, 41 hpvmnet command, 110 hpvmremove command using, 48 hpvmstart command options, 40 hpvmstatus command, 123 displaying VLANs with, 118 hpvmstop command, 47 I installing guest management software , 127 installi
examples of, 104 R re-creating vswitches, 114 redefining pNICs, 120 removing guests, 48 removing Integrity VM, 28 removing vNICs, 116 replacing devices, 140 reporting problems, 169 requirements for installing Integrity VM, 25 restricting devices, 140 S sctl device files, 101 Serviceguard using with Integrity VM, 153 setting up virtual storage, 91 shared I/O, 82 sharing devices, 139 specifying virtual storage, 91 specifying VM Host virtual storage, 92 starting distributed guests, 163 starting virtual machi
performance, 86 setting up, 91 shared, 82 specifying, 91 specifying FileDisk, 96 specifying Virtual Disk, 93 specifying Virtual DVD, 97 specifying Virtual FileDVD, 98 specifying Virtual LvDisk, 94 specifying Virtual NullDVD, 98 specifying VM Host, 92 supportability, 85 time associated with setting up, 90 using, 102 virtual storage devices creating, 81 planning, 35 virtual switches (see vswitches) virtual-to-physical cluster configuration, 156 virtual-to-virtual cluster configuration, 155 VLANS displaying in
