This chapter discusses various methods for using the virt-install tool to install operating systems as virtual machines. The virt-install program can be run as a command-line utility, with parameters specified through options, or interactively, in response to a series of prompts.x64 and x86 based systems are supported.To run Windows hardware-assisted virtual machine (HVM) domains, an HVM-capable machine that is running Solaris xVM dom0 is required. A machine is HVM-capable if it is has either an AMD Opteron Revision F or later, or an Intel CPU with VT extensions. To determine whether a machine is HVM-capable, run the virt-install program with no arguments. If the system asks whether you want a fully virtualized guest, you have an HVM-capable system.If this question is not displayed, then you have a non-HVM capable system. Become superuser, or assume the Primary Administrator role. Type virt-install without options.# virt-installIf you see the following display, you have an HVM-capable system:Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. Types of installations that can be performed include the following:Interactive Command line, with options supplied Netinstall ISO image Solaris JumpStart You will need to supply the guest domain information listed below.nameName for the guest domain. Each guest domain must have a unique name. This name serves as the label of the guest operating system. The name must be a real hostname for network installationss to work. image locationLocation of the installation software. Installation must be over a network (which includes an NFS share from the local host operating system) or be an ISO install.For example:--location nfs:my.nfs.server.com:/home/install/test/mydomainFor HVM, an ISO or CDROM device should be given instead of an image location.See virt-install Examples.Installations using http or ftp, as shown in the following examples, are supported for Linux paravirtualized domain installations only:http://my.http.server.com:/install/test/mydomain ftp://my.ftp.server.com:/install/test/mydomain vcpusThe number of CPUs for the guest domain. The default is 1. You can assign specific CPUs. If undefined, the hypervisor makes the selection. memoryAmount of RAM to be allocated to the guest, in megabytes. A running domain should use a minimum of 512 megabytes. However, to install the guest domain, 1 Gbyte (1024 megabytes) is required. graphicsGraphical console. Default is graphics. The nographics option applies to paravirtual guests only. If you intend to enable graphics support, you must decide whether the graphical installer should be used. (Optional) Virtual network interface MAC addressThis is the MAC address of the dom0's network interface that you want the domU to use to send and receive internet traffic. By default, the hypervisor tools uses the first available network interface card (NIC) when creating guest domains. The default values for the action to be taken on a domU shutdown, reboot, or crash are set by virt-install. You currently cannot change these defaults. Usage examples are provided in subsequent sections of this chapter.--accelerateUse kernel acceleration capabilities. --arch=archThe CPU architecture to simulate. Acceptable values are x86 and sparc. --autocf=AUTOCFJumpStart path, which is nfs:host:/path. The path must point to the directory containing JumpStart information, b bridge, --bridge=bridgeBridge to which to connect the network interface. If you do not specify a bridge, the system attempts to determine the default. c cdrom, --cdrom=cdromFile to use as a virtual CD-ROM device for fully virtualized guests. This option works with HVM domains and is ignored with paravirtualized domains. To install from cdrom, pass the ISO path to --location. --check-cpuVerify that assigned VCPUs do not exceed physical CPUs and output a warning if this is the case. --connect=URIConnect to hypervisor at URI. d, --debugDisplay debugging information. f disk_image, --file=disk_imageVirtual Backing Device (VBD), such as the file to use as the disk image location.The file is created by virt-install if the file does not exist. By default, virt-install creates a sparse image file. To create a non-sparse image, use the --nonsparse option on the virt-install command line. With appropriate permissions, the VBD can be on a remote system and specified with the /net/system construction.A physical partition or device can be used, such as /dev/dsk/c0t0d0s3. h,--helpDisplay list of virt-install options. k keymap, --keymap=keymapSet up keymap for a graphical console. l location, --location=locationInstallation source for a paravirtualized domU, such as nfs:host:/path. m mac_addr, --mac=mac_addrFixed MAC address for the domU. If the keywords none or random are specified, a random address will be used. n name, --name=nameName of the domU. --noacpiDisables Advanced Configuration and Power Interface (ACPI) for a fully virtualized domU. Overrides stored configuration setting specified by the --os-type and --os-variant options. --noapicDisables Programmable Interrupt Controller (APIC) for a fully virtualized domU. Overrides stored configuration setting specified by the --os-type and --os-variant options. --noautoconsoleDo not automatically try to connect to the guest console. --nonsparseDo not use sparse files for disks..Note that the use of this option causes domU creation to be significantly slower. --ostype=os_typeThe OS type for fully virtualized guests. Acceptable values are solaris, unix, linux, and windows. p, --paravirtIndicates that guest is paravirtualized. -p -nographicsThis is a paravirtual installation. Do not set up a graphical console for the guest. The console is serial. These two options are always used together.When using virt-install to create a paravirtualized guest, --nographics must be used to override the default mode.By default, consoles for HVM guests are graphics consoles. HVM installs may specify either VNC (--vnc) or Simple DirectMedia Layer (SDL) (--sdl) for graphics support. --variant=os_variantThe OS variant for fully virtualized guests. Acceptable values are fedora6, rhel5, solaris10, win2k, and vista. --vcpus=NSets the number of vcpus for the guest domain. r mem_amount, --ram=mem_amountMemory to allocate for domU instance, in megabytes.To optimize the current dom0 handling of memory, you should size memory allocated to a domU to be no more than approximately 55 percent of the total physical memory installed in your system, and then divide the allocated memory among the domUs you intend to run concurrently.For example, if you have 2 Gbytes of RAM installed in your system, you should not allocate more than approximately 1.1 Gbytes of RAM to domUs. Thus, if you only intend to run one domU, you can allocate the entire 1.1 Gbytes to it. If you intend to run two domUs concurrently, you should not allocate more than 550 MB of RAM to either domain, etc. Use 1 Gbyte or more for installations, and reduce the amount later if necessary. s disksize, --file-size=disksizeSize of the disk image (if it does not exist), in Gbytes. --sdlUse Simple DirectMedia Layer (SDL) for graphics support. This option works with some guest domains, including HVM, but cannot be used with Solaris. For more information on SDL, see Simple DirectMedia Layer. u UUID, --uuid=UUIDSpecifies the UUID as a 32–digit hexadecimal number, for the domU. If no UUID is specified, the system generates a random UUID. v , --hvmSpecifies that the guest is a hardware assisted virtual machine (HVM). --vcpus=vcpusNumber of virtual CPUs (VCPUs) to configure for the domU.From dom0, you can dynamically reset the number of active VCPUs allocated for the domain by using:# xm vcpu-set domain number_vCPUs -vncUse Virtual Network Computing (VNC) for graphics support. The graphical output of the guest is redirected over VNC. This option works with HVM domains but it does not work with paravirtualized domains. --vncportPort to use for VNC. w network, --network=networkConnect the guest to a virtual network, forwarding to the physical network with Network Address Translation (NAT). x extra_args, --extra-args=extra_argsWhen installing paravirtualized guests, specifies additional arguments to pass to the installer. After you enter the required information, the installation starts. If you enabled graphics, a VNC window containing the graphical installer opens. If graphics are not enabled, the text installer displays.For more information, see the virt-install1M man page. This example uses virt-install with options to install a Solaris domU from the command line using an ISO image. The command line options specify for virt-install to create an 18–Gbyte root disk image file /xvm/domu-x16.img. A specific MAC address is used for a particular DHCP configuration. The option --nographics because this is a Solaris paravirtualized configuration. See virt-install Examples for examples of other types of guest domains. If you invoke virt-install with command line options but do not supply all required information, the tool prompts you for the needed information.machine:root> virt-install --nographics -n domu-x16 --paravirt \ -f /xvm/domu-x16.img -r 1011 --mac=aa:ff:bb:aa:28:16 -s 18 \ -l /net/inst-server/export/xVM/x_iso/63-0419-nd.iso Starting install... Creating domain... SunOS Release 5.11 Version 64-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Configuring /dev Solaris Interactive Text (Console session) Using install cd in /dev/dsk/c0d1p0 Using RPC Bootparams for network configuration information. Attempting to configure interface xnf0... Skipped interface xnf0 Setting up Java. Please wait... Beginning system identification... Searching for configuration file(s)... Search complete. Discovering additional network configuration...When the domain creation completes, sysidcfg runs to complete the system identification.After the domain is created, the sysidcfg is initiated and you are prompted to answer a series of questions. Your screen will look similar to this:SunOS Release 5.11 Version 64-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: my-zone Loading smf(5) service descriptions: 114/114 Select a Language 1. English 2. French 3. German 4. Italian 5. Japanese 6. Korean 7. Simplified Chinese 8. Spanish 9. Swedish 10. Traditional Chinese Please make a choice (1 - 10), or press h or ? for help: What type of terminal are you using? 1) ANSI Standard CRT 2) DEC VT52 3) DEC VT100 4) Heathkit 19 5) Lear Siegler ADM31 6) PC Console 7) Sun Command Tool 8) Sun Workstation 9) Televideo 910 10) Televideo 925 11) Wyse Model 50 12) X Terminal Emulator (xterms) 13) CDE Terminal Emulator (dtterm) 14) Other Type the number of your choice and press Return: . . .For more information on the sysidcfg file, see the sysidcfg4 man page. For an example sysidcfg file, see Understanding the Solaris xVM Server Architecture, Part No 820-3089-102. virt-install -n solarisPV --paravirt -r 1024 \ --nographics -f /export/solarisPV/root.img -s 16 \ -l /ws/xvm-gate/public/isos/72-0910/solarisdvd.iso virt-install -n solarisHVM --hvm -r 1024 --vnc \ -f /export/solarisHVM/root.img -s 16 \ -c /ws/xvm-gate/public/isos/72-0910/solarisdvd.isoFor this version of virt-install, only installs from ISOs and physical CDs are supported for HVM. Network installations are not supported in this version. If a physical CD is used, remember to unmount it after use. # virt-install -n winxp --hvm -r 1024 --vnc \ -f /export/winxp/root.img -s 16 -c /windows/media.isoFor this version of virt-install, only installs from ISOs and physical CDs are supported for HVM. Network installations are not supported in this version. If a physical CD is used, remember to unmount it after use. A normal file is used to store the contents of the guest domain disk image, as opposed to using a ZFS volume, for example. virt-install --name windows1 --ram 1024 \ --cdrom /en_winxp_pro_with_sp2.iso --file /guests/windows1-disk --file-size 10 --vnc zfs create -V 8G pool/solaris1-disk virt-install --name solaris1 --ram 1024 --nographics \ --file /dev/zvol/dsk/pool/solaris1-disk \ --location nfs:install.domain.com:/export/solaris/nv75 \ --autocf nfs:install.domain.com:/export/jumpstart/solaris1 Set the VNC password property in the SMF configuration in xend before starting an HVM domain.Note that the procedures to set the VNC password and remote display are likely to change in a future release.# svccfg -s xvm/xend setprop \ config/vncpasswd = astring: password # svcadm refresh xvm/xend; svcadm restart xvm/xend If you are displaying the VNC session remotely, you must also set the vnc-listen property.For more information on setting up VNC, see the VNC man pages. Refer to How to View the VNC Man Pages.# svccfg -s xvm/xend setprop \ config/vnc-listen = astring: 0.0.0.0 # svcadm refresh xvm/xend; svcadm restart xvm/xend Verify that an xterm can be opened to display HVM installation graphics.# /usr/openwin/bin/xterm Type virt-install at the command line of the dom0 to install a guest domain (domU).# virt-installRespond to the tool's prompts:Provide a name for your new virtualized system, for example, Sdomain_1. Provide the path to installation media containing the files needed to install a domU on the virtual system (URL, path). Provide the root file system path, specifying the disk partition or file the domU should use. You are specifying how you want to assign space on the physical system for the domU. Later, you can add additional storage sources, including network-mounted, to an existing system. Provide the network setup.Virtual Shared physical device Provide the memory and CPU resources allocations. You can revise these values later. Provide mem-max memory setup.A domU can balloon, or expand, its actual memory allocation up to the maximum threshold allocated. Provide the vcpus setting. After you configure the installation server, you can run the virt-install command from dom0. Use the d option to add_install_client to specify that the client use DHCP. If the d option is not specified, the client uses bootparams. For xVM paravirtualized guests, both approaches work. Use your site-specific tool for setting up the appropriate DHCP parameters for the client.To do a network installation, use the l option and provide a path to the network installation image. When giving a machine name or IP address, the domU must be able to get to that install machine directly, not go through a router to another net. For example:-l nfs:install:/export/xvm/xvmgate-70i72-ndYou can also use an IP address instead of a machine name. For example:-l nfs:172.20.25.12:/export/xvm/xvmgate-70i72-ndvirt-install -n gath-01 -r 1000 --nographics -f /dev/dsk/c1t0d0s3 \ -m "aa:04:03:35:a8:06" -p \ -l nfs:install48:/export/xvm/xvmgate-70i72-nd To use the ISO image, use the l option with a full path to the ISO image. If a full path is given instead of the nfs:mach_name:path format of a network installation, then virt-install assumes that this is an ISO image:-l /net/install/export/xvm/solarisdvd.isovirt-install -n gath-01 -r 1000 --nographics -f /dev/dsk/c1t0d0s3 \ -m aa:04:03:35:a8:06 -p \ -l /net/install48/export/xvm/solarisdvd.iso You can quote arguments to options. While arguments, such as the path to an ISO image, are generally not quoted on the command line, quotes might be used in scripts.-l "/net/install48/export/xvm/solarisdvd.iso" JumpStart configuration files are manually created and managed. You can initiate a custom JumpStart through network installation after setting up the server. When you create a profile server, you must ensure that systems can access the JumpStart directory on the profile server during a custom JumpStart installation. Each time that you add a system for network installation, use the add_install_client command to specify the profile server. You use the add_install_client command to create the /etc/bootparams entry for the domU.To do a JumpStart with virt-install, use the --autocf option. For example:--autocf nfs:install:/export/jumpstart/jump-user/x86You cannot use a full path such as:--autocf /net/install/export/jumpstart/jump-user/x86virt-install -n gath-01 -r 1000 --nographics -f /dev/dsk/c1t0d0s3 \ -m aa:04:03:35:a8:06 -p \ -l /net/install48/export/xvm/xvmgate-70i72/solarisdvd.iso --autocf nfs:install:/export/jumpstart/jump-user/x86