vpars

[Jose F Rodriguez-Garcia]

need to see the isl come up when i do a reboot on a vpar so that i can interrupt the boot prcess to boot from tape

[Torsten. · Accepted solution]

This is the wrong idea - it is working different (did you read the manual?).

1) supported for PA-RISC systems.
2) add the tape to the vPar

# vparmodify -p winona2 -a io:1/0/14/0/0/4/0.5.0:TAPE

3) boot from tape

winona1# vparboot -p winona2 -B TAPE

4) assign points ;-)

[Jose F Rodriguez-Garcia]

sorry about that
did a vparboot and the system came back with
failed to patch new partition's kernal
don't you have to specify the path of the kernal on tape
if so how can you read the contents of the tape?

[Torsten.]

I did not understand your problem.

Please post the command you run and the result you get.

What do you want to do?

[Jose F Rodriguez-Garcia]

i want to be able to boot from an existing ignite boot tape to reload the vpar from the tape

[Torsten.]

I wrote the steps in my first post.

Is the tape taken from a vPar?

Is the system a PA-RISC (run "model")?

[Jose F Rodriguez-Garcia]

the command I am entering is
vparmodify -p vpar14 -a io:3/03/1/0/4/1.3.0:TAPE
vparboot -p vpar14 -BTAPE

the result is
vpar14 booting......
failed to patch new partition's kernal
{MON}vpar14 has halted

[Jose F Rodriguez-Garcia]

just found out that the tape was takened from a stand alone RP4440

[Torsten.]

You just found the reason, I guess.

The backup must include vPar support in the kernel.

[Jose F Rodriguez-Garcia]

how do you include support of vpar on a tape kernal?

[Torsten.]

You have 2 options:

1) install the vPar software on the source system (this will build a vPars aware kernel - this is what you need). But I'm not sure if you can install the software on your rp4440, because this system is not supported.

2) Shutdown your target system completely. Restore the image in a non-vPar environment. Install the vPar software to build a new "relocateable" kernel. Boot the vPar environment.

[whiteknight]

Hi Jose,

Failed to patch new partition's kernel
reason
------
the kernel that was build does not contain vpar.

check with
# what /stand/vmunix | grep vpar
(this should return nothing if the product is not in the kernel)

check wether you have vpar and vpar_driver in /stand/system.
#grep vpar /stand/system
(should return nothing as well)

WK
please assign points