Earlier Post we have created Control or Primary Domain by installing Logical Domain Manager (LDM), Initially all the resources are allocated to the Control Domain. We should have some resources to create a Logical domain. Let we start allocate or restrict the resource of control Domain.- Basic of LDOM
- Install Prerequisites Packages for LDM.
- Install LDM Agents. (LDM download link)
- Allocate Resource to Control Domain.
- Adding/Deleting Service Domain
- Adding/Deleting Logical Domain.
- Export ISO Image to Logical Domain
- Adding I/O Domain.
- Migrate the Logical Domain to another the Primary Domain.
Allocate Resource to Control Domain:
By assigning listed resources to the control domain, we can make available the remaining resources to Logical domain. According to the server Model we can allocate the resource to our control Domain. Here we are using T2000 server.
| Resources | Requirements |
|---|---|
| CPUs | Minimum of 8 CPUs cores |
| System Memory | Minimum of 2 GB Memory |
| MAUs (Cryptographic devices) (Optional) | Minimum of 1 MAUs |
To check the available resources on control domain ( Here we are using T2000 server).
[root@unixrock /]# ldm list-devices -a
------------------------------------------------------------------------------
Notice: the LDom Manager is running in configuration mode. Configuration and
resource information is displayed for the configuration under construction;
not the current active configuration. The configuration being constructed
will only take effect after it is downloaded to the system controller and
the host is reset.
------------------------------------------------------------------------------
CORE
ID %FREE CPUSET
0 0 (0, 1, 2, 3)
1 0 (4, 5, 6, 7)
2 0 (8, 9, 10, 11)
3 0 (12, 13, 14, 15)
4 0 (16, 17, 18, 19)
5 0 (20, 21, 22, 23)
6 0 (24, 25, 26, 27)
7 0 (28, 29, 30, 31)
VCPU
PID %FREE PM
0 0 no
1 0 no
2 0 no
3 0 no
4 0 no
5 0 no
6 0 no
7 0 no
8 0 no
9 0 no
10 0 no
11 0 no
12 0 no
13 0 no
14 0 no
15 0 no
16 0 no
17 0 no
18 0 no
19 0 no
20 0 no
21 0 no
22 0 no
23 0 no
24 0 no
25 0 no
26 0 no
27 0 no
28 0 no
29 0 no
30 0 no
31 0 no
MAU
ID CPUSET BOUND
0 (0, 1, 2, 3) primary
1 (4, 5, 6, 7) primary
2 (8, 9, 10, 11) primary
3 (12, 13, 14, 15) primary
4 (16, 17, 18, 19) primary
5 (20, 21, 22, 23) primary
6 (24, 25, 26, 27) primary
7 (28, 29, 30, 31) primary
MEMORY
PA SIZE BOUND
0x0 512K _sys_
0x80000 1536K _sys_
0x200000 62M _sys_
0x4000000 64M _sys_
0x8000000 8064M primary
IO
DEVICE PSEUDONYM BOUND OPTIONS
pci@780 bus_a yes bypass=on
pci@7c0 bus_b yes bypass=on
[root@unixrock /]#
from above output we confirmed that all the resources are currently utilized by Primary or Control Domain.
Let we start allocate the limited resources to Primary domain. Let we start from virtual CPUs.
Allocating 8 virtual CPU to primary
[root@unixrock /]# ldm set-vcpu 8 primary ------------------------------------------------------------------------------ Notice: the LDom Manager is running in configuration mode. Any configuration changes made will only take effect after the machine configuration is downloaded to the system controller and the host is reset. ------------------------------------------------------------------------------ [root@unixrock /]#Allocating 2G Memory to Primary
[root@unixrock /]# ldm set-memory 2G primary ------------------------------------------------------------------------------ Notice: the LDom Manager is running in configuration mode. Any configuration changes made will only take effect after the machine configuration is downloaded to the system controller and the host is reset. ------------------------------------------------------------------------------ [root@unixrock /]#Allocating 1 MAUs to Primary
[root@unixrock /]# ldm set-mau 1 primary ------------------------------------------------------------------------------ Notice: the LDom Manager is running in configuration mode. Any configuration changes made will only take effect after the machine configuration is downloaded to the system controller and the host is reset. ------------------------------------------------------------------------------ [root@unixrock /]#NOTE : By Adding MAUs (Cryptographics) resources (Optional), we can speed up the warm migration while we transferring the data by using encryption.
[root@unixrock /]# ldm list-bindings primary
------------------------------------------------------------------------------
Notice: the LDom Manager is running in configuration mode. Configuration and
resource information is displayed for the configuration under construction;
not the current active configuration. The configuration being constructed
will only take effect after it is downloaded to the system controller and
the host is reset.
------------------------------------------------------------------------------
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-c-- SP 8 2G 0.0% 5m
UUID
f44b4e9e-330c-4a20-c22e-a18c1c6f61b1
MAC
00:14:4f:82:5c:ee
HOSTID
0x84825cee
CONTROL
failure-policy=ignore
DEPENDENCY
master=
CORE
CID CPUSET
0 (0, 1, 2, 3)
1 (4, 5, 6, 7)
VCPU
VID PID CID UTIL STRAND
0 0 0 0.3% 100%
1 1 0 0.0% 100%
2 2 0 0.2% 100%
3 3 0 0.0% 100%
4 4 1 0.0% 100%
5 5 1 0.0% 100%
6 6 1 0.0% 100%
7 7 1 0.1% 100%
MAU
ID CPUSET
0 (0, 1, 2, 3)
MEMORY
RA PA SIZE
0x408000000 0x8000000 2G
IO
DEVICE PSEUDONYM OPTIONS
pci@780 bus_a bypass=on
pci@7c0 bus_b bypass=on
VCONS
NAME SERVICE PORT
SP
[root@unixrock /]#
Now we have successfully configured the Control domain. Although, system must be rebooted for the configuration changes take effect.[root@unixrock /]# shutdown -i6 -g0 -y [root@unixrock /]#Perfect !!!! Now we are ready to configure the service Domain.
No comments:
Post a Comment