Vpar無法啟動,報"No memory range to load kernel"請問是怎么回事??

tianxiay2ren

自從修改了每個vpar的CLM和ILM之后,除第一個以外的vpar就都無法啟動了.
哪位仁兄幫小弟看看是怎么回事唄?
有點急,在線等
====================================
具體信息如下:

SD上的一個Npar上,建立了8個vpar.
第一個vpar可以啟動,信息如下:

# vparstatus -p 019 -v
[Virtual Partition Details]
Name:         019
State:        Up
OS Version:   B.11.31
Attributes:   Dynamic,Autoboot,Nosearch
Kernel Path:  /stand/vmunix
Boot Opts:   

[CPU Details]
Min/Max:  1/64
User assigned [Path]:  
Boot processor [Path]:  0.11
Monitor assigned [Path]:  0.12
                          0.13
                          0.14

Non-cell-specific:
  User assigned [Count]:     0
  Monitor assigned [Count]:  4
Cell-specific [Count]:  Cell ID/Count
                         <none>

[IO Details]
   0.0.8
   0.0.9
   0.0.8.1.1.8.0.0.0.0.0 BOOT

[Memory Details]
ILM, user-assigned [Base  /Range]:  
                   (bytes) (MB)     
ILM, monitor-assigned [Base  /Range]:  0x40000000/2048
                      (bytes) (MB)     0x100000000/8192
ILM Total (MB):  10240  (Floating 0)

ILM Granularity (MB):  1024

CLM, user-assigned [CellID Base  /Range]:  
                          (bytes) (MB)     
CLM, monitor-assigned [CellID Base  /Range]:  0 0x70600000000/4096
                             (bytes) (MB)     1 0x72600000000/2048
CLM (CellID MB):  0 4096  (Floating 0)
                  1 2048  (Floating 0)

CLM Granularity (MB):  1024

[OL* Details]
Sequence ID: N/A

Operation: N/A

Status: N/A

=======================================

但其他vpar都無法啟動.啟動第二個vpar時的報錯信息如下:
# vparboot -p 020     
vparboot: Booting 020.  Please wait...
# No memory range to load kernel 020
Error reading program segments
Failed to load (1/0/9/1/0/4/1.0.0.0.0.0.0/stand/vmunix
[MON] 020 has halted.

=======================================

第二個vpar的詳細信息如下:
vparstatus -p 020 -v
[Virtual Partition Details]
Name:         020
State:        Down
OS Version:   Unknown
Attributes:   Dynamic,Autoboot,Nosearch
Kernel Path:  /stand/vmunix
Boot Opts:   

[CPU Details]
Min/Max:  1/64
User assigned [Path]:  
Boot processor [Path]:  
Monitor assigned [Path]:  <no path>
                          <no path>
                          <no path>
                          <no path>
                          <no path>
                          <no path>

Non-cell-specific:
  User assigned [Count]:     0
  Monitor assigned [Count]:  6
Cell-specific [Count]:  Cell ID/Count
                         <none>

[IO Details]
   0.0.1
   0.0.3
   0.0.14
   1.0.9
   2.0.1
   2.0.9
   2.0.10
   1.0.9.1.0.4.1.0.0.0.0.0.0 BOOT

[Memory Details]
ILM, user-assigned [Base  /Range]:  
                   (bytes) (MB)     
ILM, monitor-assigned [Base  /Range]:  
                      (bytes) (MB)     
ILM Total (MB):  18432  (Floating 0)

ILM Granularity (MB):  1024

CLM, user-assigned [CellID Base  /Range]:  
                          (bytes) (MB)     
CLM, monitor-assigned [CellID Base  /Range]:  
                             (bytes) (MB)     
CLM (CellID MB):  1 2048  (Floating 0)
                  2 4096  (Floating 0)

CLM Granularity (MB):  1024

[OL* Details]
Sequence ID: N/A

Operation: N/A

Status: N/A

tianxiay2ren

難道都不會嗎?

hetg407

The following is an excerpt from the HP-UX Virtual Partitions Administrator's Guide :

(PA-RISC only) Excluding the first granule, a portion of which is used by the Monitor, there must be at least one entire granule that exists below the 2 GB limit for each virtual partition. At least one granule below 2 GB is needed for the kernel in each virtual partition.