HP-UX vPars and Integrity VM V6.1.5 Administrator Guide HP Part Number: 5900-2295 Published: April 2013 Edition: 1.
© Copyright 2013 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.5...............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.4 Reserved resources.....................................................................................................79 7.1.5 Virtual CPUs..............................................................................................................79 7.1.6 Entitlement.................................................................................................................80 7.1.7 Guest memory allocation...........................................................................................
9.1.4.2 Sample script for adding multiple devices at once.................................................116 9.1.4.3 vPar/VM storage devices...................................................................................117 9.1.4.3.1 Virtual devices...........................................................................................117 9.1.4.3.2 Attached devices.......................................................................................117 9.2 Configuring vPar/VM storage................
10.4.1.2 Displaying VLAN information...........................................................................157 10.4.2 Guest-Based VLANs (AVIO)....................................................................................158 10.4.3 Configuring VLANs on virtual switches.....................................................................158 10.4.3.1 Creating and managing a vswitch with a VLAN interface....................................158 10.4.4 Configuring VLANs on physical switches..............
11.9.4.3 Viewing automatic memory reallocation.............................................................193 11.10 vPar/VM log files..........................................................................................................193 11.11 Managing the device database.......................................................................................193 11.11.1 The vPars/VM device database file...........................................................................194 11.11.
14.2 Related information.......................................................................................................226 14.3 Typographic conventions................................................................................................226 15 Documentation feedback.......................................................................229 A Rolling back to the previously installed version of Integrity VM......................231 B Sample Script for Adding Multiple Devices.................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 vPars V6.1.5 framework.....................................................................................................14 Hardware Consolidation Using Integrity VM........................................................................15 Upgrade Procedure..........................................................................................................44 Installing VirtualBase on a vPar/VM......................................................................
34 35 36 37 Itanium Processor Families...............................................................................................211 Options to the hpvmcollect Command on the VSP.........................................................219 Options to the hpvmcollect Command on Guests..........................................................222 Documentation and its location........................................................................................
1 Introduction HP-UX vPars and Integrity VM Version 6.1.5 is a 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 vPars and Integrity VM V6.1. The V6.1.5 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.5 (as well as the vPars V6.1 product) 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.
• Virtualization Services Platform (VSP) • Virtual machines 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.1.
you to create and clone virtual machines with a simple command interface. You can modify existing guests and arrange networks that provide communication through the VSP's network interface or the guest local network (localnet). Because all the guests share the same physical resources, you can be assured of identical configurations, including the hardware devices backing each guest's virtual devices.
1.7 Types of I/O The vPars and Integrity VM V6.1.5 release supports two types of I/O: accelerated virtual I/O (AVIO) and direct I/O (DIO) networking. With AVIO, I/O devices are para-virtualized. The I/O device drivers for these devices in the guest operating system are virtualization aware, eliminating some of the virtualization overhead.
Vswitch port Bus Device Function Mac Address :9 :0 :2 :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.
The asynchronous event generation occurs in addition to any notifications issued using the SCSI programming model, such as CHECK CONDITION on a subsequent I/O. When the AVIO storage driver on the vPar/VM detects the events, it takes the appropriate actions, such as discovering the new targets. For example, if new targets are added using the hpvmmodify -a command, then the vPar/VM driver automatically detects the new device without the manual scan.
• Near native network performance in vPar environments • Improved performance over AVIO networking in VM environments • CPU OL* operations with vPars • DLKM operations in the vPar/VM • Interrupt migrations in the vPar/VM and on the VSP • Running vPars/VMs with DIO as Serviceguard nodes • Support for HP-UX network providers • Support for Direct I/O networking functionality with the HP Auto Port Aggregation (APA) product.
Typical software you can run in a vPar/VM environment includes the following: • 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.
Glance running in the VSP, from Glance running in that vPar/VM. Glance also offers a number 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.
on the VSP OS using the icapmodify command and then execute the vparmodify command to complete 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.5 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.5.
NOTE: Before you add or remove memory, networking, or storage from a vPar or a VM, be sure you know if further action is required on the vPar or VM. 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 runs on HP-UX 11i v3 Integrity systems on the VSP. On the latest Integrity® Itanium® 9500 processor, V6.1.5 requires that the VSP be installed with the HP-UX 11i v3 September 2012 (AR1209) release.
Table 2 Integrity VM commands Command Description hpvm(5) Describes the Integrity VM environment. hpvmclone(1M) Describes how to create virtual machines based on existing virtual machines. hpvmcollect(1M) Describes how to collect virtual machine statistics. hpvmconsole(1M) Describes how to use the virtual machine console. hpvmcreate(1M) Describes how to create virtual machines. hpvmdevinfo(1M) Reports about storage for a virtual machine.
NOTE: HP-UX provides the gvsdmgr utility, which manages AVIO HBAs. For information about the gvsdmgr utility, see the HP-UX gvsdmgr (1M) manpage. 1.12.2 vPars commands From the VSP you can run vPars commands to create, modify, and remove virtual partitions and virtual switches. Superuser privilege is required to run the commands from the VSP. These commands cannot be run from the OA or from inside a virtual partition. Table 2 contains a summary of the VSP commands and descriptions of their use.
Table 4 Chapters in this Manual Chapter Read if... Chapter 1: “Introduction” (page 13) You are new to HP Integrity Virtual Machines. “Installing and configuring VSP for HP-UX vPars and Integrity VM V6.1.5” (page 29) You are installing and configuring the VSP. Chapter 3: Installation procedures for HP-UX vPars and Integrity VM V6.1.5 (page 35) You are installing the HP-UX vPars and Integrity VM V6.1.5 product.
2 Installing and configuring VSP for HP-UX vPars and Integrity VM V6.1.5 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.
2.3.1 vPar environment In V6.1.5, the VSP core is reserved/allocated automatically when the first vPar is created. 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.
on the size of the vPar or VM. Given below is a rough estimate of the memory overhead required for the VSP as well as individual vPars and VMs. The vPar/VM memory pool reserved is roughly about 92% of the system free memory available at the time of V6.1.5 product startup. The remaining memory is left out as free memory available for VSP use. This is in addition to the memory taken up by HP-UX to boot on the VSP.
Hyperthreading is supported in individual vPars. The setboot command in individual vPars shows that HT is ON. You can turn on lcpu_attr in individual vPars using the kctune command. By default, lcpu_attr is OFF in the vPar (default behavior of HP-UX). Note that even when lcpu_attr is OFF in the VSP, each vPar can have its individual lcpu_attr enabled to get hyperthreading functionality in the vPar. As in previous releases, hyperthreading is not supported for VMs.
3 Installation procedures for HP-UX vPars and Integrity VM V6.1.5 This chapter describes the requirements and procedures for installing vPars and Integrity VM V6.1.5. The topics include: • Installing vPars and Integrity VM V6.1.5 • Bundle names • Verifying the installation • Removing vPars and Integrity VM V6.1.5 3.1 Installing vPars and Integrity VM V6.1.5 The following sections provide the installation procedures for vPars and Integrity VM V6.1.5. 3.1.1 vPars V6.1.
NOTE: Both ProviderSvcsBase and SysFaultMgmt are included in the WBEM Management bundle — https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do? productNumber=WBEMMgmtBundle 3.1.2 Installing vPars V6.1.5 vPars V6.1.5 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 September 2012 (AR1209) on the latest Intel® Itanium® 9500 processors.
Installation of HP-UX OE in a vPar from a boot media (DVD or ISO image file): Add the media as a virtual DVD to the vPar using the vparmodify command. Boot the vPar to EFI and select virtual disk to boot HP-UX. See the vPar Commands Manual to know how to specify and add a virtual DVD to a vPar V6.1.5. 7.
Table 7 Requirements for installing Integrity VM V6.1.5 (continued) Resource Description Disk storage Sufficient disk space for the following: • The VSP operating system (see the HP-UX 11i v2 Installation and Update Guide or HP-UX 11i v3 Installation and Update Guide) • The VSP software (130 MB) • Disk space for each guest operating system, including swap space NOTE: The VSP requires swap space only as recommended by HP-UX 11i v3. Otherwise, no swap space is required for Integrity VM.
The VSP and guest configuration files are stored at /var/opt/hpvm. The new configuration files are not compatible with those of previous versions of Integrity VM. Therefore, if you are upgrading to the current version, the guest configuration files (except the /ISO-Images/ directory) are saved to the /var/opt/hpvm/backups directory. If you revert to the older version of Integrity VM, you can use the backup configuration files to restore your VSP and guest configurations. 3. 4.
3.3 Inhibitors to installing HP-UX vPars and Integrity VM The following items block HP-UX vPars and Integrity VM Version 6.1.5 from installing: • Hierarchical Files System (HFS) files in the /etc/fstab file. You must remove any entries before installing Integrity VM. Check for these entries with the following command: # grep -i hfs /etc/fstab • HP System Insight Manager (HP SIM) Server bundle.
3.7 Troubleshooting installation problems If the installation verification succeed with warnings, report the problem using the procedures described in Chapter 13 (page 219). Some problems encountered in the process of installing Integrity VM are described in the following sections. 3.7.1 Error messages during installation One or more of the following messages might be displayed during Integrity VM installation: could not write monParams: Device is busy hpvmnet * already exists /sbin/init.
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.5 • Updating previous versions of the VSP 4.1 Upgrading the VSP from previous versions of Integrity VM V3.x to Integrity VM V6.1.5 The Integrity VM Version 6.1.5 VSP requires the HP-UX 11i v3 operating system. Only HP-UX 11i v2 servers running Integrity VM 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.5 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.5 (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.5 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 219), 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.
Once you have read the product release notes and verified that you have met the system requirements, install the Integrity VM software as described in this section. NOTE: Installing the vPars and Integrity VM software requires the system to reboot. Therefore, the swinstall command line installation includes the -x autoreboot=true parameter. If you have installed Integrity VM V4.3 with September Web Release (WEB1211) AVIO bundles, you must use the -x allow_downdate=true parameter.
... 4. Verify Integrity VM software after update-ux on the VSP: VSP -> swlist -l product | grep -i B.06.10.05 HPVM B.06.10.05 Integrity VM VMAGENT B.06.10.05 HP Resource Allocation Agent for Integrity vmGuestLib B.06.10.05 Integrity VM vmGuestLib vmGuestSW B.06.10 .05 Integrity VM vmGuestSW vmKernel B.06.10.05 Integrity VM vmKernel vmProvider B.06.10.05 WBEM Provider for Integrity VM vmProvider vmVirtProvider B.06.10.05 Integrity VM vmVirtProvider VSP -> swlist | grep -i B.06.10.05 BB068AA B.06.10.
< ram_max = 128G 30,31d32 < reserved_min = 32M < reserved_max = 128G 34,36d34 < ram_dyn_target_start = 8G < ram_dyn_min = 512M < ram_dyn_max = 8G 54 Upgrading the VSP from previous versions of Integrity VM
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.
5.3 NPIV – supported limits Table 9 (page 56) lists the supported limits associated with NPIV in vPars and Integrity VM V6.1.5 on 11i v3 guests. Table 9 NPIV supported limits in vPars and Integrity VM V6.1.
Driver-Firmware Dump Timestamp TYPE NPIV Supported Driver Version = = = = N/A PFC YES @(#) fcd B.11.31.
adaptertype The adapter type as seen in the vPar. For NPIV, the adaptor type is avio_stor. bus The PCI bus number for the virtual device and can range from 0 to 7. device The PCI slot number for the virtual device and can range from 0 to 7. 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.
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. 5.4 Migrating VM guests with NPIV HBAs V6.1.
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.1.
Table 10 Attributes of a virtual partition in vPars V6.1.5 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.5 (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.5 (continued) vPar attribute 64 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.
6.7 Reserved resources and resource over-commitment HP-UX vPars and Integrity VM V6.1.5 allows the reservation of resources for virtual machines and virtual partitions. Reservations imply that a resource will be available when it is needed, with the intention of assuring that a virtual machine or virtual partition can boot at any time.
When CPU or memory resources are overdrawn, either these resources must be brought back online, or reservations on existing virtual machines or virtual partitions must be reduced or removed. Resource reservations can be removed using the hpvmmodify -P name -x resources_reserved=false command. Memory reservations can be reduced by using the hpvmmodify -r option to reduce virtual machine or virtual partition memory size.
NOTE: IP_address_of_gateway is the IP address of gateway from the LAN domain of the vPar to the LAN domain of the Ignite server. network_mask is the netmask (in dotted notation) of the LAN to which vPar is connected. 3. Boot from the install kernel using the following command: lanboot select –dn mybootprofile 4. Follow the steps as prompted by the install kernel to install HP-UX 11i. 6.
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:avio_lan:0,1,0xF2AF8F8647BF:vswitch:vswitch1:portid:1 network:avio_lan:0,5,0x569FC1F96205:vswit
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 a 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 82) 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 103). 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 184). 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.
VSP system, the virtual machine is not allowed to start, and error messages provide detailed information about the problem. After you create a virtual machine, you can use the hpvmmodify command to add, remove, or modify storage devices for the virtual machine. To add a device to an existing virtual machine, include the -a option, the same way you would on an hpvmcreate command.
guest with the start_attr attribute set to auto, the startup order is based on a memory weight and a processor weight added together.
Table 12 Configuration Limits (continued) Description Support # pCPUs in VSP HP-UX limit Memory per VM — Minimum (HP-UX 11i v2) 1 GB Memory per VM — Minimum (HP-UX 11i v3) 2 GB or the minimum required for HP-UX 11i v3 to boot Memory per VM — Maximum (HP-UX) 128 GB # virtual SCSI devices / VM or vPar— Maximum 256 AVIO # virtual NICs / VM or vPar— Maximum 62 # virtual switches — Maximum 50 # virtual NICs / vswitch 511 # file backing store devices / VM or vPar — Maximum 30 # virtual AVIO st
1 The minimum memory requirement for HP-UX 11i v2 is 512 MB. The minimum memory requirement for HP-UX 11i v3 is 1 GB (see "System Requirements" section in the HP-UX 11i v3 Installation and Update Guide); however, the HP-UX 11i v3 Installation and Update Guide warns that cold installations with 1 GB or less memory might fail or take a long time to complete. Therefore, 2 GB is recommended for cold installations of HP-UX 11i v3.
Table 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 184).
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 either the HP-UX 11i v2 or HP-UX 11i v3 operating system on the virtual machine. Or you can install the HP-UX 11i v3 operating system on the vPar.
# hpvmconsole -P host1 vMP MAIN MENU CO: CM: CL: SL: VM: HE: X: Console Command Menu Console Log Show Event Logs Virtual Machine Menu Main Help Menu Exit Connection [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.
Enter BootOption Data Type [A-Ascii U-Unicode N-No BootOption] : Save changes to NVRAM [Y-Yes N-No]: 6. N 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.
# swlist BB068AA VirtualBase # Initializing... # 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.5 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.5 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.5 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 lunpath. 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.
PciBus | | |(Addr(Target Id) / 16) <-> HP-UX lun ID | | | | | V V V V V disk 49 0/0/2/0.6.1 esdisk CLAIMED DEVICE /dev/rdisk/disk7 /dev/rdisk/disk7 Acpi(PNP0A03,0)/Pci(2|0)/Scsi(Pun16,Lun0) ^ ^ ^ ^ | | | | PciBus | PCIFtn Addr(Target Id) | PciDev HP Virtual Disk In this example, exp1 / exp2 represents the quotient from exp1 divided by exp2 (integer division), and exp1 % exp2 finds modulo of exp1 divided by exp2 (that is, finds the remainder of an integer division). 2.
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.5, 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 NPIV devices, multipathing products run on the vPar or VM and not on the VSP. For supported multipathing configurations, see the HP-UX vPars and Integrity VM V6.1.5 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.
This section describes how to enter resource statements for use with the hpvmcreate command (described in Chapter 7) and the hpvmmodify command (described in Chapter 11). The resource statement specifies the virtual storage device that will be seen by the vPar/VM and how it maps to the physical storage device on the VSP.
storage:location where: • storage is one of the following: disk, lv, file, null, attach_path, 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.
Multipath products not using NPIV for storage resources must run on the VSP; multipath solutions without NPIV devices are not supported in a vPar/VM.With NPIV devices, the multipathing products can run on the vPar or VM guest itself. 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 120)). The resource statements in the following subsections do not contain vPar/VM hardware addressing.
When logical volumes are configured this way, you only have to keep track of the volume groups to prevent media conflicts. For information about tracking virtual media allocation, see Section 9.2.1.4 (page 121). 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.
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.
CD/DVD using the appropriate IN and EJ commands. When the media is loaded, proceed with the installation. NOTE: The hpvmmodify command might fail to change a Virtual FileDVD if the device has already been modified by the virtual console. The hpvmstatus command displays the current status of the Virtual FileDVD, which might not be in its original resource state. To see the original resource statement, which is required by the hpvmmodify command to change a Virtual FileDVD, use the hpvmstatus -D command. 9.2.
# 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.iso 29978624 Jul 11 18:51 0603-FOE-D2.iso The Virtual NullDVD resource statement is dvd:avio_stor::file:/var/opt/hpvm/ISO-images/hpux/. You can configure the Virtual NullDVD to be sharable or have multipath options.
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.
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. No multipath solutions are available for attached devices on the VSP. No multipath products are supported in the vPar/VM. Manage attached devices to prevent the wrong vPars/VMs from viewing sensitive information. You can display which vPars/VMs are currently using attached devices using the hpvmstatus command. 9.2.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. For example, to create an 80 GB file on an HP-UX NFS server as a guest backing store in the shared directory called /export, use either on of the following commands: /opt/hpvm/bin/hpvmdevmgmt -S 80G /export/vm1.boot /usr/bin/dd if=/dev/zero of=/export/vm1.
A captive virtual console account is a special-purpose user account created on the VSP for each guest administrator. These types of user accounts use /opt/hpvm/bin/hpvmconsole for a shell, and the desired guest's per-guest directory for a home directory. For virtual console access, the account also requires a password, and access to its associated guest. You create this account with the hpvmcreate, hpvmclone, or hpvmmodify command.
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. The guest administrator must understand how to maintain the guest OS, install patches and applications, and set up security for the guest users of the guest OS.
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.5 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 61). 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 on the VSP and on DIO interfaces in the guest. AVIO interfaces is not supported on the guest.
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 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.
◦ Replace a direct I/O function in a vPar or VM: # 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.
To view the NICs that support DIO on a VSP, use the command: vparhwmgmt -l -p dio (or hpvmhwmgmt -l -p dio ), which shows the DIO supported cards and the assignment level they support (device or function): # vparhwmgmt -l -p dio 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
hpnet priv_net 2 Up 3 Up Shared Shared lan0 lan1 0x1cc1de40d040 15.43.212.199 0x1cc1de40d044 # hpvmhwmgmt -l -p dio | grep 0/0/0/3/0/0/7 0/0/0/3/0/0/7 lan host HP PCIe 2-p 10GbE Built- device # 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.
clues as to why the function/device cannot be added to the pool.
10.6.1 Redefining pNICs for HP-UX guests Changing the hardware address of a vswitch has the same effect as moving a network adapter from one hardware slot to another on an HP Integrity system. Similar to other HP-UX systems, the guest file /etc/rc.config.d/netconf must be modified so that INTERFACE_NAME[0] reflects the new LAN PPA assigned by the HP-UX network driver on the first guest reboot after the modification.
# hpvmnet Name Number State Mode PPA MAC Address IP Address ======== ====== ======= ========= ====== ============== =============== localnet 21 Up Shared N/A N/A vmlan0 22 Up Shared lan0 0x00306ea72c0d 15.13.114.205 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.
match, whether they are physical systems or guests. The VSP does not check for MTU mismatches for its guests. • The lanadmin card specific options that are supported on igssn on the guest are: ◦ -x:speed,fctrl,cko,type,card_info,stats drv,vmtu,and drv_pr. ◦ -X:drv_pr_on,drv_pr_off,stats clear 10.
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.
3. Run hpvmhostrdev —u to add the underlying disks of the created SLVM volume groups into the device database as restricted devices. 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 170). 4. Execute the hpvmhostgdev -a command to ensure that all devices are populated in the gdev database.
You can resolve this problem in one of two ways: • 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.
The following examples show how to add various device types to the storage pool: • File: # hpvmdevmgmt -a gdev:/var/opt/hpmv/ISO-images/hpux/112350GOLD.
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.
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 : : : : 1 0 disk /dev/rdisk/disk4 [Network Interface Details] Interface : vswitch Adapter type : avio_lan Backing : sitelan Vswitch Port : 1 Bus : 0 Device : 1 Function : 0 Mac Address : ea-2a-7b-81-8e-19 [Direct I/O Interface Details] [Misc Interface Details] Device type : Adapter type : Physical Storage type : Physical Device : serial com1 tty console To display the VSP system resource, use the -s option to the hpvmstatus command.
11.5 Creating guest administrators and operators Integrity VM provides secure access to guest machine consoles. When you create the virtual machine, you can specify groups and user accounts to have administration or operator privileges on that guest. These users are allowed to log in to the VSP under their own user accounts and to use the hpvmconsole command to perform system administration tasks on the guest virtual machine.
# passwd host1 3. Use the hpvmmodify command to provide the user with guest administration privileges: #hpvmmodify -P winguest1 -u host1:admin A guest administrator can now access the host1 virtual console by using the ssh command or telnet command on the VSP and logging in to the host1 account. The guest administrator cannot use the su command. NOTE: For security reasons, HP strongly recommends that you do not include /opt/hpvm/bin/ hpvmconsole, the virtual console image, in /etc/shells.
11.5.2 vPars/VM user accounts The configuration for captive hpvmconsole guest user accounts supports additional access controls and configurations. This change requires that the guest user accounts have the correct home directory. To ensure that the user continues to have administrative console access, use the following command: # hpvmmodify -P compass1 -u compass1:admin 11.
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. -c command Specifies a machine console command to run on the virtual machine. -e echar Specifies an alternate interrupt character.
• hpvmclone -P guestname -K Remote-Console-IP-Address -L Remote-Console-Mask • hpvmcreate -P guestname -K Remote-Console-IP-Address -L Remote-Console-Mask • hpvmmodify -P guestname -K Remote-Console-IP-Address -L Remote-Console-Mask For example: # hpvmmodify -P guestname -K 16.92.81.68 -L 255.255.252.0 NOTE: Only IPv4 addresses are supported, not IPv6. The virtual iLO Remote Console IP address must be unique and different from both the Host IP address and the Guest IP address.
The username used to access and log into the virtual iLO Remote Console must have Guest Administrator/Operator privileges. The following example creates a guest administrator name guest1admin for the guest guest1. The hpvmmodify -u option is used to grant the guest administrator privilege: # # # # # useradd -d /var/opt/hpvm/guests/guest1 -c 'guest1 console' guest1admin passwd guest1admin hpvmmodify -P guest1 -u guest1admin:admin hpvmmodify –P pqsvm53 –K xxx.xxx.xxx.xxx –L xxx.xxx.xxx.xxx telnet xxx.xxx.
11.8 Guest configuration files When the guest is created, the VSP creates the guest configuration file /var/opt/hpvm/guests/guestname. Integrity VM creates up to three guest configuration files: • The vmm_config.current file contains the current guest configuration currently set. • The vmm_config.prev file contains the last known guest configuration settings. • The vmm_config.next file contains the configuration settings that have changed since the guest was started.
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 106). 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.5 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.
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 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.
12.2 Command line interface for online and offline migration To migrate a virtual machine to another VSP, perform the following steps: 1. 2. 3. Set up SSH keys on both the source and target hosts, as described in Section 12.3.3 (page 214). 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.
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: 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. If the hpvmmigrate command's network connectivity check continues to fail, verify the vswitch and network configuration, and test connectivity with the nwmgr command.
-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. For online migration, in addition to sharing the same LAN segment for normal guest connectivity, the VSPs should be connected with a private 1 GbE (or faster) network for efficient VSP–to-VSP communications and for secure guest memory transfer.
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.
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.
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.
• 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.
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. If you set up SSH security between VSPs before adding the conventional —hpvm-migr host alias to the /etc/hosts file and you do not run secsetup on the host-alias addresses, the hpvmmigrate command fails with the message, Host key verification failed, when it attempts to use the conventional host alias.
Network time-outs are especially troublesome for certain UDP applications that are not resilient enough to tolerate packets being delayed and dropped. If you run UDP applications that assume fast network packet turnaround, you might need to reduce the frozen phase time-out value, which might cause online migrations to abort more often. However, it will preserve the integrity of the network connections to the guest.
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 Rules for selecting physical HBA ports during migration with NPIV HBAs This section summarizes the rules that the hpvmmigrate command uses to decide upon the physical HBA port (pFC) on the target host on which a particular guest NPIV HBA is created after a guest migration. These rules are applicable for both offline as well as online migrations and for VM guests as well as vPars.
#hpvmmodify -P guestname -x runnable_status=enabled WARNING! Be very careful when marking a guest Runnable when it was previously Not Runnable. Make sure this guest is Not Runnable and definitely not actually running on any other VSP. 12.3.5 Restrictions and limitations of online VM migration Administrators should carefully configure certain aspects of VSPs and guests for online migration capability.
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.05 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 106). 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.
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 sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH. ERROR NAME The name of an error, usually returned in the errno variable.
15 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, please send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
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, 116 adding virtual storage, 138 admin privileges, 178 Administrator guest, 137 VSP, 135 APA, using, 146 applications running on guests, 20 running on VSP, 20 attachable devices specifying, 132 attached devices, 117 attached I/O, 111 Auto Port Aggregation see APA autoboot, 97 Automatic cell balancing, 81 automatic memory reallocation, 192 AVIO using, 17 B BL8x0c i2 support,server, 14 boot, 66 bundle names, 39 C CD/DVD burner, virtual, 111 characteristics of virtual machine
guest user, 138 guest-based VLANs, 158 guests, 15 local networks for, 149 log files, 193 managing, 169 monitoring, 174 removing, 101 running applications on, 20 GUID manager, 226 H hard reset, 68 hardware requirements, 37 HP-UX guests creating, 103 installing, 103 hpvmclone command, 96 options, 96 hpvmcollect command, 219, 222 options, 219, 222 hpvmconsole command, 153 options, 179, 181 using, 178 hpvmcreate command, 88 options, 90 hpvmdevmgmt command, 194 hpvminfo command, 40 hpvmmigrate command, 203 hpvm
ports VLAN, 156 power off, 68 privileges guest console, 178 problems reporting, 219 processing power allocating, 80 providing access to virtual consoles, 178 R re-creating vswitches, 151 recover nonresponsive, 75 recreate remove, 69 redefining pNICs, 165 related documentation, 226 remove vPars, 69 removing guests, 101 removing Integrity VM, 40 removing vNICs, 154 replacing devices, 196 reporting problems, 219 requirements for installing Integrity VM, 37 installation, 35 reset restart, 68 restricting device
configuration, 153 creating, 145 planning, 82 virtual NICs see vNICs Virtual NullDVD specifying, 131 virtual storage adding, 138 architectures, 110 attachable devices, 132 attached, 111 configuring, 118 deleting, 139 formulating resource statements, 125 I/O stack, 119 implementations, 116 introduction, 109 making changes to, 123 management, 121 modifying, 140 multipath solutions, 120 performance, 118 setting up, 123 shared, 110 specifying, 124 specifying FileDisk, 128 specifying Virtual Disk, 126 specifying
