|Skip Navigation Links|
|Exit Print View|
|Oracle VM Server for SPARC 3.0 Administration Guide Oracle VM Server for SPARC|
This section shows the syntax usage for the ldm subcommands, defines some output terms, such as flags and utilization statistics, and provides examples that are similar to what you actually see as output.
If you are creating scripts that use ldm list command output, always use the -p option to produce the machine-readable form of the output. See How to Generate a Parseable, Machine-Readable List (-p) for more information.
# ldm --help
For more information about the ldm subcommands, see the ldm(1M) man page.
The following flags can be shown in the output for a domain (ldm list). If you use the long, parseable options (-l -p) for the command, the flags are spelled out; for example, flags=normal,control,vio-service. If not, you see the letter abbreviation; for example -n-cv-. The list flag values are position dependent. Following are the values that can appear in each of the six columns from left to right.
Column 1 – Starting or stopping domains
s starting or stopping
Column 2 – Domain status
Column 3 – Reconfiguration status
d delayed reconfiguration
r memory dynamic reconfiguration
Column 4 – Control domain
c control domain
Column 5 – Service domain
v virtual I/O service domain
Column 6 – Migration status
s source domain in a migration
t target domain in a migration
e error occurred during a migration
The per virtual CPU utilization statistic (UTIL) is shown on the long (-l) option of the ldm list command. The statistic is the percentage of time that the virtual CPU spent executing on behalf of the guest operating system. A virtual CPU is considered to be executing on behalf of the guest operating system except when it has been yielded to the hypervisor. If the guest operating system does not yield virtual CPUs to the hypervisor, the utilization of CPUs in the guest operating system will always show as 100%.
The utilization statistic reported for a logical domain is the average of the virtual CPU utilizations for the virtual CPUs in the domain. The normalized utilization statistic (NORM) is the percentage of time the virtual CPU spends executing on behalf of the guest OS. This value takes into account such operations as cycle skip. Normalized virtualization is only available when your system runs at least version 8.2.0 of the system firmware.
When PM does not perform cycle skip operations, 100% utilization equals 100% normalized utilization. When PM adjusts the cycle skip to four eights, 100% utilization equals 50% utilization. Namely, the CPU effectively has only half the possible number of cycles available. So, a fully utilized CPU has a 50% normalized utilization. Use the ldm list or ldm list -l command to show normalized utilization for both virtual CPUs and the guest OS.
# ldm -V
# ldm list
# ldm list -l
# ldm list -e
# ldm list -p
# ldm list -o resource[,resource...] ldom
console – Output contains virtual console (vcons) and virtual console concentrator (vcc) service
core – Output contains information about domains that have whole cores allocated
cpu – Output contains information about the virtual CPU (vcpu), physical CPU (pcpu), and core ID
crypto – Cryptographic unit output contains Modular Arithmetic Unit (mau) and any other supported cryptographic unit, such as the Control Word Queue (CWQ)
disk – Output contains virtual disk (vdisk) and virtual disk server (vds)
domain – Output contains variables (var), host ID (hostid), domain state, flags, UUID, and software state
memory – Output contains memory
network – Output contains media access control (mac) address , virtual network switch (vsw), and virtual network (vnet) device
physio – Physical input/output contains peripheral component interconnect (pci) and network interface unit (niu)
resmgmt – Output contains dynamic resource management (DRM) policy information, indicates which policy is currently running, and lists constraints related to whole-core configuration
serial – Output contains virtual logical domain channel (vldc) service, virtual logical domain channel client (vldcc), virtual data plane channel client (vdpcc), virtual data plane channel service (vdpcs)
stats – Output contains statistics that are related to resource management policies
status – Output contains status about a domain migration in progress
The following examples show various subsets of output that you can specify:
List CPU information for the control domain
# ldm list -o cpu primary
List domain information for a guest domain
# ldm list -o domain ldm2
List memory and network information for a guest domain
# ldm list -o network,memory ldm1
List DRM policy information for a guest domain
# ldm list -o resmgmt,stats ldm1
# ldm list-variable variable-name ldom
For example, the following command shows the value for the boot-device variable on the ldg1 domain:
# ldm list-variable boot-device ldg1 boot-device=/virtual-devices@100/channel-devices@200/disk@0:a
# ldm list-bindings ldom
Example 10-13 Configurations List
The ldm list-config command lists the logical domain configurations that are stored on the service processor. When used with the -r option, this command lists those configurations for which autosave files exist on the control domain.
# ldm list-config factory-default 3guests foo [next poweron] primary reconfig-primary
The labels to the right of the configuration name mean the following:
[current] – Last booted configuration, only as long as it matches the currently running configuration; that is, until you initiate a reconfiguration. After the reconfiguration, the annotation changes to [next poweron].
[next poweron] – Configuration to be used at the next power cycle.
# ldm list-devices -a
# ldm list-devices mem MEMORY PA SIZE 0x14e000000 2848M
# ldm list-services
To the Logical Domains Manager, constraints are one or more resources you want to have assigned to a particular domain. You either receive all the resources you ask to be added to a domain or you get none of them, depending upon the available resources. The list-constraints subcommand lists those resources you requested assigned to the domain.
# ldm list-constraints ldom
# ldm list-constraints -x ldom
# ldm list-constraints -p