booting second Guest VM as a EVA snap-clone

[navsuk]

Running rx7640 server configured for VM 3.05 I have successfully installed and configured guest VM called "test1" (also HP-UX). Than on EVA array made an snap clone of "test1" called
"testclone". Now I can't make "testclone" VM boot. The "test1" boot path was /dev/dsk/c0t1d0

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t1d0s2 (0/0/0/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t1d0s2
Root: lvol3 on: /dev/dsk/c0t1d0s2
Swap: lvol2 on: /dev/dsk/c0t1d0s2
Dump: lvol2 on: /dev/dsk/c0t1d0s2, 0

Probably I need to reconfigure kernel boot path for clone or volume groupe disk descriptor (which have to be c0t0d0) or whatever. I boot "testclone" with -lm -is and ioscan tells me that:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 0/0/0/0.0.0 sdisk CLAIMED DEVICE HP Virtual Disk
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0

How to reconfigure volume group or boot stuff?
Does anyone experienced with this stuff? Thanks a lot.

[Torsten.]

Is this "lvlnboot" come from the guest?

How about the virtual disk configuration?

Did you adjust everything???

If the disk have the same hardware path from the guest point of view there should not be any problem.

From single user mode, try to activate the VG.

[Tim Nelson]

Do you wish to boot testclone disk from test1 vGuest ? or boot testclone disk from another vGuest ?

Here is a generic list:
Present cloned disk to vHost
From vHost present cloned disk to vGuest.
Boot vGuest using presented cloned disk.

commands:
hpvmmodify -a disk:scsi::disk:/dev/rdsk/cloned_disk
hpvmconsole -P vGuest(?)
cm>pc>on>ma>co
From vGuest(?) EFI select the HW address for the presented cloned disk and boot it.
The new vGuest will look exactly like the the other, IP, hostname, configs, everything.

You will need to modify all configs to have vGuest1 and vGuestClone up at the same time.

I use Ignite to replicate VM systems as it gives you the ability to modify the configs during boot. Only takes 15-20 minutes to build.

[navsuk]

Thanks for quick replay.

The "lvlnboot -v" is from first guest vm named "test1".

Here is something for clarifying of this situation:

# uname -a
HP-UX demo7640 B.11.23 U ia64 1916613486 unlimited-user license
# hpvmastatus
ksh: hpvmastatus: not found
# uname -a
HP-UX demo7640 B.11.23 U ia64 1916613486 unlimited-user license
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
test1 4 HPUX On (OS) 1 2 0 2 GB 0
testclone 5 HPUX On (OS) 1 1 0 2 GB 0

# hpvmdevmgmt -l all
...
/dev/rdsk/c1t2d0:CONFIG=gdev,EXIST=YES,DEVTYPE=DISK,SHARE=NO:test1:4420-2020-5343-5349-4445-2031-3630-204c-5644-2020-3136-3845-5a21-ae00-4100-0020-2020-2020-4137-3635-4553-4942-4731-3638-4520-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000
/dev/rdsk/c8t0d1:CONFIG=gdev,EXIST=YES,DEVTYPE=DISK,SHARE=NO:test1:6005-08b4-0001-41c1-000b-1000-0007-0000
/dev/rdsk/c8t0d2:CONFIG=gdev,EXIST=YES,DEVTYPE=DISK,SHARE=NO:testclone:6005-08b4-0001-41c1-000b-3000-0004-0000
HPVM MANAGEMENT_DB EOF
...

VM "test1" resides on EVA LUN on real path c8t0d1 an has DVD-ROM attached at c1t2d0.
VM "testclone" doesn't have dvd but only presented virtual disk (LUN) at c8t0d2.



# hpvmstatus -P test1
...
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
dvd scsi 0 0 0 0 0 disk /dev/rdsk/c1t2d0
disk scsi 0 0 0 1 0 disk /dev/rdsk/c8t0d1
...

# hpvmstatus -P testclone
...
[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk scsi 0 0 0 0 0 disk /dev/rdsk/c8t0d2
...


So: I believe that problem is something in
definition in volume group vg00 of "testclone" VM because it poits to strange device and boot hangs with kernel panic while trying boot path 0/0/0/0.0.0
But maybe I'm wrong, that's why I'm asking...
...

[Torsten.]

But you was able to boot the new guest to single user mode?

Did you try to activate vg00?

[navsuk]

And more, I have no physical access to servers because thay are too far away to change dvds to install another soft. That's why I have no Ignite UX installed and so on...

Nevermind.

Yes, I was able to boot to single user mode
"boot vmunix -lm -is" but activating vg00 fails:

# vgchange -a y /dev/vg00
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c0t1d0s2":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c0t1d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg00":
Quorum not present, or some physical volume(s) are missing.

If I try to standard boot it fails with:

...
Boot device's HP-UX HW path is: 0/0/0/0.0.0

System Console is on the Built-In Serial Interface
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:
IP Function Name
0xe0000000010b4a60 lv_boothalt+0x110
0xe0000000010bc000 lv_check_boot+0x60
0xe0000000010bbef0 lvmconf+0x2f0

...

[navsuk]

For Tim's questions:

The VMs "test1" and "tesclone" are both equivalent guests inside host HP-UX os
of rx7640. I'd like to run and boot them independently...

As I said, I have no Ignite UX now, I was testing just doing EVA clone to avoid any installations because it's the quickest way...

[Eric SAUBIGNAC · Accepted solution]

Bonjour navsuk,

Here is your problem :

# hpvmstatus -P test1
disk scsi 0 0 0 1 0 disk /dev/rdsk/c8t0d1

# hpvmstatus -P testclone
disk scsi 0 0 0 0 0 disk /dev/rdsk/c8t0d2

You have not the same virtual hardware path to the OS LUN for the VM Guests : 0,0,0,1,0 / 0,0,0,0,0

When you clone systeme disk you MUST specify the virtual path so that it will be the same as source guest. Maybe (No HP-UX system near me to control the correct syntax :-( something like "hpvmmodify -P testclone -m disk:scsi:0,0,1:disk:/dev/rdsk/c8t0d2" will correct the problem.

If not, delete system disk "hpvmmodify -P testclone -d disk:scsi:0,0,0:disk:/dev/rdsk/c8t0d2" then add it again with "hpvmmodify -P testclone -a disk:scsi:0,0,1:disk:/dev/rdsk/c8t0d2"

Regards

Eric

[navsuk]

Thanks to all, especially to Eric.
Yes this -d and -a really solved boot problem of second guest "tesclone".

Thanks again.

[navsuk]

.