Importing a VM guest from HPVM 3.5 to HPV 4.0?

[thom_14]

I have several HPVM 3.5 guests that I need to import into an HPVM 4.0 server. I tried creating a VM, pointing it to the v3.5 guest image, and then starting it up, but in the HPVM console, I get:

WARNING: ROOT device 0x1f000002 is a non-LVM partition, disallowed on LVM disk.
WARNING: ROOT device 0x1f000002 has been deconfigured (set to 0xffffffff).


-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Non-lvm root on LVM disk
| |
-----------------------------------------------------


System Panic:

panic: LVM: Configuration failure
Stack Trace:
(yada yada yada)

It seems there has to be a way to do this - any ideas?

[Eric SAUBIGNAC · Accepted solution]

Bonjour thom,

In my mind, it should work. Of course with probably some adjustments, but it should ...

What OS inside the VM ? Could you post "hpvmstatus -V -P " for both old and new VM Host ?

Eric

[thom_14]

I don't have an hpvmstatus output available for the VM running on the old server;

# hpvmstatus -v -P omu01
Version B.04.00.00
[Virtual Machine Details]
Virtual Machine Name VM # OS Type State
==================== ===== ======= ========
omu01 63 HPUX On (EFI)

[Authorized Administrators]
Oper Groups:
Admin Groups:
Oper Users:
Admin Users:

[Virtual CPU Details]
#vCPUs Entitlement Maximum
====== =========== =======
2 5.0% 100.0%

[Memory Details]
Total Reserved
Memory Memory
======= ========
2048 MB 64 MB

[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk scsi 0 1 0 0 0 file /hpvm/omu01/.omu01.disk

[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch lan vswA 1 0 0 0 ea-9d-bd-63-17-88

[Misc Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
serial com1 tty console

[Torsten.]

You have only 1 file as backing store, so you cannot mix it up ...

Does EFI in vMP see the disk? I think yes, because it attempts to boot from. If you stop the hpux loader, can you list /stand?

Did you try to boot in LVM maintenance mode?

[thom_14]

Hadn't thought of LVM maint mode; OK, now what?

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 2091568 Kbytes, lockable: 1338608 Kbytes, available: 1561100 Kbytes

/sbin/ioinitrc:
UX:vxfs fsck: ERROR: V-3-20003: /dev/vg00/lvol1:Cannot open /dev/vg00/lvol1: No such device or address
/dev/vg00/lvol1:file system check failure, aborting ...
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted

VxVM sysboot INFO V-5-2-3390 Starting restore daemon...
VxVM sysboot INFO V-5-2-3811 Starting in boot mode...
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk


INIT: Overriding default level with level 's'

INIT: SINGLE USER MODE

INIT: Running /sbin/sh

[Torsten.]

Did you reach LVM maintenance mode?

Try to vgexport / vgimport vg00 and reboot (the guest).

[thom_14]

First I tried:

vgchange -a y /dev/vg00
lvlnboot -v /dev/vg00

Same end result.

I then did a vgexport, and tried to vgimport, but it sez there's no LVM info on the disk.

# vgimport -v /dev/vg00 /dev/dsk/c0t0d0
Beginning the import process on Volume Group "/dev/vg00".
Physical Volume "/dev/dsk/c0t0d0" contains no LVM information
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 4 0/0/1/0.0.0 sdisk CLAIMED DEVICE HP Virtual FileDisk
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1
/dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3

[Torsten.]

You need to import /dev/dsk/c0t0d0s2 (note the "s2"!)

[thom_14]

I'm still getting the panic. Here's the list of commands I ran in maintenance mode:

vgexport -v -m vg00.map -s /dev/vg00
mkdir /dev/vg00
mknod /dev/vg00/group c 64 0x000000
vgimport -v /dev/vg00 /dev/dsk/c0t0d0s2
vgchange -a y /dev/vg00
lvlnboot -v /dev/vg00
vgcfgbackup /dev/vg00

[Avinash20]

What is the output of
lvlnboot -v in maintainance mode

[thom_14]

# lvlnboot -v
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg-ovo".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg-ora".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg00".

(note: I previously activated vg00)

# vgchange -a y /dev/vg00
Activated volume group
Volume group "/dev/vg00" has been successfully changed.
# lvlnboot -v
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg-ovo".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg-ora".
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t0d0s2 (0/0/1/0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t0d0s2
Root: lvol3 on: /dev/dsk/c0t0d0s2
Swap: lvol2 on: /dev/dsk/c0t0d0s2
Dump: lvol2 on: /dev/dsk/c0t0d0s2, 0

[thom_14]

Ok, here's the sequence of commands to fix it:

From the EFI shell:

fs0:
cd EFI/HPUX
hpux -lm

Once you're in LV maintenance mode - turns out that vgexport/vgimport wasn't necessary.

vgchange -a y /dev/vg00
vgcfgbackup /dev/vg00
lvlnboot -r /dev/vg00/lvol3
lvlnboot -b /dev/vg00/lvol1
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
lvlnboot -v /dev/vg00
reboot

3 VM's down - 15 more to go!

Thanks again for the help!

[Torsten.]

in a previous port: I'm still getting the panic.

So you did not do a reboot?

Now it is fixed, isn't it?

[thom_14]

It is fixed now, using the sequence of commands I listed above.