| Normally, we don't interact directly with vpmon ; it is loaded in memory, managing all vPar resources, but ostensibly not a visible resource within an individual partition. In some instances, we may want to interact with vpmon in order to boot individual vPars to investigate a problem that is not allowing a specific vPar to boot. We can interact with vpmon by either halting all of our existing vPars or by interacting with ISL and stipulating that hpux should only load vpmon and nothing else:
Main Menu: Enter command or menu > bo pri Primary Boot Path: 2/0/1/0/0.0 Do you wish to stop at the ISL prompt prior to booting? (y/n) >> y Initializing boot Device. Boot IO Dependent Code (IODC) Revision 0 Boot Path Initialized. HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL> ISL> hpux /stand/vpmon Boot : disk(2/0/1/0/0.0.0.0.0.0.0;0)/stand/vpmon 614400 + 168736 + 16898800 start 0x23000 Welcome to VPMON (type '?' for a list of commands) MON> ? Supported Commands: ? Print list of commands cat Dump contents of file to screen cbuf Dump contents of console buffer getauto Print the AUTO file help Print list of commands lifls List files in LIF directory log View the event log ls List files in a directory readdb Read a partition DB reboot Reboot system scan Scan the system toddriftreset Reset the TOD drift of all vpars vparload Load vPar vparinfo Display vPar info bootpath Display monitor boot path MON>
From here we can issue commands such as vparinfo and ls to investigate the underlying vPar configuration.
MON> vparinfo Resources not assigned to any partition ------------------------------------- 2 0xfffffffffc200000 1 0 TYPE=14 SV_MODEL=170 2/0 0xfffffff848000000 1 0 TYPE= 7 SV_MODEL= 12 2/5 0xfffffffffc205000 1 0 TYPE= 1 SV_MODEL= 9 2/11 0xfffffffffc27a000 1 0 TYPE= 0 SV_MODEL= 4 2/13 0xfffffffffc27e000 1 0 TYPE= 0 SV_MODEL= 4 Names of the partitions in the database: ---------------------------------------- vPar0 (down) vPar1 (down) Available Free Memory: 0 MB Available MEM RANGE: 0x0000000000000000-0x00000000ffffffff (4194304 Kb) MON> MON> bootpath disk(2/0/1/0/0.0.0.0.0.0.0) MON> getauto hpux /stand/vpmon -a MON> ls -l drwxr-xr-x 2 0 0 65536 lost+found -rw-r--r-- 1 0 3 4948 ioconfig -rw-r--r-- 1 0 3 19 bootconf -r--r--r-- 1 0 3 1063 system drwxr-xr-x 2 0 3 1024 krs drwxr-xr-x 2 0 3 1024 system.d drwxr-xr-x 4 0 3 2048 build -rwxr-xr-x 1 0 0 28133624 vmunix drwxrwxrwx 5 0 0 1024 dlkm -r--r--r-- 1 0 3 82 kernrel -rw------- 1 0 0 12 rootconf drwxr-xr-x 2 0 0 1024 krs_tmp drwxr-xr-x 2 0 0 1024 krs_lkg -r--r--r-- 1 0 3 1058 system.prev drwxrwxrwx 5 0 3 1024 dlkm.vmunix.prev -rwxr-xr-x 1 0 3 27239144 vmunix.prev -r-xr-xr-x 1 2 2 1062320 vpmon -rw------- 1 0 0 17813008 vpmon.dmp -rw------- 1 0 0 8232 vpdb MON>
We can decide to load a specific vPar from vpmon using the vparload command. If we want to boot a Virtual Partition using a specific boot method, e.g., single user mode, we use the “o <boot option> option to vparload ; these are effectively the options we would pass to the hpux secondary loader. Should we need to boot from a different kernel, we use the “b <kernel> option to vparload :
MON> vparload -p vPar0 -o "-is" -b /stand/vmunix [MON] Booting vPar0... [MON] Console client set to vPar0 [MON] Console server set to vPar0 [vPar0] [MON] vPar0 loaded gate64: sysvec_vaddr = 0xc0002000 for 2 pages NOTICE: nfs3_link(): File system was registered at index 3. NOTICE: autofs_link(): File system was registered at index 6. NOTICE: cachefs_link(): File system was registered at index 7. td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 2/0/12/0/0 fddi4: INITIALIZING: 0150 PCI FDDI card in slot 2/0/10/0/0 Entering cifs_init... Initialization finished successfully... slot is 9 Host is virtual System Console slave Logical volume 64, 0x3 configured as ROOT Logical volume 64, 0x2 configured as SWAP Logical volume 64, 0x2 configured as DUMP Swap device table: (start & size given in 512-byte blocks) entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608 read_ss_nvm: Cannot validate NVM - -2 Starting the STREAMS daemons-phase 1 System Console is virtual Checking root file system. log replay in progress replay complete - marking super-block as CLEAN Root check done. Create STCP device files Starting the STREAMS daemons-phase 2 $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw  for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $ Memory Information: physical page size = 4096 bytes, logical page size = 4096 bytes Physical: 2086912 Kbytes, lockable: 1565460 Kbytes, available: 1801848 Kbytes /sbin/ioinitrc: /sbin/krs_sysinit: INIT: Overriding default level with level 's' INIT: SINGLE USER MODE INIT: Running /sbin/sh #
| NOTE : After you install the Virtual Partitions software, your kernel is now relocatable to an address controlled by vpmon . This is in stark contrast to your old kernel. It is strongly advised that you make a backup copy of your kernel after you install the Virtual Partitions software. If you don't, and you try to boot from your vmunix.prev file, you will get the following error message:
MON> vparload -p vPar0 -o "-is" -b /stand/vmunix.prev [MON] Booting vPar0... Kernel file is not relocatable for vPar0 File address is 0x0000000000020000 and memory address is 0x0000000004000000 Failed to load (2/0/1/0/0.0.0;)/stand/vmunix.prev [MON] vPar0 has halted. MON>
|
Now that we are in single user mode, we can effect any changes as necessary, e.g., fixing a broken kernel or repairing a broken vg00 (use the option “o “lm to vparload to boot in maintenance mode). | 