T2000 ldmd start issues

Hello all,

Just finished the setup of ldoms on a T2000 but ldmd can't get started. What I see is...

[ May 14 16:41:46 Executing start method ("/opt/SUNWldm/bin/ldmd_start") ]

Added to channel ds, service dr-cpu, versions 1.0

Added to channel ds, service fma-cpu-service, versions 1.0

Added to channel fmactl, service fma-phys-cpu-service, versions 1.0

Added to channel ds, service fma-mem-service, versions 1.0

Added to channel fmactl, service fma-phys-mem-service, versions 1.0

Added to channel fmactl, service fma-pri-service, versions 1.0

Added to channel spds, service mdstore, versions 1.0

Added to channel ds, service md-update, versions 1.0

Added to channel ds, service domain-shutdown, versions 1.0

Added to channel ds, service domain-panic, versions 1.0

Added to channel spds, service pri, versions 1.0

Added to channel ds, service var-config, versions 1.0

fatal error: Device busy: Unable to open VLDC instance /devices/virtual-devices@100/channel-devices@200/virtual-channel@0:hvctl for contacting hypervisor

[ May 14 16:41:47 Method "start" exited with status 1 ]

[ May 14 16:41:47 Executing start method ("/opt/SUNWldm/bin/ldmd_start") ]

Added to channel ds, service dr-cpu, versions 1.0

Added to channel ds, service fma-cpu-service, versions 1.0

Added to channel fmactl, service fma-phys-cpu-service, versions 1.0

Added to channel ds, service fma-mem-service, versions 1.0

Added to channel fmactl, service fma-phys-mem-service, versions 1.0

Added to channel fmactl, service fma-pri-service, versions 1.0

Added to channel spds, service mdstore, versions 1.0

Added to channel ds, service md-update, versions 1.0

Added to channel ds, service domain-shutdown, versions 1.0

Added to channel ds, service domain-panic, versions 1.0

Added to channel spds, service pri, versions 1.0

Added to channel ds, service var-config, versions 1.0

warning: Error attempting to obtain the PRI from the system controller: Timer expired

warning: Error attempting to obtain the PRI from the system controller: Timer expired

warning: Error attempting to obtain the PRI from the system controller: Timer expired

fatal error: Could not obtain the PRI from the system controller

doing a ls on the virtual-channel...

crw-1 rootsys94, 0 May 14 16:41 /devices/virtual-devices@100/channel-devices@200/virtual-channel@0:hvctl

Machine is on Firmware 6.4.4 and patched up with the required patches. Any suggestions on what is going on here?

Thanks for looking.

[2669 byte] By [paebersolda] at [2007-11-27 4:15:43]
# 1

Two cases where I've known this to occur are:

1) Upgrading from the Early Access bits without blowing away old configs

2) Rebooting the control domain with guests bound/active.

When you say "Just finished the setup of ldoms" - what commands have you run ?

Powering off the control domain and running 'resetsc' on the SC may fix it.

merwicka at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 2

I had done the following...

install OS

install ldom patches

reboot box

install ldom software LDoms_Manager-1_0-RR (instal-ldm)

and ldmd didn't fire up.

few reboots later still no joy. However your suggestion of power off and resetsc worked a treat. ldmd up and running. Many thanks.

paebersolda at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 3
I did the same, and I got the ldmd core-dumped.As I did this with the RC3, it worked fine.
mm09a at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 4
Did you install the required ALOM CMT firmware? Also, if you were using RC3 or older, you have to delete your old SP configs from the ALOM. They'll cause nasty issues!
unixconsolea at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 5
I had the same issue when I upgrade from RC3 to 1.0 RR. After reset the SC, the LDom manager finally started.
SteveCa at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 6

I had done the same that you

install OS

install ldom patches

reboot box

install ldom software LDoms_Manager_1.0_RC3 instead of LDoms_Manager-1_0-RR (instal-ldm)

and ldmd didn't fire up.

Your suggestion of power off and resetsc didn't work. ldmd down.

I did the next

sc>poweroff

sc>resetsc

sc>poweron -c

Have you any more idea?

Thanks

vickyubua at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 7
Try the followingsSC> bootmode config="factory-default"SC> poweroffSC> resetsc -ySC> poweron
SteveCa at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 8
Never mind. All set.Message was edited by: nightengale
nightengalea at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...
# 9
Thanks StevecNow ldm is runningThank you very much
vicky@ubu.esa at 2007-7-12 9:22:06 > top of Java-index,Administration Tools,Logical Domains for CoolThreads Servers...