Exploring DRD Rehosting in HP-UX 11i v2 and 11i v3 (July 2010)

The hpvmstatus command can be used to verify that the new VM was successfully created and

to determine the virtual MAC address of the new VM:

# hpvmstatus -d -P drdivm2

[Virtual Machine Devices]

[Storage Interface Details]

[Network Interface Details]

network:avio_lan:0,0,0xB22171007484:vswitch:myvswtch

[Misc Interface Details]

serial:com1::tty:console

2. On the VM host, add a disk to the source VM, “drdivm1“, that is large enough to contain all the

logical volumes in the root volume group. The backing store can be a raw disk or an LVM or

VxVM volume, and must be available—not in use on the host or on any other VM.

# hpvmmodify -P drdivm1 -a disk:avio_stor::disk:/dev/rdisk/disk15

Special consideration for HP- UX 11i v2

: If the Simple Generating VM Approach is used,

the clone target must be defined on the simple source VM with the hpvmresource triple. If it is

added in this step, the hpvmmodify command (assuming the device file on the VM host is

/dev/dsk/c5t0d0).

# hpvmmodify -P drdivm1 \

-a disk:avio_stor:0,1,1:disk:/dev/dsk/c5t0d0

If the target disk has already been added to the system, the triple in use can be checked by

issuing:

# hpvmstatus –P drdivm1 –d

The next actions take place on the source VM:

3. On the source VM, run the drd clone command to create a boot disk for the new VM.

Before running drd clone, you need to determine the device file of the newly added disk.

On HP-UX 11i v3, run ioscan –fNC disk on the source VM. (Do not use the –k option

because the VM needs to discover the newly added disk.) The instance number displayed is the

number to be appended to “disk” in the device file. For example, if the disk has instance number

3, the device file is /dev/disk/disk3.

On HP-UX 11i v2, run ioscan –fnC disk on the source VM. (Do not use the –k option

because the VM needs to discover the newly added disk.) The newly displayed device file can

then be used for the clone target.

The following command on HP-UX 11i v3 creates a clone of the source VM to the disk

/dev/disk/disk3, which is the device file of the disk with backing store /dev/disk/disk18

on the host. The –x overwrite=true option is used to ignore any LVM, VxVM, or boot

records that might exist on the new disk.