VM not coming Up...

Makesh Annamalai — Thu, 04 Oct 2007 02:24:12 GMT

Hi All,

I had a Intergrity Vm running for a year. Its a rx7620 Box which has 8 HBA cards. but suddenly of the card failed in which the Lun was assigned to the VM. So the Lun was changed to other HBA card. but the machine is not coming up even after changing the disk path in the VM.

Here's the history.

Old setup :-

Vm disks

Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
====== ========== === === === === === ========= =========================
disk scsi 0 1 0 0 0 disk /dev/rdsk/c19t0d5
disk scsi 0 1 0 1 0 disk /dev/rdsk/c19t1d0

After changing the Path to different HBA card:-

Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
====== ========== === === === === === ========= =========================
disk scsi 0 1 0 0 0 disk /dev/rdsk/c20t0d1
disk scsi 0 1 0 1 0 disk /dev/rdsk/c8t0d2

Now the machine comes up in Single user mode & does not get to the init 3.when is start the machine

# hpvmstart -p8
(C) Copyright 2000 - 2006 Hewlett-Packard Development Company, L.P.
Opening minor device and creating guest machine container
Creation of VM, minor device 5
Allocating guest memory: 6144MB
allocating low RAM (0-80000000, 2048MB)
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/5ea89260-58e4-11db-bce0-0017084c687d/vmm_config.current): Allocated 2147483648 bytes at 0x6000000100000000
allocating firmware RAM (ffaa0000-ffab5000, 84KB)
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/5ea89260-58e4-11db-bce0-0017084c687d/vmm_config.current): Allocated 86016 bytes at 0x6000000180000000
allocating high RAM (100000000-200000000, 4096MB)
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/5ea89260-58e4-11db-bce0-0017084c687d/vmm_config.current): Allocated 4294967296 bytes at 0x60000001c0000000
Loading boot image
Image initial IP=102000 GP=5E4000
Initialize guest memory mapping tables
Starting event polling thread
Starting thread initialization
Daemonizing....
hpvmstart: Successful start initiation of guest

In the console :-

(C) Copyright 2004 Hewlett-Packard Development Company, L.P.All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.027

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 6135 MB
loading section 0
....................................................... (complete)
loading section 1
.............. (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
...................
Launching /stand/vmunix
SIZE: Text:28134K + Data:6753K + BSS:5233K = Total:40121K
Console is on Serial COM1
Booting kernel...

Disabling 8259s

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 6135 MB 6135 MB 6135 MB
Kernel : 6135 MB 6135 MB 6135 MB
User : 5077 MB 4423 MB 4440 MB
-------------------------------------------------------------------------

Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
Boot device's HP-UX HW path is: 0/0/1/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
LCalling function e000000000fdfea0 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
Found adjacent data tr. Growing size. 0x3449000 -> 0x7449000.
Pinned PDK malloc pool: base: 0xe000000100bb7000 size=119076K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.

MFS is defined: base= 0xe000000100bb7000 size= 4980 KB

Unpinned PDK malloc pool: base: 0xe000000108000000 size=131072K
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
0 cec_gen
0/0 gh2p
0/0/0/0 iether
Initializing the Ultra320 SCSI Controller at 0/0/1/0. Controller firmware versio n is 00.00.00.00
0/0/1/0 mpt
0/0/3/0 legacyio
0/0/3/0/1 asio0
0/1 gh2p
0/2 gh2p
0/3 gh2p
0/4 gh2p
0/5 gh2p
0/6 gh2p
0/7 gh2p
120 processor
250 pdh
250/0 ipmi
250/1 acpi_node
0/0/1/0.0 tgt
0/0/1/0.0.0 sdisk
0/0/1/0.1 tgt
0/0/1/0.1.0 sdisk
0/0/1/0.15 tgt
0/0/1/0.15.0 sctl
Boot device's HP-UX HW path is: 0/0/1/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
LVM : Failure in attaching PV (0/0/1/0.0.0) to the root volume group.
error no : 5
LVM : Activation of root volume group failed
Quorum not present, or some physical volume(s) are missing

-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Could not configure root VG
If new kernel, HPUX> boot /stand/vmunix -lm ; pvck -y /dev/rdsk/....
| |
-----------------------------------------------------

System Panic:

panic: LVM: Configuration failure
Stack Trace:
IP Function Name
0xe000000001129c60 lv_boothalt+0x110
0xe0000000011296d0 lv_bootconf+0x3c0
0xe0000000011310e0 lvmconf+0x2e0
0xe000000001136c90 im_lvmconf+0x70
0xe0000000014d6c30 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Thu Jun 07 14:52:39 IST 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $

sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
This system does not support a crash dump under these circumstances.
Contact your HP support representative for assistance.

*** VM restarting ***

Please assist !

Re: VM not coming Up...

Torsten. — Thu, 04 Oct 2007 02:34:48 GMT

"LVM : Failure in attaching PV (0/0/1/0.0.0) to the root volume group.
error no : 5
LVM : Activation of root volume group failed
Quorum not present, or some physical volume(s) are missing"

First check ioscan and the vg status from single user mode.

You may also try to boot to LVM maintenance mode and export/import vg00 to reflect the changes.

Re: VM not coming Up...

Makesh Annamalai — Thu, 04 Oct 2007 03:12:53 GMT

Here the diskinfo. Cud u pls guide on the vgexport & import

# ioscan -kfnC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 0/0/1/0.0.0 sdisk CLAIMED DEVICE HP Virtual Disk
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s2 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s2 /dev/rdsk/c0t0d0s3
disk 1 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP Virtual Disk
/dev/dsk/c0t1d0 /dev/dsk/c0t1d0s2 /dev/dsk/c0t1d0s4 /dev/dsk/c0t1d0s6 /dev/rdsk/c0t1d0 /dev/rdsk/c0t1d0s2 /dev/rdsk/c0t1d0s4 /dev/rdsk/c0t1d0s6
/dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s3 /dev/dsk/c0t1d0s5 /dev/dsk/c0t1d0s7 /dev/rdsk/c0t1d0s1 /dev/rdsk/c0t1d0s3 /dev/rdsk/c0t1d0s5 /dev/rdsk/c0t1d0s7

Re: VM not coming Up...

Torsten. — Thu, 04 Oct 2007 07:33:01 GMT

What disks are in vg00?

vgchange -a y -q n vg00
vgdisplay -v vg00

topic Re: VM not coming Up... in Operating System - HP-UX

VM not coming Up...

Re: VM not coming Up...

Re: VM not coming Up...

Re: VM not coming Up...