Operating System - HP-UX
1847704 Members
5730 Online
110265 Solutions
New Discussion

extra <no Path> cpus at unbounded CPUs for vpar

 
kenken_3
Regular Advisor

extra <no Path> cpus at unbounded CPUs for vpar

Hi,

We have mixed hpux11.23 and hpux11.11 Vpars at the same napr. for my hpux11.11 vpar, I assigned 1 bounded and 3 unbounded CPUs. However, I noticed there are some extra cpus at the counting of unbounced CPUs.

Here is the output of the vparstatus -v -p vparname:
# vparstatus -v -p vparname
vparstatus: Warning: Command version is different from monitor version. Some fields may not be displayed.
[Virtual Partition Details]
Name: vparname
State: Up
OS Version: B.11.11
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 1/16
Bound by User [Path]:
Bound by Monitor [Path]: 2.10
Unbound [Path]: 2.12
2.13
2.14




[IO Details]
2.0.4
2.0.6
2.0.12
2.0.14
2.0.4.1.0.4.0.0.0.0.0.0.0 BOOT

[Memory Details]
Specified [Base /Range]:
(bytes) (MB)

Total Memory (MB): 12288

I try to use vparmodify -p vparname -m cpu::1 to reduce all the unbounded cpu first, but it gives me "vPar does not own enough non-CLP processors" error message.

anyone encounter this before?

thanks

wang & wang
3 REPLIES 3
likid0
Honored Contributor

Re: extra <no Path> cpus at unbounded CPUs for vpar

Hy,

You can try and directly remove the cpu you wan't, try with:

vparmodify -d cpu:2.14 -p PPINTE2

with vparstatus -d you can check how are your cpus spread, and their path

vPar does not own enough non-CLP processors, looks like you are triying to remove to many cell local processors, you need at least one.


Windows?, no thanks
kenken_3
Regular Advisor

Re: extra <no Path> cpus at unbounded CPUs for vpar

Orange, thanks.

Actually, I want to keep those 2.12, 2.13 and 2.14, but want to remove those CPUs since it allocates 6 unbound cpus from the vpar and I want to clear that.
wang & wang
likid0
Honored Contributor

Re: extra <no Path> cpus at unbounded CPUs for vpar

But with the command you are launching:

#vparmodify -p vparname -m cpu::1

You would leave the vpar only with one cpu.

Is that what you wan't to do?
Windows?, no thanks