vPars not booting in Superdome2

[lampscholar]

Hello,

Installed the HPUX 1203 with vPars6.1 in a npar of superdome2 and created the vpars in it. The vpars is not booting either with a disk file (existing image file) / new disk via the Ignite server / with a disk that already has a installed hpux image. It just shuts down the vpar while trying to load kernel. And the log for the vpars says

Creation of VM, minor device 1
Device file = /var/opt/hpvm/uuids/ef8b95ac-643c-11e1-ab05-b499ba625b6a/vm_dev
Memory MAP: 1240045ea000 - 7a16000
Memory MAP: 124010000000 - 78000000
guestStatsStartThread: Started guestStatsCollectLoop - thread = 6
Starting thread initialization
Watchdog Timer flags loaded: expiration(0x0) use(0x0)
Diagnostics message: Diagnostic connected with Virtual Partition with pid 2031
Specific Core OLD thread created
Starting infinite loop
Specific Core OLD thread being terminated errno=65535

Watchdog Timer flags saved: expiration(0x0) use(0x0)

====================================================
Virtual machine stopped at Fri Mar  2 07:23:43 2012
====================================================

The console output says,

Console is on virtual console - via PCDP
Booting kernel...

HP-UX will call firmware in physical-addressing mode
AvioSyscall(0): 1241cfe07000:e00000fffefff000


*** vPar shutdown ***

Is this a known problem / any suggestions to go on?

Thanks in advance!

[Vas]

vPar 6 is  only for  Integrityy Blades and not for Superdome 2 yet. The last release of vPars supported on Superdome 2 is 5.08 which is available on Sep 2011 VSE  media.

[Doug_Lamoureux]

Your existing image probably doesn't have the correct HP-UX update.  The vPar (guest) on an SD2 must be running 1203 as well. Take a look at your syslog.log file on the VSP - it should have a message that says the guest has an unsupported OS.  This is documented in the Admin Guide - but the Admin Guides are not available for 6.1 yet.

Cheers,

Doug

[Torsten.]

As said, this vPars version is not supported on SD2 (yet).

[Dave Olker]

A few comments:

1. The March 2012 release is not out yet so I'm wondering where you got a copy of it
2. When 1203 is released it will support vPars v6.1 on an SD2
3. Doug Lamoureux is correct.  The only supported OS running/booting in a v6.1 vPar on an SD2 is 1203.  This is why none of your existing boot disks can be used to boot a v6.1 vPar (assuming they are not already running 1203).  If you're not able to use Ignite to install a new vPar on the SD2 it's because your Ignite server has not been updated with the version of Ignite on the 1203 media.  Any Ignite server used to bring up v6.1 vPars on SD2 would need to be updated from the 1203 media so that the kernel it uses to boot the v6.1 vPar is the 1203 kernel.  That's why your vPar immediately panics when loading the kernel - it's not a 1203 kernel.

Dave