dd from raw disk to rlvol

[butti]

Hi,
I have a VM (vm1) with a Raw Disk (root)

disk avio_stor 0 0 0 0 0 disk /dev/rdisk/disk20

and an other VM (vm2) with a LV Raw Disk.

disk avio_stor 0 1 0 0 0 lv /dev/vg_vmhost2/rdisk1

I have cloned the Raw Disk to the LV Disk
dd if=/dev/rdisk/disk20 of=/dev/vg_vmhost2/rdisk1

Why doesn't vm2 start from the lvol Disk.??
Thanks for your help.

- - - - - - - - - - Prior Console Output - - - - - - - - - -
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
hpvmdynmem load: complete hpvmdynmem_load=0xe000000131dd2c40
Boot device's HP-UX HW path is: 0/0/1/0.0.0
iether1: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0

System Console is on the Built-In Serial Interface
WARNING: Open failed on device 0x1f000002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
W

System Console is on the Built-In Serial Interface
WARNING: Open failed on device 0x1f000002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f000002 (error 0x5).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f000002 (error 0x5).
WARNING: Can not read LVM BOOT information (BDRA).
WARNING: SWAP device 0xfffffffe is a non-LVM partition, disallowed on LVM disk.
WARNING: SWAP device 0xfffffffe has been deconfigured (set to 0xffffffff).
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend

System Panic:

panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000f5d860 vfs_mountroot+0x1d0
0xe000000001276960 im_mountroot+0x60
0xe00000000166e1f0 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Fri Mar 13 13:54:57 CET 2009
_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: No dump space is configured. Physical memory will not be dumped.
ERROR: Configured dump space is insufficient to hold dump metadata.
Physical memory will not be dumped.

**** Dumping Guest Image ****

**** Done with dump (10712Kbytes) ****


*** VM restarting ***
EFI version 1.10 [14.62] Build flags: EFI64 Running on Intel(R) Itanium Processor EFI _DEBUG

[V. Nyga]

Hi,

>I have a VM (vm1) with a Raw Disk (root)
>and an other VM (vm2) with a LV Raw Disk.

Do you have two different hardware, or why is the configuration different?

It seems like the you can't just clone the system because of that.

>System Panic:
>panic: all VFS_MOUNTROOTs failed: NEED >DRIVERS ?????

-> It seems like you have to build it new from cd/dvd. Or you have to add drivers to the first system, so the second can use it.

HTH
Volkmar

[butti]

Hi,

the second VM is on the same host as vm1.

Thanks,

[SoorajCleris]

I think its because of the difference in device path and LVM info.

[butti]

I'm going to clone the vm1 on vm2 for testing with lvm Disk. Is the only way Ignite ??

Thank's

[Eric SAUBIGNAC]

Bonjour,

I was passing through there ... I think one part of the answer is in the question : the virtual hardware path is not the same between both VM

disk avio_stor 0 0 0 0 0 disk /dev/rdisk/disk20

against

disk avio_stor 0 1 0 0 0 lv /dev/vg_vmhost2/rdisk1

It is about the same thing than if you tried to boot a physical system with a boot disk with a modified SCSI ID.

So modify the target virtual SCSI ID to be the same than the source VM (0,0,0) and it should be better. Or boot in maintenance mode (-lm) then re-import vg00.

Hope this will help

Eric

[butti]

Hi,

I'm also think so, but the following error appears.
I'm not able to create the device on vm2 with the same Path like vm1

Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
vm1: disk avio_stor 0 0 0 0 0 disk /dev/rdisk/disk20


VMHOST:/root#hpvmmodify -P vm2 -a disk:avio_stor:0,0,0:lv:/dev/vg_vm2/rdisk1
hpvmmodify: ERROR (vm2): No available targets remain on bus 0 device 0.
hpvmmodify: ERROR (vm2): Unable to load defaults for '/dev/vg_vm2/rdisk1'.
hpvmmodify: Device disk:avio_stor:0,0,1:lv:/dev/vg_vm2/rdisk1 has a conflicting device address.
hpvmmodify: Unable to create device.
hpvmmodify: Unable to modify the guest.

Does it appears because both vm's are on the same host??

Thanks,
butti

[Eric SAUBIGNAC]

"No available targets remain on bus 0 device 0" ? Probably the truth. What about "hpvmstatus -P vm2"

[butti]

Hi,

this are the Storage Details from vm2

[Storage Interface Details]
Guest Physical
Device Adaptor Bus Dev Ftn Tgt Lun Storage Device
======= ========== === === === === === ========= =========================
disk avio_stor 0 1 0 0 0 lv /dev/vg_swkr2butti/rdisk1
dvd scsi 0 2 0 0 0 file /var/opt/ignite/iso_files/dvd_11.23.iso

[Eric SAUBIGNAC · Accepted solution]

You should have posted the whole output from "hpvmstatus -P vm2" ...

anyway, I guess that Bus 0 / Device 0 is already in use bye a virtual lan card ? In this case, you will not be able to add a disk at (0,0,0)

I do suggest that you re-design again the target vm2 so that virtual hardware of vm2 will have the same virtual bus / device / target address scheme than vm1 : stop vm2, remove all virtual devices, then add back virtual devices with same bus / device / target as in vm1

And I forgot in my previous post :"Does it appears because both vm's are on the same host??" --> definitively no

I am sorry, but I am to go away and will not be able to follow this thread (no Internet at home ;-). May be on next monday if I find time enough.

Good luck

Eric

[Torsten.]

You should try to boot the VM into LVM maintenance mode and vgexport/vgimport vg00 to adjust the new path.

[butti]

You are right,

the lan Card was on this bus.
After i deleted the lan card, i could creat the Disk on the juiste bus.

Thanks