The Oracle VM Agent setup tool configures the control domain with 1 CPU core. If the server has 16 GB of memory or more, the control domain is allocated 8 GB of memory. If the server has less than 16 GB of memory, the control domain is allocated 2 GB of memory and a warning message is displayed [1] . If you encounter performance issues because the control domain does not have enough CPUs or memory, you can increase the number of CPU cores and the amount of memory assigned to the control domain. Note, with the Oracle VM Agent, you cannot assign less than 1 CPU core and 2 GB of memory to the control domain, while 8 GB of memory for the control domain is the recommended minimum.
Use the following procedure to change the number of CPU cores or the amount of memory assigned to the control domain:
To change the number of CPU cores or memory assigned to the control domain
Connect as root to the control domain.
Specify the number of CPU cores to assign to the control domain. For example, to assign 2 cpu cores to the control domain:
# svccfg -s ovs-config setprop config/core_count=2
Specify the amount of memory (in GB) to assign to the control domain. For example, to assign 16 GB of memory to the control domain:
# svccfg -s ovs-config setprop config/memory_size=16
Refresh and restart the ovs-config service:
# svcadm refresh ovs-config # svcadm restart ovs-config
The restart of the ovs-config service automatically reconfigures the control domain with the specified number of CPU cores and amount of memory and restarts the other Oracle VM Agentservices (ovs-agent and ovmwatch). Check that all services come back online:
# svcs ovm/* STATE STIME FMRI online 15:40:59 svc:/ovm/ovs-config:default online 15:40:59 svc:/ovm/ovmwatch:default online 15:41:18 svc:/ovm/ovs-agent:default
If a service fails to restart and goes into the maintenance state, check for errors in the log file of the service. The restart of the ovs-config service fails if the control domain cannot be configured with the specified number of CPU cores and amount of memory.
Note that the reconfiguration of the control domain is achieved dynamically without rebooting the control domain, but the new configuration persists if the control domain is rebooted. The reconfiguration can be achieved while virtual machines are running, and the change impacts any running virtual machines. The server can continue to be managed with Oracle VM Manager while the ovs-agent is not fully restarted.
To restore the default configuration, use the same steps to set the core_count and memory_size to 0.
[1] This is only likely to occur on older SPARC systems such as the T2, T2+ and the T3, since these systems can have a minimum of 4 GB or 8 GB of memory. Newer servers like the T4 (with a minimum of 16 GB) and the T5 (with a minimum of 128 GB), are unaffected and are automatically configured so that the control domain is allocated a full 8 GB of memory.