HP Integrity Virtual Machines 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 1 Intended Audience.............................................................................................................................11 2 New and Changed Information in This Edition................................................................................11 3 Typographic Conventions.....................................................................
3.4 Changing Virtual Machine Configurations.....................................................................................36 3.5 Cloning Virtual Machines...............................................................................................................39 3.6 Stopping Virtual Machines..............................................................................................................42 3.7 Removing Virtual Machines....................................................................
7.2.1.2 Performance of Virtual Devices.......................................................................................75 7.2.1.3 VM Storage Multipath Solutions.....................................................................................77 7.2.1.4 VM Storage Management................................................................................................78 7.2.1.5 VM Storage Changes.......................................................................................................
9.5 Guest Configuration Files..............................................................................................................120 9.6 Dynamic Memory..........................................................................................................................120 9.6.1 Managing Dynamic Memory from the VM Host..................................................................120 9.6.1.1 Viewing Dynamic Memory on the VM Host................................................................
11.3.6 Verifying That Distributed Guests Can Fail Over...............................................................150 11.3.7 Managing Distributed Guests.............................................................................................151 11.3.7.1 Starting Distributed Guests.........................................................................................151 11.3.7.2 Stopping Distributed Guests.......................................................................................151 11.
Glossary.........................................................................................................................231 Index...............................................................................................................................
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 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. Refer to the HP Integrity Virtual Machines Release Notes for recent updates to the product documentation. 1 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.
• • • • • • • • • • 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 x86, Itanium, AMD64, and Intel Extended Memory Technology 64 (Intel EM64T) HP Integrity Essentials G
1 Introduction This chapter describes the Integrity VM product, including: • • • • • Section 1.1: “About HP Integrity Virtual Machines” (page 15) Section 1.2: “Running Applications in the Integrity VM Environment” (page 16) Section 1.3: “Related Products” (page 17) Section 1.4: “Using the Integrity VM Documentation” (page 18) Section 1.5: “Using This Manual” (page 19) 1.
platform. Even the system administration privileges can be allocated to specific virtual machine administrators. One way to benefit from Integrity VM is to run multiple virtual machines on the same physical machine. There is no set limit to the number of virtual machines that can be configured, but no more than 256 virtual machines can be booted simultaneously on a single VM Host. Each virtual machine is isolated from the others. The VM Host administrator allocates virtual resources to the guest.
• • • • • System performance monitoring tools (GlancePlus, Measureware, OpenView Operations Agent) Utility pricing tools (Instant Capacity, Pay per use) Hardware management tools (nPartition Manager, storage and network management tools) Multipath storage solutions HP Serviceguard can be run on the VM Host system or on HP-UX guests. Do not run applications on the VM Host system, such as Oracle, Workload Manager (WLM), and so forth.
• • HP Integrity Virtual Server Environment (VSE) — A graphical user interface for managing HP Integrity central managed systems (CMS). Runs under HP Systems Insight Manager. For more information, see the HP VSE Management Software Quick Start Guide. This version of Integrity VM requires VSE version A.02.50 or later.
• • • • • • • hpvmnet(1M) - describes how to create and modify virtual networks. hpvmstart(1M) - describes how to start virtual machines. hpvmstatus(1M), - describes how to get statistics about the guests. hpvmstop(1M) - describes how to stop a virtual machine. hpvmremove(1M) - describes how to remove a virtual machine. hpvmresources(1M) - describes how to specify the storage and network devices used by virtual machines. p2vassist(1M) - describes how to move applications from one server to another.
Table 1-1 Chapters of this Manual (continued) Chapter Read if... Chapter 10: “Migrating Virtual Machines” (page 131) You need to move virtual machines from one system to another. Chapter 11: “Using HP Serviceguard with Integrity VM” You need to set up Serviceguard to manage your VM Host (page 141) system or your virtual machines. Chapter 12: “Reporting Problems with Integrity VM” (page 155) You encounter problems while creating or using virtual machines.
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 21) Section 2.2: “Installation Procedure” (page 23) Section 2.3: “Upgrading from Earlier Versions of Integrity VM” (page 24) Section 2.4: “Verifying the Installation of Integrity VM” (page 24) Section 2.5: “Removing Integrity VM” (page 24) 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 (refer to 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 4GB (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 “VM Host System Requirements” (page 21), 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.
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.3 Upgrading from Earlier Versions of Integrity VM When you upgrade Integrity VM from an earlier version, you should: 1. Shut down all running guests (using the hpvmstop command). If you do not stop the guests, they are stopped as part of the Integrity VM installation procedure.
# 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: “Removing Virtual Machines” (page 43). 2.6 Reserving VM Host Devices You can protect the storage and network resources used by the VM Host against usage and corruption by virtual machines by marking the VM Host devices as restricted devices.
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 27) Section 3.2: “Using the hpvmcreate Command” (page 33) Section 3.3: “Starting Virtual Machines” (page 35) Section 3.4: “Changing Virtual Machine Configurations” (page 36) Section 3.5: “Cloning Virtual Machines” (page 39) 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 33) Dynamic memory If you omit the option, dynamic memory is not enabled for the guest. -x keyword=parameter Section 3.1.
3.1.3 Virtual CPUs Use the -c number_vcpus option to the command to specify the number of virtual CPUs (vCPUs) that the virtual machine can use. If you do not specify the number of vCPUs, the default is 1. For 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.
The amount of memory to allocate is the total of the following: • 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.
• • 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: “Creating vswitches” (page 100). To create the virtual machine and allocate the vswitch to it, use the —a option to the hpvmcreate command.
device:scsi::VM Host storage specification • VM Host storage specification defines where and how the virtual machine storage is supplied on the VM Host. Specify it using the following format: storage:location Where storage is one of the following: — disk — lv — file — null — attach And location is a VM Host system file. For complete information about constructing storage specifications for virtual machines, see Section 7.2.2.1: “VM Guest Storage Specification” (page 81).
3.1.7 Creating Virtual Machine Labels The —l option specifies the label of the virtual machine. The virtual machine label is a descriptive label unique to this virtual machine. The label can be useful in identifying a specific virtual machine in the hpvmstatus -V display. The label can contain up to 256 alphanumeric characters, including A-Z, a-z, 0-9, the dash (-), the underscore character (_), and the period (.). If white space is desired, the label must be quoted (""). 3.1.
Table 3-2 Options to the hpvmcreate Command (continued) Option Description -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 alocated. If you omit this option when you create the virtual machine, the default is 10%. -E cycles -r amount Memory allocated. If you omit this option when you create the virtual machine, the default is 2 GB. -a rsrc Virtual devices created.
winguest2 compass1 9 WINDOWS Off 12 UNKNOWN Off 1 1 3 0 1 0 2 GB 2 GB 0 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. The Runsysid column indicates the VM Host that runs the virtual machine in a Serviceguard cluster. If the virtual machine runs on the local VM Host, or if Serviceguard is not configured, the Runsysid is zero.
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-4 Options to the hpvmmodify Command (continued) Option Description -N new-vm-name Specifies a new name for the virtual machine. The name can consist of up to 256 alphanumeric characters including A-Z, a-z, 0-9, the dash (-), the underscore character (_), and the period (.). The virtual machine name cannot start with a dash (-). -l vm_label Modifies the descriptive label for this virtual machine.
Table 3-4 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.
Initialize guest memory mapping tables 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 45). For information about creating Windows guests, see Chapter 5 (page 49). 3.
Table 3-5 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 71). For information about forming a virtual network device specification, see Chapter 8 (page 99).
Table 3-5 Options to the hpvmclone Command (continued) Option Description -u user[:{admin|oper}] Specifies a user authorization. The specified administrative level (admin or oper) is applied to the specified user group. -x keyword=parameter Specifies values for dynamic memory setting associated with the guest, including: • • • • • dynamic_memory_control ram_dyn_type ram_dyn_min ram_dyn_max ram_dyn_target_start For more information about dynamic memory, see Section 9.6: “Dynamic Memory” (page 120).
different backing store, or run only one of the guests at a time. For more more information, see Chapter 7 “Creating Virtual Storage Devices”. Use the —b option to specify a storage device to be physically duplicated in the cloning process. This feature allows the user to specify any number of storage devices and supports all of the possible physical device types (disk, lv, and file).
# hpvmstop -P compass1 -Q # To quickly shut down all three virtual machines that are running on the VM Host, enter the following command: # hpvmstop -a -F Stopping virtual machine compass1 Stopping virtual machine compass2 Stopping virtual machine compass3 You can also use the hpvmconsole command to force the virtual machine to shut down. However, after you install the guest operating system, you should use the standard operating system commands and procedures on the guest to shut it down. 3.
The following section describes a problem that might be encountered during virtual machine creation. 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.
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 45) • Section 4.2: “Installing HP-UX Guest Management Software” (page 47) • Section 4.3: “Troubleshooting HP-UX Guest Creation” (page 48) 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.
• 11iv2 indicates HP-UX 11.23. For HP-UX 11.23 guests, the guest depot file is: /opt/hpvm/guest-images/hpux/11iv2/hpvm_guest_depot.11iv2.sd • 11iv3 indicates HP-UX 11.31. For HP-UX 11.31 guests, the guest depot file is: /opt/hpvm/guest-images/hpux/11iv3/hpvm_guest_depot.11iv3.sd Complete instructions for installing the guest management software are in the README.txt file in /opt/hpvm/guest-images/hpux directory. HP-UX guests reboot as part of the guest management software installation process. 4.
5 Creating Windows Guests You can install HP Integrity Windows 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 49) • Section 5.2: “Installing Windows Guests” (page 49) • Section 5.3: “Managing Windows Guests” (page 58) • Section 5.
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 - 2006 Hewlett-Packard Development Company, L.P.
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. The procedure for installing the operating system depends on the type of media you are installing from: • To install the Windows operating system from the reinstall kit (OPK), follow the instructions in “Installing from HP Reinstall (OPK) Media” (page 51).
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. ================================================================= Select a task by typing a letter A, B, C or Q and then press enter: WARNING, SELECTING A, B OR C WILL ERASE THE DATA ON BOOT DRIVE.
Loading device drivers EFI Boot Manager ver 1.10 [14.62] [Build: Thu Jun 8 12:30:44 2006] Please select a boot option Windows Server 2003, Enterprise EFI Shell [Built-in] Boot option maintenance menu Use ^ and v to change option(s). Use Enter to select an option Default boot selection will be booted in 30 seconds Starting: Windows Server 2003, Enterprise ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Starting Windows... 7.
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.1 SAC> NOTE: If the system displays System model could not be verified, simply acknowledge the dialog. When asked to confirm, select No and then reboot the virtual machine. 12.
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... screen is displayed. The status bar shows the following: Setup is loading files (Windows Executive)..
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 “Installing Windows Guests” (page 49), 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 Escape-Tab SAC>...Escape-Tab Setup is being restarted................. EVENT: A new channel has been created. Use "ch -?" for channel help.
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 infomration 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 63) • Section 6.2: “Installing Linux Guests from ISO Images” (page 64) • Section 6.3: “Installing Linux Guests from a Boot Disk and Network Server” (page 68) • 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 RedHat Installation DVDs (recommended) (described in Section 6.2: “Installing Linux Guests from ISO Images” (page 64)).
allocating firmware RAM (ffaa0000-ffab5000, 84KB) /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 Language Support Select your primary language plus any additional languages, then enter OK. Time Zone Selection Select a city in your time zone from the 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.
6.3 Installing Linux Guests from a Boot Disk and Network Server This section describes how obtain the Linux Installation (Boot) image from a boot disk and then obtain the Linux packages to be installed from a network server. This procedure assumes the Linux installation directory tree has been created from the ISO images on a network server. For more information, see Red Hat Enterprise Linux 4; Installation Guide for x86, Itanium, AMD64, and Intel Extended Memory Technology 64 (Intel EM64T).
• • From the EFI shell From the File menu To boot from the EFI shell: a. Go to the EFI shell. For example: fs0 fs1 fs2 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig5D1D1134-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part2,Sig5DB58D88-C809-11DB-9AEB-000000000000) : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun1,Lun0)/CDROM(Entry0) EFI lists devices with filesystems detected as fs{n}. In the above example, fs0 and fs1 are older filesystems that are present on the disk.
. Welcome to Red Hat Enterprise Linux 6. The boot program presents a few screens that allow you to specify the network parameters of the guest (IP address, netmask, gateway, DNS), the network name of the server, and the directory path to the installation tree on the server. Respond to the screens as described in Table 6-3. Table 6-3 Linux Guest Network Installation Screens Screen Title Response Language Selection Select your language and enter OK. Select Installation Method NFS or FTP and enter OK.
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 71) • Section 7.2: “Configuring Integrity VM Storage” (page 74) • Section 7.3: “Using Integrity VM Storage” (page 92) 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 For more information, see... Virtual DVD Disc in a VM Host physical DVD drive Section 7.2.2.3.4: “Virtual DVDs” (page 86) Virtual FileDVD ISO file on a VM Host VxFS file system Section 7.2.2.3.6: “Virtual NullDVDs” (page 88) Virtual NullDVD (empty) VM Host physical DVD drive or VxFS directory Section 7.2.2.3.3: “Virtual FileDisks” (page 86) 7.1.3.2.
7.2.1.1 VM Storage Supportability Before you configure virtual machine storage, make sure the VM Host storage can be supported by the virtual machine. • All VM Host storage available for use by a VM must meet support requirements for the Integrity server and OS version that comprise the VM Host. If the physical storage is not supported by the VM Host, it is not supported for use by a virtual machine.
Figure 7-1 Integrity VM Storage IO Stack Virtual File Disk File Systems Layer Virtual LvDisk Logical Volume Managers Layer Virtual Disk Attached Devices Disk Drivers Layer Integrity Vm Passthrough Drivers Layer VM Host Driver Services HP-UX Interface Driver HP-UX Interface Driver HP-UX Interface Driver Physical Adapter Physical Adapter Physical Adapter Physical Media Physical Media Physical Media For a virtual I/O operation to be completed, it has to travel round trip between the virtual stor
It is important to know exactly where the virtual media is located on physical storage devices. With Integrity VM, a single physical disk might be sliced into logical volumes or files. Slicing up physical disks increases utilization, but it can affect the performance of the physical device. The guest OS treats the virtual disk as a whole disk, not as a part of a physical one. Over-slicing physical storage can overload a physical device's ability to handle virtual I/O that is meant for whole disks.
Each multipath software solution for HP-UX 11.23 interacts at different layers on the I/O stack. Since Integrity VM also interacts with different layers in the I/O stack, only certain options apply to each virtual media type.
Beyond avoiding sub-LUN collisions, whole LUN collisions also need to be avoided. The same storage resource, virtual or attached, cannot be specified more than once to the same virtual machine. Under HP-UX 11.23, most storage device files are defined per path. Be careful not to specify a given device twice. Figure 7-4 shows an example of two device files, /dev/rdsk/c6t2d0 and /dev/rdsk/c11t2d0 pointing to the same physical disk.
No changes to any virtual media can take place on the VM Host until the virtual device that uses the media is removed from the active VM. Attempts to change virtual devices that have I/O active on them is denied by the hpvmmodify command. Once an active virtual machine is allocated virtual media for a virtual device, that virtual machine owns that media and can access it any time.
• • VM guest storage specification defines where and what storage is seen in the virtual machine (see Section 7.2.2.1: “VM Guest Storage Specification” (page 81)) VM Host storage specification defines where and how the virtual machine storage is supplied on the VM Host (see Section 7.2.2.2: “VM Host Storage Specification” (page 81)) For examples of how to construct resource statements, see Section 7.2.2.3: “VM Storage Resource Statements” (page 82). 7.2.2.
• storage is one of the following: disk, lv, file, null, or attach The selection of storage type defines what VM Host system files apply. For example, lv implies the use of logical volume character device files. For virtual devices, the selection of VM Host storage determines what type of virtual media the virtual device will use. For example, the selection of lv for a virtual disk, makes it a Virtual LvDisk to the VM. A VM Host storage entity can only be used for one VM device type at a time.
valid supported configurations before being used for Integrity VM storage resources (see Section 7.2.1.3: “VM Storage Multipath Solutions” (page 77)). The resource statements in the following subsections do not contain VM hardware addressing. The PCI bus, PCI slot, and SCSI target numbers are optional. 7.2.2.3.1 Virtual Disks A Virtual Disk is an emulated SCSI disk whose virtual media comes from a VM Host disk LUN. The VM Host disk LUN is specified using a character device file.
7.2.2.3.2 Virtual LvDisks A Virtual LvDisk is an emulated SCSI disk whose virtual media is provided by a raw VM Host logical volume. To specify a VM Host logical volume, use a character device file. The character device file is owned by either LVM or VxVM. Virtual LvDisks cannot be shared simultaneously across active virtual machines. Only one active virtual machine at time can be given a particular Virtual LvDisk resource.
Allocated PE Used PV 2048 1 LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV /dev/lvrackA/disk3 available/syncd 8192 2048 2048 1 LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV /dev/lvrackA/disk4 available/syncd 8192 2048 2048 1 --- Physical volumes --PV Name PV Status Total PE Free PE Autoswitch /dev/dsk/c4t1d0 available 8681 489 On In this example, the Virtual LvDisk Resource Statement is disk:scsi::lv:/dev/lvrackA/rdisk2.
To use VxVM, the Virtual LvDisk resource statement is disk:scsi::lv:/dev/vx/rdsk/VxvmTest1/vxvm_2. For information about multipath solutions for Virtual LvDisks, see Section 7.2.1.3: “VM Storage Multipath Solutions” (page 77). 7.2.2.3.3 Virtual FileDisks A Virtual FileDisk is an emulated SCSI disk whose virtual media comes from a VM Host file. The VM Host file is specified using the absolute pathname to the file. The file can be on a VxFS file system locally mounted on the VM Host.
The Virtual DVD resource statement takes the form of: dvd:scsi::disk:/dev/rdsk/cXtYdZ Where /dev/rdsk/cXtYdZ is an HP-UX character device file representing a VM Host CD/DVD drive. Typically, the HP-UX sdisk character file will already be created before booting the VM Host. If it is not, it can be created and managed using the ioscan, insf, and rmsf utilities. For example: # ioscan -funC disk disk 0 0/0/2/0.0.0.
(see Section 7.3.2.3: “Modifying VM Storage Devices” (page 94)). The ISO files should be marked with proper permissions; they must not be world writable. For example: # ls -l /var/opt/hpvm/ISO-images/hpux total 26409104 -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root sys sys sys sys 3774611456 4285267968 3149987840 1629978624 Jul Jul Jul Jul 11 11 11 11 16:59 17:05 18:42 18:51 0505-FOE.iso 0512-FOE.iso 0603-FOE-D1.iso 0603-FOE-D2.
In this example, the Virtual NullDVD resource statement is dvd:scsi::null:/dev/rdsk/c0t0d0. If the VM Host administrator does not want to give access to the VM Host CD/DVD drive to the guest administrator, you can set up a Virtual NullDVD to a file system directory containing the ISO files that the guest administrator wants to access. This resource statement would take the following form: dvd:scsi::null:/pathname Where /pathname is the file system directory where the ISO files are located.
Where /dev/rscsi/cXtYdZ is an HP-UX sctl device file to the device type specified. To create an HP-UX sctl device file, follow these steps: 1. Run ioscan to pick up any new devices that may have just been connected: # ioscan 2. Locate the device designated for attachment. 2a. Install any device special files for these new devices: # insf -e 2b. Check to see if the new devices were claimed by VM Host: # ioscan -fun The following is an example of a claimed tape device: tape 1 0/2/1/0.5.
Claimed = /dev/rmt/c6t5d0BEST SCTL = /dev/rscsi/c6t5d0 The following is an example of media changer device: Claimed = /dev/rac/c6t0d0 SCTL = /dev/rscsi/c6t0d0 The following is an example of CD/DVD burner device: Claimed = /dev/rdsk/c4t3d2 SCTL = /dev/rscsi/c4t3d2 Once the /dev/rscsi file has been located, proceed to step 5. 4b. If the device is unclaimed, a /dev/rscsi file must be created containing numbers corresponding to the hardware address.
devices, attached devices can be attached and detached dynamically across active virtual machines (see Section 7.3: “Using Integrity VM Storage” (page 92)). Also, as the device is being attached to a virtual machine, it cannot be opened by the VM Host at the time of or during attachment. Because tapes, media changers, and CD/DVD burners are not virtualized, media changes with them must be done physically.
7.3.1.2 Guest Administrator The VM Guest Administrator is responsible for the proper maintenance of a guest OS. As such, this person needs access to the virtual console by the VM Host administrator to control the virtual machine. The guest administrator must understand how to maintain the guest OS, install patches and applications, and set up security for the guest users of the guest OS.
The resource statement for adding an Integrity VM storage device does not require virtual hardware addressing. If the PCI bus, slot and SCSI target numbers are not specified, Integrity VM automatically chooses the first position available for the device. For example: # hpvmmodify -P myvmm -a 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 1 0 disk /dev/rdsk/c3t2d0 7.3.2.
3. 4. 5. Based on the virtual media type, set up and configure the VM Host to form a valid VM Host storage specification. Take into account the other demands on VM Host resources to avoid virtual machine storage conflicts. Use the VM Host storage specification with the hpvmmodify command to modify the virtual device resource. Verify that the old VM Host resource is no longer in use by a virtual machine.
type: CD-ROM size: 0 Kbytes bytes per sector: 0 [After inserting a new disc on the VM Host CD/DVD drive] vMP> in Insertable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev -------------------------------------------[1] 0/0/1/0.7.
vMP> in Insertable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev -------------------------------------------[1] 0/0/1/0.7.0 (0,1,7) dvd Enter menu item number or [Q] to Quit: 1 Insertable File Backing Stores Num File --------------------[1] 0505-FOE.iso [2] 0512-FOE.iso [3] 0603-FOE-D1.iso [4] 0603-FOE-D2.
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 “Creating Virtual Machines” (page 27). 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.
Using redundant pNICs and APA, you can ensure high availability of the guest networks and provide greater capacity for the VM Host system running many guests with network-intensive applications. You can configure HP-UX VLANs for the guests. VLANs isolates broadcast and multicast traffic by determining which destinations should receive that traffic, thereby making better use of switch and end-station resources. With VLANs, broadcasts and multicasts go only to the intended nodes in the VLAN. 8.
Table 8-1 Options to the hpvmnet Command (continued) Option Description -u portid:portnum:vlanid:[vlanid | none] Configures the port portnum on the virtual switch so that it is isolated to the VLAN specified by vlanid. See Section 8.4: “Configuring VLANs” (page 106) for more information. -V Enables verbose mode, displaying information detailed information about one or all vswitches. -v Displays the version number of the hpvmnet command in addition to the vswitch information.
connected to the physical network. For example, to create a local network vswitch named clan0, enter the following commands: # hpvmnet -c -S clan0 # hpvmnet -b -S clan0 All VNICs connected to that vswitch will then be on the same local network. The VM Host does not communicate on local networks. If you omit the -n option when you create a vswitch, the default is to use localnet. The localnet vswitch can be used as a local network and VNICs can be specified for a guest.
0/1/2/0 0/4/1/0 0x00306E3977AB 1 0x00306E4CE96E 2 UP UP lan1 snap1 lan2 snap2 2 3 ETHER ETHER Yes Yes 119 119 The hardware path from the output of lanscan on the guest matches the path in the guest configuration file. The Station Address in the lanscan output also matches the guest virtual MAC address in the guest configuration file. 8.2.2 Modifying vswitches You can use the -C option to change the physical network interface card (pNIC) the guest has in use.
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 -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 Vswitches start automatically when the VM Host system is started. You can start the vswitch manually using the —b option to the hpvmnet command.
• [hardware-address] (optional), formatted as bus,device,mac-addr. If you do not specify the hardware address, or a portion of it, the information is generated for you. HP recommends allowing Integrity VM to generate the hardware address.
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 the lanadmin(1M) command to configure VLANs on a remote HP-UX host.
When VLANs are configured on the vswitch and the guests are required to communicate over a VLAN with a remote node outside the VM Host, you might need to set up the physical network appropriately for the VLAN. For information about configuring VLANs on the switches, refer to the product documentation for the physical network adapters.
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 113) 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.
# passwd guest1 3. Use the hpvmmodify command to provide the user with guest administration privileges: #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.
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.
Setting ram_dyn_type to any or driver enables the other dynamic memory configuration controls. The minimum (ram_dyn_min) and maximum (ram_dyn_max) values bound the value of ram_dyn_target_start. The value of ram_dyn_target_start is set to 2 GB. 9.6.1.1 Viewing Dynamic Memory on the VM Host On the VM Host, dynamic memory software is included with Integrity VM. Dynamic memory parameters and status are displayed for each guest using the standard Integrity VM commands.
Table 9-3 Dynamic Memory Characteristics (continued) Characteristic Setting Description Maximum memory valueM (for megabytes) or valueG (for gigabytes) The upper bounds for ram_target and ram_dyn_target_start Current memory valueM (for megabytes) or valueG (for gigabytes) The current memory size of the guest (normally equal to target memory) Comfortable minimum valueM (for megabytes) or valueG (for gigabytes) A value for ram_target which can be used to reduce the guest memory but allow it suffici
Table 9-4 Dynamic Memory Control Command Options Keyword Value Pair Description dynamic_memory_control={1|0} Specifies whether a sufficiently privileged user on the guest (such as root) can change the dynamic memory values while the guest is running. To disable guest-side dynamic memory control, specify 0. If the guest is not active, the only effect is the modification of the guest configuration file. On the running guest, the change becomes effective immediately.
• • The minimum amount of memory that the virtual machine can use is 1222 MB. The maximum amound of memory that the virtual machine can use is 6 GB (all the memory that is allocated to the guest) The amount of memory to which the guest memory is reduced after it starts is 2G. • 9.6.2 Managing Dynamic Memory from the Guest Dynamic memory management from the guest must be enabled from the VM Host.
# hpvmmgmt -V -l ram [Dynamic Memory Information] ======================================= Type : driver Current memory : 2103 MB Target memory : 2103 MB Comfortable minimum : 2423 MB Minimum memory : 1222 MB Maximum memory : 6144 MB Boot memory : 6135 MB Free memory : 124 MB Available memory : 286 MB Memory pressure : 12 Memory chunksize : 65536 KB Driver Mode(s): STARTED ENABLED GUESTCTL To modify the guest memory to 4 GB, enter the following command: # hpvmmgmt -x ram_target=4096M Attempting to increase
9.6.3.3 Guest Performance Considerations During normal operation of a system which has a workload running on it, the large pages may become fragmented over time. This is true on the VM Host as well as a virtual machine running the HP-UX operating system. If the virtual machine's memory is fragmented, the dynamic memory subsystem will be unable to reduce the size of guest. This is due to the minimum chunk size used for the reduction.
9.6.3.6 Enable Dynamic Memory on the Guest and on the VM Host The guest management software must be installed on the guest before you can use dynamic memory parameters on the VM Host system. For example, if the guest management software is not installed, the hpvmstatus command displays the following: # hpvmstatus -V -P guest0 . . . [Dynamic Memory Information] NOTE: Dynamic data unavailable, configured values only Type : driver Minimum memory : 1024 MB Target memory : 2048 MB Maximum memory : 3072 MB . . .
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.8 Managing the Device Database Integrity VM cannot detect all potential backing store conflicts, and does not always prevent misconfigured guests from booting. Conflicts can arise from the following: • Specifying the same backing store for more than one virtual device.
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.
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. For information about installing the optional VMMigrate bundle, which provides the hpvmmigrate command, see “Installing Integrity VM” (page 21). This chapter includes the following sections: • Section 10.
The basic virtual machine migration configuration includes a source machine and a target machine. Both must be running Integrity VM and must be able to run the guests. Both machines must conform to their operating system requirements and restrictions, and both must be able to provide the allocated resources to the guest. If the guest uses 2 GB of memory on one machine, it must be able to use that amount on the other machine.
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. -hdest-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 141) • 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 Serviceguard in Guest 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 Serviceguard in Guest configurations to meet your specific requirements. The following sections describe the Serviceguard in Guest configurations. 11.
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 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 149). Start the Serviceguard package, as described in Section 11.3.4: “Starting the Distributed Guest” (page 149). 11.3.1 Configuring the Integrity VM Multiserver Environment The Integrity VM multiserver environment provides an integrated environment when guests are configured as Serviceguard packages.
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.2 Creating Guests as Packages On the VM Host, create a package configuration file and control script for the guest using the following procedure: 1. Install Integrity VM and create the guest with all necessary virtual storage devices and vswitches.
• • • • 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. The utility uses the guest name that you supply as an argument to create and populate the /etc/cmcluster/guest-name/ directory with a set of template files that contain basic Serviceguard parameter settings. HP recommends that you review and modify these template files as needed for your specific multiserver environment.
200 access policies can be added to this cluster. Modifying configuration on node host1 Modifying configuration on node host2 Modify the cluster configuration ([y]/n)? y Marking/unmarking volume groups for use in the cluster 0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100% Modifying the cluster configuration for cluster cluster1. Modifying node host1 in cluster cluster1. Modifying node host2 in cluster cluster1. Modifying the package configuration for package compass1.
PACKAGE compass1 STATUS up STATE running 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 running Network_Parameters: INTERFACE STATUS PRIMARY up STANDBY up STANDBY up STANDBY up STANDBY up PRIMARY up
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. Do not use the Integrity VM commands (hpvmstart, hpvmstop, and hpvmmigrate) to manage distributed guests. 11.3.7.
3. 4. 5. 6. Install the Integrity VM product as described in Chapter 2: “Installing Integrity VM” (page 21). Move the distributed guest back to the VM Host system using the cmhaltpkg and cmrunpkg commands. Log in to the distributed guest and remove the toolkit as described in Section 11.4.2: “Guest Toolkit Removal” (page 152). Repackage the guest using the procedure described in Section 11.4.3: “Repackaging Guests” (page 152). 11.4.
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.1 Serviceguard in Host Troubleshooting If the distributed guest does not start or failover, check both the /var/adm/syslog/syslog.log file and the package log file (/etc/cmcluster/guest—name/guest—name.log). If a package fails to start, ServiceGuard performs a package halt.
multiple failures if no standby LANs are available, or when one or more switches, hubs, interfaces or cables fail. A common issue when starting a package is the lack of available memory. See Chapter 3: “Creating Virtual Machines” (page 27) for more information about providing the required memory resources. 11.5.2 Creating Distributed Guests This manual describes how to use the hpvmsg_package script to help you configure guests as Serviceguard packages.
12 Reporting Problems with Integrity VM Report defects through your support channel. Use the following 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: “Installing the Guest Management Software” (page 117). 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.
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 Status as of April 2007 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.00 Version A.01.20 Version A.02.00 VM Host Support HP-UX 11i V2 May, 2005 HP-UX 11i V2 HP-UX 11i V2 May, 2005 May, 2005 through Sept, 2006 through Sept, 2006 Version A.03.00 Notes HP-UX 11i V2 New versions of Sept, 2006 through Integrity VM are June, 2007 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.
HP-UX patches may be required for proper operation, and should be installed onto HP-UX guest operating systems as necessary. Refer to the Integrity VM Release Notes for specific patch information. A.5 Windows and Linux Guest Support Integrity VM Version A.01.00 Version A.01.20 Version A.02.00 Version A.03.
A.7 Storage Interface Support Integrity VM Versions A.01.00 and A.01.20 Version A.02.00 Version A.03.
Storage Device Multipathing Software Supported with Integrity VM A.01.00 and A.01.20 Multipathing Software Multipathing Software Notes Supported with Supported with Integrity Integrity VM A.02.00 VM A.0300 VxVM Logical • Veritas DMP Volume • EMC PowerPath • HP SecurePath A-A / A-P VxFS File System • • • • PVLinks Veritas DMP EMC PowerPath HP SecurePath A-A / A-P Multipathing software is supported on the Integrity VM Host only.
Integrity VM Manpages 167
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.
hpvmnet(1M), hpvmremove(1M), hpvmresources(5), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvmmgmt(1M), hpvminfo(1M) 169
hpvmclone(1M) NAME hpvmclone -- Create a new virtual machine that is a copy of an existing virtual machine.
-e percent Specifies the percentage of CPU resources to which each of the new guest's virtual CPUs is entitled. If the entitlement is not specified with this option or the -E 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%.
of memory and CPU power. The os_type is one of the following: HP-UX, WINDOWS, or LINUX. This parameter is not case-sensitive. The version is specific to the operating system type. The version specifies a descriptive text string of the version of the operating system. The version string can consist of up to 256 alphanumeric characters, including A-Z, a-z, 0-9, the dash (-), the underscore character (_), and the period (.). If white space is desired then version must be quoted.
If the letter is left off, the unit type defaults to megabytes. If the -r option is omitted, the amount of memory is that of the existing virtual machine. -S Specifies that the cloned guest must share the same virtual LAN (VLAN) ports as the source guest. By default, the hpvmclone command allocates VLAN ports that are different from those allocated to the guest that is the source of the clone operation. -g [+]group :{ | admin | oper} Specifies group authorization.
• • • • vm_name or vm_number does not exist, cannot be accessed, is not a virtual machine, or is corrupt. The hpvmclone command and Integrity VM are at different revision levels. The same resource was allocated more than once. A resource allocated to another virtual machine was specified, and the force flag (-F) was not used. EXAMPLES Clone the virtual machine named compass2, to create a new virtual machine named compass5.
hpvmnet(1M), hpvmremove(1M), hpvmresources(5), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvmmgmt(1M), hpvminfo(1M) 175
hpvmcollect(1M) NAME hpvmcollect -- Collects crash dumps, logs, system status, and configuration on the VM Host and guests for post-mortem analysis.
-l Leaves the collected information in the directory rather than an archiving it. Valid on both the VM Host and the guest. -s hostname 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. -h Displays the help message. Valid on both the VM Host and the guest. -P vm_name Specifies the unique name of the virtual machine to be archived. Valid on the VM Host only.
Copying guest's tombstone file ...................................... Copying guest's console log file .................................... Copying hpvm configuration .......................................... Copying hpvm control script ......................................... Copying guest's config file ......................................... Getting status of the guest ......................................... Getting detailed status of the guest ................................
The collection is "//hpvmcollect_archive/guest1_Jan.10.07_182804EST.tar.gz" AUTHORS The hpvmcollect command was developed by the Hewlett-Packard Company.
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.
0: Successful program execution. 1: Invalid option or invalid argument to an option (usage error). 2: All other program failures (operational error). DIAGNOSTICS The hpvmconsole command displays error messages on stderr for any of the following conditions: • • • An invalid option is specified. The hpvmconsole command and Integrity VM are at different revision levels. An operational error was encountered.
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.
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. -s Sanity-checks the virtual machine configuration and returns warnings or errors, but does not create the virtual machine. This option is used to invoke the hpvmcreate command's resource checking for a virtual machine configuration without actually creating the virtual machine.
volume, a virtual DVD backed by an ISO file, a virtual network interface backed by virtual switch localnet, and a virtual network interface backed by virtual switch hostnet: # hpvmcreate -P cougar -c 2 -r 2G \ -a disk:scsi::disk:/dev/rdsk/c3t1d0 \ -a disk:scsi::disk:/dev/rdsk/c2t1d0s1 \ -a disk:scsi::lv:/dev/vg00/rguestvol1 \ -a dvd:scsi::file:/var/opt/hpvm/ISO-images/hpux/1123505GOLD.
hpvmdevmgmt(1M) NAME hpvmdevmgmt -- Manage the devices that are associated with the VM Host and the guests.
-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.
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. A value was omitted for an argument that requires one, or a value was supplied for an argument that does not take one. The hpvmdevmgmt command and Integrity Virtual Machines are at different revision levels.
hpvminfo(1M) NAME hpvminfo -- Display information about the Integrity VM environment. SYNOPSIS hpvminfo [ -V | -M | -X ] [-v] DESCRIPTION Allows you to determine whether you are running in a guest or on the VM Host. When run in a guest, this command returns information to identify the VM Host as well as the guest Information can be presented in several formats. The -M option displays in a machine-readable format, while the -X option displays in the XML format.
# hpvminfo hpvminfo: Running on an HPVM host. The following example demonstrates the command 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 | dest-IP-addr }] -l dest-vm-label -N new-vm-name [ -e percent | -E cycles ] [-m storage-resource] [-C] [-b] [-d] [-F] hpvmmigrate [-v] hpvmmigrate [-H] DESCRIPTION The hpvmmigrate 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.
errors may prevent the virtual machine from booting on the destination VM Host. Any validation errors will be logged in the Integrity VM command log. -v Displays the version number of the hpvmmigrate command. -H Displays the usage of the hpvmmigrate command. RETURN VALUES The hpvmmigrate command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred.
hpvmcollect(1M), hpvmmgmt(1M), hpvminfo(1M) 195
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=valueor] [-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.
-x keyword=value Specifies virtual machine characteristics. Use the following keywords: • -x ram_target={0 | start | amount} Specifies the guest RAM target, where the values are: — — — 0 indicates the dynamic memory driver will reduce the memory on the guest to what it determines is a comfortable minimum that would not result in guest memory being paged out. start indicates the guest dynamic memory size will be 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), hpvmremove(1M), hpvmresources(5), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvminfo(1M) 198
hpvmmodify(1M) NAME hpvmmodify -- Rename a virtual machine or modify the attributes of a 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%. In addition to the guest calculation, Integrity VM reserves processing power for essential system functions such as logging, networking, and file system daemons. The -e and the -E options are mutually exclusive. -E cycles Specifies the virtual machine's CPU entitlement in CPU cycles.
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. The response will affect the default selection of certain virtual machine attributes, such as amount of memory and CPU power. The os_type is one of the following: HP-UX, WINDOWS, or LINUX. This parameter is not case-sensitive.
-c number-vcpus Specifies the number of virtual CPUs this virtual machine sees at boot time. If unspecified, the number defaults to one. -r amount Specifies the amount of memory available to this virtual machine. The sizes are expressed as integers, optionally followed by one of the following letters: • • M -megabytes G -gigabytes If the letter is omitted, the unit defaults to megabytes. -R amount Specifies the amount of memory held in reserve for this virtual machine.
RETURN VALUES The hpvmmodify command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. 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.
Following are sample warning messages returned when hpvmmodify is executed with various configuration problems on the guest myguest1: HPVM guest myguest1 configuration problems: Warning 1: Guest needs more vcpus than server supports. Warning 2: Insufficient free memory for guest. Warning 3: Insufficient swap resource for guest. Warning 4: Insufficient cpu resource for guest. Warning 5 on item /dev/rdsk/c2t1d0: Device file '/dev/rdsk/c2t1d0' in use by another guest.
hpvmnet(1M) NAME hpvmnet -- Create and control an Integrity Virtual Machines virtual network switch (vswitch).
The hpvmnet command without options displays summary information about all vswitches configured on the VM host. The hpvmnet command recognizes the following command-line options and arguments: -S vswitch-name Specifies the unique name of the virtual switch. The name of the vswitch is limited to eight characters. The -S and -s options are mutually exclusive. -s vswitch-number Specifies the unique number of the virtual switch. The vswitch number is reported using the hpvmnet command.
-r Stops and restarts a vswitch. -n nic-id Designates the network interface on the VM Host that this vswitch will use. Network interfaces are displayed by the lanscan command. If -n is not specified when creating a vswitch, a local vswitch will be created. -u portid:portnumber:vlanid:{vlan-id | none } Specifies the VLAN identifier for the specific vswitch and port.
# hpvmnet -c -S switch2 -n 0 Display all the vswitches on this VM Host: # hpvmnet Name Number ======== ====== localnet 1 hostnet 296 vmvlan 13 myswitch 241 State ======= Up Up Up Up Mode ========= Shared Shared Shared Shared NamePPA MAC Address ======== ============== N/A lan1 0x00306e4a92ef lan900 0x00306e4bc7bf lan0 0x00306e4a93e6 IP Address =============== N/A 16.116.8.
# hpvmnet -d -s 6 -F Start the vswitch named switch1: # hpvmnet -b -S switch1 Stop the vswitch named switch1: y # hpvmnet -h -S switch1 hpvmnet: Halt the vswitch 'switch1'? [n/y]: Configure port 2 on vswitch switch1 with VLAN identifier 100: # hpvmnet -S switch1 -u portid:2:vlanid:100 Display information about VLAN ports configured for the vswitch named myswitch: # hpvmnet -S myswitch Name Number State Mode PPA MAC Address IP Address ======== ====== ======= ========= ====== ============== ==============
hpvm(5), hpvmclone(1M), hpvmcollect(1M), hpvmconsole(1M),hpvmcreate(1M), hpvmdevmgmt(1M), hpvminfo(1M), hpvmmigrate(1M), hpvmmodify(1M), hpvmremove(1M), hpvmresources(5), hpvmstart(1M), hpvmstatus(1M), hpvmstop(1M), p2vassist(1M) On the Integrity VM guest: hpvmcollect(1M), hpvmmgmt(1M), hpvminfo(1M) 210
hpvmremove(1M) NAME hpvmremove -- Remove an Integrity Virtual Machines virtual machine. SYNOPSIS hpvmremove { -P vm-name | -p vm-number } [-F] [-Q] DESCRIPTION The hpvmremove command deletes a virtual machine's configuration information and frees any resources associated with it. Once the virtual machine has been removed all resources associated with the virtual machine become available for allocation to other virtual machines.
• • vm_name is in some state other than Off. The hpvmremove command and Integrity Virtual Machines are at different revision levels. EXAMPLES Delete the virtual machine myguest: # hpvmremove -P myguest hpvmremove: Remove the virtual machine myguest? [n]: y Delete a virtual machine using its unique identifier, using the force option: # hpvmremove -F -p 333 Remove a running guest: # hpvmremove -P hpux1 hpvmremove: The guest is currently running, not able to remove. hpvmremove: Unable to continue.
hpvmresources(5) NAME hpvmresources -- Specifying virtual storage and virtual network devices. SYNOPSIS Virtual resource specification DESCRIPTION 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 (:).
• • 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 (,).
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. If you specify only a portion of the virtual network device hardware address (for example, just the MAC address), you must include the commas (for example ,,aa-bb-cc-00-11-22).
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.
RETURN VALUES The command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred. DIAGNOSTICS The hpvmstart command displays error messages on stderr for any of the following conditions: • • • • • An invalid option is specified. The vm-name or vm-number does not exist, cannot be accessed, is not a virtual machine, or is corrupt. The virtual machine is in some state other than Off, and cannot be started.
hpvmstatus(1M) NAME hpvmstatus -- Display status information about one or more virtual machines.
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 Displays the version number of the hpvmstatus command. The version number is displayed first, followed by information specified by other options. -V Displays detailed information (verbose mode) about the virtual machines.
• • Maximum: The maximum amount of CPU entitlement this virtual machine can use. Percent Usage: The percentage of the VM Host physical CPUs this virtual machine has used during the last interval period. Cumulative Usage: The number of VM Host CPU cycles this virtual machine has consumed since it was booted.
Display the attributes and resources attached to the virtual machine config2: # hpvmstatus -P config2 [Virtual Machine Details] Virtual Machine Name VM # OS Type State ==================== ===== ======= ======== config2 2 HPUX On (OS) [Authorized Administrators] Oper Groups: Admin Groups: Oper Users: Admin Users: [Virtual CPU Details] #vCPUs Entitlement Maximum ====== =========== ======= 1 10.0% 100.
# hpvmstatus -s [HPVM Server System Resources] Processor speed = 900 Mhz Total physical memory = 6132 Mbytes Total number of processors = 2 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
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.
-F Specifies the force option. Omits the confirmation dialog before resetting the virtual machine. This option is intended for use by scripts and other noninteractive applications. -q Makes certain scripted operations less verbose (quiet mode). -Q Quietly performs the command. The default is to prompt for confirmation of the command before performing it. RETURN VALUES The hpvmstop command exits with one of the following values: 0: Successful completion. 1: One or more error conditions occurred.
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 applicationd 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.
2 ) Select Applications 3 ) Add Data Directories/Files 4 ) Consolidate Applications ----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 FILES section below).
• Add Data Directories/Files Specifies the directories or files that contain the application configuration and data. Enter absolute paths that refer to directories and files that already exist. Some known, system level directories are rejected by default (such as ./, /var, and /usr). If you specify a software depot, p2vassist reads the data directories from the depot definition. These directories appear as a suggestion to the user.
Transferring /opt/hpws/webmin directory to vmp2v, please wait... Application Sucessfully consolidated on host: vmp2v Press to return to menu: 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.
gcc gdbm . . hpuxwsAPACHE hpuxwsTOMCAT hpuxwsWEBMIN hpuxwsXML . . vim xpm zlib 4.1.0 1.8.3 gcc gdbm B.2.0.55.03 B.5.5.9.04 A.1.070.07 A.2.00 HP-UX HP-UX HP-UX HP-UX 7.0 3.4k 1.2.3 vim xpm zlib Apache-based Web Server Tomcat-based Servlet Engine Webmin-based Admin XML Web Server Tools 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.
4 ) Consolidate Applications ----0 ) Return Enter Option Number: 4 Consolidate Applications ============================== This option will consolidate application(s) installed on the current system and then migrate into another a suitable target system. The target system is the machine which will host the consolidated application(s). This wizard requires that non-interactive Secure Shell (ssh) access be set up between this system and the target server.
Glossary This glossary defines the terms and abbreviations as they are used in the Integrity VM product documentation. 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”. This port arrangement provides more data bandwidth than would otherwise be available.
guest administrator The administrator of a virtual machine. A guest administrator can operate the virtual machine using the hpvmconsole command with action that can affect the specific guest only. guest application A software application that runs on a guest. guest application package A guest application that has been configured as a Serviceguard package. guest console The virtual machine console that is started by the hpvmconsole command.
Serviceguard Serviceguard allows you to create high-availability clusters of HP 9000 or HP Integrity servers. Many customers using Serviceguard want to manage virtual machines as Serviceguard packages. A Serviceguard package groups application services (individual HP-UX processes) together and maintains them on multiple nodes in the cluster, making them available for failover. SGeRAC Serviceguard extension for real application clusters. SGeSAP Serviceguard extension for SAP.
Index A adapters virtual storage, 73 adding virtual storage, 93 admin privileges, 116 Administrator guest, 93 VM Host, 92 APA, using, 99 applications running on guests, 16 running on VM Host, 16 attachable devices specifying, 89 attached devices, 74 attached I/O, 73 Auto Port Aggregation (see APA) B bundle names, 22 C CD/DVD burner, virtual, 73 characteristics of virtual machines, 27 cloning guests VLAN information, 108 cloning virtual machines, 39 Cluster in a box configuration, 143 configuration files f
options, 155, 158 hpvmconsole command, 102 options, 117, 119 using, 116 hpvmcreate command, 33 options, 34 hpvmdevmgmt command, 128 hpvminfo command, 24 hpvmmigrate command, 132 hpvmmodify command, 36 hpvmnet command, 100 hpvmremove command using, 43 hpvmstart command, 102 options, 35 hpvmstatus command, 113 displaying VLANs with, 108 hpvmstop command, 42 I installing guest management software , 117 installing HP-UX guest management software, 47 installing HP-UX guests, 45 installing Integrity VM, 21, 23 i
removing guests, 43 removing Integrity VM, 24 removing VNICs, 106 replacing devices, 130 reporting problems, 155 requirements for installing Integrity VM, 21 restricting devices, 130 S sctl device files, 91 Serviceguard using with Integrity VM, 141 Serviceguard in Guest configuring, 142 Serviceguard in Guests configuration procedure, 144 Serviceguard in host configuration, 145 setting up virtual storage, 80 shared I/O, 72 sharing devices, 129 specifying virtual storage, 81 specifying VM Host virtual storag
modifying, 94 multipath solutions, 77 performance, 75 setting up, 80 shared, 72 specifying, 81 specifying FileDisk, 86 specifying Virtual Disk, 83 specifying Virtual DVD, 86 specifying Virtual FileDVD, 87 specifying Virtual LvDisk, 84 specifying Virtual NullDVD, 88 specifying VM Host, 81 supportability, 75 time associated with setting up, 80 using, 92 virtual storage devices creating, 71 planning, 31 virtual switches (see vswitches) Virtual/physical cluster configuration, 144 Virtual/virtual cluster configu
