Guest Ldom bind error

Question

I have created two guest ldoms ldg1 and ldg3 with the following config
Name: ldg1
State: active
Flags: transition
OS:
Util: 100%
Uptime: 23h 57m
Vcpu: 4
vid pid util strand
0 4 100% 100%
1 5 100% 100%
2 6 100% 100%
3 7 100% 100%
Memory: 2G
real-addr phys-addr size
0x8000000 0x88000000 2G
Vars: nvramrc=devalias disk /virtual-devices@100/channel-devices@200/disk@0
devalias vnet0 /virtual-devices@100/channel-devices@200/network@0
use-nvramrc?=true
Vdisk: vdisk0 vol1@primary-vds0
service: primary-vds0 @ primary
[LDC: 0x1]
Vnet: vnet0 [LDC: 0x4]
[Peer LDom: ldg3, mac-addr: 0:14:4f:f8:1:14]
mac-addr=0:14:4f:fb:fd:3
service: primary-vsw0 @ primary
[LDC: 0x2]
Vcons: [via LDC:3]
ldg1@primary-vcc0 [port:5000]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x0]
Name: ldg3
State: active
Flags: transition
OS:
Util: 100%
Uptime: 10s
Vcpu: 4
vid pid util strand
0 8 100% 100%
1 9 100% 100%
2 10 100% 100%
3 11 100% 100%
Mau: 1
mau cpuset (8, 9, 10, 11)
Memory: 2G
real-addr phys-addr size
0x8000000 0x108000000 2G
Vdisk: vdisk0 vol3@primary-vds0
service: primary-vds0 @ primary
[LDC: 0x0]
Vnet: vnet0 [LDC: 0x2]
[Peer LDom: ldg1, mac-addr: 0:14:4f:fb:fd:3]
mac-addr=0:14:4f:f8:1:14
service: primary-vsw0 @ primary
[LDC: 0x1]
Vcons: [via LDC:3]
ldg3@primary-vcc0 [port:5001]
Vldcc: vldcc0 [Domain Services]
service: primary-vldc0 @ primary
[LDC: 0x4]
When I create a third guest Ldom ldg2 , and issued the command
ldm bind ldg2
I receive this error
Unable to bind console client vcons0
After spending some time to resolve this issue i set the mau to 0 on ldg3
and unbound the domain and again executed a bind on ldg2 - it worked this time.
Has any one encountered this error earlier , I am aware of the fact that adding an mau to the control domain will prevent dynamic reconf of resources , but does adding an mau to guest ldom prevents you from binding other ldoms ? your thoughts are appreciated .

Answer 1

Hi, did you get the same error message about being unable to bind the console client?
The mau count has no bearing on the ability to bind other domains; only the ability to perform cpu DR on the domain that has the maus bound. The real determining factor is probably whether the other guest domain is bound or not. My hypothesis is that the LDom Manager is incorrectly concluding that there's a conflict for the console's TCP port, which is exactly the problem described in CR 6596652.
Can you also confirm that you specifically issued the ldm destroy & ldm create commands to completely destroy & recreate the domain that won't bind?
Thanks.
-Eric