HP-UX vPars and Integrity VM V6.1 Administrator Guide HP Part Number: 5900-1577 Published: March 2012 Edition: 1.
© Copyright 2012 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.
Contents 1 Introduction.............................................................................................13 1.1 Intended audience.............................................................................................................13 1.2 Common Manageability of vPars and VMs...........................................................................13 1.3 About vPars......................................................................................................................14 1.
Upgrading the VSP from previous versions of Integrity VM.............................43 4.1 Upgrading the VSP from previous versions of Integrity VM V3.x to Integrity VM V6.1..................43 4.1.1 Study the current HP-UX 11i v2 to HP-UX 11i v3 update documentation...............................45 4.1.2 Analyze HP-UX 11i v2 based Integrity VM server............................................................45 4.1.2.1 Run the HP-UX msv2v3check tool.......................................................
7.1.5 Virtual CPUs..............................................................................................................77 7.1.6 Entitlement.................................................................................................................78 7.1.7 Guest memory allocation.............................................................................................78 7.1.8 Automatic cell balancing.............................................................................................
9.1.4.3 vPar/VM storage devices...................................................................................115 9.1.4.3.1 Virtual devices...........................................................................................115 9.1.4.3.2 Attached devices.......................................................................................115 9.2 Configuring vPar/VM storage...........................................................................................116 9.2.1 Storage considerations...
10.4.2 Guest-Based VLANs (AVIO)....................................................................................156 10.4.3 Configuring VLANs on virtual switches.....................................................................156 10.4.3.1 Creating and managing a vswitch with a VLAN interface....................................156 10.4.4 Configuring VLANs on physical switches..................................................................157 10.5 Using direct I/O networking...........................
11.10 vPar/VM log files..........................................................................................................189 11.11 Managing the device database.......................................................................................189 11.11.1 The vPars/VM device database file...........................................................................190 11.11.2 Using the hpvmdevmgmt command..........................................................................190 11.11.2.
14.3 Typographic conventions................................................................................................223 A Rolling back to the previously installed version of Integrity VM......................225 B Sample Script for Adding Multiple Devices.................................................227 Glossary..................................................................................................233 Index................................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 vPars V6.1 framework.......................................................................................................14 Hardware Consolidation Using Integrity VM........................................................................15 Upgrade Procedure..........................................................................................................44 Installing VirtualBase on a vPar/VM......................................................................
34 35 36 37 Itanium Processor Families...............................................................................................207 Options to the hpvmcollect Command on the VSP.........................................................215 Options to the hpvmcollect Command on Guests..........................................................218 Documentation and its location........................................................................................
1 Introduction HP-UX vPars and Integrity VM Version 6.1 is a new product bundle that brings together vPars and Integrity VM functionality in a single, common, easy-to-use management environment. This product is a follow-on to HP-UX Virtual Partitions v6.0 and HP Integrity VM V4.3. The V6.1 product supports either a VM-only environment or a vPar-only environment, but not a mixed VM and vPar environment. A VM-only environment has the same user experience as an Integrity VM V4.3 follow-on release.
1.3 About vPars vPars V6.1 is a follow-on release to the vPars V6.0 HP-UX Virtual Partitions product that enables you to run multiple instances of HP-UX simultaneously on a Virtualization Services Platform (VSP). Each virtual partition is assigned a subset of hardware, runs a separate instance of HP-UX, and hosts its own set of applications. As each instance of HP-UX is isolated from all other instances, vPars provides application and Operating System (OS) fault isolation.
The VSP virtualizes physical processors, memory, and I/O devices, allowing you to allocate them as virtual resources to each virtual machine. Virtual machines are abstractions of real, physical machines. The guest operating system runs on the virtual machine just as it would run on a physical Integrity server, with no special modification. In addition to the vPars and Integrity VM V6.
can be assured of identical configurations, including the hardware devices backing each guest's virtual devices. Testing upgraded software and system modifications is a simple matter of entering a few commands to create, monitor, and remove virtual machines. Integrity VM can improve the availability and capacity of your data center. Virtual machines can be used to run isolated environments that support different applications on the same physical hardware.
drivers for these devices in the guest operating system are virtualization aware, eliminating some of the virtualization overhead. However, the guest operating system still does not have direct visibility to the underlying hardware and the remaining virtualization overheads prevent the guest from achieving near native performance for certain I/O intensive workloads.
Function Mac Address :0 :2a-2e-5a-05-0a-bc Here is the output of the vparstatus command related to the AVIO adapters of a single vPar: [IO Details] hba:avio_stor:0,0,0x50014C2000000002,0x50014C2800000002:npiv:/dev/fcd0 network:avio_lan:0,1,0xb28c71e0a57b:vswitch:sitelan:portid:2 NOTE: The CLI accepts either avio_lan or aviolan and either avio_stor or aviostor.
Changing the underlying backing storage of a vPar/VM is best done when the it is not running to avoid damaging it. If the change is to a running vPar/VM, the administrator is responsible for knowing that the change will not adversely affect the health of the running environment. Although HP-UX vPars and Integrity VM does check to determine if the device is in use, those checks are not 100% reliable, because the vPar/VM might or might not be using the device at the time it is checked.
• Running vPars/VMs with DIO as Serviceguard nodes • Support for HP-UX network providers NOTE: The direct I/O networking functionality is not currently supported with the HP Auto Port Aggregation (APA) product. For more information about using direct I/O networking, see “Using direct I/O networking” (page 158) 1.8 Running applications in vPars or Integrity VM environments The VSP is the manageability platform for vPars or VMs.
• HP-UX 11i V3 Virtual Server Operating Environment (VSE-OE) • Software installation tools (Ignite-UX and Software Distributor-UX) • System performance monitoring tools (GlancePlus, Measureware, OpenView Operations Agent) Applications do not have to be changed to run on a vPar/VM OS. Operating system patches and hardware restrictions apply to vPars.
of virtualization-related measurements. Note, Glance refers to virtual environments as logical systems. • Using HP Global Workload Manager (gWLM) If you use gWLM within Insight Dynamics — Matrix OE to manage virtual machines, when you upgrade the VSP, make sure the gWLM agent on that host is running gWLM A.07.01 or greater. Also, the managing Insight Dynamics — VSE Central Management Station (CMS) must be running A.07.00 or greater, as described in the HP Insight Dynamics —VSE 7.
the activation of the cores on the vPar v6.x guest OS. Similarly, for a deactivation operation, execute the vparmodify command on the vPar v6.1 guest OS and then execute a icapmodify command on the VSP OS. iCAP commands issued from the OA activate or deactivate cores only in the VSP. vparmodify commands have to be issued in the VSP to move the core to and from a vPar v6.1. If there is only one core in the VSP and the rest assigned to vPars a deactivation request from the OA will fail.
1.11 Related products Some of the HP products that you can use with vPars and Integrity VM include: • HP-UX operating system — HP-UX vPars and Integrity VM run on HP-UX 11i v3 Integrity systems on the VSP. V6.1 requires that the VSP be installed with the HP-UX 11i v3 March 2012 release. For more information, see the HP-UX 11i v3 Installation and Update Guide. • HP WBEM Services for HP-UX — Many related products, such as Virtual Server Manager and gWLM, require the VSP system be running HP WBEM Services.
Table 2 Integrity VM commands (continued) Command Description hpvmconsole(1M) Describes how to use the virtual machine console. hpvmcreate(1M) Describes how to create virtual machines. hpvmdevinfo(1M) Reports about storage for a virtual machine. hpvmdevmgmt(1M) Describes how to modify the way virtual devices are handled. hpvmdevtranslate(1M) Translates Integrity VM guest devices to agile devices. hpvmhostgdev(1M) Manages Integrity VSP devices available for virtual machine access.
Table 2 contains a summary of the VSP commands and descriptions of their use. The following sections provide brief information about each command. For more information about the commands, see the respective manpages. Table 3 VSP commands in vPars Command Description vparboot(1M) Boots a virtual partition. vparcreate(1M) Creates a new virtual partition. vparmodify(1M) Renames or modifies the resources of a virtual partition. It can also suspend the configuration of the virtual partition.
Table 4 Chapters in this Manual (continued) Chapter Read if... Chapter 7: “Creating virtual machines” (page 75) You are setting up new virtual machines on your VSP system. Chapter 8: “Installing the HP-UX guest operating system and software” (page 101) You are creating vPars and VMs that will run the HP-UX operating system. Chapter 9: “Creating virtual storage devices” (page 107) You need to make changes to the storage devices used by the VSP or virtual environments.
2 Installing and configuring VSP for HP-UX vPars and Integrity VM V6.1 Installation of the VSP is the same whether you want to run a vPars only environment or a VM only environment. The software bundles that need to be installed on the VSP are the same in either case. This chapter describes the following: • VSP installation requirements • Configuring the VSP • VSP cores • VSP memory • Hyperthreading setting on VSP • VSP I/O configuration • VSP kernel tunables 2.
not visible to HPUX commands in the VSP. In V6.1, all the non-VSP cores are visible to the VSP. When vPars are started, these cores are deallocated from the VSP. A single VSP core can service vPar management requests and moderate to heavy I/O loads. When the VSP core becomes saturated, the response time of vPar commands and other applications being run on the VSP might increase.
The Integrity VM product, on startup, reserves a significant portion of the free system memory available on the VSP for the vPar/VM memory pool. The memory left as available in the VSP is sufficient for the optimal functioning of the vPars and Integrity VM product functionality and features on the VSP. Typically, about 92% of free memory available at the Integrity VM product start time (after HP-UX has booted up on the VSP) is reserved for the vPar/VM memory pool.
In addition to the VSP memory overhead, individual vPars and VMs have a memory overhead depending on their size. A rough estimation of the individual guest memory overhead can be done using the following formula: Guest memory overhead = cpu_count * (guest_mem * 0.4% + 64M) Where: guest_mem is the guest (vPar/VM) memory size cpu_count is 1 for vPar and num_vcpus for VM. (Memory overhead in a vPar is independent of number of cpus in a vPar) . For example, a 16G 4vCPU VM, the overhead is roughly about 512M.
For AVIO, HP strongly recommends that you use the same AVIO components from the same release on both the VSP and vPar/VMs, for example, both from the OE or both from the same Web Release (for example, WEB1103). The AVIO network VSP driver allows simultaneous access to a vswitch from vPar/VMs configured with or without AVIO vPar/VM drivers for their virtual network interface cards (vNICs). Existing vPar/VMs continue to operate correctly, and their configurations remain unchanged.
3 Installation procedures for HP-UX vPars and Integrity VM V6.1 This chapter describes the requirements and procedures for installing vPars and Integrity VM V6.1. The topics include: • Installing vPars and Integrity VM V6.1 • Bundle names • Verifying the installation • Removing vPars and Integrity VM V6.1 3.1 Installing vPars and Integrity VM V6.1 The following sections provide the installation procedures for vPars and Integrity VM V6.1. 3.1.1 vPars V6.1 installation requirements vPars V6.
3.1.2 Installing vPars V6.1 vPars V6.1 may be packaged in a software depot and installed in the VSP using the swinstall command. The minimum OE version for the VSP is HP-UX 11i v3 March 2012 (AR1203). The minimum OE version for a vPar is HP-UX 11i v3 September 2011 (AR1109) on HP Integrity Server Blade system BL8x0c i2 servers and HP-UX 11i v3 March 2012 (AR1203) on HP Integrity Superdome 2 servers.
7. If the vPar is using HP-UX 11i v3 September 2011, install VirtualBase on the vPar from the DVD: swinstall –x autoreboot=true –s VirtualBase NOTE: VirtualBase is installed by default with HP-UX 11i v3 March 2012. 3.1.3 Integrity VM installation requirements To prepare your VSP system for Integrity VM installation, your configuration must satisfy the hardware, software, and network requirements described in this section.
Table 7 Requirements for installing Integrity VM V6.1 (continued) Resource Description Memory For information about memory overhead estimation, see “VSP memory overhead estimation” (page 31). Network configuration A configured and operational network. To allow guests network access, the VSP must have at least one functioning network interface card (NIC). For more information about configuring network devices for virtual machines, see Chapter 10 (page 143).
• The VirtualBase software is installed in the /opt/hpvm/guest-images directory. • The Integrity VM software and data files are installed in the /var/opt/hpvm directory. • The Integrity VM commands are installed in the /opt/hpvm/bin directory. You can now create virtual machines using the hpvmcreate command, as described in Chapter 7 (page 75). Integrity VM installation modifies certain kernel parameters.
3.4 Verifying the installation of vPars and Integrity VM To verify that Integrity VM installed successfully, enter the following command: # hpvminfo hpvminfo: Running on an HPVSP. To see exactly what versions of specific bundles are installed, enter the swlist command and look for the following bundles: BB068AA B.06.10 HP-UX vPars & Integrity VM v6 GUIDMGR A.01.00.579 HP-UX GUID Manager VirtualBase B.06.
You can ignore these messages. 3.7.2 Warning during startup if HP SIM is installed Integrity VM generates a warning during startup if HP SIM is installed, but Integrity VM continues to start. The HP SIM product consumes memory and CPU resources that would otherwise be available for running virtual machines. The amount of memory and CPU consumed varies depending on the specific system configuration.
4 Upgrading the VSP from previous versions of Integrity VM This chapter describes how to upgrade the VSP from an older version. The chapter topics include: • Upgrading the VSP from previous version of Integrity VM V3.x to V6.1 • Updating previous versions of the VSP 4.1 Upgrading the VSP from previous versions of Integrity VM V3.x to Integrity VM V6.1 The Integrity VM Version 6.1 VSP requires the HP-UX 11i v3 operating system. Only HP-UX 11i v2 servers running Integrity VM Version 3.0 or Version 3.
Figure 3 Upgrade Procedure 1. Study current 11i v2 to 11i v3 upgrade documentation. 2. Analyze the HP-UX 11i v2 based Integrity VM server using tools. Decide whether 3. to perform a cold install or update_ux. 4. Update hardware requiring new firmware or replace obsolete adapters. 5. Final check - assure all guests boot and then backup both server and guests. ...cold install Perform 6. cold install or update_ux. update_ux... 7.
The first thing the administrator must do is to identify subsystems on the 11i v2 Integrity VM server that are incompatible with or that are not supported on 11i v3. Some incompatibility issues can be exposed by tools, and others are found in referenced documents. The most common update problems are caused by the following: • Unsupported hardware adapters or firmware • Memory and system disk space requirements (HP-UX 11i v3 has increased both of these.
The msv2v3check tool is free software provided on the http://software.hp.com website. Go to this website, search for msv2v3check, and download this free tool. These analysis utilities are aimed primarily at mass storage problems and problems that are specific to existing virtual machines. In most cases, you can take actions to resolve these incompatibilities before doing the upgrade, such as loading new firmware.
4.1.2.2 Determine HP-UX 11i v3 memory and system disk requirements Integrity VM V6.1 memory requirements vary depending on the number and size of virtual machines supported by the Integrity VM server. When upgrading from an 11i v2 Integrity VM server, use the following steps to determine the amount of memory required for the 11i v3 Integrity VM server: 1. When your 11i v2 Integrity VM server is running at peak load, use the Integrity VM hpvmstatus –s command to display the available memory. 2.
UNIX offering. The DC-OE includes HP-UX vPars and Integrity VM (BB068AA) and the VirtualBase bundle. • HP-UX 11i High Availability OE (HA-OE) For customers requiring continuous access to data and applications, the HA-OE delivers the protection of Serviceguard and related software. The HA-OE also delivers all the software in the Base OE plus what has shipped until now in the Enterprise OE. Table 8 lists the HP-UX 11i v2 to HP-UX 11i v3 supported OE server upgrades.
If you have installed the evaluation version of Integrity VM (software bundle T2801AA), remove the evaluation software before installing the Integrity VM product (see Section 3.5 (page 40)). 4.1.4 Perform required hardware and firmware upgrades Perform all hardware and firmware upgrades that are supported on 11i v2 and that are needed for 11i v3 while still running on 11i v2. This allows the administrator to verify that all guests are fully functional with the changes before upgrading to 11i v3.
11. Determine the order of installation of layered products, including vPars and Integrity VM V6.1 (BB068AA), so that all dependencies are met. For example, if Veritas is used to provide backing storage for guests, install it before Integrity VM. 12. Install all 11i v3 compatible layered products that are required for equivalent functionality to the 11i v2 VSP. 13. Install Integrity VM Version 6.1 to the 11i v3 VSP. NOTE: See Section 3.
4.1.6 Verifying vPars/VM after installing layered products Follow these steps after installing layered products: 1. Start and stop each guest, one at a time, and make sure that they boot to their OS. 2. Use the guest troubleshooting section, Chapter 13 (page 215), to resolve guest booting problems. 3. Upgrade each guest with the new guest kit. 4. Make sure there are no network issues 5. If the guest OS is no longer supported, upgrade the guest OS.
NOTE: Installing the vPars and Integrity VM software requires the system to reboot. Therefore, the swinstall command line installation includes the autoreboot=true parameter. To install the HP Integrity VM software, follow these steps: 1. If you have the installation media, mount it. If you are installing from the network, identify the VSP and path name that correspond to the software distribution depot that contains the BB068AA bundle (for example, my.server.foo.com:/depot/path). 2.
5 Using NPIV with vPars and Integrity VM NPIV allows creation of multiple virtual Fibre Channel ports (VFCs) over one physical port (PFC) on a Virtualization Services Platform (VSP). The VSP serves as the management platform for the vPars and virtual machines. Each of these virtual ports should be created with a unique World Wide Name (WWN) to identify it, just like the unique embedded WWN by which a physical port is identified.
Table 9 NPIV supported limits in vPars and Integrity VM V6.
If NPIV is supported, running the command again with the new npiv_info option provides information about all of the running virtual HBAs currently associated with this physical HBA: # /opt/fcms/bin/fcmsutil /dev/fcd0 npiv_info PFC Hardware Path = 0/0/0/5/0/0/0 PFC DSF = /dev/fcd0 PFC Class Instance = 0 PFC Driver state = ONLINE PFC Port WWN = 0x5001438001459910 PFC Node WWN = 0x5001438001459911 PFC Switch Port WWN = 0x201400051ef06bd3 PFC Switch Node WWN = 0x100000051ef06bd3 FlexFC Virtual Fibre Channel (VF
vWWP A valid (64 bit), unique (virtual) Port WWN that is assigned to the NPIV HBA. This is analogous to the unique Port WWN that is associated with physical HBAs. vWWN A valid (64 bit), unique (virtual) Node WWN that is assigned to the NPIV HBA. This is analogous to the unique Node WWN that is associated with physical HBAs. storage The physical storage type in the host. For NPIV, this is npiv. device The physical device in the host corresponding to the virtual device.
Example 3 Finding out if WWNs are supported # ioscan -kfNC fc Class I H/W Path Driver S/W State H/W Type Description =================================================================== fc 0 0/2/0/0/0/0 fcd CLAIMED INTERFACE HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter (FC Port 1) fc 1 0/2/0/0/0/1 fcd CLAIMED INTERFACE HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter (FC Port 2) # fcmsutil /dev/fcd0 Vendor ID is Device ID is PCI Sub-system Vendor ID is PCI Sub-system ID is PCI Mode ISP Code version I
Example 4 Deleting an NPIV resource vparmodify -P vPar1 -d hba:avio_stor:,,0x50060b00006499b9, 0x50060b00006499ba:npiv:/dev/fcd1 For the relevant vPar, you can use this syntax by copying it from the I/O details of the vparstatus command output and pasting it where required. For more information about NPIV, see the white paper, HP-UX vPars 6.0 & 6.1 and Integrity VM 4.3 & 6.1 N_Port ID Virtualization (NPIV), on the BSC website.
6 Creating virtual partitions To create virtual partitions, you must run appropriate commands from the VSP or use the HP-UX Integrity Virtual Server Manager, the GUI application that can be accessed from the Tools page in HP SMH of the VSP. This chapter discusses the various tasks that can be performed from the VSP using commands. For tasks you can perform using the GUI, see the HP-UX Integrity Virtual Server Manager Help that comes with the GUI application. CAUTION: In V6.
Table 10 Attributes of a virtual partition in vPars V6.1 vPar attribute Description vPar ID (name or number) You can specify either a number -p vpar_id or name. If you do not specify either a number or a name, a vPar name in the format vParXXXX (where XXXX represents the vPar Id number), with leading zeros is automatically assigned to the newly created vPar.
Table 10 Attributes of a virtual partition in vPars V6.1 (continued) vPar attribute Description Command option I/O (virtual devices) You can allocate virtual network -a rsrc switches and virtual storage devices to the virtual partition. The VSP presents devices to the virtual partition as virtual devices. Default value If you leave out this option when you create a vPar, the vPar will not have access to network and storage devices. The vPar network consists of vNICs and vswitches.
Table 10 Attributes of a virtual partition in vPars V6.1 (continued) vPar attribute 62 Description Command option Default value Group with If you omit this option, group -g group:{admin|oper} administrator or accounts will not have admin or operator privileges oper privileges. If you do not specify the group authorization, then only the root user has access to the virtual console.
Example 5 Create a default virtual partition Run the vparcreate command to create a basic virtual partition with the default values of 1 CPU, 2 GB memory, and no I/O. Later, use the vparmodify command to add I/O and modify other attributes. # vparcreate [Creating vPar0001.
For additional information about configuring NPIV, see the vparresources3(5) manpage and the relevant NPIV sections in this guide. 6.1.
the vparconsole command to start, and enter the console in interactive mode right after the start. Example 10 Boot the virtual partition called Oslo vparboot -p Oslo OR vparconsole -P Oslo -fic 'pc -on' 6.3 Modifying a virtual partition You can modify all the attributes that you specify while creating a vPar. You can rename the vPar, modify the resources, and change group and user level authorization.
By default, the vparstatus command displays summary information. To view detailed information you must use the -v option. You can also view the vPar information in machine-readable format using the -M option. The information that the vparstatus command (and hpvmstatus command) displays includes the following: • Number and name of the vPar. • State of the vPar – active or inactive. • Run-state of the active or inactive vPar. • Summary of CPU, I/O, and memory resource allocations.
vparreset -f -p Oslo -d IMPORTANT: In the case of both hard reset and power-off, the operating system of the vPar is abruptly shut down and the crash dump of the OS is not saved. HP recommends shutting down the vPar from the vPar using the shutdown command. Soft reset (transfer of control - TOC) When you do not specify any option with the vparreset command, a soft reset is performed by default. In a soft reset, the crash dump of the OS running on the vPar is saved.
NOTE: To modify netconf, you might have to mount all the file systems using the mountall command to be able to access the editor that is required to modify the netconf file. To avoid the long boot time, boot to single user mode and modify the netconf file with the new LAN instance number. NOTE: With portable image support in HP-UX 11i v3 March 2012, this constraint does not exist any more. See the usage of kctune gio_portable_image in the Portable Image documentation on the BSC website, 6.
Available VSP memory = 884 Mbytes Available swap space = 7032 Mbytes Total memory allocated for vPars and VMs = 12544 Mbytes Memory in use by vPars and VMs = 13568 Mbytes Available memory for vPars or VMs is overdrawn by 1024 Mbytes Available memory for 0 (max avail.) CPU VM = N/A Mbytes Available memory for 0 (max avail.
NOTE: Before using the Ignite-UX server approach, ensure the following: • The vPar is created and assigned a network interface. • At least one disk has been added to the vPar with sufficient space to install HP-UX 11i on it. • The Ignite-UX server is set up and accessible from the LAN interface assigned to the vPar. To install HP-UX 11i on a vPar using an Ignite-UX server: 1. 2. Boot the vPar to EFI.
Example 12 Using vparstatus to determine the WWN of an NPIV HBA vparstatus -P Vpar1 -d [Virtual Partition Devices] [Storage Interface Details] disk:avio_stor:0,0,0:avio_stor:/dev/rdisk/disk31 disk:avio_stor:0,0,1:lv:/dev/vg_on_host/rlvol3 hba:avio_stor:0,4,0x50060b00006499b9,0x50060b00006499ba:npiv:/dev/fcd1 hba:avio_stor:1,3,0x50060b00006499a0,0x50060b00006499a8:npiv:/dev/fcd0 [Network Interface Details] network:lan:0,1,0xF2AF8F8647BF:vswitch:vswitch1:portid:1 network:lan:0,5,0x569FC1F96205:vswitch:vswitch
configuration on a per vPar basis. The -x active_config=false option must be used with either the vparcreate or the vparmodify command. You can deactivate a vPar configuration only if the vPar is in the inactive state, that is, the run-state must be DOWN. To deactivate a single vPar configuration, the vparmodify command must be used with the -x active_config=false option.
6.12 Recovering a nonresponsive vPar In the rare event that the OS of a vPar becomes nonresponsive, there is no prompt from a network connection nor through the virtual console (vparconsole). In such a situation, you may need to manually reset the partition. To recover a vPar that is nonresponsive, you can use the vparreset command. To recover a nonresponsive vPar, use the vparreset -g command. This results in a graceful shutdown of the OS. The vPar can then be restarted.
7 Creating virtual machines After you install the vPars and Integrity VM product, you can create virtual machines and virtual resources for the virtual machines to use. This chapter includes the following topics: • Specifying VM characteristics • Using the hpvmcreate command • Starting VMs • Changing VMs configurations • Cloning VMs • Stopping VMs • Removing VMs • Troubleshooting virtual machine creation problems 7.
Table 11 Characteristics of an VM (continued) Virtual Machine Characteristic Default Setting Command Option Where Described Virtual devices If you omit this option when -a rsrc you create the virtual machine, it has access to no network and storage devices. Section 7.1.10 (page 80) Virtual machine label If you omit this option, the virtual machine has no label. -lvm_label Section 7.1.
7.1.3 Guest operating system type Use the -O os_type option to specify the type of operating system that will run on the virtual machine. This option is not required. For os_type, specify hpux. For specific information about installing HP-UX guests, see Chapter 8 (page 101). If you do not supply the operating system type, it defaults to UNKNOWN. When you install the operating system and boot the guest, this guest configuration parameter is automatically set to the appropriate operating system type.
num, and disables the others. Disabled virtual CPUs no longer show up in the guest in commands such as top or GlancePlus, and no longer consume resources on the VSP. However, disabled virtual CPUs still appear on the VSP, for example in the hpvmsar command. 7.1.6 Entitlement Use the -e or -E option to specify the virtual machine's entitlement. Virtual machine entitlement is the minimum amount of processing power guaranteed to the virtual machine from each virtual CPU.
operating system and its administrative functions. For more information about the memory requirements of the VSP, see Section 3.1.3 (page 37). Guest memory allocation can be viewed and allocated dynamically (that is, without stopping the guest) by using dynamic memory parameters, as described in Section 11.9 (page 180). 7.1.8 Automatic cell balancing When creating a guest, Integrity VM determines the best fitting locality domain for the new guest when the VSP is predominantly Cell Local Memory(CLM).
CPU cores currently in use or reserved for later use = 0 Available VSP memory = 884 Mbytes Available swap space = 7032 Mbytes Total memory allocated for vPars and VMs = 12544 Mbytes Memory in use by vPars and VMs = 13568 Mbytes Available memory for vPars or VMs is overdrawn by 1024 Mbytes Available memory for 0 (max avail.) CPU VM = N/A Mbytes Available memory for 0 (max avail.
Traffic from an AVIO guest LAN network device is directed to the pNIC directly by a separate host module rather than by the vswitch. You can create vswitches before or after creating guests that access the vswitches. If you create the virtual machine before creating the vswitch, the virtual machine is created and warning messages display the specific problem. This allows you to create virtual machines for future configurations. To create a vswitch, enter the hpvmnet -c command.
• VM-guest-storage-specification defines where and what storage is seen in the virtual machine. This is formatted as: device:adapter-type:hardware-address: You can specify one of the following devices: ◦ disk ◦ dvd ◦ tape ◦ changer ◦ burner ◦ hba • adapter-type is avio_stor on an HP-UX guest. • hardware-address or pcibus, pcislot,aviotgt (optional) specifies the virtual device PCI bus number, PCI slot number, and AVIO target number.
the following command modifies the virtual machine named host1, adding a virtual DVD device backed by the physical disk device /c1t1d2. The virtual hardware address is omitted and will be generated automatically. # hpvmmodify -P host1 -a dvd:avio_stor::disk:/dev/rdisk/disk2 You can modify storage devices while the virtual machine is running. It is not necessary to restart the virtual machine; however, it may be necessary to re-scan for devices on the virtual machine.
A rough estimate of the processor weight calculation is: (minimum guest cpu entitlement * number of virtual processors) / (100 * number of host processors) Guests are expected to start in order of highest weight to lowest. You can adjust the order by setting the sched_preference attribute (Section 3.2.6). If a guest fails to start for any reason, the sequence continues with the next guest.
Table 12 Configuration Limits (continued) Description Support # virtual switches — Maximum 50 # virtual NICs / vswitch 511 # file backing store devices / VM or vPar — Maximum 30 # virtual AVIO storage devices /VM Maximum 256 # file backing store devices /VM Maximum 30 Maximum size of backing store for AVIO (disk, lvol, file) > 2TB Maximum # PCI functions per vParVM for DIO 16 7.1.15 Sizing guidelines The sizing guidelines for Integrity Virtual Machines Version 4.
v3 Installation and Update Guide warns that cold installations with 1 GB or less memory might fail or take a long time to complete. Therefore, 2 GB is recommended for cold installations of HP-UX 11i v3. NOTE: The amount of memory you should allocate to the guest must be sufficient to allow the guest operating system to boot. This amount might differ from the defaults documented here. For specific memory requirements, see the product documentation for the operating system and applications on the guest. 7.
Table 14 Options to the hpvmcreate Command (continued) Option -x keyword=parameter Description Specifies values for dynamic memory setting associated with the guest, including: • dynamic_memory_control • ram_dyn_type • ram_dyn_min • ram_dyn_max • ram_dyn_target_start • ram_dyn_entitlement=amount • amr_enable={0|1} • amr_chunk_size=amount • sched_preference • graceful_stop_timeout For more information about dynamic memory, see Section 11.9 (page 180).
Table 14 Options to the hpvmcreate Command (continued) Option Description Specifies whether the virtual machine is managed by Serviceguard or gWLM (or both). For the argument, specify one or more of the following parameters: -i package-name • SG indicates that the VSP is a Serviceguard cluster node. • SG-pkgname indicates that the VSP is a Serviceguard package. • GWLM indicates that the VSP is managed by gWLM. • NONE indicates there are no external managers.
Table 15 Options to the hpvmstart Command Option Description -P vm-name Specifies the name of the virtual machine. Specify either the -P option or the -p option. -p vm_number Specifies the number of the virtual machine. To determine the virtual machine number, enter the hpvmstatus command. -F Suppresses all resource conflict checks and associated warning messages (force mode). Use force mode for troubleshooting purposes only.
NOTE: When configuring or starting Integrity VM guests, the following warning message might be displayed if storage associated with the guest appears to be performing very poorly. hpvmcreate: WARNING (host): Device /dev/rdisk/c6t9d0 took 32 seconds to open. 7.4 Changing virtual machine configurations You can create a virtual machine with characteristics that the VSP cannot supply at the time of creation. This allows you to create virtual machines to run after system configuration changes.
Table 16 Options to the hpvmmodify Command Option Description -P vm-name Specifies the name of the virtual machine. You must specify either the -P option or the -p option.. -p vm_number Specifies the number of the virtual machine. To determine the virtual machine number, enter the hpvmstatus command. -F Suppresses all resource conflict checks and associated warning messages (force mode). Use force mode for troubleshooting purposes only.
Table 16 Options to the hpvmmodify Command (continued) Option Description -a rsrc Adds a virtual storage or network device to the virtual machine. For more information, see hpvmresources(5). -m rsrc Modifies an existing I/O resource for a virtual machine. The resource is specified as described below. You must specify the hardware address of the device to modify. The physical device portion of the rsrc specifies a new physical device that replaces the one in use. -d rsrc Deletes a virtual resource.
Table 16 Options to the hpvmmodify Command (continued) Option Description -j [0|1] Specifies whether the virtual machine is a distributed guest (that is, managed by Serviceguard) and can be failed over to another cluster member running Integrity VM. Do not specify this option. This option is used internally by Integrity VM.
locked PAL RAM: 00000000ffaa4000 (4KB) locked Min Save State: 00000000ffaa5000 (1KB) RAM alignment: 40000000 Memory base low : 6000000100000000 Memory base FW : 6000000140000000 Loading boot image Image initial IP=102000 GP=62C000 Initialize guest memory mapping tables Starting event polling thread Starting thread initialization Daemonizing.... hpvmstart: Successful start initiation of guest 'host1' The virtual machine host1 is started. Now the guest operating system must be installed.
Table 17 Options to the hpvmclone Command (continued) Option Description -e percent[:max_percent] | -E cycles[:max_cycles] Specifies the virtual machine's CPU entitlement in CPU cycles. To specify the percentage of CPU power, enter the following option: -e percent[:max_percent] To specify the clock cycles, enter one of the following options: -E cycles[:max_cycles]M (for megahertz) -E cycles[:max_cycles]G (for gigahertz) -l vm_label Specifies a descriptive label for this virtual machine.
Table 17 Options to the hpvmclone Command (continued) Option Description -r amount Specifies the amount of memory available to this virtual machine. Specify the amount as either amountM (for megabtyes) or amountG (for gigabytes). -S amount 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.
host1 host2 host3 2 HPUX On (OS) 3 UNKNOWN Off 4 HPUX Off 1 1 1 1 1 1 1 1 1 2 GB 1 GB 2 GB 0 0 0 You can create a clone of host3 by entering the following command.
Table 18 Options to the hpvmstop Command (continued) Option Description -g Performs a graceful shutdown on the virtual machine. -F Forces the command to act without requiring confirmation. NOTE: The -F option is deprecated in Integrity VM commands; this option should be used only at the direction of HP Support. -Q Performs the operation without requiring you to confirm the command. -q Makes certain scripted operations less verbose (quiet mode).
7.7 Removing virtual machines To remove a virtual machine from the VSP, use the hpvmremove command. By default, you are required to confirm this action. Table 19 describes the options to the hpvmremove command. Table 19 Options to the hpvmremove Command Option Description -P vm-name Specifies the name of the virtual machine. You must include either the —P or —p option. -p vm_number Specifies the number of the virtual machine. To display the virtual machine number, enter the hpvmstatus command.
1. 2. 3. Verify that the path name to the file-backing store is correct and that the physical storage device is mounted. Verify that the size of the physical storage device is divisible by 512 bytes (for a disk device) or 2048 (for a DVD device). Modify the virtual machine using the hpvmmodify command.
8 Installing the HP-UX guest operating system and software To create HP-UX guests, install the HP-UX operating system on the vpar or virtual machine. To install the HP-UX guest operating system, follow the procedures in the following sections: • Installing the HP-UX guest operating system • Installing the HP-UX vPar/VM VirtualBase software • Troubleshooting HP-UX guest creation NOTE: The following topics apply to both vPars and Integrity VM. 8.
CO: CM: CL: SL: VM: HE: X: Console Command Menu Console Log Show Event Logs Virtual Machine Menu Main Help Menu Exit Connection [host1] vMP> The hpvmconsole command opens the virtual machine console. From the virtual console, you can control the virtual machine just as if it were a physical Integrity server. 3. In response to the virtual machine prompt, enter the co command: [host1] vMP> co EFI Boot Manager ver 1.10 [14.
Save changes to NVRAM [Y-Yes N-No]: 6. Y Exit the EFI Boot Maintenance Management screen to return to the EFI Boot Manager screen. Boot from the new boot entry, indicated by the virtual machine's MAC address:. EFI Boot Maintenance Manager ver 1.10 [14.62] Add a Boot Option.
# Contacting target "foo"... ERROR: Software "BB068AA" was not found on host "foo:/". ERROR: Software "VirtualBase" was not found on host "foo:/". For more information about using Ignite-UX golden images, see the Ignite-UX Administration Guide. 8.3 Installing VirtualBase on a vPar/VM After you install the guest OS, you might need to install or update VirtualBase on the vPar/VM .
NOTE: If you receive the following messages during boot or reboot of a vPars or VM, you can safely ignore them: montecito_proc_features: PROC_GET_FEATURES returned 0xfffffffffffffff8 CPU00 failed to synchronize its interval timer with CPU03 within 46 Ticks CPU00 failed to synchronize its interval timer with CPU04 within 46 Ticks CPU00 failed to synchronize its interval timer with CPU06 within 46 Ticks CPU00 failed to synchronize its interval timer with CPU07 within 46 Ticks CPU00 failed to synchronize its i
9 Creating virtual storage devices This chapter describes what vPars and Integrity VM V6.1 storage is, how to configure it, and how to use it. The topics included in this chapter are: • Introduction to vPar/VM storage • Configuring vPar/VM storage • Using vPar/VM storage NOTE: The information in this chapter also applies to vPars, as well as VMs. 9.1 Introduction to vParVM storage The way you configure and manage vPar/VM storage affects the way virtual machines perform.
and tuning operating systems for the virtual platform. At the same time, vPars and Integrity VM V6.1 provides more virtualization choices to VSP administrators, so that they can find the best balance between virtualization and performance to meet their needs. 9.1.1.4 Storage security To avoid problems while supporting multiple vPars/VMs on one physical machine, vPars and Integrity VM V6.1 isolates each virtual machine and virtual partition.
9.1.2.2 Attached I/O Attached I/O allows a vPar/VM to access to a VSP LUN directly. In this architecture, the vPar/VM storage subsystem attaches a LUN on the VSP 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.
To find the lunpath hardware path of a device, see Section 6.1.3.2. Once the lunpath hardware path is obtained, use the hpvmmodify command to add the tape to a guest. For example, use the following command to assign the second lunpath to guest1: # hpvmmodify -P guest1 -a tape:avio_stor::attach_path:0/7/1/1.0x500104f00048b29e.0x0 The following examples add, delete, and modify attached devices: Add # hpvmmodify -P guest1 -a tape:avio_stor:0,5,0:attach_path:0/1/1/0.0x50060b0000332254.
====================================================================== tape 5 64000/0xfa00/0x1 estape CLAIMED DEVICE online 0/5/0/0/0/0.0x500110a0008b9de2.0x0 /dev/rtape/tape5_BEST /dev/rtape/tape5_BESTn /dev/rtape/tape5_BESTb /dev/rtape/tape5_BESTnb HP # ioscan -m lun /dev/rtape/tape6_BEST Class I Lun H/W Path Driver S/W State H/W Type Health Description ====================================================================== tape 6 64000/0xfa00/0x3 estape CLAIMED DEVICE online STK 0/4/1/0.
/dev/rtape/tape6_BESTn:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=YES: lunpath3,lunpath6,lunpath5,lunpath4:0x01.0x00.0x03.0x500104f0004732d8 9.1.3.4 Mapping AVIO storage devices on HP-UX guests This section explains how to map an AVIO storage device on an HP-UX guest to an hpvmstatus display on the Integrity VSP either at the EFI console or at the HP-UX operating system.
disk | |(Addr(Target Id) % 16) <-> HP-UX tgt ID PciBus | | |(Addr(Target Id) / 16) <-> HP-UX lun ID | | | | | V V V V V 49 0/0/2/0.6.
Table 20 Patch Dependencies for AVIO Attached Devices Patch Number HP-UX Version VSP Guest Notes PHKL_38604 11i v3 Yes Yes Hard1 dependency for guest, and soft2 dependency for VSP. PHKL_38605 11i v3 Yes No Soft dependency on VSP. PHKL_38750 11i v3 Yes Yes Recommended patch. 1 Enforced during swinstall. 2 Required only if attached devices are configured. No enforcement using swinstall. 9.1.3.
multiple devices at a time takes less time than adding them one at a time, with one device per call to hpvmcreate and then one device per call in subsequent calls to hpvmmodify. You can add any number of devices at a time up to the supported limit. However, you might find that adding multiple devices at a time per call to hpvmmodify not only takes less time than adding all of them at once, but also using one particular number of devices at a time provides better hpvmmodify performance than others.
9.2 Configuring vPar/VM storage This section describes how to plan and set up vPar/VM storage, including the following topics: • Storage considerations • Setting up virtual storage 9.2.1 Storage considerations When you configure storage for a vPar/VM, consider the following: • Storage supportability • Storage performance • Storage multipath solutions • Storage management • Storage changes • Virtual storage setup time The following sections explain each of these considerations. 9.2.1.
Figure 5 Storage I/O Stack Virtual File Disk File Systems Layer Virtual LvDisk Logical Volume Managers Layer Virtual Disk Attached Devices Disk Drivers Layer Integrity Vm Passthrough Drivers Layer VSP 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 storage adapter and th
help ensure the best performance by understanding the impact of the physical storage and the way I/O accesses it. It is important to know exactly where the virtual media is located on physical storage devices. With vPars and Integrity VM V6.1, 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.
to the virtual media are properly emulated as media errors sent to the guest OS, not as path failures. • The VSP does not return specific errors to Integrity VM for hardware path failures. vPars and Integrity VM does not detect such events and does not pass them to the vPar/VM. For supported multipathing configurations, see the HP-UX vPars and Integrity VM V6.1 Release Notes at http://www.hp.com/go/hpux-hpvm-docs. 9.2.1.
Figure 8 Bad Multipath Virtual Media Allocation Physical Adapter Physical Adapter Physical Storage /dev/rdsk/c6t2d1 /dev/rdsk/c11t2d1 Also, the same storage resource, virtual or attached, cannot be simultaneously shared between virtual machines, unless otherwise specifically exempted. Figure 9 shows a Virtual LvDisk being shared across virtual machines, which is not supported.
9.2.1.5 VM storage changes Depending on how you set up storage for a vPar/VM, the resulting configuration can be more or less difficult to change. The ability to change virtual media depends on the type of virtual media used. Whole disks are not normally adjustable in terms of size, but some high-end storage enclosures might permit the adjustment of a LUN without losing that LUN's data. Logical volumes are adjustable without losing any data.
The following is an outline of a complete resource statement for specifying a virtual storage device: VM-guest-storage-specification:VM-Host-storage-specification where: • VM-guest-storage-specification defines where and what storage is seen in the vPar/VM (see Section 9.2.2.1 (page 122)) • VM-Host-storage-specification defines where and how the vPar/VM storage is supplied on the VSP (see Section 9.2.2.2 (page 122)) For examples of how to construct resource statements, see Section 9.2.2.3 (page 123).
• storage is one of the following: disk, lv, file, null, attach, or npiv. The selection of storage type defines what VSP system files apply. For example, lv implies the use of logical volume character device files. For virtual devices, the selection of VSP storage determines what type of virtual media the virtual device uses. For example, the selection of lv for a virtual disk, makes it a Virtual LvDisk to the VM. It does not support the attach storage type.
All multipath products for storage resources must run on the VSP; multipath solutions are not supported in a vPar/VM. All multipath solutions used on the VSP must be in valid supported configurations before being used for vPar/VM storage resources (see Section 9.2.1.3 (page 118)). The resource statements in the following subsections do not contain vPar/VM hardware addressing. The PCI bus, PCI slot, and AVIO target numbers are optional. 9.2.2.3.
to prevent media conflicts. For information about tracking virtual media allocation, see Section 9.2.1.4 (page 119). If you are using LVM, the Virtual LvDisk resource statement takes the following form: disk:avio_stor::lv:/dev/vg_name/rlvol_name Where /dev/vg_name/rlvol_name is an LVM character device file for rlvol_name on vg_name.
In this example, the Virtual LvDisk resource statement is disk:avio_stor::lv:/dev/lvrackA/rdisk2. To use VxVM, the Virtual LvDisk resource statement takes the following form: disk:avio_stor::lv:/dev/vx/rdisk/dg_name/v_name where /dev/vx/rdisk/dg_name/v_name is a VxVM character device file for volume v_name on disk group dg_name.
The Virtual FileDisk resource statement takes the following form: disk:avio_stor::file:/pathname/file where the /pathname/file specifies the VSP file used as virtual media. A VxFS file system can be created on top of a whole disk or logical volume. For files over 2 GB, VxFS requires the file system be marked with a largefiles option. The mkfs command can be used to create the VxFS file systems directly. Once the file systems are created, mount can be used to mount them onto the VSP file system.
In this example, the Virtual DVD resource statement is dvd:avio_stor::disk:/dev/rdisk/disk7. For a vPar/VM to recognize a Virtual DVD, physical media must be present inside the VSP CD/DVD drive. If media is not added at vPar/VM start time, it can be inserted into the VSP CD/DVD drive after the vPar/VM is already up. A rescan by the guest OS picks up the new media and adds the Virtual DVD to the vPar/VM.
A Virtual FileDVD reverts to its original resource statement when the guest shuts down or reboots. Therefore, after you install a guest from multiple CDs or DVDs, you must reload the Virtual FileDVD when the guest reboots to complete the installation. Stop the automatic EFI reboot and insert the CD/DVD using the appropriate IN and EJ commands. When the media is loaded, proceed with the installation.
files to use from the virtual console. The file directory must be a locally mounted VxFS file system. NFS file systems are not supported. If the ISO files are world writable, they are not available from the virtual console. For the following ISO files: # 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 Jul 11 :59 0505-FOE.iso 4285267968 Jul 11 17:05 0512-FOE.iso 3149987840 Jul 11 18:42 0603-FOE-D1.
# ioscan -Nfun The following is an example of a claimed tape device: tape 1 64000/0xfa00/0x19 estape CLAIMED DEVICE /dev/rtape/tape1_BEST /dev/rtape/tape1_BESTn /dev/rtape/BESTb /dev/rtape/tape1_BESTnb HP Ultrium 1-SCSI If the device is not seen in ioscan -fun, proceed to step 2c. Otherwise, go to step 3. c.
Because tapes, media changers, and CD/DVD burners are not virtualized, media changes with them must be done physically. Therefore, all media changes with attached devices must be done by individuals with access to that physical storage. Changes to attached devices might require the device to be unlocked from an active guest OS. Attached devices remain in the last lock state the guest OS put it in when the device is detached or the virtual machine is shut down. Empty devices are attached and are not locked.
◦ Logical Server Manager (LSM) 6.2 ◦ HP Infrastructure Orchestration (HPIO) 6.2 ◦ HP Insight Software 6.2 When creating NFS-mounted backing-store files, HP recommends that you create these files locally on the NFS server, if possible. You can use either the hpvmdevmgmt command, if available on the NFS server, or the dd command.
9.3.1.2 Creating vPar/VM administrator and operator accounts In prior versions of Integrity VM, admin console access is available, and one such account per guest is allowed. The administrator account name must match the guest name. The new version of vPars and Integrity VM provides proper access controls and individual accountability for these accounts. A captive virtual console account is a special-purpose user account created on the VSP for each guest administrator.
> testme4 # hpvmmodify -P testme -u testme4 # passwd testme4 Note the addition of the slash and period (/.) to the end of the argument to the -d option, which ensures there is no confusion with HP-UX shared home directories. 9.3.1.3 Guest administrator The vPar/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 VSP administrator to control the vPar/VM.
NOTE: When a DVD without a disk in the drive is added to a guest, specify the backing store type of null, for example: # hpvmmodify -P guest -a dvd:avio_stor::null:/dev/rdisk/disk# Run ioscan on the booted guest if the guest if running HP-UX. If an empty DVD drive is given the backing store type disk, the following example shows the result: # hpvmmodify -P testguest -a dvd:avio_stor::disk:/dev/rdisk/disk31 hpvmmodify: WARNING (testguest): DVD or burner: '/dev/rdisk/disk31' currently has no disk.
1. 2. 3. Based on the all vPar/VM storage considerations, choose a storage device to add. Based on the device type, set up and configure the VSP to form a valid resource statement. This includes accounting VSP resources to avoid future storage conflicts. Use the valid resource statement with the hpvmmodify command to add or attach the vPar/VM storage device. The resource statement for adding an vPar/VM storage device does not require virtual hardware addressing.
disk avio_stor 0 1 0 0 0 disk /dev/rdisk/disk5 disk avio_stor 0 1 0 2 0 disk /dev/rdisk/disk9 To delete an AVIO storage device, specify the following: host# hpvmmodify -P guest1 -d disk:avio_stor:0,5,0:disk:/dev/rdisk/disk11 9.3.2.3 Modifying storage devices The VSP administrator or the guest administrator can modify an vPar/VM storage device. The VSP administrator can use the hpvmstatus and hpvmmodify commands to change the virtual media of virtual devices.
# diskinfo /dev/rdisk/disk7 AVIO describe of /dev/rdisk/disk7: vendor: HP product id: Virtual DVD type: CD-ROM size: 665600 Kbytes bytes per sector: 2048 vMP> ej Ejectable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev Pstore Path ------------------------------------------------------------------------[1] 0/0/1/0.7.
For information about AVIO support, see the HP-UX vPars and Integrity VM V6.1 Release Notes at http://www.hp.com/go/hpux-hpvm-docs. Prior to running the hpvmmodify command shown previously, devices unsupported by AVIO need to be moved to a new HBA, using the hpvmmodify delete and add operations. NOTE: Guest operating systems, applications, or configuration files sensitive to device names or hardware paths need to be repaired after the move.
SCSI describe of /dev/rdisk/disk0: vendor: HP product id: Virtual FileDVD type: CD-ROM size: 3686144 Kbytes bytes per sector: 2048 For attached devices, modifications are made physically on the device. The guest OS supplies commands for loading and unloading tapes using media changers. But loading new media into the media changer, changing tapes in standalone drives, and changing discs with CD/DVD burners are accomplished manually.
10 Creating virtual networks You can allocate virtual network devices or virtual network interface cards (vNICs) to the vPar or VM when you create the them with the hpvmcreate command or when you modify an existing vPar/VM using the hpvmmodify command, as described in Chapter 7 and “Creating virtual partitions” (page 59). 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.
• VSP physical network interface card (pNIC) — the physical network adapter, which may be configured with Auto Port Aggregation (APA). (For more information about APA, see the HP Auto Port Aggregation (APA) Support Guide.) NOTE: Trunking software such as APA is supported only on the VSP, not on the guest. APA can be configured on the VSP to provide a highly available LAN for the vswitch (APA in active/passive mode) or to increase the bandwidth of the vswitch LAN (APA active/active mode).
Table 21 Options to the hpvmnet Command Option Description -b Boots a vswitch. The vswitch must be booted before it can accept network traffic. All vswitches are booted automatically when Integrity VM is started. -c Creates a new vswitch. -h Halts one or all vswitches. You are asked to confirm this action. -F Omits the confirmation dialog before halting, deleting, or rebooting the vswitch. This option is intended for use by scripts and other noninteractive applications (Force mode).
Table 21 Options to the hpvmnet Command (continued) Option Description -v Displays the version number of the hpvmnet command in addition to the vswitch information. -C Changes the specified vswitch. If used with the -N option, the changes are made to the cloned vswitch. You must include either the -S or -s option. -N new-vswitch-name Creates a new vswitch based on the existing vswitch. For new_vswitch_name, specify the unique name of the new virtual switch.
NOTE: The Cisco switch for HP BladeSystem c-Class Server Blades has a protocol error that causes it to respond to every MAC address. Because MAC addresses are unique, Integrity VM checks that the generated guest virtual MAC address is unique. If one of these bad switches is on your network, Integrity VM's check will fail. The hpvmcreate command might fail with messages like the following: hpvmcreate: hpvmcreate: WARNING (host): Failed after 3 attempts. WARNING (host): Unable to create Ethernet MAC Address.
======== ====== ======= ========= ======== ============== =============== localnet 1 Up Shared N/A N/A hostnet 296 Up Shared lan0 0x00306e4a93e6 If lan0 goes down, enter the following command to swap to use lan1: # hpvmnet -C -S # hpvmnet Name Number ======== ====== localnet 1 hostnet 296 hostnet -n 1 State ======= Up Up Mode NamePPA ========= ======== Shared Shared lan1 MAC Address IP Address ============== =============== N/A N/A 0x00306e4a92ef 10.2.
hpvmnet: Remove the vswitch 'clan1'? [n/y] y The default command function (if you press Enter) is to not perform the function of the command. To perform the command function, enter y. In the case of commands where a confirmation is required, such as the hpvmnet -h command, you can include the —Q option to override the confirmation process. This is useful in scripts and processes that are not interactive.
# hpvmnet -S clan1 -h hpvmnet: Halt the vswitch 'clan1'? [n]: y Auto Port Aggregation (APA) can be configured on the VSP to provide a highly available LAN for the vswitch (APA in active/passive mode) or to increase the bandwidth of the vswitch LAN (APA active/active mode). Before you stop APA, halt the vswitches associated with it. If you do not bring down the vswitch first, the hpvmnet command reports an incorrect MAC address for the vswitch. 10.2.
network:adapter-type:[hardware-address]:vswitch:vswitch-name The guest virtual network device information consists of the following fields, separated by colons: • network • adapter-type, which can be either lan or avio_lan • [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.
The virtual network entry in the guest configuration file includes the guest information on the left side of the equal sign (=), and VSP information on the right. The data about the guest LAN example includes the following information: lan(0,0) Bus 0 and device number 0 indicate the guest LAN hardware path. 0xEEEE4077E7EB Guest virtual MAC address. switch(clan1) The vswitch name is clan1. 4 The VLAN port number is 4.
10.4.1 Port-Based VLANs Figure 11 illustrates a basic virtual machine VLAN that allows guests on different VSP systems to communicate. Figure 11 Integrity VM VLAN Configuration Example Guest VM1 VSwitch1 Guest VM2 VSwitch2 VLAN1 Guest VM3 PNIC 1 PNIC 1 PNIC 2 PNIC 2 VSP VSwitch1 Guest VM4 VSwitch2 VLAN1 VSP 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.
Frames arriving at the vswitch from a guest can be “tagged” by the vswitch. Tagging consists of inserting the VLAN ID information into the MAC header before forwarding the frame on. Tagged frames destined for a guest are always stripped of the tag information in the frame before being forwarded. For Integrity VM, only tag-unaware guests are supported. To configure a VLAN, follow this procedure: 1. Create and start the vswitch.
10.4.1.1 Cloning guests with VLAN information If you use the hpvmclone command to clone guests, the operation automatically assigns new port numbers for new guests. To assign the same port number to the new guest, use the —S option, as follows: # hpvmclone -P vm1 -N vmclone1 -S This command creates a new guest (vmclone1) based on the existing guest vm1, and preserves the vswitch port number so that the new guest will have access to the same VLANs as the existing guest. 10.4.1.
Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlandID Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlanID Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlanId Port Number Port State Active VM Untagged VlanId Reserved VMs Adaptor Tagged VlanID : : : : : : vm1 none vm1 avio_lan none 2 : : : : : : : Active vm1 100 vm1 avio_lan none : 3 : : : : : : 4 : : : : : : Active vm2 none vm2 avio_lan none Active vm2 100 vm2 avio_lan none 10.4.
lan0 lan1 lan2 lan3 lan900 lan901 lan902 lan903 lan904 UP UP UP UP UP DOWN DOWN DOWN DOWN 0x0017A4AB5461 0x0017A4AB5460 0x001A4B06E90A 0x001A4B06E90B 0x001A4B06E90B 0x000000000000 0x000000000000 0x000000000000 0x000000000000 igelan igelan iether iether hp_apa hp_apa hp_apa hp_apa hp_apa 1000Base-T 1000Base-T 1000Base-T 1000Base-T hp_apa hp_apa hp_apa hp_apa hp_apa lan900 To configure a PPA of the VLAN interface (VPPA) with a VLAN ID = 20 on the lan900 aggregate, enter the following: # nwmgr -a -S vlan
VLAN interfaces on the host for the relevant VLANs. Use the lanadmin command to configure VLANs on a remote HP-UX host. For example, to configure a VLAN interface with VLAN ID 100 on lan4, enter the following command: # lanadmin -V create vlanid 100 4 Successfully configured lan5000: vlanid 100 name UNNAMED pri 0 tos 0 tos_override IP_HEADER pri_override CONF_PRI ppa 4 10.
# hpvmmodify -P vpar -m lan:dio:b,d,macAddr:hwpath:new-hwpath ◦ Modify the MAC address: # hpvmmodify -P vpar -m lan:dio:b,d,new-macAddr:hwpath:hwpath • The hpvmstatus command — allows you to: ◦ See vPar and VM configurations. The direct I/O network functions are included in the #NETs count. # hpvmstatus ◦ See specific vPar or VM I/O details: # hpvmstatus -P vm -d NOTE: • There are no new switches specific to direct I/O for the hpvmstatus command.
H/W Path -------------0/0/0/3/0/0/0 0/0/0/3/0/0/1 0/0/0/3/0/0/2 0/0/0/3/0/0/3 0/0/0/3/0/0/4 0/0/0/3/0/0/5 0/0/0/3/0/0/6 0/0/0/3/0/0/7 0/0/0/4/0/0/0 0/0/0/4/0/0/1 0/0/0/4/0/0/2 0/0/0/4/0/0/3 0/0/0/4/0/0/4 0/0/0/4/0/0/5 0/0/0/4/0/0/6 0/0/0/4/0/0/7 Class ------lan lan lan lan lan lan lan lan lan lan lan lan lan lan lan lan Owner ----host host host host host host host host host host host host host host host host Description ------------------------HP PCIe 2-p 10GbE BuiltHP PCIe 2-p 10GbE BuiltHP PCIe 2-p 10G
# hpvmhwmgmt -p dio -a 0/0/0/3/0/0/7 hpvmhwmgmt: Sibling path '0/0/0/3/0/0/0' (lan0) is being used as vswitch 'hpnet'. hpvmhwmgmt: Sibling path '0/0/0/3/0/0/1' (lan1) is being used as vswitch 'priv_net'. hpvmhwmgmt: Lan devices used as vswitches cannot be added to the DIO pool. hpvmhwmgmt: Unable to manage dio pool resource.
0/0/0/4/0/0/0 (lan2) 0/0/0/4/0/0/1 (lan3) DATA CRITICAL RESULTS: Interface lan2: COMMAND cmnetd PID 2907 Interface lan2: COMMAND cmnetd PID 2907 Service-Guard(SG) Usage: The interfaces listed below are being used by SG: lan2 Use the hvmdevinfo command to display the hardware device mapping between vPar/VM and the VSP.
Configure LAN interfaces ............................ * . FAIL When the guest is running, you can use the lanscan command to identify the new LAN PPA and to modify netconf. For example: # lanscan Hardware Station Path Address 0/0/5/0 0x02636C6E3030 Crd Hdw Net-Interface In# State NamePPA 1 UP lan3 snap3 NM ID 1 MAC Type ETHER HP-DLPI DLPI Support Mjr# Yes 119 In the preceding example, before the modification, the LAN PPA was 0. The new LAN PPA on the first boot after the modification is 3.
vmlan4 23 Up Shared lan4 0x00127942fce3 192.1.2.205 vmlan900 24 Up Shared lan900 0x00306e39815a 192.1.4.205 NOTE: The lanadmin command is deprecated and will be removed in a future HP-UX release. HP recommends that you use the nwmgr command to perform all network interface-related tasks. The following table shows the nwmgr command that performs the same task as the lanadmin command: Table 23 The nwmgr command Task Legacy Command nwmgr Command Check the status of the transmit CKO.
11 Managing vPars/VMs To manage a vPar/VM, connect to the vPar/VM using a remote connection and use the operating system administration procedures appropriate to the guest OS. vPars and Integrity VM provides utilities for managing vPars and virtual machines from the VSP and from inside the vPar/VM. This chapter describes how to manage vPars/VMs using Integrity VM commands and utilities, including the use of Logical Server Management (LSM) to manage VMs.
NOTE: The SLVM volume groups must be in the activated mode before running the hpvmhostrdev script. For information about deactivated volume groups, see Section 11.1.2 (page 166). 4. Execute the hpvmhostgdev -a command to ensure that all devices are populated in the gdev database. The hpvmhostgdev command analyzes disklist and lvlist output and adds unused gdevs to the device database. NOTE: If you add new devices in the future, run the hpvmhostgdev -a script again.
• If the volume group is to remain deactivated, the VSP administrator can manually add the physical volume as a restricted device with the hpvmdevmgmt command. • Or, after activating the volume group, execute the hpvmhostrdev command, so that the VSP storage management database is updated accordingly. An HP-UX system administrator can deactivate a volume group using the vgchange command.
• File: # hpvmdevmgmt -a gdev:/var/opt/hpmv/ISO-images/hpux/112350GOLD.ISO:attr:PRESERVE=YES • VxVM volume: # hpvmdevmgmt -a gdev:/dev/vx/rdisk/guestdg/vxvm_g2:attr:PRESERVE=YES To remove a device from the storage pool, used the following command: # hpvmdevmgmt -d gdev:/dev/rdisk/disk23 NOTE: Adding devices to the storage pool does not prevent them from being used by the HP-UX operating system or other Integrity VM commands. The storage pool does not fully support lunpaths or directories.
11.2.3 Changes to the hpvmmodify command The hpvmmodify -x command has been changed to allow changing the modify_status, and visible_status, and register_status attributes with the -x option, in addition to runnable_status.
The following example sets the device /dev/rdisk/disk100 as a restricted device: # hpvmdevmgmt -a rdev:/dev/rdisk/disk100 11.2.5 Unpresenting SAN devices to Integrity VSPs Unpresenting SAN devices that were configured to be used by guests causes the guest to fail to start. If SAN devices must be unpresented, guests configured to use those devices should be reconfigured to no longer require them.
• EFI indicates the vPar/VM is running normally in EFI. • OS indicates the vPar/VM is running normally in the operating system. • ATTN! indicates the guest is not responding to interrupts. Table 24 describes the options to the hpvmstatus command. Table 24 Options to the hpvmstatus Command Option Description -v Displays the version of the Integrity VM product that is running on the VSP.
OS Version Number : State : Off Start type : Manual Console type : vt100-plus Guest's hostname : Guest's vNIC IP Preference : Guest's IPv4 address : EFI location : /opt/hpvm/guest-images/common/efi Pattern File location : /opt/hpvm/guest-images/common/patterns.
Target Lun Physical Storage type Physical Device : : : : 0 0 disk /dev/rdisk/disk5 Device type Adapter type Ioscan format Bus Device Function Target Lun Physical Storage type Physical Device : : : : : : : : : : disk avio_stor 0/0/0/0.1.
Table 25 Options to the hpvmsar Command (continued) Option Display Description -F Integrity VM core Memory Metrics Display -G Guest Dynamic Memory, Swap, Paging Display -H Host Memory, Swap, Paging Display -I Guest Interrupt Display -N Guest AVIO Network traffic by vswitch Display -S Vswitch AVIO Network traffic by Port Display 11.5 Creating guest administrators and operators Integrity VM provides secure access to guest machine consoles.
1. Using the useradd command, set up an /etc/passwd entry for each guest on the VSP. The user name of the account must be the same as the guest name and must have no more than 8 characters. For example: # useradd -d /var/opt/hpvm/guests/host1 \ -c 'host1 console' -s /opt/hpvm/bin/hpvmconsole host1 This example uses the following options: 2. • The -d option specifies the home directory for the host1 account. • The -c option specifies a comment text string that describes the account.
11.5.1 Administrator account names The virtual console administrator name can be any valid HP-UX login name. To continue accessing the virtual console, existing guest console accounts must be added to the authorization list for the associated guest with the usermod command. This allows multiple accounts to map to the guest, and requires the account names to be valid HP-UX login strings.
You can pass a command to the vPar/VM console using the —c option to the hpvmconsole command. For example, to start a virtual machine named host1, enter the following command: # hpvmconsole -P host1 -c "pc -on" Table 26 lists the options to the hpvmconsole command. Table 26 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.
11.7 Using the virtual iLO Remote Console The vPars and Integrity VM virtual iLO Remote Console feature allows you access to the guest console by logging into a specific IP address. You can assign each guest a virtual iLO Remote Console IP Address with which the end user can connect using either telnet or Secure Shell (SSH). After login authentication, the guest console is immediately available. The user no longer needs to know the VSP machine IP address or guest name.
# hpvmstatus -P guestname .... [Remote Console] Remote Console Ip Address: Remote Console Net Mask: 16 .92.81.68 255.255.252.0 When users connect to the virtual iLO Remote Console IP Address, they must log in using the standard telnet or ssh system authentication. After authenticating, they receive immediate access to the guest console: # ssh -l guest1admin 16.92.81.
connections, the SSH client verifies that the host key sent by the server matches the local copy. If the keys do not match, the SSH client prints an error message. The virtual iLO Remote Console uses the host system's SSH server host keys. If the guest is migrated to another host system (using Online VM Migration), these host keys will change. When an end user does an SSH connection, they will receive an error message. The end user must manually delete the local copy of the host key.
Table 27 Dynamic Memory Control Command Options Keyword Value Pair Description dynamic_memory_control={1|0} Specifies whether a sufficiently privileged user on the guest (such as root) can change the dynamic memory values while the guest is running. To disable guest-side dynamic memory control, specify 0 (zero). If the guest is not active, the only effect is the modification of the guest configuration file. On the running guest, the change takes effect immediately.
-x ram_dyn_type = any | driver -x ram_dyn_min = minimum size for memory size changes -x ram_dyn_max = maximum size for memory size changes You can configure a virtual machine to reduce its memory size early in a boot process, making the virtual machine available but maintaining lower memory overhead on the VSP system. Use the following -x option to enable this feature: -x ram_dyn_target_start = memory size after boot You can supply several dynamic memory keywords on the same command line.
Table 28 Dynamic Memory Characteristics Characteristic Setting Description Type none No dynamic memory support any Dynamic memory is configured on the host, but the dynamic memory subsystem on the guest has not started and reported the implementation type. driver Dynamic memory is implemented in a driver and does not use Guest OS Online Add/Delete features. OLAD Dynamic memory is implemented using Guest OS Online Add/Delete features.
The following example displays active usage of the VSP and guest(s) dynamic memory usage values, along with the guest memory utilization. The guest's current swapping and paging and translation address memory misses per second are included. For a description of each column displayed, see the hpvmsar manpage. The dash (-) in the example indicates the guest named ux2 is not currently booted. # hpvmsar -G -A HP-UX witch4 B.11.
Table 29 Options to the hpvmmgmt Command (continued) -M Displays verbose attribute and resource information in a machine-readable format. -X Displays verbose attribute and resource information in the XML format. -x ram_target={0 | start | amount} Specifies the guest RAM target, where: • 0 indicates the guest dynamic memory will be reduced to a comfortable minimum value. • start indicates the guest dynamic memory will be set back to the boot time value.
11.9.3.1 Dynamic memory restrictions Use of dynamic memory is subject to the following restrictions: • The size of a virtual machine cannot be increased above its original boot size (as specified with the -r option). • If the virtual machine memory has become fragmented, attempting to reduce the size of the virtual machine might fail or might take a very long time. If you cannot reduce the size of the virtual machine to the desired size, abort the operation by setting a new target size.
# hpvmstatus -V -P host1 . . . [Dynamic Memory Information] Type : driver Minimum memory : 1222 MB Target memory : 2103 MB Maximum memory : 6144 MB Current memory : 2103 MB Comfortable minimum : 27 MB Boot memory : 6135 MB Free memory : 0 MB Available memory : 286 MB Memory pressure : 100 Memory chunksize : 65536 KB Driver Mode(s) : STARTED ENABLED . . . An indication of this problem is a small or zero amount of free memory and a large memory pressure value (100).
hpvmmgmt: Unable to continue. # hpvmmgmt -x ram_target=2048 Failed to open dynamic memory driver, error: No such device. Failed to set dynamic value error: No such device hpvmmgmt: Unable to continue. For information about installing the VirtualBase software, see Section 8.3 (page 104). 11.9.3.7 Upgrade the VirtualBase software when upgrading Integrity VM The dynamic memory software has two components: the VSP support and the HP-UX guest support.
11.9.4.2 Enabling automatic memory reallocation on a VM By default, VMs are not enabled for automatic memory reallocation. Only VMs that support dynamic memory can use automatic memory reallocation. Use the following -x options to enable automatic memory reallocation on a VM: -x amr_enable -x ram_dyn_entitlement=minimum memory size in MB This option is supported on running VMs. No error occurs if this is executed for a VM that does not support dynamic memory, but it is ignored.
• Overlapping physical storage allocated for different backing store types. If a guest uses a logical volume (for example, rlvol1) as a backing store device, the disks used by the volume group on which the logical volume is made (for example, /dev/vg01) cannot be used as backing stores. • Veritas VxVM DMP device files (files under /dev/vx/rdmp/) are not supported by Symantec for whole disk backing stores for virtual machines. You can use the ioscan and sam commands to detect these conflicts.
Table 30 Options to the hpvmdevmgmt Command Option Description -l Lists an entry. To list all entries, enter the following {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.
# hpvmdevmgmt -m gdev:/var/opt/hpvm/ISO-images/hpux/:attr:SHARE=YES # hpvmmodify -P host1 -a dvd:avio_stor::null:/var/opt/hpvm/ISO-images/hpux/ # hpvmmodify -P host2 -a dvd:svio_stor::null:/var/opt/hpvm/ISO-images/hpux/ Virtual DVDs and virtual network devices can be shared. DVDs are not shareable unless you specify otherwise. Sharing of virtual devices or hardware backing stores must be carefully planned in order to prevent data corruption.
11.11.3 Inspect and edit the repair script The hpvmdevmgmt -r report and repair-script function might identify one or more new pathnames for disks whose old pathnames no longer exist. The repair-script performs that reassignment using the hpvmdevmgmt -n command. In general, you should inspect and edit the script before running it for the following reasons: • All replace commands, hpvmdevmgmt —n, in the script are commented out.
fs1 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part3,SigBEC59C70-E6C8-11DB-8004-D6217B60E588) blk0 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0) blk1 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part1,SigBEC59C34-E6C8-11DB-8002-D6217B60E588) blk2 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part2,SigBEC59C52-E6C8-11DB-8003-D6217B60E588) blk3 : Acpi(PNP0A03,0)/Pci(0|0)/Scsi(Pun0,Lun0)/HD(Part3,SigBEC59C70-E6C8-11DB-8004-D6217B60E588) startup.nsh> echo -off setting hpux path(\EFI\HPUX)...
12 Migrating virtual machines and vPars There are several different forms of migration. With the hpvmmigrate command, you can move either an offline virtual partition or virtual machine, or a live, online virtual machine running a guest operating system and applications from a source VSP system to a target VSP system.
The basic virtual machine or vPar migration environment includes a source machine and a target machine. Both must be running vPars and Integrity VM V6.1 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.
• Balancing VSP workloads • Optimizing physical resource utilization With Online VM Migration, you can migrate all your VMs off of a VSP to one or more other VSPs without interrupting the workload activity on the virtual machine. A common reason to do this is for maintenance of the VSP system: hardware, firmware or software. You can configure the hardware that does not have hot-plug support. You can update the firmware, which requires the system to be shut down.
To check if a guest can be migrated to the target VSP, use the hpvmmigrate -s option. 12.1.2 Reasons for migrating virtual machines or vPars offline This sections lists reasons why you might want to migrate a virtual machine or vPar offline. For example: • The vPar or VM might be stopped, so you need to move the configuration information offline. • Migrating the virtual machine or vPar offline does not use the VSP resources (like memory and CPUs) on the source and target VSPs.
1. 2. 3. Set up SSH keys on both the source and target hosts, as described in Section 12.3.3 (page 210). Present all SAN storage assigned to the virtual machine to the target VSP (if it is not already there). If using offline migration and the guest is booted, stop the guest on the source host, using the hpvmstop or hpvmconsole command. You can also use the hpvmmigrate -d command to stop the guest during the migration.
it is reported, and the virtual machine is not migrated. You can specify the -F option (force) to suppress the errors and force the virtual machine migration to the target VSP. CAUTION: Use the -F option with caution, because some errors can prevent a virtual machine from working properly on the target VSP. The -F option is deprecated in Integrity VM commands; this option should be used only at the direction of HP Support.
Table 33 Options to the hpvmmigrate Command (continued) Option Description -C For offline migrations, physically copies the storage device specified with the -m option to the target VSP during the migration process. If specified before the first -m option, it applies to all -m options that specify an appropriate type of storage. This might take a long time to complete if a large amount of storage needs to be copied.
Table 33 Options to the hpvmmigrate Command (continued) Option Description -k Creates the virtual machine configuration on the target VSP and marks it Not Runnable, but does not change the virtual machine on the source VSP. This is used primarily to distribute virtual machine configurations for Serviceguard. -l new-vm-label Specifies a descriptive label for the virtual machine, which can be useful in identifying a specific virtual machine in the hpvmstatus command verbose display.
Table 33 Options to the hpvmmigrate Command (continued) Option Description -s Indicates that the migration should not occur, but the hpvmmigrate command should check whether or not the migration is possible. Because virtual machines and their hosts are dynamic, a successful -s trial does not always guarantee a subsequent successful migration.
is called host2, and the target VSP's private network is called host2–hpvm-migr (that is, host2–hpvm-migr is an alias for the private network defined in /etc/hosts). NOTE: The hpvmmigrate command does not check that you are using a private network to migrate your guest. Using a private network is important for security and to maintain the performance of your site's public network.
NOTE: The Online VM Migration feature is not supported for a guest running as a Serviceguard node. Therefore, disable online migration for all guests that are Serviceguard nodes. For example: # hpvmmodify -P sg_node1 -x online_migration=disabled A transient network error might cause the hpvmmigrate command's vswitch connectivity check to report a failure. If the connectivity check fails, retry the migration by re-issuing the hpvmmigrate command.
A vswitch of the same name, connected to the same network must be available on the source and target VSP servers. The hpvmmigrate command does connectivity checking before migration. You can use the hpvmmigrate -w option to bypass the vswitch connectivity checks, but only use -w if you are certain that the source and target vswitches are connected to the same subnet. Otherwise, your guest will lose network connectivity after migrating.
server minpoll 4 maxpoll 6 After configuring the guest's /etc/ntp.conf file, assuming NTP is already enabled (that is, the XNTPD variable in /etc/rc.config.d/netdaemons is set to 1, as in export XNTPD=1), you can run the following commands on an HP-UX guest to sync its time with the VSP and restart xntpd: /sbin/init.d/xntpd stop /usr/sbin/ntpdate -b /sbin/init.
533 MT/s bus, CPU version C2 24 logical processors (2 per socket) Vendor identification: GenuineIntel Processor version info: 0x0000000020000704 Family 32, model 0, stepping 7 Processor capabilities: 0x0000000000000005 Implements long branch Implements -byte atomic operations . . . # hostname host20 # machinfo -v CPU info: 4 Intel(R) Itanium 2 9000 series processors (1.
INTERFACE_NAME[3]=lan3 IP_ADDRESS[3]=10.3.81.142 SUBNET_MASK[3]=255.255.252.0 BROADCAST_ADDRESS[3]="" INTERFACE_STATE[3]="" DHCP_ENABLE[3]=0 INTERFACE_MODULES[3]="" Example output from netstat on the host2 VSP system: # netstat -in Name Mtu lan3 1500 lan0 1500 lo0 32808 Network 10.3.80.0 .17.80.0 127.0.0.0 Address Ipkts ... 10.3.81.142 1022313379 ... .17.81.142 2420913 ... 127.0.0.1 123762 ... You can also use the nwmgr command to help verify the connection.
Because this is just a convention implemented local to each host, administrators can use it or not.. If this convention is configured correctly, both target and target-hpvm-migr resolve to the proper address. For example: • hpvmmigrate -h host39 — Look up host39-hpvm-migr first, and if not found, look up host39. • hpvmmigrate -h host39-hpvm-migr — Look up host39–hpvm-migr. • hpvmmigrate -h host39.atl — Look up host39.atl. Of course, target.fully.qualified.domain-name will not be modified.
If a VSP is reinstalled at some point after using the secsetup script to configure SSH keys, you might receive warning messages from ssh commands about keys changed, or bad keys in your known_hosts file. In this case, use the ssh-keygen -R hostname command to remove obsolete keys from the known_hosts file, and then use the secsetup command again to configure new keys.
For example, if a guest stops I/O to storage for too long, it could experience I/O errors and applications could fail or the operating system could crash. If a guest is frozen for too long, external network connections to the guest can time out and network connections can be dropped. Network time-outs are especially troublesome for certain UDP applications that are not resilient enough to tolerate packets being delayed and dropped.
Do not mark disks SHARE=YES for devices assigned to virtual machiness that will migrate (unless more than one virtual machine will share the storage on the same VSP). Marking a device SHARE=YES can lead to more than one virtual machine using the device at the same time and can lead to disk corruption. 12.3.4.4 Using NTP on the VM guests Using NTP is strongly recommended for Online VM Migration environments. Each guest should include all potential VSPs as servers in its ntp.
Online migration support among Integrity servers is limited by the processor architecture. Online migration among servers with processor family 31 is supported regardless of the model number within that family. Migration among servers with processor family 32 and model numbers 0 or 1 is supported. Otherwise, online migration is supported among servers with identical processor family and model number. To check if a guest can be migrated to the target VSP, use the -s option to the hpvmmigrate command.
13 Reporting problems with vPars and Integrity VM Report vPars and Integrity VM defects through your support channel. Follow these instructions to collect data to submit with your problem report. 1. Run the hpvmcollect command to gather information about the guest before modifying any guest. Preserve the state of the VSP and the vPar/VM to best match the environment when the VSP failed. If multiple guests are running, run the hpvmcollect command for guest that was running at the time. 2. 3. 4.
Table 35 Options to the hpvmcollect Command on the VSP (continued) Option Description -c Includes the latest crash dump directory in the archive. This option is used if the guest or the VSP 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.
HPVSP crash/log collection tool version B.06.10.00 Gathering info for post-mortem analysis of guest 'host1' on host Collecting I/O configuration info ................................... OK Collecting filesystem info .......................................... OK Collecting system info .............................................. OK Collecting lan info ................................................. OK Running lanshow ..................................................... NO Collecting installed sw info ..
13.1.2 Using the hpvmcollect command on vPars/VMs To use the hpvmcollect command on the vPar/VM, you must first install the vPar/VM VirtualBase software on the vPar/VM (if it is not already installed) as described in Section 8.3 (page 104). Table 36 describes the options to the hpvmcollect command on the guest. Table 36 Options to the hpvmcollect Command on Guests Option Description -c Includes the latest crash dump directory in the archive. This option is used if the vPar/VM or the VSP fails or hangs.
13.2 Managing the size of the VMM driver log file The monitor log file (/var/opt/hpvm/common/hpvm_mon_log) is limited in size to 1024 KB. When the log file grows larger than this, it is copied to a new file (hpvm_mon_log.$time), and an empty one is created for the new log. To allow this log file to increase to 102400 KB, include the following line in the /etc/rc.config.
14 Support and other resources 14.1 Contacting HP 14.1.1 Before you contact HP Be sure to have the following information available before you call contact HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level 14.1.
integrated with HP Systems Insight Manager. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight Remote Support Advanced. Details for both versions are available at: http://www.hp.com/go/insightremotesupport To download the software, go to Software Depot: http://www.software.hp.com Select Insight Remote Support from the menu on the right. NOTE: HP recommends using Insight Remote Support on the VSP system.
14.3 Typographic conventions This document uses the following typographical conventions: %, $, or # A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells. A number sign represents the superuser prompt. audit(5) A manpage. The manpage name is audit, and it is located in Section 5. Command A command name or qualified command phrase. Computer output Text displayed by the computer. Ctrl+x A key sequence.
A Rolling back to the previously installed version of Integrity VM In the unlikely event that you need to roll back to a previous version of Integrity VM, this appendix provides the information needed to perform the rollback. The preferred method for rolling back to a previously installed version of Integrity VM is to restore the system image that was backed up before installing the current version of Integrity VM on the VSP.
B Sample Script for Adding Multiple Devices The following example provides a script that enables you to specify multiple storage devices at once for a guest. #!/bin/ksh # --------------------------------------------------------------------------------------# HP Integrity VM example script. # # SUMMARY: # # Add disks to an Integrity VM (guest) in 'batch mode' with hpvmmodify, using AVIO. # # SYNOPSIS # # ./thisscript [-a] -P guestname -f disklistfile [-N #] [-n #] [-t #] [-qT] [-F flags] # or # .
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # -q Quite mode - no display of hpvmmodify command that will run -t targetmax Max target value to use for -a disk:avio_stor:[b,d,targetmax]... Valid values: 0 - special case: script will use full 0-127 range 15...127 - script will use specified max 1... 14 - not valid for this script, since 0-14 is the normal default range for target values if -t is not specified.
# setup BUS,DEV,TGT for next call TGT=$TGT+1 if [ $TGT -gt $WRKTGT ] then TGT=0 DEV=$DEV+1 fi # Skip b,d of 0,3 if [ $BUS -eq 0 ] && [ $DEV -eq $DEVSKIP ] then DEV=$DEV+1 fi if [ $DEV -gt $DEVMAX ] then DEV=0 BUS=$BUS+1 fi if [ $BUS -gt $BUSMAX ] then # NOTE: should not be here, but error out just in case. echo "ERROR: Max supported bus value exceeded, no more room for another adaptor.
typeset -i XN ADDFLAG=0 AUTOBDT=0 QUIET=0 USERDISKCNT=0 USERTGT=0 XN=$XNDEFAULT # # Get cmd line options # while getopts :aF:f:HhN:n:P:qTt: option do case $option in a) # add flag - do actual call to hpvmmodify ADDFLAG=1 a=$a+1 ;; F) # hpvmmodify flags FLAGS=$OPTARG F=$F+1 ;; f) # disklist file DISKLISTFILE=$OPTARG f=$f+1 ;; H) # Help usage exit 0 ;; h) # help usage exit 0 ;; N) # number of disks to add from the disklistfile USERDISKCNT=$OPTARG N=$N+1 ;; n) # number of disks to add at a time XN=$OPTARG n=$
exit 1 fi if [ ! -s "$DISKLISTFILE" ] then echo "ERROR: Disklist file: $DISKLISTFILE is a zero-length file." exit 1 fi GUESTSTATUS="`hpvmstatus -P $GUESTNAME -M 2> /dev/null`" if [ -z "$GUESTSTATUS" ] then echo "ERROR: Could not find guest: $GUESTNAME" exit 1 fi if [ $t -eq 1 ] then if [ $USERTGT -gt 0 ] && [ $USERTGT -lt 15 ] then echo "ERROR: User specified target max (-t $USERTGT) must be 0 or in range 15...127.
ADDRSRC="-a disk:avio_stor:$BDT:disk:$DISK" ADDCMD="$ADDCMD $ADDRSRC" DISKIDX=$DISKIDX+1 CMDIDX=$CMDIDX+1 # Run hpvmmodify if at the add multiplier (-n) or at the last disk if [ $CMDIDX -eq $XN ] || [ $DISKIDX -eq $DISKCNT ] then # Do the hpvmmodify if [ $QUIET -eq 0 ] then echo "Calling: $TIMECMD $ADDCMD" fi if [ $ADDFLAG -eq 1 ] # check for -a flag then $TIMECMD $ADDCMD RETVAL=$? if [ $RETVAL -ne 0 ] then typeset -i FINALCNT FINALCNT=$DISKIDX-$XN echo "ERROR - hpvmmodify failed.
Glossary This glossary defines the terms and abbreviations as they are used in the Integrity VM product documentation. Accelerated Virtual Input/Output See AVIO adoptive node The cluster member where the package starts after it fails over. APA Auto Port Aggregation. An HP-UX software product that creates link aggregates, often called “trunks,” which provide a logical grouping of two or more physical ports into a single “fat pipe”.
cluster Two or more systems configured together to host workloads. Users are unaware that more than one system is hosting the workload. cluster member A cluster node that is actively participating in the Serviceguard cluster. cluster node A system (VSP or guest) configured to be a part of a Serviceguard cluster. Deconfigured The term used to describe the health of a resource that has been marked as unusable by the Health Repository. Such a resource will be excluded from partition activity.
ILM Interleaved Memory. Is implemented as Partition Memory in HP Superdome 2, which includes Direct Access Partition Memory and Agent Access Partition Memory Integrity Virtual Machines The HP Integrity Virtual Machines product, which allows you to install and run multiple systems (virtual machines) on the same physical host system. Integrity VM See Integrity Virtual Machines.. ISSE HP Instant Support Enterprise Edition. A secure remote support platform for business servers and storage devices.
SGeRAC Serviceguard extension for real application clusters. SGeSAP Serviceguard extension for SAP. shared device A virtual device that can be used by more than one virtual machine. SLM Non-interleaved memory that can be quickly accessed by processors residing on the same cell as the memory. This is the same concept as CLM. socket local memory See SLM start virtual machines To start a virtual machine that has been booted before. See also boot virtual machines.
WBEM Web-Based Enterprise Management. A set of Web-based information services standards developed by the Distributed Management Task Force, Inc.A WBEM provider offers access to a resource. WBEM clients send requests to providers to get information about and access to the registered resources. workload The collection of processes in a virtual machine.
Index A adapters virtual storage, 114 adding virtual storage, 136 admin privileges, 174 Administrator guest, 135 VSP, 133 APA, using, 144 applications running on guests, 20 running on VSP, 20 attachable devices specifying, 130 attached devices, 115 attached I/O, 109 Auto Port Aggregation see APA autoboot, 95 Automatic cell balancing, 79 automatic memory reallocation, 188 AVIO using, 17 B BL8x0c i2 support,server, 14 boot, 64 bundle names, 39 C CD/DVD burner, virtual, 109 characteristics of virtual machine
setting up, 150 guest operating system, 77 guest user, 136 guest-based VLANs, 156 guests, 15 local networks for, 147 log files, 189 managing, 165 monitoring, 170 removing, 99 running applications on, 20 GUID manager, 222 H hard reset, 66 hardware requirements, 37 HP-UX guests creating, 101 installing, 101 hpvmclone command, 94 options, 94 hpvmcollect command, 215, 218 options, 215, 218 hpvmconsole command, 151 options, 175, 177 using, 174 hpvmcreate command, 86 options, 88 hpvmdevmgmt command, 190 hpvminfo
virtual storage devices, 81 pNICs, 144 ports VLAN, 154 power off, 66 privileges guest console, 174 problems reporting, 215 processing power allocating, 78 providing access to virtual consoles, 174 R re-creating vswitches, 149 recover nonresponsive, 73 recreate remove, 67 redefining pNICs, 162 related documentation, 222 remove vPars, 67 removing guests, 99 removing Integrity VM, 40 removing vNICs, 152 replacing devices, 192 reporting problems, 215 requirements for installing Integrity VM, 37 installation, 3
allocating, 150 virtual networks configuration, 151 creating, 143 planning, 80 virtual NICs see vNICs Virtual NullDVD specifying, 129 virtual storage adding, 136 architectures, 108 attachable devices, 130 attached, 109 configuring, 116 deleting, 137 formulating resource statements, 123 I/O stack, 117 implementations, 114 introduction, 107 making changes to, 121 management, 119 modifying, 138 multipath solutions, 118 performance, 116 setting up, 121 shared, 108 specifying, 122 specifying FileDisk, 126 specif
