Information Technology Reference
In-Depth Information
The rest of the Solaris installation is as usual, and is not shown here.
The disk space occupied by virtual disks may be smaller than its apparent size.
As demonstrated by the following lines, a 10 GB virtual disk containing a newly
installed copy of Oracle Solaris takes up only a little more than 2.5 GB of disk
space.
#
ls -l /ldoms/ldom1/
total 5292263
-rw------T 1 root root 10737418240 Aug 14 16:45 disk0.img
#
zfs list rpool/ldoms/ldom1
NAME USED AVAIL REFER MOUNTPOINT
rpool/ldoms/ldom1 2.52G 61.6G 2.52G /ldoms/ldom1
The disk space consumed will depend on how much of the virtual disk has been
populated by the guest operating system and how well the data is compressed if
ZFS compression is being used.
From the control domain, you can use the
ldm
command to observe the activity
of the domain, and to see which CPU, memory, network disk, cryptographic ac-
celerator, and console resources are bound to it. The following example shows the
short and long forms of
ldm list
. The control domain's console is
SP
, indicating
that its console is accessed via the service processor, which is typical for Solaris on
a SPARC server. The line for the guest domain shows the virtual console service
port number used to access the domain's console.
In this example, you can see the number of virtual CPUs and the physical CPUs
to which they are bound. For instance,
ldom1
's virtual CPU 0 is on physical CPU
4. The long listing format shows the utilization of each virtual CPU.
#
ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- SP 4 3G 1.2% 1h 3m
ldom1 active -n---- 5000 4 1G 29% 22m
#
ldm list -l ldom1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldom1 active -n---- 5000 4 1G 17% 22m
SOFTSTATE
Solaris running
MAC
00:14:4f:f9:fe:c8
Search WWH ::
Custom Search