I have created a flash-archive using latest ldmp2v-Tool of my source-machine
which is a 280R running solaris 10 5/08. This Installation does not contain
/platform/sun4v/*
My ldom is running on a T5220 with:
Logical Domain Manager (v 1.2)
Hypervisor control protocol v 1.3
Using Hypervisor MD v 1.1
System PROM:
Hypervisor v. 1.7.2. @(#)Hypervisor 1.7.2.a 2009/05/05
19:32\015
OpenBoot v. 4.30.2. @(#)OBP 4.30.2.b 2009/06/16 07:02
The creation of the ldom using the ldmp2 prepare step was sucessfully.
Booting the ldom is not possible:
{0} ok boot
Boot device: disk File and args:
The file just loaded does not appear to be executable.
I think this is due to the fact that no proper sun4v-bootsector is found. So i
booted my ldom from a Solaris 10 5/08 ISO-Image and tried the following:
mount /dev/dsk/c0d0s0 /a
mount /dev/dsk/c0d0s3 /a/var
pkgadd -R /a -d /cdrom/Solaris_10/Product SUNWcar.v SUNWcakr.v SUNWcart200.v
SUNWcpc.v SUNWiopc.v SUNWkvm.v SUNWkvmt200.v SUNWn2cp.v SUNWust1.v SUNWust2.v
SUNWldomr.v SUNWldomu.v
After that i successfully installed the kernelpatch 139555-08 using patchadd -R
/a and updated the bootsector and bootarchive doing:
/a/usr/sbin/installboot /a/usr/platform/`uname -i`/lib/fs/ufs/bootblk
/dev/rdsk/c0d0s0
bootadm update-archive -R /a
When i boot my LDOM now the following happens:
{0} ok boot -a -s -v -r
Boot device: /virtual-devices at 100/channel-devices at 200/disk at 0 File and
args: -a -s -v -r
module /platform/SUNW,SPARC-Enterprise-T5220/kernel/sparcv9/unix: text at
[0x1000000, 0x10b373d] data at 0x1800000
module /platform/SUNW,SPARC-Enterprise-T5220/kernel/sparcv9/genunix: text at
[0x10b3740, 0x127420f] data at 0x1899a40
module /platform/SUNW,SPARC-Enterprise-T5220/kernel/misc/sparcv9/platmod: text
at [0x1274210, 0x1274227] data at 0x18efd18
module
/platform/SUNW,SPARC-Enterprise-T5220/kernel/cpu/sparcv9/SUNW,UltraSPARC-T2:
text at [0x1274240, 0x127995f] data at 0x18f0480
Name of system file [/etc/system]:
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Ethernet address = 0:14:4f:fb:4e:e9
root filesystem type [ufs]:
Enter physical name of root device
[/virtual-devices at 100/channel-devices at 200/disk at 0:a]:
mem = 2097152K (0x80000000)
avail mem = 1932435456
root nexus = SPARC Enterprise T5220
pseudo0 at root
pseudo0 is /pseudo
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
virtual-device: cnex0
cnex0 is /virtual-devices at 100/channel-devices at 200
vdisk at 0 is online using ldc at 0,0
channel-device: vdc0
vdc0 is /virtual-devices at 100/channel-devices at 200/disk at 0
root on /virtual-devices at 100/channel-devices at 200/disk at 0:a fstype ufs
iscsi0 at root
iscsi0 is /iscsi
pseudo-device: dld0
dld0 is /pseudo/dld at 0
cpu0: UltraSPARC-T2 (chipid 0, clock 1582 MHz)
cpu1: UltraSPARC-T2 (chipid 0, clock 1582 MHz)
<--- The kernel hangs here forever and i have absolutely no clue why?
After breaking the system at this state i got:
...
cpu0: UltraSPARC-T2 (chipid 0, clock 1582 MHz)
cpu1: UltraSPARC-T2 (chipid 0, clock 1582 MHz)
Debugging requested; hardware watchdog suspended.
c)ontinue, s)ync, r)eset? s
panic[cpu1]/thread=2a100f71ca0: sync initiated
sched: trap type = 0x0
pid=0, pc=0x0, sp=0x0, tstate=0x0, context=0xe3f
o0-o7: 0, 0, 0, 0, 0, 0, 0, 0
g1-g7: 0, 0, 0, 0, 0, 0, 0
000002a100f71390 unix:sync_handler+144 (1826400, 0, 0, 1, 1, 10ac000)
%l0-3: 000000000185c8a0 0000000001894370 0000000001894000 0000000000000000
%l4-7: 0000000001878800 0000000000000000 0000000001872000 0000000000000000
000002a100f71460 unix:vx_handler+80 (2a100f715c0, 1835890, 10abc00, 0, 1835998,
1833078)
%l0-3: 0000000001835998 0000000000000000 0000000000000001 0000000000000001
%l4-7: 0000000001826c00 0000000001000000 0000000001000000 000000000101e5bc
000002a100f71510 unix:promif_enter_mon+144 (1833000, 10afc00, 10afc00, 73,
10afe00, 2a100f715c0)
%l0-3: 00000000018291c8 0000000001833078 00000000010afdf0 00000000010afde8
%l4-7: 00000000010afde0 000000000000000c 00000000ff122000 7300000000000000
000002a100f715d0 unix:kern_cif_handler+28 (2a100f717e8, 10afc00, 1833300, 0, 1,
104c204)
%l0-3: 000002a100f71634 0000000000000200 0000000000000009 0000000000000008
%l4-7: 000003000541e000 0000000000000016 000003000541ea18 000003000175cb80
000002a100f71680 unix:client_handler+2c (104bef0, 2a100f717e8, 0, 1835888,
187c000, 104bef0)
%l0-3: 0000000001872380 0000000000000001 0000000001826c00 0000000000000001
%l4-7: 0000000000000016 000000000000001e 0000000000000016 000003000541e000
000002a100f71730 unix:prom_enter_mon+24 (0, 3002, 1862c00, 1, 1829390, 1833300)
%l0-3: 000000000189b570 000000007009f7f0 0000000000000000 00000000018a0c00
%l4-7: 0000030001494cc0 00000000018a0c00 0000000000000000 0000000000000070
000002a100f71800 unix:debug_enter+118 (0, a, a, 1826400, 0, 1872000)
%l0-3: 0000000000000002 0000000000a7388d 0000000004000000 0000000080000000
%l4-7: 0000000000000020 00000700022c62c0 00000000000003ff 0000000000000000
000002a100f718d0 unix:abort_seq_softintr+94 (1826400, 18f1800, 3000541e000,
2a100f71d78, 1, 189fc00)
%l0-3: 0000000001834e60 0000006f13d05cc6 0000000000000000 0000000000000000
%l4-7: 0000000000000000 00000000018f1800 00000000010ad400 0000000001012788
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Resetting...
Does anybody have a hint here?
Second question: When I boot with an Solaris 10 5/09 ISO Image i got no option
to update my 10 5/08 to 10 5/09. Why?
Third question: Is there a way to mount a sliced zvol apart from slice 0? mount
-F ufs /dev/zvol/dsk/ldom/test/disk0 /mnt works perfectly for slice 0 but how
do i mount slice 3 or 4?
Thanks for your answers
Christian Rost
--
This message posted from opensolaris.org
