vpar creation

[J Turner]

I have an rx8640 with a prtion 0.
I can boot to the mon and I can boot to EFI, I can boot to the nPars.
The vpar that is there returns an err 30 when I try to boot it.
I went to the mon and it shows the vpar has no cpus assigned to it.
Can someone help me get 1 vpar loaded on this partition.
I read the N partition Admin guide but I cant create a genisis partition because I have production running on partition 1

Thanks

[Geoff Wild · Accepted solution]

Uh....production on the npar????

Anyways, here's how I created vpars:

I used HW Path for CPU....


# swverify T1335CC


Set vpar mode:

# vparenv -m vPars
vparenv: Warning: The CLM EFI variable has a value 0 which is less than the minimum required. Setting the CLM EFI variable to the value 128.
vparenv: Warning: The ILM EFI variable has a value 0 which is less than the minimum required. Setting the ILM EFI variable to the value 128.



# vparenv
vparenv: The next boot mode setting is "vPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.
vparenv: Note: Any changes in the above settings will become effective
only after the next system reboot.
vparenv: Note: The maximum possible CLM granules per cell is 256.
vparenv: Note: The maximum possible ILM granules for this system is 1024.



# vparenv -g ilm:1024 -g clm:1024


# vparenv
vparenv: The next boot mode setting is "vPars".
vparenv: The ILM granule size setting is 1024.
vparenv: The CLM granule size setting is 1024.
vparenv: Note: Any changes in the above settings will become effective
only after the next system reboot.
vparenv: Note: The maximum possible CLM granules per cell is 256.
vparenv: Note: The maximum possible ILM granules for this system is 1024.


# vparcreate -p pcvp1101 \
-a cpu:::1:2 \
-a cpu:0.120 \
-a mem::8192 \
-g ilm:1024:y \
-g clm:1024:y \
-a io:0.0.8 \
-a io:0.0.10 \
-a io:0.0.12 \
-a io:0.0.0.2.0.6.0:BOOT
Authorizing allocation of CPUs. Please wait...
Capturing the Hardware path to EFI path mapping of bootable disks:
Done.
vparcreate: Note: Database is created with the following information:
CLM granularity is 1024 MBytes
ILM granularity is 1024 MBytes
All the subsequent virtual partition's CLM or ILM memory specifications must be an integral multiple of the corresponding granularity.




reboot




EFI Boot Manager ver 1.10 [14.61] Please select a boot option
OS might use only the primary console set via boot manager or conconfig command

HP-UX Primary Boot: 0/0/0/2/0.0x6.0x0
HP-UX HA Alternate Boot: 0/0/0/3/0.0x6.0x0
EFI Shell [Built-in]
Internal DVD (Upper) Cabinet 0 [Acpi(HWP0002,PNP0A03,0)/Pci(2|1)
SYS LAN 0 Cabinet 0 [Acpi(HWP0002,PNP0A03,0)/Pci(1|0)/Mac(001B78
Boot Option Maintenance Menu


Use ^ and v to change option(s). Use Enter to select an option
Use > and < to view long descriptions
Hot Key: 'S' or 's' to start the EFI Shell

Selected boot option: HP-UX Primary Boot: 0/0/0/2/0.0x6.0x0

Loading.: HP-UX Primary Boot: 0/0/0/2/0.0x6.0x0

Executing Image: "\EFI\HPUX\HPUX.EFI"
Optional Data : NONE

Starting: HP-UX Primary Boot: 0/0/0/2/0.0x6.0x0


(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.035

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix -lq
Seconds left till autoboot - 7
Type 'help' for help

HPUX> boot /stand/vpmon vparload -p pcvp1101


Create next vpar:


vparcreate -p pcvp1102 \
-a cpu::2 \
-a cpu:::2:4 \
-a cpu:0.122 \
-a cpu:0.123 \
-a mem::16384 \
-a io:0.0.14 \
-a io:0.0.6 \
-a io:0.0.4 \
-a io:0.0.14.1.0.4.0.3.8.0.1.3.0:BOOT



Create next vpar:

# vparcreate -p pcvp1103 \
-a cpu::2 \
-a cpu:::2:4 \
-a cpu:0.121 \
-a cpu:1.120 \
-a mem::16384 \
-a io:0.0.2 \
-a io:0.0.1 \
-a io:1.0.8 \
-a io:1.0.8.1.0.4.0.4.8.0.1.3.2:BOOT


# vparcreate -p pcvp1104 \
-a cpu::2 \
-a cpu:::2:4 \
-a cpu:1.122 \
-a cpu:1.123 \
-a mem::16384 \
-a io:1.0.10 \
-a io:1.0.12 \
-a io:1.0.14 \
-a io:1.0.10.1.0.4.0.3.8.0.1.3.4:BOOT


vparcreate -p pcvp1105 \
-a cpu::1 \
-a cpu:::1:2 \
-a cpu:1.121 \
-a io:1.0.6 \
-a io:1.0.4 \
-a io:1.0.2 \
-a mem::8192 \
-a io:1.0.2.1.0.4.0.4.8.0.1.3.6:BOOT

[J Turner]

All I have running now is the MON and the npar.
Can I do this from the Npar?

[Pupil_1]

You should have ur non-prod partition come up in the npar mode and then in the npar mode, use the vparcreate commands. In ur case if you see vparstatus o/p coming back with no cpu, you could add cpu with vparmodify -a cpu::1 -p .

I not sure if you could create a vpar without any cpu. what's the o/p of vparinfo from MON>

[J Turner]

vpar0 could not take ownership of module at 1/0/0.2.0.6.0 because it does not exist
vpar0 could not take ownership of module at 1/0/0.3.0.6.0 because it does not exist
vpar0 could not take ownership of module at 1/0 because it does not exist
vpar0 could not take ownership of module at 1/0/0.2.0.6.0.0.0 because it does not exist
MON> vparinfo
Names of the partitions in the database:
----------------------------------------

vpar0 (down)

Cell 0 total cpus 8 free cpus 8
Cell 3 total cpus 8 free cpus 8
The following CPUs are unassigned:
0/120 0/121 0/122 0/123 0/124 0/125 0/126 0/127 3/120 3/121 3/122 3/123 3/124 3/125 3/126 3/127
The following CPUs are disabled:

ILM Memory: total 64890 MB free 56698 MB
Cell 0 CLM Memory total 0 MB free 0 MB
Cell 3 CLM Memory total 0 MB free 0 MB

Available MEM RANGEs:
ILM : 0x0000000020000000-0x0000000037ffffff (393216 Kb)
ILM : 0x0000000038000000-0x000000003fefffff (130048 Kb)
ILM : 0x0000000100000000-0x0000000b4cdfffff (43202560 Kb)
ILM : 0x0000000b4cf00000-0x0000000b4fffffff (50176 Kb)
ILM : 0x0000000b50000000-0x0000000ff7ffffff (19529728 Kb)
ILM : 0x0000004040000000-0x00000040f7ffffff (3014656 Kb)
ILM : 0x00000040f8000000-0x00000040ffbfffff (126976 Kb)

Monitor Reserved MEM RANGE: 0x0000000000000000-0x0000000014d9bfff (341616 Kb)
Firmware Reserved MEM RANGE: 0x0000000014d9c000-0x0000000014e7dfff (904 Kb)
Monitor Reserved MEM RANGE: 0x0000000014e7e000-0x0000000014fd7fff (1384 Kb)
Firmware Reserved MEM RANGE: 0x0000000014fd8000-0x0000000017ffffff (49312 Kb)
Monitor Reserved MEM RANGE: 0x0000000018000000-0x000000001fffefff (131068 Kb)
Firmware Reserved MEM RANGE: 0x000000003fffe000-0x000000003fffffff (8 Kb)
Firmware Reserved MEM RANGE: 0x00000707fc000000-0x00000707ffffffff (65536 Kb)
Firmware Reserved MEM RANGE: 0x00000887fc000000-0x00000887ffffffff (65536 Kb)

[Geoff Wild]

Yes - everything prior to my "reboot" was done when the system was in npar mode.

BTW - it is good to document all your hardware and save it while in npar mode...things like:

ioscan-funC.disk.out
ioscan-kC-processor.out
inq.disks
ioscan-k-Bus-Adapter.out
ioscan-kfnC-tty.out

inq is a utility from EMC - as my storage is on EMC...

Rgds...Geoff

[J Turner]

I did this.
vparcreate -p vpar2 -a cpu::2 -a cpu:::2:4 -a mem::8092 -a io:3/0/0/2/0.6.0:BOOT -a io:3/0/0
booted to the mon and did a vparload -p vpar2 and got this.
vPar "vpar2" failed to load the kernel for either trying to boot an unsupported kernel in vPars environment or having incorrect vPars software installed on the boot device.
Error loading "vpar2". Shutting down "vpar2"...

Can I boot vpar2 to a lan so I can image it from the ignite server?

[J Turner]

MON> bootpath

Then go to nPars.vparmodify -p "vparname" -a io:0/0/0/2/0.6.0:BOOT

It works