test

Logical Domains 1.3 Administration Guide

Chapter 4 Setting Up Services and Logical Domains

This chapter describes the procedures necessary to set up default services, your control domain, and guest domains.

You can also use the Logical Domains Configuration Assistant to configure logical domains and services. See Appendix D, Logical Domains Configuration Assistant.

This chapter covers the following topics:

Output Messages

You receive the following message after the first operation that cannot be performed dynamically on any device or for any service on the primary domain:


Initiating delayed reconfigure operation on LDom primary. All
configuration changes for other LDoms are disabled until the
LDom reboots, at which time the new configuration for LDom
primary will also take effect.

You receive the following notice after every subsequent operation on the primary domain until reboot:


Notice: LDom primary is in the process of a delayed
reconfiguration. Any changes made to this LDom will only take
effect after it reboots.

Creating Default Services

You must create the following virtual default services initially to be able to use them later:

ProcedureCreate Default Services

  1. Create a virtual disk server (vds) to allow importing virtual disks into a logical domain.

    For example, the following command adds a virtual disk server (primary-vds0) to the control domain (primary).


    primary# ldm add-vds primary-vds0 primary

  2. Create a virtual console concentrator (vcc) service for use by the virtual network terminal server daemon (vntsd) and as a concentrator for all logical domain consoles.

    For example, the following command would add a virtual console concentrator service (primary-vcc0) with a port range from 5000 to 5100 to the control domain (primary).


    primary# ldm add-vcc port-range=5000-5100 primary-vcc0 primary

  3. Create a virtual switch service (vsw) to enable networking between virtual network (vnet) devices in logical domains.

    Assign a GLDv3-compliant network adapter to the virtual switch if each of the logical domains needs to communicate outside the box through the virtual switch.

    For example, the following command would add a virtual switch service (primary-vsw0) on network adapter driver nxge0 to the control domain (primary).


    primary# ldm add-vsw net-dev=nxge0 primary-vsw0 primary

    This command automatically allocates a MAC address to the virtual switch. You can specify your own MAC address as an option to the ldm add-vsw command. However, in that case, it is your responsibility to ensure that the MAC address specified does not conflict with an already existing MAC address.

    If the virtual switch being added replaces the underlying physical adapter as the primary network interface, it must be assigned the MAC address of the physical adapter, so that the Dynamic Host Configuration Protocol (DHCP) server assigns the domain the same IP address. See Enabling Networking Between the Control/Service Domain and Other Domains.


    primary# ldm add-vsw mac-addr=2:04:4f:fb:9f:0d net-dev=nxge0 primary-vsw0 primary

  4. Verify the services have been created by using the list-services subcommand.

    Your output should look similar to the following.


    primary# ldm list-services primary
VDS
    NAME             VOLUME         OPTIONS          DEVICE
    primary-vds0
 
VCC
    NAME             PORT-RANGE
    primary-vcc0     5000-5100
 
VSW
    NAME             MAC               NET-DEV   DEVICE     MODE
    primary-vsw0     02:04:4f:fb:9f:0d nxge0     switch@0   prog,promisc

Initial Configuration of the Control Domain

Initially, all system resources are allocated to the control domain. To allow the creation of other logical domains, you must release some of these resources.

ProcedureSet Up the Control Domain

Note –

This procedure contains examples of resources to set for your control domain. These numbers are examples only, and the values used might not be appropriate for your control domain.

  1. Determine whether you have cryptographic devices in the control domain.


    primary# ldm list -o crypto primary

  2. Assign cryptographic resources to the control domain.

    The following example would assign one cryptographic resource to the control domain, primary. This leaves the remainder of the cryptographic resources available to a guest domain.


    primary# ldm set-mau 1 primary

  3. Assign virtual CPUs to the control domain.

    For example, the following command would assign 4 virtual CPUs to the control domain, primary. This leaves the remainder of the virtual CPUs available to a guest domain.


    primary# ldm set-vcpu 4 primary

  4. Assign memory to the control domain.

    For example, the following command would assign 4 gigabytes of memory to the control domain, primary. This leaves the remainder of the memory available to a guest domain.


    primary# ldm set-memory 4G primary

  5. Add a logical domain machine configuration to the service processor (SP).

    For example, the following command would add a configuration called initial.


    primary# ldm add-config initial

  6. Verify that the configuration is ready to be used at the next reboot.


    primary# ldm list-config
factory-default
initial [next poweron]

    This list subcommand shows the initial configuration set will be used once you powercycle.

Rebooting to Use Logical Domains

You must reboot the control domain for the configuration changes to take effect and for the resources to be released for other logical domains to use.

ProcedureReboot

  1. Shut down and reboot the control domain.


    primary# shutdown -y -g0 -i6
    Note –

    Either a reboot or powercycle instantiates the new configuration. Only a powercycle actually boots the configuration saved to the service processor (SP), which is then reflected in the list-config output.

Enabling Networking Between the Control/Service Domain and Other Domains

By default, networking between the control domain and other domains in the system is disabled. To enable this, the virtual switch device should be configured as a network device. The virtual switch can either replace the underlying physical device (nxge0 in this example) as the primary interface or be configured as an additional network interface in the domain.

Note –

Perform the following procedure from the control domain's console, as the procedure could temporarily disrupt network connectivity to the domain.

ProcedureConfigure the Virtual Switch as the Primary Interface

  1. Print out the addressing information for all interfaces.


    primary# ifconfig -a

  2. Plumb the virtual switch. In this example, vsw0 is the virtual switch being configured.


    primary# ifconfig vsw0 plumb

  3. (Optional) To obtain the list of all virtual switch instances in a domain, you can list them.


    primary# /usr/sbin/dladm show-link | grep vsw
vsw0            type: non-vlan  mtu: 1500       device: vsw0

  4. Unplumb the physical network device assigned to the virtual switch (net-dev), which is nxge0 in this example.


    primary# ifconfig nxge0 down unplumb

  5. To migrate properties of the physical network device (nxge0) to the virtual switch (vsw0) device, do one of the following:

    • If networking is configured using a static IP address, reuse the IP address and netmask of nxge0 for vsw0.


      primary# ifconfig vsw0 IP_of_nxge0 netmask netmask_of_nxge0 broadcast + up

    • If networking is configured using DHCP, enable DHCP for vsw0.


      primary# ifconfig vsw0 dhcp start

  6. Make the required configuration file modifications to make this change permanent.


    primary# mv /etc/hostname.nxge0 /etc/hostname.vsw0
primary# mv /etc/dhcp.nxge0 /etc/dhcp.vsw0
    Note –

    If necessary, you can also configure the virtual switch as well as the physical network device. In this case, plumb the virtual switch as in Step 2, and do not unplumb the physical device (skip Step 4). You must then configure the virtual switch with either a static IP address or a dynamic IP address. You can obtain a dynamic IP address from a DHCP server. For additional information and an example of this case, see Configuring Virtual Switch and Service Domain for NAT and Routing.

Enabling the Virtual Network Terminal Server Daemon

You must enable the virtual network terminal server daemon (vntsd) to provide access to the virtual console of each logical domain. Refer to the vntsd(1M) man page for information about how to use this daemon.

ProcedureEnable the Virtual Network Terminal Server Daemon

Note –

Be sure that you have created the default service vconscon (vcc) on the control domain before you enable vntsd. See Creating Default Services for more information.

  1. Use the svcadm(1M) command to enable the virtual network terminal server daemon, vntsd(1M).


    primary# svcadm enable vntsd

  2. Use the svcs(1) command to verify that the vntsd daemon is enabled.


    primary# svcs vntsd
STATE          STIME    FMRI
online         Oct_08   svc:/ldoms/vntsd:default

Creating and Starting a Guest Domain

The guest domain must run an operating system that understands both the sun4v platform and the virtual devices presented by the hypervisor. Currently, this means that you must run at least the Solaris 10 11/06 OS. Running the Solaris 10 10/09 OS provides you with all the Logical Domains 1.3 features. See the Logical Domains 1.3 Release Notes for any specific patches that might be necessary. Once you have created default services and reallocated resources from the control domain, you can create and start a guest domain.

ProcedureCreate and Start a Guest Domain

  1. Create a logical domain.

    For example, the following command would create a guest domain named ldg1.


    primary# ldm add-domain ldg1

  2. Add CPUs to the guest domain.

    For example, the following command would add four virtual CPUs to guest domain ldg1.


    primary# ldm add-vcpu 4 ldg1

  3. Add memory to the guest domain.

    For example, the following command would add 2 gigabytes of memory to guest domain ldg1.


    primary# ldm add-memory 2G ldg1

  4. Add a virtual network device to the guest domain.

    For example, the following command would add a virtual network device with these specifics to the guest domain ldg1.


    primary# ldm add-vnet vnet1 primary-vsw0 ldg1

    Where:

    • vnet1 is a unique interface name to the logical domain, assigned to this virtual network device instance for reference on subsequent set-vnet or remove-vnet subcommands.

    • primary-vsw0 is the name of an existing network service (virtual switch) to which to connect.

    Note –

    Steps 5 and 6 are simplified instructions for adding a virtual disk server device (vdsdev) to the primary domain and a virtual disk (vdisk) to the guest domain. To learn how ZFSTM volumes and file systems can be used as virtual disks, see Export a ZFS Volume as a Single Slice Disk and Using ZFS With Virtual Disks.

  5. Specify the device to be exported by the virtual disk server as a virtual disk to the guest domain.

    You can export a physical disk, disk slice, volumes, or file as a block device. The following examples show a physical disk and a file.

    • Physical Disk Example. The first example adds a physical disk with these specifics.


      primary# ldm add-vdsdev /dev/dsk/c2t1d0s2 vol1@primary-vds0

      Where:

      • /dev/dsk/c2t1d0s2 is the path name of the actual physical device. When adding a device, the path name must be paired with the device name.

      • vol1 is a unique name you must specify for the device being added to the virtual disk server. The volume name must be unique to this virtual disk server instance, because this name is exported by this virtual disk server to the clients for adding. When adding a device, the volume name must be paired with the path name of the actual device.

      • primary-vds0 is the name of the virtual disk server to which to add this device.

    • File Example. This second example is exporting a file as a block device.


      primary# ldm add-vdsdev backend vol1@primary-vds0

      Where:

      • backend is the path name of the actual file exported as a block device. When adding a device, the backend must be paired with the device name.

      • vol1 is a unique name you must specify for the device being added to the virtual disk server. The volume name must be unique to this virtual disk server instance, because this name is exported by this virtual disk server to the clients for adding. When adding a device, the volume name must be paired with the path name of the actual device.

      • primary-vds0 is the name of the virtual disk server to which to add this device.

  6. Add a virtual disk to the guest domain.

    The following example adds a virtual disk to the guest domain ldg1.


    primary# ldm add-vdisk vdisk1 vol1@primary-vds0 ldg1

    Where:

    • vdisk1 is the name of the virtual disk.

    • vol1 is the name of the existing volume to which to connect.

    • primary-vds0 is the name of the existing virtual disk server to which to connect.

    Note –

    The virtual disks are generic block devices that are associated with different types of physical devices, volumes, or files. A virtual disk is not synonymous with a SCSI disk and, therefore, excludes the target ID in the disk label. Virtual disks in a logical domain have the following format: cNdNsN, where cN is the virtual controller, dN is the virtual disk number, and sN is the slice.

  7. Set auto-boot and boot-device variables for the guest domain.

    The first example command sets auto-boot\? to true for guest domain ldg1.


    primary# ldm set-var auto-boot\?=true ldg1

    The second example command sets boot-device to vdisk for the guest domain ldg1.


    primary# ldm set-var boot-device=vdisk ldg1

  8. Bind resources to the guest domain ldg1 and then list the domain to verify that it is bound.


    primary# ldm bind-domain ldg1
primary# ldm list-domain ldg1
NAME          STATE    FLAGS  CONS   VCPU MEMORY   UTIL  UPTIME
ldg1          bound    -----  5000   4    2G

  9. To find the console port of the guest domain, you can look at the output of the preceding list-domain subcommand.

    You can see under the heading Cons that logical domain guest 1 (ldg1) has its console output bound to port 5000.

  10. Connect to the console of a guest domain from another terminal by logging into the control domain and connecting directly to the console port on the local host.


    $ ssh admin@controldom.domain
$ telnet localhost 5000

  11. Start the guest domain ldg1.


    primary# ldm start-domain ldg1

Installing Solaris OS on a Guest Domain

This section provides instructions for several different ways you can install the Solaris OS on a guest domain.

ProcedureInstall Solaris OS on a Guest Domain From a DVD

  1. Insert the Solaris 10 OS DVD into the DVD drive.

  2. Stop the volume management daemon, vold(1M) on the primary domain.


    primary# svcadm disable volfs

  3. Stop and unbind the guest domain (ldg1). Then add the DVD with DVDROM media as a secondary volume (dvd_vol@primary-vds0) and virtual disk (vdisk_cd_media), for example.

    c0t0d0s2 is where the Solaris OS media resides


    primary# ldm stop ldg1
primary# ldm unbind ldg1
primary# ldm add-vdsdev /dev/dsk/c0t0d0s2 dvd_vol@primary-vds0
primary# ldm add-vdisk vdisk_cd_media dvd_vol@primary-vds0 ldg1

  4. Check to see that the DVD is added as a secondary volume and virtual disk.


    primary# ldm list-bindings
NAME             STATE    FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME 
primary          active   -n-cv   SP      4     4G       0.2%  22h 45m
...
VDS 
   NAME             VOLUME         OPTIONS          DEVICE
   primary-vds0     vol1                            /dev/dsk/c2t1d0s2
   dvd_vol                                          /dev/dsk/c0t0d0s2
....
------------------------------------------------------------------------------
NAME             STATE    FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
ldg1             inactive -----           60    6G
...
DISK
   NAME             VOLUME                      TOUT DEVICE  SERVER
   vdisk1           vol1@primary-vds0
   vdisk_cd_media   dvd_vol@primary-vds0
....

  5. Bind and start the guest domain (ldg1).


    primary# ldm bind ldg1
primary# ldm start ldg1
LDom ldg1 started
primary# telnet localhost 5000
Trying 027.0.0.1...
Connected to localhost.
Escape character is '^]'.
 
Connecting to console "ldg1" in group "ldg1" ....
Press ~? for control options ..

  6. Show the device aliases in the client OpenBootTM PROM.

    In this example, see the device aliases for vdisk_cd_media, which is the Solaris DVD, and vdisk1, which is a virtual disk on which you can install the Solaris OS.


    ok devalias
vdisk_cd_media  /virtual-devices@100/channel-devices@200/disk@1
vdisk1          /virtual-devices@100/channel-devices@200/disk@0
vnet1           /virtual-devices@100/channel-devices@200/network@0
virtual-console /virtual-devices/console@1
name            aliases

  7. On the guest domain's console, boot from vdisk_cd_media (disk@1) on slice f.


    ok boot vdisk_cd_media:f -v
Boot device: /virtual-devices@100/channel-devices@200/disk@1:f  File and args: -s
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.

  8. Continue with the Solaris OS installation menu.

ProcedureInstall Solaris OS on a Guest Domain From a Solaris ISO File

  1. Unbind the guest domain.

    The following shows ldg1 as the guest domain:


    primary# ldm unbind ldg1

  2. Add the Solaris ISO file as a secondary volume and virtual disk.

    The following uses solarisdvd.iso as the Solaris ISO file, iso_vol@primary-vds0 as a secondary volume, and vdisk_iso as a virtual disk:


    primary# ldm add-vdsdev /export/solarisdvd.iso  iso_vol@primary-vds0
primary# ldm-vdisk vdisk vdisk_iso iso_vol@primary-vds0 ldg1

  3. Check to see that the Solaris ISO file is added as a secondary volume and virtual disk.


    primary# ldm list-bindings
NAME             STATE    FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME 
primary          active   -n-cv   SP      4     4G       0.2%  22h 45m
...
VDS 
   NAME             VOLUME         OPTIONS          DEVICE
   primary-vds0     vol1                            /dev/dsk/c2t1d0s2
   iso_vol                                          /export/solarisdvd.iso
....
------------------------------------------------------------------------------
NAME             STATE    FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
ldg1             inactive -----           60    6G
...
DISK
   NAME             VOLUME                      TOUT DEVICE  SERVER
   vdisk1           vol1@primary-vds0
   vdisk_iso        iso_vol@primary-vds0
....

  4. Bind and start the guest domain (ldg1).


    primary# ldm bind ldg1
primary# ldm start ldg1
LDom ldg1 started
primary# telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
 
Connecting to console "ldg1" in group "ldg1" ....
Press ~? for control options ..

  5. Show the device aliases in the client OpenBoot PROM.

    In this example, see the device aliases for vdisk_iso, which is the Solaris ISO image, and vdisk_install, which is the disk space.


    ok devalias
vdisk_iso       /virtual-devices@100/channel-devices@200/disk@1
vdisk1          /virtual-devices@100/channel-devices@200/disk@0
vnet1           /virtual-devices@100/channel-devices@200/network@0
virtual-console /virtual-devices/console@1
name            aliases

  6. On the guest domain's console, boot from vdisk_iso (disk@1) on slice f.


    ok boot vdisk_iso:f -v
Boot device: /virtual-devices@100/channel-devices@200/disk@1:f  File and args: -s
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.

  7. Continue with the Solaris OS installation menu.

ProcedureJump-Start a Guest Domain

  1. To jump-start a guest domain, use a normal JumpStart procedure with the following profile syntax changes from a regular Solaris OS JumpStart procedure to a JumpStart procedure specific to Logical Domains as shown in the following two examples.

    Normal JumpStart Profile 


    filesys c1t1d0s0 free /
filesys c1t1d0s1 2048 swap
filesys c1t1d0s5 120 /spare1
filesys c1t1d0s6 120 /spare2

    Virtual disk device names in a logical domain differ from physical disk device names in that they do not contain a target ID (tN) in the device name. Instead of the normal cNtNdNsN format, virtual disk device names are of the format cNdNsN, where cN is the virtual controller, dN is the virtual disk number, and sN is the slice. Modify your JumpStart profile to reflect this change as in the following profile example.

    Actual Profile Used for a Logical Domain 


    filesys c0d0s0 free /
filesys c0d0s1 2048 swap
filesys c0d0s5 120 /spare1
filesys c0d0s6 120 /spare2
    Note –

    You must use the MAC address of the virtual network (vnet) device as reported by the ldm(1M) command for your jumpstart configuration and not the one reported in the banner for the guest.