3.6 Booting a Newly Created vPar from an
Ignite
-UX Server
I am now going to create my second Virtual Partition using the design specifications I created earlier:
root @uksd3 #
vparcreate -p vPar1 -a cpu::2 -a cpu:::1:2 -a cpu:2/12 -a mem::2048
-a io:2/0/4 -a io:2/0/6 -a io:2/0/9 -a io:2/0/8 -a io:2/0/4/0/0.8.0:BOOT
root @uksd3 #
vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================ ===== ========== ========================= =====
vPar0 Up Dyn,Auto /stand/vmunix
vPar1
Down
Dyn,Auto /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num Memory (MB)
CPU Bound/ IO # Ranges/
Virtual Partition Name Min/Max Unbound devs Total MB Total MB
============================== ================ ==== ====================
vPar0 1/ 2 1 1 10 0/ 0 2048
vPar1 1/ 2 1 1 5 0/ 0 2048
root @uksd3 #
We can see that this Virtual Partition is currently
down
. This is to be expected, as the
next
task I need to perform is to install the software onto the boot disk for this vPar. The problem that may become apparent is that there is no BCH interface for this vPar. The BCH interface pertains to the original server/nPar. Consequently, I need to use the
vparboot
command to boot the
subsequent
vPars from the Ignite-UX server. Once
booted
, we should navigate to the console for this partition (accessed via the system console and using the
ctrl-a
key sequence) and continue with the installation of HP-UX.
root @uksd3 #
vparboot -p vPar1 -I hpwin050,/opt/ignite/boot/WINSTALL
vparboot: Booting vPar1. Please wait...
root @uksd3 #
root @uksd3 #
[MON] vPar1 loaded
root @uksd3 #
<ctrl-a>
[vPar1]
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 4.
NOTICE: autofs_link(): File system was registered at index 6.
NOTICE: cachefs_link(): File system was registered at index 7.
Host is virtual System Console slave
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
read_ss_nvm: Cannot validate NVM - -2
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'V
w 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: 2013184 Kbytes, lockable: 1490464 Kbytes, available: 1727340 Kbytes
======= 11/05/03 21:19:27 EST HP-UX Installation Initialization. (Wed Nov 05 21:19:27
EST 2003)
@(#) Ignite-UX Revision B.4.4.29
@(#) install/init (opt) $Revision: 10.277 $
* Scanning system for IO devices...
System Console is virtual
* Querying disk device: 2/0/4/0/0.8.0 ...
* Querying disk device: 2/0/4/0/0.10.0 ...
NOTE: Default (boot) source does not appear to be a valid (or complete)
install source, switching source to Network
* Setting keyboard language.
NOTE:
The console firmware terminal type is currently set to "vt100". If you
are using any other type of terminal you will see "garbage" on the
screen following this message.
If this is the case, you will need to either change the terminal type
set in the firmware via GSP (if your GSP firmware version supports
this feature), or change your terminal emulation to match the
firmware. In either case you will need to restart if your terminal and
the firmware terminal type do not match.
Press the 'b' key if you want to reboot now.
Welcome to Ignite-UX!
Use the <tab> key to navigate between fields, and the arrow keys
within fields. Use the <return/enter> key to select an item.
Use the <return/enter> or <space-bar> to pop-up a choices list. If the
menus are not clear, select the "Help" item for more information.
Hardware Summary: System Model: 9000/800/SD32000
+---------------------+----------------+-------------------+ [ S
c
an Again ]
Disks: 2 ( 67.8GB) Floppies: 0 LAN cards: 1
CD/DVDs: 0 Tapes: 0 Memory: 1966Mb
Graphics Ports: 0 IO Buses: 3 CPUs: 3 [ H/W
D
etails ]
+---------------------+----------------+-------------------+
[
I
nstall HP-UX ]
[
R
un a Recovery Shell ]
[
A
dvanced Options ]
[ Re
b
oot ] [
H
elp ]
We are using the
vparboot
command to instigate the installation of HP-UX. Subsequent boots for this vPar will normally be handled by
vpmon
. The other times we use
vparboot
are when a vPar is in a
down
state (after issuing a command such as
shutdown “h
) and we want to restart HP-UX.
As with any installation, setting up the Operating System and third party software on a Virtual Partition can take some considerable time. Once we have installed HP-UX, the Virtual Partition software, all relevant patches and all relevant third-party applications, each Virtual Partition will function in the same way as any standard HP-UX server.
root @uksd5 #
vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================ ===== ========== ========================= =====
vPar0 Up Dyn,Auto /stand/vmunix
vPar1 Up Dyn,Auto /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num Memory (MB)
CPU Bound/ IO # Ranges/
Virtual Partition Name Min/Max Unbound devs Total MB Total MB
============================== ================ ==== ====================
vPar0 1/ 2 1 1 10 0/ 0 2048
vPar1 1/ 2 1 1 5 0/ 0 2048
root @uksd5 #
As we can see, our second partition is now up and running. We can also check which processors are visible to this partition, as well as which processors have been allocated.
root @uksd5 #
ioscan -fnkC processor
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
processor 0 2/11 processor CLAIMED PROCESSOR Processor
processor 1 2/12 processor CLAIMED PROCESSOR Processor
processor 2 2/13 processor CLAIMED PROCESSOR Processor
root @uksd5 #
Again, this makes some kind of sense, as the kernel can see
bound
as well as
all
unbound
processors.
root @uksd5 #
vparstatus -vp vPar1
[Virtual Partition Details]
Name: vPar1
State: Up
Attributes: Dynamic,Autoboot
Kernel Path: /stand/vmunix
Boot Opts:
[CPU Details]
Min/Max: 1/2
Bound by User [Path]: 2.12
Bound by Monitor [Path]:
Unbound [Path]: 2.13
[IO Details]
2.0.4
2.0.6
2.0.9
2.0.8
2.0.4.0.0.8.0 BOOT
[Memory Details]
Specified [Base /Range]:
(bytes) (MB)
Total Memory (MB): 2048
root @uksd5 #
Here we can confirm which processors have actually been allocated to this partition. We can now move on and discuss managing Virtual Partitions.
|