Adding Resources to VPars

[Pete Randall]

(yes, I know this should probably go in the "virtualization" category - but I want to make sure it's seen for a moment or two before banishment)

I'm adding some resources (two additional processors and 8Gb RAMM) to a machine that is set up to run two VPars. Right now, one VPar has 1 Gb of memory and one processor - the other has the remaining 7Gb of memory and the remaining 3 processors.

I want to increase each partition by one processor and X amount of memory. My initial research says that I should interrupt the boot process and load vpmon from the ISL prompt. Then I can run the vparmodify command to make my changes so it would look like this

ISL > hpux /stand/vpmon
vparmodify -p part1 -m cpu::2
vparmodify -p part1 -m mem::2048
vparmodify -p part2 -m cpu::4
vparmodify -p part2 -m mem::14336

What do you think? Any suggestions? Comments? Critiques? Flames?

Details:

# model
9000/800/rp7410
# uname -r
B.11.11
# vparstatus -V
Version 1.1


Pete

[Turgay Cavdar]

Hi Pete,
You can do CPU changes online, no need to shutdown the servers.You can also use:
vparmodify -p part1 -a cpu::1

For RAM addition, shutdown part2, then run vparmodify command from part1:
vparmodify -p part2 -m mem::14336

Boot part2,then shutdown part1, run the command from part2:
vparmodify -p part1 -m mem::2048

Finally boot part1.

[Pete Randall]

Turgay,

Thanks. I'm aware that I could do this online but I should point out that the server is going to be down anyway!


Pete

[Torsten.]

Since this is a RISC machine, you should at least boot 1 partition (vpar). Do the modifications from the running vPar to the downed partitions (check maximum CPU settings too). Then boot them. If needed, do the same with the first vPar (shutdown, modify, boot).

[Pete Randall]

OK, but why?

[Torsten.]

Sorry, why what?

[Pete Randall]

Why " Since this is a RISC machine, you should at least boot 1 partition (vpar). Do the modifications from the running vPar".?

What difference does it make whether I do it from vpmon or a running machine and why does the fact that it's a RISC machine make any difference to anything?

[Turgay Cavdar · Accepted solution]

Hi Pete,
You cant run vparmodify from vpmon. Is ih hp-ux command, in order to run vparmodify at least one hp-ux should alive.

[Torsten.]

You cannot do modifications directly from vpmon.

On (most) Integrities you need to boot to nPars mode after adding CPU/RAM. This is not needed on RISC machines. If an Integrity is on nPars mode, you can do the modifications from there.

For all such modifications in vPars mode 1 vPars must be up (always). The vPar to be modified must be down (unless you have dynamic RAM or CPU).

[Pete Randall]

Ahhhh! That would make sense. The book I'm working from *seemed* to suggest that vparmodify could be run from vpmon. If that's not the case then I have no choice.

[Torsten.]

It would be a good idea to integrate the vpmon directly into the firmware - probably - with a possibility to do modifications from the MP or whatever...

But this is just an idea.

But since this is not reality, you need to do the mentioned steps...

[Steven E. Protter]

Shalom,

Your plan looks fine. If the CPU's are not bound, they can be moved about without bringing the system down.

Alas, sadly, memory can not be moved around that way.

My experience with with both PA-RISC (rp8420)
and IA-64(dome) vpar/npar, 11.11,11.23,11.31

SEP

[Pete Randall]

OK - that went half well. I was able to assign the memory without any problems but when I tried to increase the number of processors I got an error. Details:

root# vparstatus -p sire -v
[Virtual Partition Details]
Name: sire
State: Up
Attributes: Dynamic,Autoboot
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 1/6
Bound by User [Path]:
Bound by Monitor [Path]: 1.10
Unbound [Path]:

[IO Details]
1.0.1
1.0.10
1.0.12
1.0.1.0.0.1.1.6.0.0.0.0.0 BOOT

[Memory Details]
Specified [Base /Range]:
(bytes) (MB)
Total Memory (MB): 2048
root# vparmodify -p sire -m cpu::2
vparmodify: Error: "-m cpu::2": Operation requires the full version of virtual partitions.
root#


Admittedly, my version of vPars is ancient, possibly even the very first (freebie) one:

vParManager B.11.11.01.02 Virtual Partition Manager for HP-UX

Does this mean I'm going to have to upgrade my vPar version just to change the number of cpu(s)? If I was starting from scratch I could put 4 cpus into one par and 2 into the other. Why can't I modify it?


Pete

[Turgay Cavdar]

Can you send "vparstatus -P" and "vparstatus -A" "vparstatus -vp vpa_name" outputs. man vparstatus says that "vparstatus -V" shows version number of the vparstatus output,not vpar version.


Is your vpar is down while adding the CPU(may be it is required for this non-full version)?

[Pete Randall]

Yes, the vPar was down - as we discussed in the first part of this question - brought one par up, attempted to modify the other - got error.

Here's the requested outputs:

# vparstatus -p sire -P
vparstatus: Error: Invalid option -P.

the vparstatus -vp was already posted


# vparstatus -A
[Unbound CPUs (path)]: 1.11
1.12
[Available CPUs]: 2

[Available I/O devices (path)]: 1.0.2
1.0.4
1.0.6
1.0.8
1.0.14

[Unbound memory (Base /Range)]:
(bytes) (MB)
[Available memory (MB)]: 0



Pete

[Turgay Cavdar]

Hi,
I mean:
# vparstatus -P



Have you tried to add by giving specific CPU?
# vparmodify -p sire -a cpu:1.11

[Pete Randall]

vparstatus -P
vparstatus: Error: Invalid option -P.

No, I haven't tried to add a particular CPU and won't be albe to until I can down the machine. Since getting downtime is difficult, I would like to have a firmer answer rather than just "something to try".


Pete

[Torsten.]

"-P" prints the product version, e.g.

vparstatus -P
Commands product information: A.04.06
Monitor product information: A.04.06

But this option came later.


Please use

# swlist | grep -i "Virtual Partitions"

to get the version.

Example:

T1335AC A.03.05.07 HP-UX Virtual Partitions

[Pete Randall]

# swlist | grep -i "Virtual Partitions"
VPARSBASE A.02.02.00 HP-UX Virtual Partitions - Base Version


Pete

[Steven E. Protter]

Shalom,

Pete, you should not have to give a specific cpu. You are of course welcome for resource management reasons to try, but based on my recent experience with vpar, you will get the same response as you did when you did not specify the cpu.

I know lab environment is tough to come by, but you might benefit from getting the latest version of vpar for 11.11 and planning a downtime to do that upgrade and CPU assignment as planned earlier.



SEP

[Pete Randall]

That's kind of my last resort, Steve. I don't want to but if nothing else works.

My problem at this point is trying to find the time to do the research to find out the way to accomplish this. If I could just figure out how to clear out the vpmon db file and start from scratch there, then I wouldn't have to try to modify.


Pete

[Pete Randall]

I think I've found my answer (whether I like it or not).

In the documentation I have, under Supported Systems and Requirements, it says:

The VPARBASE product provides the capability for creating 2 virtual partitions, of which one virtual partition has only 1 CPU.

That pretty well eliminates any chance of my 4 CPU/1 CPU configuration. I guess it's time to contemplate upgrade.


Pete

[Torsten.]

Pete, your version is out of support since 2005 - by the way.

[Pete Randall]

Yeah, I know, Torsten. We used the freebie version because the bean counters wouldn't let us spend any more money. We subsequently got a license and have had updates arrive periodically but I've never installed because (number 1) it's a production machine and (number 2) it's been working just fine.

I just didn't do a good enough job of checking requirements for adding the processors.


Pete

[Pete Randall]

I just noticed in my previous post that I called it a 4 cpu/1 cpu configuration. I wouldn't want to confuse anyone. That should have read 4/2.


Pete