Configuring second service domain
Has anybody successfully configure a second service domain apart from the control domain? The following are the steps:
1) Create a split PCI configuration
2) Patch and install Logical Domain Manager on second service domain
3) Upon reboot, Logical Domain Manager fails to start (one LDM only?)
4) Uninstall Logical Domain Manager on second service domain
5) Configure network and disk services on Control Domain
# second service domain is lds1
$ ldm add-vds lds1-vds0 lds1
$ ldm add-vsw net-dev=e1000g2 lds1-vsw0 lds1 (e1000g2 is on the PCI bus on the second service domain)
$ shutdown -y -g0 -i6
Upon restart, OBP can no longer find the boot disk which is a file image on a disk in the Control Domain.
$ telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is'^]'.
Connecting to console"lds1" in group"lds1" ....
Press ~?for control options ..
~ ?
{0} ok boot
Boot device: net File and args:
ERROR: boot-read fail
Can't locate boot device
There is no way I can stop the second service domain as well.
$ ldm list
Name StateFlagsConsVCPU MemoryUtil Uptime
primary active-t-cvSP44G13% 11m
lds1 active-td-v500044G100% 1h 15m
$ ldm stop lds1
LDom lds1 stop notification failed
What has went wrong?
Please also clear my doubts:
1) The Logical Domain Manager should be installed only on Control Domain or each Service Domain as well?
2) Where do I configure the services for the second service domain? control domain or in the second service domain?
3) How do I add devices that belong to the second service domain if the configuration is done in control domain? Wouldn't there be naming conflict?
For example, before PCI split, the control domain has e1000g0 - e1000g3 network interfaces. After the PCI split, the e1000g0 and e1000g1 belong to control domain, and e1000g2 and e1000g3 belong to the second service domain. However, inside both domains the network interfaces are simply e1000g0 and e1000g1.
