vpar - how to boot from previous kernel

[f. halili]

I made a mistake after kconfig -i. How can i boot from previous kernel of the vpar?

[Michael Steele_2 · Accepted solution]

vparload -p winona2 -b /stand/vmunix.prev

[Steven E. Protter]

Shalom,

Both EFI and the PA-RISC equivalent have interactive boot options.

http://docs.hp.com/en/T1335-90001/T1335-90001.pdf

See page 26 boot section.

Boot Sequence: The Details
With or without vPars, the firmware loads and launches ISL.
ISL>
In a computer without vPars, at the ISL prompt, the secondary system
loader hpux loads the kernel /stand/vmunix:
ISL> hpux /stand/vmunix


So if you are PA-RISC looks like you just run

hpux /stand/vmunix.prev
Or whatever you named the last one.

Itanium:
http://docs.hp.com/en/T1335-90051/T1335-90051.pdf

See page 33.

EFI prompt.

SEP

[f. halili]

I tried:

MON> vparload -p myhost -b /stand/vmunix.prev


And I'm getting below:

[MON]
vPar "myhost" failed to load the kernel due to: non-bootable boot media; incorrect vPars software installed; or incorrect boot media EFI path in vPars database.
Try using "vparload -p rmyhost -E 0" to load the vPar.
Error loading "rtiimga". Shutting down "rtiimga"...
[MON] myhost has halted.

Thanks,
f. halili

[Steven E. Protter]

Sorry.

8. Launch HP-UX from the EFI shell prompt:
Shell> fsN:
fsN:\> efi\hpux\hpux boot vmunix


Gave you the wrong page number.

SEP

[f. halili]

Oh... I have HPUX 11.31 and Itanium.

[Raj D.]

f.halili,

-How many vpar do you have.

If you have two vpar, Can you boot using : MON:> vparload -all

- Then logon to the working vpar and try starting the 2nd vpar , using
# vparboot -p 2nd_vpar_name -b /stand/vmunix.prev


- Do you have vparstaus -v output , taken earlier, or dp you know the boot path of the vpar.
- ALso if you dont interupt the normal boot process what error message you are getting.


Hth,
Raj.

[Don Morris_1]

This is v3 -- not v1. You need to boot a backup configuration, not just a vmunix.

So, the vparload command as given is right -- but target /stand/backup/vmunix or the like. (backup is usually created by the kc tools unless you tell it not to, so that's my best guess... last_install may be there if you never cleaned it up, other than that I'd be guessing as to what configurations you have available).

It would help to know what's causing the problem with the configuration you made a mistake with.... it is not booting at all? If so, what's the error? (missing driver would need an alternate kernel, wrong tunable setting and you could use the -o option to vparload to set tunable values on the boot command line).

[Michael Steele_2]

Well, you can try:

vparload -p winona2 -B 0.8.0.0.2.0 (* where the HW path is the alternate path *)

...but I think your vpdb is corrupt. Fortunately, in integrity a vpdb.backup is kept. So you can try:

MON> readdb /stand/vpdb.backup

And then retry the vparload's.

See attached Vpar Admin Guide for additional help.

[f. halili]

thanks