Adding vPar fileset to a golden image built in an HPVM

[Olivier Masse]

I'm trying to build an "all-in-one" Golden Image that holds the VM guest libraries, as well as the vPar software. It will then be easy to install that image on anything, be a VM, physical server, or vPar.

IIRC, I *think* that in the past, the vPar-compatible HP-UX kernel was different from the standard kernel, as it had to be relocatable and it could boot only on vPars. But I think that was with PA-RISC, now I'm 100% ia64.

I've been able to merge for quite some time the VM guest libraries in my all-in-one Golden Image, it works well. But I'm trying to add the vPars software and it doesn't work, as it checks if I'm installing on a supported server and in my case, the golden system I'm using is not supported (it's a VM).

Instead of spending long hours experimenting and trying a force-install of the vPar software in a VM with disastrous results, maybe someone already did this and would have a suggestion?

Else I'll need to have two sets of Golden Images: one for vPars (which needs to be built and maintained on a vPar, which requires me to dedicate one for this) and one for VMs and physical servers. That's not great.

Thanks

[Steven E. Protter]

Shalom,

Honestly I thing you need two sets of images, one for the host system, one for the VM system and a two step installation process.

I can't see a way to do an all in one golden image.

SEP

[Torsten.]

I don't think this can work, because you can only install one of them - vPars or HPVM.

Consider to create your golden image without both, but place the products on the ignite server. So you can probably install the golden image together with the needed software.

[Olivier Masse]

Okay I'll change my question then.

Can I ignite a vPar with a Golden Image that doesn't have any vPar-related fileset, then add the vPar filesets once it's installed?

That probably didn't use to work due to the PA kernel restriction I mentioned above, but it might work on ia64? I don't have any free vPar available to test this.

Thanks

[Torsten.]

vPar software must be installed at the same time as the OS. If the OS has no vPars, it will not start.

[smatador]

Hi,

In fact, if you configure the installation in the sw_sel to install the vpar fileset after the first recover, you normaly can install the vpar just after made the restore.
So, I suppose you have a vpar, you made the vparcreate and after that you recover the ignite archives, when the recover is ok, the installation proceed with the installation of the vpar fileset that you have made on the depot and of course reboot.
The trouble maybe come now, because you should probably search to boot with hpux /stand/vpmon, but the disk don't have the flag because even if you install vpar during the installation, you don't set it.
Well, if you put a post-install script that set the disk to boot on /stand/vpmon maybe you could do what you want to do....

I really prefer made a clone of a vpar is more easy ;)
Hope it helps

[likid0]

As Torsten mentions, I have a golden Image with just the system, and on the ignite server I have the VM_client sofware and the vpar software with all it's deps, at installation time a choos whatever I need, and it works fine.

[Olivier Masse]

Fair enough. I only have a plain Golden Image but I guess I'll rtfm the Ignite docs to see how I can pull this off. Thanks everyone.