LDOMs on T2000 and T2540 , guest domains from FC LUN's

Hi,
I have some T2000 servers and ont 2540 FC storage. each servers have one HBA only, and 73 GB of mirrored internal disk space
I would like to implement LDOM's here. I would like to confirm if we can have the guest domains booted off from the SAN storage LUN's. (Guest OS to be installed on LUN's exported to T2000 from 2540 storage)
Any help will be highly apreciated
Many thanks in advance
Ushas symon

Hi,
Guest LDOM images can be on anything, as it is transparent to the LDOM. Remember the Control domain is actually serving the filesystems to the guest LDOM`s. So they can either be whole LUN`s, zfs devices, mounted filesystems, anything really. You could even have a LDOM guest image on a NFS filesystem if you really wanted..
I have setup the majority of systems using the SAN attached to the Control domain, and then setup ZFS filesystems on these LUN`s and placed disk images on the ZFS filesystems. This means that we can use ZFS snapshots on the control domain if we need to do any patching etc.etc.
I would also suggest that you have a minimum of 2 connections to each of your SAN devices. One connection is bad, m`kay? :D
Edited by: krankyd on Sep 23, 2009 1:01 AM

Similar Messages

Vds_add_vd() error and frozen guest domain

Hello all,
trying to setup a guest domain but getting a frozen domain at the end of the process. Seems to be a combination of some other issues on the forum. Commands run...
# ldm add-domain myldom1
# ldm add-vcpu 8 myldom1
# ldm add-memory 4G myldom1
# ldm add-vnet vnet1 primary-vsw0 myldom1
# ldm add-vdsdev /dev/dsk/c0t3d0s2 vol1@primary-vds0
# ldm add-vdisk vdisk1 vol1@primary-vds0 myldom1
# ldm set-variable auto-boot\?=false myldom1
# ldm set-variable boot-device=/virtual-devices@100/channel-devices@200/disk@0 myldom1
# ldm bind-domain myldom1
# ldm list-domain
Name State Flags Cons VCPU Memory Util Uptime
primary active -t-cv SP 4 2G 3.2% 6m
myldom1 bound ----- 5000 8 4G
# ldm list-bindings myldom1
Name: myldom1
State: bound
Flags:
OS:
Util:
Uptime:
Vcpu: 8
vid pid util strand
0 4 100%
1 5 100%
2 6 100%
3 7 100%
4 8 100%
5 9 100%
6 10 100%
7 11 100%
Memory: 4G
real-addr phys-addr size
0x8000000 0x88000000 4G
Vars: auto-boot?=false
boot-device=/virtual-devices@100/channel-devices@200/disk@0
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Vnet: vnet1
mac-addr=0:14:4f:f9:f7:be
service: primary-vsw0 @ primary
[LDC: 0x1]
Vdisk: vdisk1 vol1@primary-vds0
service: primary-vds0 @ primary
[LDC: 0x2]
Vcons: [via LDC:3]
myldom1@primary-vcc0 [port:5000]
# ldm start-domain myldom1
LDom myldom1 started
# ldm list-domain
Name State Flags Cons VCPU Memory Util Uptime
primary active -t-cv SP 4 2G 0.6% 7m
myldom1 active -t--- 5000 8 4G 100% 7s
# telnet localhost 5000
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying ::1...
telnet: Unable to connect to remote host: Network is unreachable
and in /var/adm/messages...
May 23 11:38:11 isdsyddev13 vds: [ID 556514 kern.info] vds_add_vd(): Failed to add vdisk ID 0
Tried stopping/unbinding the domain and then rebooting the primary domain, still doesn't work. Removed the guest domain, rebooted, recreated, still doesn't work. Any ideas on what else I can try? Thanks

Hi merwick,
thanks for the reply. Running sol10 11/06 (u3) with patch 124921. The disk wasn't in use anywhere else but vxvm is installed on the box which got me thinking. Seems I was getting hit by the veritas DMP issue (bug 6522993) even though the disk in question wasn't being used by vxvm directly. A "vxdisk rm" solved the issues. So first guest domain up and running :) Happy days. Uninstalled vxvm from the system as well and am off to try out zfs as boot disks (as described in the Ldom admin guide). Thanks again.

Install OS from cdrom failed on guest domain

I am trying to install Soloris OS on guest domain of SUN T2000 server, but it failed for "WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout connecting to virtual disk server... retrying"
it seems abnormal that the SOFTSTATE of primary and the guest domain is always in "Openboot initializing" and the SOFTSTATE in the Logic domain adminstration document is "Solaris running". Is it the failing reson?
Here is the output of "ldm list -l"
bjt2000sa3:/root-# ldm list-domain -l
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -t-cv SP 16 15G 0.1% 19m
SOFTSTATE
{color:#ff0000}Openboot initializing{color}
VCPU
VID PID UTIL STRAND
0 0 0.5% 100%
1 1 0.0% 100%
2 2 0.0% 100%
3 3 0.0% 100%
4 4 0.0% 100%
5 5 0.0% 100%
6 6 0.0% 100%
7 7 0.1% 100%
8 8 0.1% 100%
9 9 0.0% 100%
10 10 0.1% 100%
11 11 0.1% 100%
12 12 0.1% 100%
13 13 0.0% 100%
14 14 0.0% 100%
15 15 0.1% 100%
MAU
CPUSET
(0, 1, 2, 3)
MEMORY
RA PA SIZE
0x8000000 0x8000000 15G
VARIABLES
auto-boot-on-error?=true
auto-boot?=true
boot-device=disk0:a
diag-switch?=true
IO
DEVICE PSEUDONYM OPTIONS
[pci@780|mailto:pci@780] bus_a
[pci@7c0|mailto:pci@7c0] bus_b
VDS
NAME VOLUME OPTIONS DEVICE
primary-vds0 cdrom1 /dev/rdsk/c0t0d0s2
volldg1 /export/install_ldg1
VCC
NAME PORT-RANGE
primary-vcc0 5000-5100
VSW
NAME MAC NET-DEV DEVICE MODE
primary-vsw0 00:14:4f:f9:60:ac e1000g0 [switch@0|mailto:switch@0] prog,promisc
VCONS
NAME SERVICE PORT
SP
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg1 active -t--- 5000 16 15G 6.3% 4m
SOFTSTATE
{color:#ff0000}Openboot initializing{color}
VCPU
VID PID UTIL STRAND
0 16 100% 100%
1 17 0.0% 100%
2 18 0.0% 100%
3 19 0.0% 100%
4 20 0.0% 100%
5 21 0.0% 100%
6 22 0.0% 100%
7 23 0.0% 100%
8 24 0.0% 100%
9 25 0.0% 100%
10 26 0.0% 100%
11 27 0.0% 100%
12 28 0.0% 100%
13 29 0.0% 100%
14 30 0.0% 100%
15 31 0.0% 100%
MAU
CPUSET
(16, 17, 18, 19)
MEMORY
RA PA SIZE
0x8000000 0x3c8000000 15G
VARIABLES
auto-boot?=true
boot-device=vdisk
NETWORK
NAME SERVICE DEVICE MAC
vnet1 [primary-vsw0@primary|mailto:primary-vsw0@primary] [network@0|mailto:network@0] 00:14:4f:fb:c7:63
DISK
NAME VOLUME TOUT DEVICE SERVER
cdrom1 [cdrom1@primary-vds0|mailto:cdrom1@primary-vds0] 5 [disk@0|mailto:disk@0] primary
vdisk1 [volldg1@primary-vds0|mailto:volldg1@primary-vds0] [disk@1|mailto:disk@1] primary
VCONS
NAME SERVICE PORT
ldg1 [primary-vcc0@primary|mailto:primary-vcc0@primary] 5000
Thanks all in advance!

Sreesobh,
Thanks for your information!
I config it as "/dev/dsk/c0t0d0s2" and tried again. But it still doesn't work.
bjt2000sa3:/root-# ldm list -l
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -t-cv SP 16 15G 1.0% 26m
SOFTSTATE
Openboot initializing
VCPU
VID PID UTIL STRAND
0 0 2.6% 100%
1 1 0.9% 100%
2 2 0.7% 100%
3 3 0.6% 100%
4 4 0.9% 100%
5 5 0.9% 100%
6 6 0.9% 100%
7 7 0.8% 100%
8 8 1.3% 100%
9 9 0.7% 100%
10 10 0.5% 100%
11 11 0.8% 100%
12 12 1.1% 100%
13 13 0.7% 100%
14 14 0.8% 100%
15 15 1.0% 100%
MAU
CPUSET
(0, 1, 2, 3)
MEMORY
RA PA SIZE
0x8000000 0x8000000 15G
VARIABLES
auto-boot-on-error?=true
auto-boot?=true
boot-device=disk0:a
diag-switch?=true
IO
DEVICE PSEUDONYM OPTIONS
pci@780 bus_a
pci@7c0 bus_b
VDS
NAME VOLUME OPTIONS DEVICE
primary-vds0 cdrom /dev/dsk/c0t0d0s2
volldg1 /export/install_ldg1
VCC
NAME PORT-RANGE
primary-vcc0 5000-5100
VSW
NAME MAC NET-DEV DEVICE MODE
primary-vsw0 00:14:4f:f9:60:ac e1000g0 switch@0 prog,promisc
VCONS
NAME SERVICE PORT
SP
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg1 active -t--- 5000 16 15G 6.3% 3m
SOFTSTATE
Openboot initializing
VCPU
VID PID UTIL STRAND
0 16 100% 100%
1 17 0.0% 100%
2 18 0.0% 100%
3 19 0.0% 100%
4 20 0.0% 100%
5 21 0.0% 100%
6 22 0.0% 100%
7 23 0.0% 100%
8 24 0.0% 100%
9 25 0.0% 100%
10 26 0.0% 100%
11 27 0.0% 100%
12 28 0.0% 100%
13 29 0.0% 100%
14 30 0.0% 100%
15 31 0.0% 100%
MAU
CPUSET
(16, 17, 18, 19)
MEMORY
RA PA SIZE
0x8000000 0x3c8000000 15G
VARIABLES
auto-boot?=true
boot-device=vdisk
NETWORK
NAME SERVICE DEVICE MAC
vnet1 primary-vsw0@primary network@0 00:14:4f:fb:c7:63
DISK
NAME VOLUME TOUT DEVICE SERVER
cdrom cdrom@primary-vds0 5 disk@0 primary
vdisk1 volldg1@primary-vds0 disk@1 primary
VCONS
NAME SERVICE PORT
ldg1 primary-vcc0@primary 5000
bjt2000sa3:/root-#
bjt2000sa3:/root-# telnet localhost 5000
Trying ::1...
telnet: connect to address ::1: Network is unreachable
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connecting to console "ldg1" in group "ldg1" ....
Press ~? for control options ..
Netra T2000, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.27.4, 15360 MB memory available, Serial #66693703.
Ethernet address 0:14:4f:f9:aa:47, Host ID: 83f9aa47.
Boot device: vdisk File and args:
WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout connecting to virtual disk server... retrying
WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout connecting to virtual disk server... retrying
{0} ok devalias
vdisk1 /virtual-devices@100/channel-devices@200/disk@1
cdrom /virtual-devices@100/channel-devices@200/disk@0
vnet1 /virtual-devices@100/channel-devices@200/network@0
virtual-console /virtual-devices/console@1
net /pci@780/network@1,1
disk /pci@7c0/scsi@1/disk@0
scsi /pci@7c0/scsi@1
ttyb /virtual-devices/console@4
nvram /virtual-devices/nvram@3
ttya /virtual-devices/console@1
vdisk /virtual-devices/disk@0
name aliases
Your time is appreciated

LDOM Guest domains show c0d0 as 100% using iostat -cxn

I have a T5220 split into one primary and 3 guest domains. When the primary is re-booted an iostat -cxn on the guest domains shows c0d0 as 100% in the %b column. This is causing BMC Patrol to report a problem.
Searches of sunsolve and google have not given any pointers - possibly due to the vagueness of the question.
This situation only seems to occur when the primary domain is re-booted without the guest ldoms being re-booted.
Any help would be much appreciated.
Greg Hitchcock

I'm not at liberty to give you a specific timeline but have a look at this http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=2191993

Guest Domain Freezes with 100% utilization

I setup LDOM on a Sun Fire T2000 with one control domain and one guest domain. The guest domain is sharing the disk (on slice 6) with the control domain.
The slice is set as boot disk for the guest domain. Upon starting the guest domain, the utilization goes 100%. A telnet to the virtual console gets refused connection.
When I try to stop and unbind the guest domain (with a reboot), the slice is no longer unusable. format and newfs commands both cannot operate on the slice. What's wrong?
sc>showhost
Sun-Fire-T2000 System Firmware 6.4.4 2007/04/20 10:13
Host flash versions:
   Hypervisor 1.4.1 2007/04/02 16:37
   OBP 4.26.1 2007/04/02 16:26
   POST 4.26.0 2007/03/26 16:45
# Control Domain
$ cd LDoms_Manager-1_0-RR
$ Install/install-ldm
$ ldm add-vdiskserver primary-vds0 primary
$ ldm add-vconscon port-range=5000-5100 primary-vcc0 primary
$ ldm add-vswitch net-dev=e1000g0 primary-vsw0 primary
$ ldm set-mau 1 primary
$ ldm set-vcpu 4 primary
$ ldm set-memory 4g primary
$ ldm add-config initial
$ shutdown -i6 -g0 -y
# Guest Domain
$ ldm add-domain myldom1
$ ldm add-vcpu 4 myldom1
$ ldm add-memory 2g myldom1
$ ldm add-vnet vnet1 primary-vsw0 myldom1
$ ldm add-vdiskserverdevice /dev/dsk/c0t1d0s6 vol1@primary-vds0
$ ldm add-vdisk vdisk1 vol1@primary-vds0 myldom1
$ ldm set-variable auto-boot\?=false myldom1
$ ldm set-variable boot-device=vdisk1 myldom1
$ ldm bind-domain myldom1
$ ldm start-domain myldom1
$ telnet localhost 5000Truss output of format command:
AVAILABLE DISK SELECTIONS:
write(1, "\n\n A V A I L A B L E ".., 29)      = 29
ioctl(0, TCGETA, 0xFFBFFB34)                    = 0
ioctl(1, TCGETA, 0xFFBFFB34)                    = 0
ioctl(0, TCGETA, 0xFFBFFACC)                    = 0
ioctl(1, TCGETA, 0xFFBFFACC)                    = 0
ioctl(1, TIOCGWINSZ, 0xFFBFFB40)                = 0
open("/dev/tty", O_RDWR|O_NDELAY)               = 3
ioctl(3, TCGETS, 0x000525BC)                    = 0
ioctl(3, TCSETS, 0x000525BC)                    = 0
ioctl(3, TCGETS, 0x000525BC)                    = 0
ioctl(3, TCSETS, 0x000525BC)                    = 0
       0. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
write(1, "               0 .   c 0".., 56)      = 56
          /pci@780/pci@0/pci@9/scsi@0/sd@1,0
write(1, "                     / p".., 45)      = 45
ioctl(3, TCSETS, 0x000525BC)                    = 0
ioctl(3, TCSETS, 0x000525BC)                    = 0
close(3)                                        = 0
ioctl(0, TCGETA, 0xFFBFF1EC)                    = 0
fstat64(0, 0xFFBFF108)                          = 0
Specify disk (enter its number): write(1, " S p e c i f y   d i s k".., 33)     = 33
read(0, 0xFF2700F8, 1024)       (sleeping...)
0
read(0, " 0\n", 1024)                           = 2
open("/dev/rdsk/c0t1d0s2", O_RDWR|O_NDELAY)     = 3
brk(0x00058810)                                 = 0
brk(0x00068810)                                 = 0
brk(0x00068810)                                 = 0
brk(0x00078810)                                 = 0
selecting c0t1d0
write(1, " s e l e c t i n g   c 0".., 17)      = 17
ioctl(3, 0x04C9, 0xFFBFFA54)                    = 0
[disk formatted]
write(1, " [ d i s k   f o r m a t".., 17)      = 17
open("/etc/mnttab", O_RDONLY)                   = 4
ioctl(4, (('m'<<8)|7), 0xFFBFFA64)              = 0
open("/dev/rdsk/c0t1d0s0", O_RDWR|O_NDELAY)     = 5
fstat(5, 0xFFBFF5E0)                            = 0
ioctl(5, 0x0403, 0xFFBFF59C)                    = 0
close(5)                                        = 0
llseek(4, 0, SEEK_CUR)                          = 0
close(4)                                        = 0
fstat64(2, 0xFFBFEBA0)                          = 0
Warning: Current Disk has mounted partitions.
write(2, " W a r n i n g :   C u r".., 46)      = 46
resolvepath("/", "/", 1024)                     = 1
sysconfig(_CONFIG_PAGESIZE)                     = 8192
open("/dev/.devlink_db", O_RDONLY)              = 4
fstat(4, 0xFFBFF1F8)                            = 0
mmap(0x00000000, 40, PROT_READ, MAP_SHARED, 4, 0) = 0xFEF50000
mmap(0x00000000, 24576, PROT_READ, MAP_SHARED, 4, 32768) = 0xFEF38000
open("/devices/pseudo/devinfo@0:devinfo", O_RDONLY) = 5
ioctl(5, 0xDF82, 0x00000000)                    = 57311After failing to configure LDOM, I boot from a Solaris DVD to do reinstall the OS. It looks like the e1000g0 has some kind of fault.
{0} ok boot cdrom
Boot device: /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom@0,0:f File and args:
SunOS Release 5.10 Version Generic_118833-33 64-bit Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: mac_open e1000g0 failed
WARNING: mac_open e1000g0 failed
WARNING: mac_open e1000g0 failed
WARNING: Unable to setup switching mode
Configuring devices.
WARNING: bypass cookie failure 71ece
NOTICE: tavor0: error during attach: hw_init_eqinitall_fail
NOTICE: tavor0: driver attached (for maintenance mode only)
NOTICE: pciex8086,105e - e1000g[0] : Adapter 1000Mbps full duplex copper link is up.What is the meaning of this?
Message was edited by:
JoeChris@Sun

Hi,
In the case of bug 6530040, the recovery method in the Release Notes is to reboot the system. In my case, even after the reboot the vds still does not close the device. I suspect I might use a wrong way to reboot the system. Can you give me an example for a system with control domain (primary) and a single guest domain (myldom1).
My steps would be as follow:
$ ldm stop-domain myldom1
$ ldm unbind-domain myldom1
$ reboot
Do I miss any step?
LDOM seems to have problem releasing the network interface e1000g0 also. How do I release it?
{0} ok boot cdrom
Boot device: /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom@0,0:f File and args:
SunOS Release 5.10 Version Generic_118833-33 64-bit Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: mac_open e1000g0 failed
WARNING: mac_open e1000g0 failed
WARNING: mac_open e1000g0 failed
WARNING: Unable to setup switching mode
Configuring devices.
WARNING: bypass cookie failure 71ece
NOTICE: tavor0: error during attach: hw_init_eqinitall_fail
NOTICE: tavor0: driver attached (for maintenance mode only)
NOTICE: pciex8086,105e - e1000g[0] : Adapter 1000Mbps full duplex copper link is up.Thank you
Message was edited by:
JoeChris@Sun

Backup the Complete Guest Domain

Hi All,
What is the best way to backup the complete Guest Domain including the configuration and all, so that it can be migrated to another server.
Thanks in advance

The best way in my opinion is NOT to copy the guest domain.
instead just have the vdisk beck-end device be on a shared storage ( via san of nfs ) and then just use ldom migration to migrate the guest domain to another server
Ori

Remove a domain from Exchange 2003, now other domains cannot send to the old domain error 5.1.1

We have a single Exchange 2003 server. We have multiple mail domains on the server, but are slowly moving to a hosted email solution. I moved the first domain, I will call it
domainABC, to our hosted solution. I have removed all exchange mailboxes from the users, and deselected the domain from Recipient Policies. I then ran the policy.
Whenever I send an email to anyone on Domain ABC from any other domain on the Exchange server, I get the 5.1.1 message. I am not sure what to do next - any help would be appreciated...
Brian

Hi Brian,
Could you post the detail information for the NDR message?
When you migrate all the users to the host email server, did you change mx record point to the new server?
You also can use this tool to help you check for the inbound email test (for Domain ABC).
Exchange Remote Connectivity Analyzer
https://www.testexchangeconnectivity.com/
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Guest LDOM disk access through multiple IO domains

Hi All,
I am working on a configuration, wherein the boot disk to the Guest LDOM is being provided through an image file hosted on a VxVM diskgroup (vmdg1). The configuration has another copy of the same image file being provided through another VxVM diskgroup (vmdg2)l through another virtual disk service.
let me clear the configuration a little more in detail
A T-5240 server having 2 IO domains configured
Primary (Control domain + IO domain + Service domain) configuration
A VxVM diskgrop (vmdg1) having a boot image file
Secondary (IO domain + Service domain) configuration
A VxVM diskgroup (vmdg2) having a copy of the boot image file
these devices are exported through their respective virtual disk services with the same mpgroup name to a guest LDOM. The vdsisk is then assigned to the guest ldom which is using the volume through the primary service.
When the guest LDOM is started it starts with the disk export through the Primary domain. All writes happen fine. When the VxVM diskgroup is deported from the Primary the Guest LDOM still remains online as starts using the disk image path through the secondary domain.
I then bring the VxVM diskgroup and the mounts back online on the Primary domain and deport the diskgroup from the secondary domain to see if it failsback to the image through the Primary domain. The Guest LDOM now is in a hung state and does not allow access through the local console or through network logins.
Has anyone see such a problem? Also is it recommended to use disk based image as a backend device in mpgroups through "ldm add-vdsdev" ?
TIA,
Sudhir

As far as I know then only way to "re-balance" the I/O across the domains is to unbind/bind the guests. Not a great answer, but this could be done as part of the guests patching cycle.
I think there is an RFE to provide MPxIO-like features to guests.

Can I install Sun Cluster on LDOM guest domain. Is Oracle RAC a supported c

Hello,
Can I install Sun Cluster on LDOM guest domains. Is Oracle RAC on LDOM guest domains of 2 physical servers a supported configuration from oracle?
Many thanks in advance
Ushas Symon

Hello,
The motive behind using LDOm Guest domains as RAC node is to have a better control of the resource allocation, since i will be having more than one guest domains which should perform different functions. The customer wants to have ORACLE RAC alone (without sun cluster).
I will have two T5120's and one 2540 shared storage.
My plan of configuration is to have
Control&IO Domain with 8VCPU, 6GB mem
one LDOM guest domain on each physical machine with 8 VCPU's, 8GB of memory, shared n/w and disks participating as RAC node's. (Don't know yet if i will use solaris cluster or not)
one guest domain on each physical machine with 12 VCPU's, 14GB of memory, shared n/w and disks participating as BEA weblogic cluster nodes (not on solaris cluster)
One guest domain on each physical machine with 4 VCPU's, 4GB of memory,shared n/w and disks participating as apache web cluster (on solaris cluster)
Now, My question is, is it a supported configuration to have guest domains as Oracle RAC participants for 11gR2 (either with or without solaris cluster).
If I need to configure RAC nodes on solaris cluster, is it possible to have two independent clusters on LDOM , one 2 node cluster for RAC and another 2 node cluster for apache web?
Kindly advise
Many thanks in advance
Ushas Symon

How to reboot a guest domain when hung and ldm stop-domain doesn't work

Hi, the configuration is as follows.
SF T1000 (32 threads/16gb) memory
Latest Firmware and the LDOM patch (-02) applied.
This is how the LDOMs are setup.
Instance CPUs Memory
Service domain 4 2g
ldom1 4 2g
ldom2 4 2g
ldom3 4 2g
ldom4 4 2g
ldom5 4 2g
ldom6 4 2g
ldom7 4 1.9g
All guest domains are running on disk-images on mirrored BE on service domain. Size around 7 gb and SUNWCXall installed.
However, I have had a few hangs, especially when working over the virtual switch on the domains.
At the moment ldom1 is totally hung. See below for info:
bash-3.00# ldm list-domain
Name State Flags Cons VCPU Memory Util Uptime
primary active -t-cv SP 4 2G 0.5% 1d 1h 17m
ldom1 active -t--- 5000 4 2G 25% 2h 14m
ldom2 active -t--- 5001 4 2G 0.2% 2h 35m
ldom3 active ----- 5002 4 2G 0.2% 47m
ldom4 active ----- 5003 4 2G 0.2% 1d 1h 10m
ldom5 active -t--- 5004 4 2G 0.3% 1d 1h 10m
ldom6 active -t--- 5005 4 2G 0.2% 1d 1h 10m
ldom7 active -t--- 5006 4 1900M 0.2% 7h 29m
bash-3.00#
bash-3.00# ldm stop-domain ldom1
LDom ldom1 stop notification failed
bash-3.00#
bash-3.00# telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connecting to console "ldom1" in group "ldom1" ....
Press ~? for control options ..
<COMMENT: ~w sent!>
Warning: another user currently has write permission
to this console and forcibly removing him/her will terminate
any current write action and all work will be lost.
Would you like to continue?[y/n] y
< COMMENT: I don't get any response when hitting enter and ~# (break) doesn't seem to work....>
I cannot ssh to ldom1 since it appears to be dead!
Anyone know if I can send some sort of reset to this hung domain? How can I troubleshoot it?
Regards,
Daniel

UPDATE 2
=========
When I attached to ldom3 through the console services, this domain also had
hung.
Below is some LDOM information.
bash-3.00# ldm list-services
Vldc: primary-vldc0
Vldc: primary-vldc3
Vds: primary-vds0
vdsdev: vol1 device=/ldoms/be/ldom_1.img
vdsdev: vol5 device=/ldoms/be/ldom_5.img
vdsdev: vol6 device=/ldoms/be/ldom_6.img
vdsdev: vol7 device=/ldoms/be/ldom_7.img
vdsdev: vol2 device=/ldoms/be/ldom_2.img
vdsdev: vol3 device=/ldoms/be/ldom_3.img
vdsdev: vol4 device=/ldoms/be/ldom_4.img
Vcc: primary-vcc0
port-range=5000-5100
Vsw: primary-vsw0
mac-addr=0:14:4f:f8:66:9f
net-dev=bge0
mode=prog,promisc
Vsw: primary-vsw1
mac-addr=0:14:4f:f9:dd:53
net-dev=bge1
mode=prog,promisc
bash-3.00# ldm list-devices
vCPU:
vCPUID %FREE
MAU:
Free MA-Units:
cpuset (0, 1, 2, 3)
cpuset (4, 5, 6, 7)
cpuset (8, 9, 10, 11)
cpuset (12, 13, 14, 15)
cpuset (16, 17, 18, 19)
cpuset (20, 21, 22, 23)
cpuset (24, 25, 26, 27)
cpuset (28, 29, 30, 31)
Memory:
Available mblocks:
PADDR SIZE
0x3fec00000 20M (0x1400000)
I/O Devices:
Free Devices:
bash-3.00# ldm list-domains
Unknown command list-domains; use --help option for list of available commands
bash-3.00# ldm list-domain
Name State Flags Cons VCPU Memory Util Uptime
primary active -t-cv SP 4 2G 0.7% 1d 4h 8m
ldom1 active -t--- 5000 4 2G 0.3% 1h 24m
ldom2 active -t--- 5001 4 2G 0.6% 5h 26m
ldom3 active ----- 5002 4 2G 25% 3h 38m
ldom4 active ----- 5003 4 2G 0.1% 1d 4h 1m
ldom5 active -t--- 5004 4 2G 0.1% 1d 4h 1m
ldom6 active -t--- 5005 4 2G 0.7% 1d 4h 1m
ldom7 active -t--- 5006 4 1900M 0.1% 10h 20m
bash-3.00#
bash-3.00# ldm list-bindings
Name: primary
State: active
Flags: transition,control,vio service
OS:
Util: 0.5%
Uptime: 1d 4h 11m
Vcpu: 4
vid pid util strand
0 0 0.9% 100%
1 1 0.8% 100%
2 2 0.2% 100%
3 3 0.3% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x8000000 2G
Vars: reboot-command=boot
IO: pci@780 (bus_a)
pci@7c0 (bus_b)
Vldc: primary-vldc0
[LDC: 0x0]
[(HV Control channel)]
[LDC: 0x1]
[LDom primary   (Domain Services channel)]
[LDC: 0x3]
[LDom primary   (FMA Services channel)]
[LDC: 0xb]
[LDom ldom1     (Domain Services channel)]
[LDC: 0x22]
[LDom ldom5     (Domain Services channel)]
[LDC: 0x27]
[LDom ldom6     (Domain Services channel)]
[LDC: 0x2d]
[LDom ldom7     (Domain Services channel)]
[LDC: 0x10]
[LDom ldom2     (Domain Services channel)]
[LDC: 0x18]
[LDom ldom3     (Domain Services channel)]
[LDC: 0x1d]
[LDom ldom4     (Domain Services channel)]
Vldc: primary-vldc3
[LDC: 0x14]
[spds (SP channel)]
[LDC: 0xd]
[system-management (SP channel)]
[LDC: 0x6]
[sunvts (SP channel)]
[LDC: 0x7]
[sunmc (SP channel)]
[LDC: 0x8]
[explorer (SP channel)]
[LDC: 0x9]
[led (SP channel)]
[LDC: 0xa]
[flashupdate (SP channel)]
Vds: primary-vds0
vdsdev: vol1 device=/ldoms/be/ldom_1.img
vdsdev: vol5 device=/ldoms/be/ldom_5.img
vdsdev: vol6 device=/ldoms/be/ldom_6.img
vdsdev: vol7 device=/ldoms/be/ldom_7.img
vdsdev: vol2 device=/ldoms/be/ldom_2.img
vdsdev: vol3 device=/ldoms/be/ldom_3.img
vdsdev: vol4 device=/ldoms/be/ldom_4.img
[LDom ldom1, dev-name: vol1]
[LDC: 0xe]
[LDom ldom5, dev-name: vol5]
[LDC: 0x25]
[LDom ldom6, dev-name: vol6]
[LDC: 0x2a]
[LDom ldom7, dev-name: vol7]
[LDC: 0x30]
[LDom ldom2, dev-name: vol2]
[LDC: 0x13]
[LDom ldom3, dev-name: vol3]
[LDC: 0x1b]
[LDom ldom4, dev-name: vol4]
[LDC: 0x20]
Vcc: primary-vcc0
[LDC: 0xf]
[LDom ldom1, group: ldom1, port: 5000]
[LDC: 0x26]
[LDom ldom5, group: ldom5, port: 5004]
[LDC: 0x2c]
[LDom ldom6, group: ldom6, port: 5005]
[LDC: 0x31]
[LDom ldom7, group: ldom7, port: 5006]
[LDC: 0x15]
[LDom ldom2, group: ldom2, port: 5001]
[LDC: 0x1c]
[LDom ldom3, group: ldom3, port: 5002]
[LDC: 0x21]
[LDom ldom4, group: ldom4, port: 5003]
port-range=5000-5100
Vsw: primary-vsw0
mac-addr=0:14:4f:f8:66:9f
net-dev=bge0
[LDC: 0xc]
[LDom ldom1, name: vnet1, mac-addr: 0:14:4f:fa:1e:4d]
[LDC: 0x23]
[LDom ldom5, name: vnet0, mac-addr: 0:14:4f:f9:ae:a1]
[LDC: 0x28]
[LDom ldom6, name: vnet0, mac-addr: 0:14:4f:f8:27:b8]
[LDC: 0x2e]
[LDom ldom7, name: vnet0, mac-addr: 0:14:4f:f9:1f:5d]
[LDC: 0x11]
[LDom ldom2, name: vnet0, mac-addr: 0:14:4f:f8:c9:7c]
[LDC: 0x19]
[LDom ldom3, name: vnet0, mac-addr: 0:14:4f:fb:d9:6d]
[LDC: 0x1e]
[LDom ldom4, name: vnet0, mac-addr: 0:14:4f:fb:df:2c]
mode=prog,promisc
Vsw: primary-vsw1
mac-addr=0:14:4f:f9:dd:53
net-dev=bge1
[LDC: 0x2b]
[LDom ldom1, name: vnet2, mac-addr: 0:14:4f:fa:b1:f0]
[LDC: 0x24]
[LDom ldom5, name: vnet1, mac-addr: 0:14:4f:f9:b2:b0]
[LDC: 0x29]
[LDom ldom6, name: vnet1, mac-addr: 0:14:4f:fb:f5:c3]
[LDC: 0x2f]
[LDom ldom7, name: vnet1, mac-addr: 0:14:4f:f8:3a:3e]
[LDC: 0x12]
[LDom ldom2, name: vnet1, mac-addr: 0:14:4f:f9:88:a0]
[LDC: 0x1a]
[LDom ldom3, name: vnet1, mac-addr: 0:14:4f:fa:aa:57]
[LDC: 0x1f]
[LDom ldom4, name: vnet1, mac-addr: 0:14:4f:f9:33:59]
mode=prog,promisc
Vldcc: vldcc1 [FMA Services]
service: ldmfma
service: primary-vldc0 @ primary
[LDC: 0x4]
Vldcc: vldcc2 [SP channel]
service: spfma
[LDC: 0x5]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x2]
Vldcc: hvctl [Hypervisor Control]
service: primary-vldc0 @ primary
[LDC: 0x0]
Vcons: SP
Name: ldom1
State: active
Flags: transition
OS:
Util: 0.3%
Uptime: 1h 27m
Vcpu: 4
vid pid util strand
0 4 0.5% 100%
1 5 0.6% 100%
2 6 0.1% 100%
3 7 0.0% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x88000000 2G
Vars: auto-boot?=false
boot-device=/virtual-devices@100/channel-devices@200/disk@0:a vdisk
nvramrc=devalias vnet /virtual-devices@100/channel-devices@200/network@0
use-nvramrc?=true
Vnet: vnet1 [LDC: 0xb]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0xd]
[Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0xf]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x4]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x6]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0x8]
[Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
mac-addr=0:14:4f:fa:1e:4d
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet2 [LDC: 0xc]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xe]
[Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0x10]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0x5]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x7]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0x9]
[Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
mac-addr=0:14:4f:fa:b1:f0
service: primary-vsw1 @ primary
[LDC: 0xa]
Vdisk: vdisk1 vol1@primary-vds0
service: primary-vds0 @ primary
[LDC: 0x2]
Vcons: [via LDC:3]
ldom1@primary-vcc0 [port:5000]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldom2
State: active
Flags: transition
OS:
Util: 0.1%
Uptime: 5h 29m
Vcpu: 4
vid pid util strand
0 8 0.6% 100%
1 9 0.1% 100%
2 10 0.0% 100%
3 11 0.2% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x108000000 2G
Vars: boot-device=vdisk
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x3]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x4]
[Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x5]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0xd]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0xf]
[Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
mac-addr=0:14:4f:f8:c9:7c
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet1 [LDC: 0x7]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0x8]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0x9]
[Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0xa]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0xe]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0x10]
[Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
mac-addr=0:14:4f:f9:88:a0
service: primary-vsw1 @ primary
[LDC: 0x6]
Vdisk: vdisk2 vol2@primary-vds0
service: primary-vds0 @ primary
[LDC: 0xb]
Vcons: [via LDC:12]
ldom2@primary-vcc0 [port:5001]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldom3
State: active
Flags:
OS:
Util: 24%
Uptime: 3h 42m
Vcpu: 4
vid pid util strand
0 12 100% 100%
1 13 1.4% 100%
2 14 1.4% 100%
3 15 1.4% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x188000000 2G
Vars: boot-device=vdisk
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x3]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x4]
[Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x5]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x6]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0xf]
[Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
mac-addr=0:14:4f:fb:d9:6d
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet1 [LDC: 0x8]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0x9]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xa]
[Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0xb]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0xc]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x10]
[Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
mac-addr=0:14:4f:fa:aa:57
service: primary-vsw1 @ primary
[LDC: 0x7]
Vdisk: vdisk3 vol3@primary-vds0
service: primary-vds0 @ primary
[LDC: 0xd]
Vcons: [via LDC:14]
ldom3@primary-vcc0 [port:5002]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldom4
State: active
Flags:
OS:
Util: 0.2%
Uptime: 1d 4h 4m
Vcpu: 4
vid pid util strand
0 16 0.4% 100%
1 17 0.3% 100%
2 18 0.1% 100%
3 19 0.0% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x208000000 2G
Vars: boot-device=vdisk
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x3]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x4]
[Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x5]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x6]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x7]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d]
mac-addr=0:14:4f:fb:df:2c
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet1 [LDC: 0x9]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xa]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xb]
[Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0xc]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0xd]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0xe]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57]
mac-addr=0:14:4f:f9:33:59
service: primary-vsw1 @ primary
[LDC: 0x8]
Vdisk: vdisk4 vol4@primary-vds0
service: primary-vds0 @ primary
[LDC: 0xf]
Vcons: [via LDC:16]
ldom4@primary-vcc0 [port:5003]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldom5
State: active
Flags: transition
OS:
Util: 0.2%
Uptime: 1d 4h 4m
Vcpu: 4
vid pid util strand
0 20 0.6% 100%
1 21 0.0% 100%
2 22 0.3% 100%
3 23 0.0% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x288000000 2G
Vars: boot-device=vdisk
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0xd]
[Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0xf]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x3]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x5]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0x9]
[Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
mac-addr=0:14:4f:f9:ae:a1
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet1 [LDC: 0x7]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xe]
[Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0x10]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0x4]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x8]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0xa]
[Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
mac-addr=0:14:4f:f9:b2:b0
service: primary-vsw1 @ primary
[LDC: 0x6]
Vdisk: vdisk5 vol5@primary-vds0
service: primary-vds0 @ primary
[LDC: 0xb]
Vcons: [via LDC:12]
ldom5@primary-vcc0 [port:5004]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldom6
State: active
Flags: transition
OS:
Util: 0.3%
Uptime: 1d 4h 4m
Vcpu: 4
vid pid util strand
0 24 0.5% 100%
1 25 0.3% 100%
2 26 0.5% 100%
3 27 0.0% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x308000000 2G
Vars: boot-device=vdisk
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x6]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0xf]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f9:1f:5d] [LDC: 0x3]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x5]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0xa]
[Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
mac-addr=0:14:4f:f8:27:b8
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet1 [LDC: 0x8]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xc]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0x10]
[Peer LDom: ldom7, mac-addr: 0:14:4f:f8:3a:3e] [LDC: 0x4]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0x9]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0xb]
[Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
mac-addr=0:14:4f:fb:f5:c3
service: primary-vsw1 @ primary
[LDC: 0x7]
Vdisk: vdisk6 vol6@primary-vds0
service: primary-vds0 @ primary
[LDC: 0xd]
Vcons: [via LDC:14]
ldom6@primary-vcc0 [port:5005]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldom7
State: active
Flags: transition
OS:
Util: 0.4%
Uptime: 10h 23m
Vcpu: 4
vid pid util strand
0 28 0.6% 100%
1 29 0.1% 100%
2 30 0.3% 100%
3 31 0.2% 100%
Memory: 1900M
real-addr phys-addr size
0x8000000 0x388000000 1900M
Vars: boot-device=vdisk
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:1e:4d] [LDC: 0x6]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:ae:a1] [LDC: 0x7]
[Peer LDom: ldom6, mac-addr: 0:14:4f:f8:27:b8] [LDC: 0x3]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f8:c9:7c] [LDC: 0x5]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fb:d9:6d] [LDC: 0xb]
[Peer LDom: ldom4, mac-addr: 0:14:4f:fb:df:2c]
mac-addr=0:14:4f:f9:1f:5d
service: primary-vsw0 @ primary
[LDC: 0x1]
Vnet: vnet1 [LDC: 0x9]
[Peer LDom: ldom1, mac-addr: 0:14:4f:fa:b1:f0] [LDC: 0xd]
[Peer LDom: ldom5, mac-addr: 0:14:4f:f9:b2:b0] [LDC: 0xe]
[Peer LDom: ldom6, mac-addr: 0:14:4f:fb:f5:c3] [LDC: 0x4]
[Peer LDom: ldom2, mac-addr: 0:14:4f:f9:88:a0] [LDC: 0xa]
[Peer LDom: ldom3, mac-addr: 0:14:4f:fa:aa:57] [LDC: 0xc]
[Peer LDom: ldom4, mac-addr: 0:14:4f:f9:33:59]
mac-addr=0:14:4f:f8:3a:3e
service: primary-vsw1 @ primary
[LDC: 0x8]
Vdisk: vdisk7 vol7@primary-vds0
service: primary-vds0 @ primary
[LDC: 0xf]
Vcons: [via LDC:16]
ldom7@primary-vcc0 [port:5006]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
bash-3.00#

Volume as install disk for Guest Domain and Live Upgrade

Hi Folks,
I am new to LDOMs and have some questions - any pointers, examples would be much appreciated:
(1) With support for volumes to be used as whole disks added in LDOM release 1.0.3, can we export a whole LUN under either VERITAS DMP or mpxio control to guest domain and install Solaris on it ? Any gotchas or special config required to do this ?
(2) Can Solaris Live Upgrade be used with Guest LDOMs ? or is this ability limited to Control Domains ?
Thanks

The answer to your #1 question is YES.
Here's my mpxio enabled device.
non-STMS device name STMS device name
/dev/rdsk/c2t50060E8010029B33d16 /dev/rdsk/c4t4849544143484920373730313036373530303136d0
/dev/rdsk/c3t50060E8010029B37d16 /dev/rdsk/c4t4849544143484920373730313036373530303136d0
create the virtual disk using slice 2
ldm add-vdsdev /dev/dsk/c4t4849544143484920373730313036373530303136d0s2 77bootdisk@primary-vds01
add the virtual disk to the guest domain
ldm add-vdisk apps bootdisk@primary-vds01 ldom1
the virtual disk will be imprted as c0d0 which is the whole lun itself.
bind, start ldom 1 and install OS (i used jumpstart) and it partitioned the boot disk c0d0 as / 15GB, swap the remaining space (10GB)
when you run format, print command on both guest and primary domain on this disk you'll see the same slice/size information
Part Tag Flag Cylinders Size Blocks
0 root wm 543 - 1362 15.01GB (820/0/0) 31488000
1 swap wu 0 - 542 9.94GB (543/0/0) 20851200
2 backup wm 0 - 1362 24.96GB (1363/0/0) 52339200
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
I havent used DMP but HDLM (Hitachi Dynamic link manager) seems not supported by ldom as i cannot make it work :(
I have no answer on your next question unfortunately.

Removing Guest VM From Domain Upon Deletion

We use System Center 2012 R2 Virtual Machine Manager to deploy VMs to our Hyper-V servers. We are starting to use the VM templates to automate our system deployments. These templates are configured to use a randomly generated hostname, and join the company
AD Domain.
The creation and joining of the domain are working correctly, but upon deletion of the guest VM is it not removed from the domain. Does SCVMM or Hyper-V offer a way to automate the removal of guest VMs from the domain upon their deletion?

There is no way to handle the "domain un-join" or the deletion of domain computer accounts.
The answer is to use scripts that drive SCVMM; find the VM, delete the VM, delete the computer account (running under credentials that can do this action).
If you drink the system center cool-aid - then Operations Manager is your friend.
Again, SCVMM / Hyper-V do not do this for you. They really don't perform the domain join for you. The VM is presented with an unattend.xml with the domain and user information to perform the join.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

LDOMS - virtual disks export mutiple times to different guest domains

Experts,
From control domain, can I export one storage LUN to two guest domains?
ldm add-vdsdev /dev/dsk/c1t5d0s0 disk1@primary-vds0
ldm add-vdisk disk1 disk1@primary-vds0 ldom1
Ok
ldm add-vdsdev /dev/dsk/c1t5d0s0 disk2@primary-vds0
Gives error. With –f flag it works.
ldm add-vdisk disk2 disk2@primary-vds0 ldom2
Is it permitted configuration?

A virtual disk back end can be exported multiple times either through the same or different virtual disk servers. Each exported instance of the virtual disk back end can then be assigned to either the same or different guest domains.
When a virtual disk back end is exported multiple times, it should not be exported with the exclusive (excl) option. Specifying the excl option will only allow exporting the back end once. The back end can be safely exported multiple times as a read-only device with the ro option.
chears
ME

Guest domains fail to boot from SAN disk after power-cycle

Control Domain Environment
# uname -a
SunOS s0007 5.10 Generic_139555-08 sun4v sparc SUNW,T5440
# ./ldm -V
Logical Domain Manager (v 1.1)
Hypervisor control protocol v 1.3
Using Hypervisor MD v 0.1
System PROM:
Hypervisor v. 1.7.0 @(#)Hypervisor 1.7.0 2008/12/11 13:42\015
OpenBoot v. 4.30.0 @(#)OBP 4.30.0 2008/12/11 12:16
After a power-cycle the guest domains did not boot from SAN disks, they
tried to boot from the network.
# ./ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- SP 16 8G 0.5% 4d 20h 46m
s0500 active -t---- 5000 8 8G 12% 4d 20h 46m
s0501 active -t---- 5001 8 4G 12% 4d 20h 46m
s0502 active -t---- 5002 16 8G 6.2% 4d 20h 46m
s0503 active -t---- 5003 8 2G 12% 4d 20h 46m
s0504 active -t---- 5004 8 4G 0.0% 4d 20h 46m
s0505 active -t---- 5005 4 2G 25% 4d 20h 46m
s0506 active -t---- 5006 4 2G 25% 4d 20h 46m
s0507 active -t---- 5007 4 2G 25% 4d 20h 46m
s0508 active -t---- 5008 4 2G 25% 4d 20h 46m
Connecting to console "s0508" in group "s0508" ....
Press ~? for control options ..
Requesting Internet Address for 0:14:4f:fa:b9:1b
Requesting Internet Address for 0:14:4f:fa:b9:1b
Requesting Internet Address for 0:14:4f:fa:b9:1b
Requesting Internet Address for 0:14:4f:fa:b9:1b
If we reboot the quest domains now, it works.
It seems the disks are not ready at the
time the guest domains boot.
We see this on systems with many guest domains.
Is there any logfile, where we could find the reason for this?
Or is this a known issue?

Press F12 on boot to choose CD/DVD as a temporary boot device.
My hunch is that there's something wrong with the SSD itself, though.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

I recently upgraded to Lion and am using the current version. I cannot remove the guest account from the startup screen. I disabled it in the system pref but it still appears.

I downloaded and installed the most recent verison of Lion for my iMac. After doing so I noticed that my start up screen now has a "guest" account. I went into settings and disabled the "guest" account. Still, the startup sceen displays a "guest" account and allows one to start the computer in a "safari" only mode.
How do I removed the "guest" account from the start up screen and disable access via the "guest" account?

Have a read here OS X 10.7.2 with iCloud showing Guest user account at log-in
To get rid of it, uncheck "Find my Mac" in System Peferences -> iCloud
Stefan

LDOMs on T2000 and T2540 , guest domains from FC LUN's

Similar Messages

Maybe you are looking for