vPAR Consoles hung, cannot cycle through with Control A

[Chris Magargee_2]

We have the following vPAR Environment set up:

rp8440 - Alls cells are of part of one nPAR.
Admin vPAR running 11.31 with vPAR SW version A.05.04.01.
Three (3) vPARs running 11.11 with vPAR SW version A.03.05.07.

All the current vPARs are functioning properly.

I am trying to create a new 11.11 vPAR and after the first boot of the Ignite process I get the following error message on the console:

[MON]
Rebooting ...press any key within 10 seconds to stop boot
[MON] Booting ...
Kernel file is not relocatable for
File address is 0x0000000000020000 and memory address is 0x0000000028000000
Error reading program segments
Failed to load (0/0/6/1/0/4/0.1.79.0.9.6.5;)/stand/vmunix
Failed to load

After this point the Control A no longer functions and I cannot scroll through the other 4 vPARs and VPMON consoles.

Now I have pretty much figured out I have an issue with my Ignite process, but why would it lockup the consoles?

The first time this occurred I tried to bounce the Admin vPAR (the original nPAR OS instance) to see if that would restart VPMON, no luck. I had to finally shutdown all the active vPARs, reboot VPMON, and then bring back up all the vPARs. Of course after that the Control A was working again until I re-ran the Ignite on the new vPAR and it hung the consoles one more time.

Is there anyway to restart VPMON itself without bringing down all the active vPARs? I need to debug my Ignite process, but it gets complicated if the consoles hang every time it tries to boot and then I have to coordinate downtime with the folks using the active ones.

Thanks!
Chris

[Torsten.]

The problem is you are trying to boot a non-vPars instance (OS without vPars software) in a vPars machine.

You should never do this.

Logon to another vPar directly and check what the status is now.

[Chris Magargee_2]

Ah, so you are saying my Ignite process is not adding in the vPAR SW package? I have that as part of configuration files to add the vPAR SW package from the Depot during the Ignite. I will check to make sure it doing it.

As for my main question, do you know anyway to reboot VPMON without bringing everything down?

[Torsten. · Accepted solution]

You cannot reboot the vpmon, but load only after an nPar reset.


This message

Kernel file is not relocatable

indicates that vPar software isn't there (kernel is not vPars aware).

[Chris Magargee_2]

Yep, I checked the Ignite log for the client and it failed to install the vPAR SW packages. So I need to fix that and hopefully the next go through it comes up and does not hang the consoles.

So I can assume that when I try to boot a non-vPAR enable OS it will cause issues with VPMON, which in turn can hang the consoles. Plus I have to bring everyone down to restart VPMON, bummer.

Thanks for the help! Points to awarded.

Chris