Upgrading to Integrity VM Version 4.0 from 3.X

The workaround is to either use network depots, thus avoiding the DVD drive, or to temporarily

reduce the kernel tunable parameter base_pagesize to 4K, do your installations, and then restore the

parameter to 64K.

Here is an example of using the workaround to install Integrity VM from the VSE-OE media after the

host has already been migrated to HP-UX 11i v3:

1. Install VMKernelSW (and any other desired bundles) from DVD #1:

# swinstall -x autoreboot=true -s <DVD #1> VMKernelSW

2. After system reboots (forced by swinstall in previous step), set base_pagesize to 4k:

# kctune base_pagesize=4

3. Reboot the system

4. Install T2767BC from (and any other desired bundles) DVD #2:

# swinstall -x autoreboot=true -s <DVD #2> T2767BC

5. Reset base_pagesize to 64K:

# kctune base_pagesize=64

6. Reboot the system

If the Guests won’t Start

Two of the more common reasons that VM guests may not start after an upgrade are if hyper-

threading gets enabled or Virtual Partitions are running. Symptoms that may be seen include the

following commands and responses:

Figure 6. Symptoms of Hyper-threading or Virtual Partitions being enabled

# hpvminfo

hpvminfo: Not on an HPVM guest or host.

# hpvmcreate

hpvmcreate: HPVM currently not running.

hpvmcreate: Unable to initialize.

hpvmcreate: Unable to create the guest.

# hpvmnet -c -S mynet -n 0

hpvmnet: HPVM currently not running.

hpvmnet: Unable to continue.

# hpvmcreate -P dev01 -c 2 -r 2G -B manual -l Mmyvm01 FS VM dev01 \

-g group:admin -u user:admin -O HPUX -a disk:scsi::lv:/dev/vgvm01/rdev01 \

-a network:lan::vswitch:

hpvmcreate: HPVM currently not running

hpvmcreate: Unable to initialize

hpvmcreate: Unable to create the guest.

You can tell that the problem is hyper-threading by running the setboot command with no options. If

the system supports hyper-threading and it is enabled, the last two lines of the output will say:

Hyperthreading : ON

: ON (next boot)

You can fix the problem by issuing the commands:

setboot –m; shutdown –r

Conversely, you can tell if the problem is virtual partitions by running the commands:

# /sbin/vecheck; echo $?