virt-install.pod 53.1 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
=pod

=head1 NAME

virt-install - provision new virtual machines

=head1 SYNOPSIS

B<virt-install> [OPTION]...

=head1 DESCRIPTION

B<virt-install> is a command line tool for creating new KVM, Xen, or Linux
container guests using the C<libvirt> hypervisor management library.
See the EXAMPLES section at the end of this document to quickly get started.

B<virt-install> tool supports graphical installations using (for example)
VNC or SPICE, as well as text mode installs over serial console. The guest
can be configured to use one or more virtual disks, network interfaces,
audio devices, physical USB or PCI devices, among others.

The installation media can be held locally or remotely on NFS, HTTP, FTP
servers. In the latter case C<virt-install> will fetch the minimal files
necessary to kick off the installation process, allowing the guest
to fetch the rest of the OS distribution as needed. PXE booting, and importing
an existing disk image (thus skipping the install phase) are also supported.

Given suitable command line arguments, C<virt-install> is capable of running
completely unattended, with the guest 'kickstarting' itself too. This allows
30 31 32 33 34
for easy automation of guest installs.

Many arguments have sub options, specified like opt1=foo,opt2=bar, etc. Try
--option=? to see a complete list of sub options associated with that
argument, example: virt-install --disk=?
35

36
Most options are not required. Minimum requirements are --name, --memory,
37
guest storage (--disk or --filesystem), and an install option.
38 39


40
=head1 CONNECTING TO LIBVIRT
41

42
=over 4
43

44
=item B<--connect> URI
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74

Connect to a non-default hypervisor. If this isn't specified, libvirt
will try and choose the most suitable default.

Some valid options here are:

=over 4

=item qemu:///system

For creating KVM and QEMU guests to be run by the system libvirtd instance.
This is the default mode that virt-manager uses, and what most KVM users
want.

=item qemu:///session

For creating KVM and QEMU guests for libvirtd running as the regular user.

=item xen:///

For connecting to Xen.

=item lxc:///

For creating linux containers

=back

=back

75 76 77 78



=head1 GENERAL OPTIONS
79 80 81

General configuration parameters that apply to all types of guest installs.

82 83 84
=over 4

=item B<-n> NAME
85

86
=item B<--name> NAME
87 88 89 90 91 92 93

Name of the new guest virtual machine instance. This must be unique amongst
all guests known to the hypervisor on the connection, including those not
currently active. To re-define an existing guest, use the C<virsh(1)> tool
to shut it down ('virsh shutdown') & delete ('virsh undefine') it prior to
running C<virt-install>.

94
=item B<--memory> OPTIONS
95

96 97 98 99 100 101 102
Memory to allocate for the guest, in MiB. This deprecates the -r/--ram option.
Sub options are available, like 'maxmemory', 'hugepages', 'hotplugmemorymax'
and 'hotplugmemoryslots'.  The memory parameter is mapped to <currentMemory> element,
the 'maxmemory' sub-option is mapped to <memory> element and 'hotplugmemorymax'
and 'hotplugmemoryslots' are mapped to <maxMemory> element.

To configure memory modules which can be hotunplugged see B<--memdev> description.
103

104
Use --memory=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemoryAllocation>
105

106
=item B<--memorybacking> OPTIONS
107 108 109 110 111

This option will influence how virtual memory pages are backed by host pages.

Use --memorybacking=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemoryBacking>

112
=item B<--arch> ARCH
113 114 115 116

Request a non-native CPU architecture for the guest virtual machine.
If omitted, the host CPU architecture will be used in the guest.

117
=item B<--machine> MACHINE
118 119 120 121 122

The machine type to emulate. This will typically not need to be specified
for Xen or KVM, but is useful for choosing machine types of more exotic
architectures.

123
=item B<--metadata> OPT=VAL,[...]
124

125
Specify metadata values for the guest. Possible options include name, uuid, title, and description. This option deprecates -u/--uuid and --description.
126

127 128
Use --metadata=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMetadata>

129 130 131 132 133 134 135 136 137 138 139 140
=item B<--events> OPT=VAL,[...]

Specify events values for the guest. Possible options include on_poweroff, on_reboot, and on_crash.

Use --events=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsEvents>

=item B<--resource> OPT=VAL,[...]

Specify resource partitioning for the guest.

Use --resource=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#resPartition>

141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158
=item B<--sysinfo> OPT=VAL,[...]

Configure sysinfo/SMBIOS values exposed to the guest OS. '--sysinfo host' can be used to expose the host's SMBIOS info to the VM, otherwise values can be manually specified.

Use --sysinfo=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsSysinfo>

=item B<--qemu-commandline> ARGS

Pass options directly to the qemu emulator. Only works for the libvirt qemu driver. The option can take a string of arguments, for example:

  --qemu-commandline="-display gtk,gl=on"

Environment variables are specified with 'env', for example:

  --qemu-commandline=env=DISPLAY=:0.1

Complete details about the libvirt feature: L<https://libvirt.org/drvqemu.html#qemucommand>

159
=item B<--vcpus> OPTIONS
160 161 162 163 164 165 166 167 168

Number of virtual cpus to configure for the guest. If 'maxvcpus' is specified,
the guest will be able to hotplug up to MAX vcpus while the guest is running,
but will startup with VCPUS.

CPU topology can additionally be specified with sockets, cores, and threads.
If values are omitted, the rest will be autofilled preferring sockets over
cores over threads.

169
'cpuset' sets which physical cpus the guest can use. C<CPUSET> is a comma separated list of numbers, which can also be specified in ranges or cpus to exclude. Example:
170 171 172 173 174 175 176

    0,2,3,5     : Use processors 0,2,3 and 5
    1-5,^3,8    : Use processors 1,2,4,5 and 8

If the value 'auto' is passed, virt-install attempts to automatically determine
an optimal cpu pinning using NUMA data, if available.

177 178
Use --vcpus=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsCPUAllocation>

179
=item B<--numatune> OPTIONS
180 181 182 183

Tune NUMA policy for the domain process. Example invocations

    --numatune 1,2,3,4-7
184
    --numatune 1-3,5,mode=preferred
185 186

Specifies the numa nodes to allocate memory from. This has the same syntax
187
as C<--vcpus cpuset=> option. mode can be one of 'interleave', 'preferred', or
188 189 190
'strict' (the default). See 'man 8 numactl' for information about each
mode.

191
Use --numatune=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsNUMATuning>
192

193
=item B<--memtune> OPTIONS
194 195 196 197 198 199 200 201

Tune memory policy for the domain process. Example invocations

    --memtune 1000
    --memtune hard_limit=100,soft_limit=60,swap_hard_limit=150,min_guarantee=80

Use --memtune=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemoryTuning>

202
=item B<--blkiotune> OPTIONS
203 204 205 206 207 208 209 210

Tune blkio policy for the domain process. Example invocations

    --blkiotune 100
    --blkiotune weight=100,device_path=/dev/sdc,device_weight=200

Use --blkiotune=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsBlockTuning>

211
=item B<--cpu> MODEL[,+feature][,-feature][,match=MATCH][,vendor=VENDOR],...
212 213

Configure the CPU model and CPU features exposed to the guest. The only
214
required value is MODEL, which is a valid CPU model as known to libvirt.
215

216
Libvirt's feature policy values force, require, optional, disable, or forbid,
217 218 219 220 221
or with the shorthand '+feature' and '-feature', which equal 'force=feature'
and 'disable=feature' respectively

Some examples:

222
=over 4
223 224 225 226 227 228 229 230 231 232 233

=item B<--cpu core2duo,+x2apic,disable=vmx>

Expose the core2duo CPU model, force enable x2apic, but do not expose vmx

=item B<--cpu host>

Expose the host CPUs configuration to the guest. This enables the guest to
take advantage of many of the host CPUs features (better performance), but
may cause issues if migrating the guest to a host without an identical CPU.

234 235 236 237
=item B<--cpu host-model-only>

Expose the nearest host CPU model configuration to the guest.
It is the best CPU which can be used for a guest on any of the hosts.
238

239 240 241 242 243 244 245 246 247 248 249
=item B<--cpu cell0.memory=1234,cell0.cpus=0-3,cell1.memory=5678,cell1.cpus=4-7>

Example of specifying two NUMA cells. This will generate XML like:

  <cpu>
    <numa>
      <cell cpus="0-3" memory="1234"/>
      <cell cpus="4-7" memory="5678"/>
    </numa>
  </cpu>

250 251 252 253
=item B<--cpu host-passthrough,cache.mode=passthrough>

Example of passing through the host cpu's cache information.

254
=back
255

256
Use --cpu=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsCPU>
257

258
=item B<--security> type=TYPE[,label=LABEL][,relabel=yes|no]
259 260 261 262 263 264 265 266 267

Configure domain security driver settings. Type can be either 'static' or
'dynamic'. 'static' configuration requires a security LABEL. Specifying
LABEL without TYPE implies static configuration.

To have libvirt automatically apply your static label, you must specify
relabel=yes. Otherwise disk images must be manually labeled by the admin,
including images that virt-install is asked to create.

268 269
Use --security=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#seclabel>

270
=item B<--features> FEAT=on|off,...
271 272 273 274

Set elements in the guests <features> XML on or off. Examples include acpi,
apic, eoi, privnet, and hyperv features. Some examples:

275
=over 4
276 277 278 279 280 281 282 283 284

=item B<--features eoi=on>

Enable APIC PV EOI

=item B<--features hyperv_vapic=on,hyperv_spinlocks=off>

Enable hypver VAPIC, but disable spinlocks

285 286 287 288 289 290 291 292
=item B<--features kvm_hidden=on>

Allow the KVM hypervisor signature to be hidden from the guest

=item B<--features pvspinlock=on>

Notify the guest that the host supports paravirtual spinlocks for example by exposing the pvticketlocks mechanism.

293 294 295 296 297
=item B<--features gic_version=2>

This is relevant only for ARM architectures. Possible values are "host" or
version number.

298 299 300 301 302 303
=item B<--features smm=on>

This enables System Management Mode of hypervisor. Some UEFI firmwares may
require this feature to be present. (QEMU supports SMM only with q35 machine
type.)

304 305 306 307
=back

Use --features=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsFeatures>

308
=item B<--clock> offset=OFFSET,TIMER_OPT=VAL,...
309 310 311

Configure the guest's <clock> XML. Some supported options:

312
=over 4
313 314 315 316 317 318 319 320 321 322 323 324 325 326

=item B<--clock offset=OFFSET>

Set the clock offset, ex. 'utc' or 'localtime'

=item B<--clock TIMER_present=no>

Disable a boolean timer. TIMER here might be hpet, kvmclock, etc.

=item B<--clock TIMER_tickpolicy=VAL>

Set a timer's tickpolicy value. TIMER here might be rtc, pit, etc. VAL
might be catchup, delay, etc. Refer to the libvirt docs for all values.

327 328
=back

329
Use --clock=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsTime>
330 331


332
=item B<--pm> OPTIONS
333

334
Configure guest power management features. Example suboptions include suspend_to_mem=on|off and suspend_to_disk=on|off
335 336 337 338 339 340

Use --pm=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsPowerManagement>



=back
341

342
=head1 INSTALLATION OPTIONS
343

344
=over 4
345

346 347
=item B<-c> OPTIONS

348
=item B<--cdrom> OPTIONS
349

350
File or device used as a virtual CD-ROM device.
351 352 353 354 355 356
It can be path to an ISO image, or to a CDROM device. It can also be a URL
from which to fetch/access a minimal boot ISO image. The URLs take the same
format as described for the C<--location> argument. If a cdrom has been
specified via the C<--disk> option, and neither C<--cdrom> nor any other
install option is specified, the C<--disk> cdrom is used as the install media.

357 358 359
=item B<-l> LOCATION

=item B<--location> OPTIONS
360 361 362 363 364 365 366 367 368 369

Distribution tree installation source. virt-install can recognize
certain distribution trees and fetches a bootable kernel/initrd pair to
launch the install.

With libvirt 0.9.4 or later, network URL installs work for remote connections.
virt-install will download kernel/initrd to the local machine, and then
upload the media to the remote host. This option requires the URL to
be accessible by both the local and remote host.

370 371 372 373 374 375 376 377
--location allows things like --extra-args for kernel arguments, and using --initrd-inject. If you want to use those options with CDROM media, you have a few options:

* Run virt-install as root and do --location ISO

* Mount the ISO at a local directory, and do --location DIRECTORY

* Mount the ISO at a local directory, export that directory over local http, and do --location http://localhost/DIRECTORY

378 379 380 381
The C<LOCATION> can take one of the following forms:

=over 4

382 383 384
=item http://host/path

An HTTP server location containing an installable distribution image.
385

386 387 388
=item ftp://host/path

An FTP server location containing an installable distribution image.
389 390 391

=item nfs:host:/path or nfs://host/path

392
An NFS server location containing an installable distribution image. This requires running virt-install as root.
393

394
=item DIRECTORY
395

396
Path to a local directory containing an installable distribution image. Note that the directory will not be accessible by the guest after initial boot, so the OS installer will need another way to access the rest of the install media.
397

398
=item ISO
399

400
Mount the ISO and probe the directory. This requires running virt-install as root, and has the same VM access caveat as DIRECTORY.
401 402 403 404 405 406 407 408 409

=back

Some distro specific url samples:

=over 4

=item Fedora/Red Hat Based

410
http://download.fedoraproject.org/pub/fedora/linux/releases/25/Server/x86_64/os
411

412
=item Debian
413 414 415

http://ftp.us.debian.org/debian/dists/stable/main/installer-amd64/

416 417 418 419
=item Ubuntu

http://us.archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/

420 421 422 423 424 425 426 427 428 429 430 431 432 433
=item Suse

http://download.opensuse.org/distribution/11.0/repo/oss/

=item Mandriva

ftp://ftp.uwsg.indiana.edu/linux/mandrake/official/2009.0/i586/

=item Mageia

ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/1

=back

434
=item B<--pxe>
435 436 437 438

Use the PXE boot protocol to load the initial ramdisk and kernel for starting
the guest installation process.

439
=item B<--import>
440 441 442 443 444

Skip the OS installation process, and build a guest around an existing
disk image. The device used for booting is the first device specified via
C<--disk> or C<--filesystem>.

445
=item B<--livecd>
446 447 448

Specify that the installation media is a live CD and thus the guest
needs to be configured to boot off the CDROM device permanently. It
449
may be desirable to also use the C<--disk none> flag in combination.
450

451 452 453
=item B<-x> EXTRA

=item B<--extra-args> OPTIONS
454 455 456 457 458 459

Additional kernel command line arguments to pass to the installer when
performing a guest install from C<--location>. One common usage is specifying
an anaconda kickstart file for automated installs, such as
--extra-args "ks=http://myserver/my.ks"

460
=item B<--initrd-inject> PATH
461 462 463 464 465 466 467

Add PATH to the root of the initrd fetched with C<--location>. This can be
used to run an automated install without requiring a network hosted kickstart
file:

--initrd-inject=/path/to/my.ks --extra-args "ks=file:/my.ks"

468
=item B<--os-variant> OS_VARIANT
469

470
Optimize the guest configuration for a specific operating system (ex.
471
'fedora18', 'rhel7', 'winxp'). While not required, specifying this
472 473
options is HIGHLY RECOMMENDED, as it can greatly increase performance
by specifying virtio among other guest tweaks.
474 475 476

By default, virt-install will attempt to auto detect this value from
the install media (currently only supported for URL installs). Autodetection
477 478
can be disabled with the special value 'none'. Autodetection can be
forced with the special value 'auto'.
479

480 481
Use the command "osinfo-query os" to get the list of the accepted OS
variants.
482

483
=item B<--boot> BOOTOPTS
484 485 486 487 488 489 490 491 492 493 494 495 496

Optionally specify the post-install VM boot configuration. This option allows
specifying a boot device order, permanently booting off kernel/initrd with
option kernel arguments, and enabling a BIOS boot menu (requires libvirt
0.8.3 or later)

--boot can be specified in addition to other install options
(such as --location, --cdrom, etc.) or can be specified on its own. In
the latter case, behavior is similar to the --import install option: there
is no 'install' phase, the guest is just created and launched as specified.

Some examples:

497
=over 4
498 499 500 501 502 503 504 505 506 507 508

=item B<--boot cdrom,fd,hd,network,menu=on>

Set the boot device priority as first cdrom, first floppy, first harddisk,
network PXE boot. Additionally enable BIOS boot menu prompt.

=item B<--boot kernel=KERNEL,initrd=INITRD,kernel_args="console=/dev/ttyS0">

Have guest permanently boot off a local kernel/initrd pair, with the
specified kernel options.

509 510 511 512 513 514
=item B<--boot kernel=KERNEL,initrd=INITRD,dtb=DTB>

Have guest permanently boot off a local kernel/initrd pair with an
external device tree binary. DTB can be required for some non-x86
configurations like ARM or PPC

515 516
=item B<--boot loader=BIOSPATH>

517
Use BIOSPATH as the virtual machine BIOS.
518

519 520 521 522 523 524 525 526 527 528 529
=item B<--boot menu=on,useserial=on>

Enable the bios boot menu, and enable sending bios text output over
serial console.

=item B<--boot init=INITPATH>

Path to a binary that the container guest will init. If a root C<--filesystem>
has been specified, virt-install will default to /sbin/init, otherwise
will default to /bin/sh.

530 531 532 533 534 535 536
=item B<--boot uefi>

Configure the VM to boot from UEFI. In order for virt-install to know the
correct UEFI parameters, libvirt needs to be advertising known UEFI binaries
via domcapabilities XML, so this will likely only work if using properly
configured distro packages.

537
=item B<--boot loader=/.../OVMF_CODE.fd,loader_ro=yes,loader_type=pflash,nvram_template=/.../OVMF_VARS.fd,loader_secure=no>
538 539 540 541 542

Specify that the virtual machine use the custom OVMF binary as boot firmware,
mapped as a virtual flash chip. In addition, request that libvirt instantiate
the VM-specific UEFI varstore from the custom "/.../OVMF_VARS.fd" varstore
template. This is the recommended UEFI setup, and should be used if
543 544
--boot uefi doesn't know about your UEFI binaries. If your UEFI firmware
supports Secure boot feature you can enable it via loader_secure.
545

546 547
=back

548 549
Use --boot=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsOS>

550
=item B<--idmap> OPTIONS
551 552 553 554 555 556 557 558 559 560 561 562 563

If the guest configuration declares a UID or GID mapping,
the 'user' namespace will be enabled to apply these.
A suitably configured UID/GID mapping is a pre-requisite to
make containers secure, in the absence of sVirt confinement.

--idmap can be specified to enable user namespace for LXC containers

Example:
    --idmap uid_start=0,uid_target=1000,uid_count=10,gid_start=0,gid_target=1000,gid_count=10

Use --idmap=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsOSContainer>

564 565 566 567 568 569
=back





570
=head1 STORAGE OPTIONS
571

572
=over 4
573

574
=item B<--disk> OPTIONS
575 576 577 578 579 580

Specifies media to use as storage for the guest, with various options. The
general format of a disk string is

    --disk opt1=val1,opt2=val2,...

581 582 583 584 585
The simplest invocation to create a new 10G disk image and associated disk device:

    --disk size=10

virt-install will generate a path name, and place it in the default image location for the hypervisor. To specify media, the command can either be:
586

587
    --disk /some/storage/path[,opt1=val1]...
588 589 590 591 592 593 594 595

or explicitly specify one of the following arguments:

=over 4

=item B<path>

A path to some storage media to use, existing or not. Existing media can be
596
a file or block device.
597 598

Specifying a non-existent path implies attempting to create the new storage,
599 600
and will require specifying a 'size' value. Even for remote hosts, virt-install
will try to use libvirt storage APIs to automatically create the given path.
601

602 603 604 605
If the hypervisor supports it, B<path> can also be a network URL, like
http://example.com/some-disk.img . For network paths, they hypervisor will
directly access the storage, nothing is downloaded locally.

606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623
=item B<pool>

An existing libvirt storage pool name to create new storage on. Requires
specifying a 'size' value.

=item B<vol>

An existing libvirt storage volume to use. This is specified as
'poolname/volname'.

=back

Other available options:

=over 4

=item B<device>

624
Disk device type. Value can be 'cdrom', 'disk', 'lun' or 'floppy'. Default is
625 626 627
'disk'. If a 'cdrom' is specified, and no install method is chosen, the
cdrom is used as the install media.

628 629 630 631
=item B<boot_order>

Guest installation with multiple disks will need this parameter to boot correctly after being installed. A boot_order parameter will take values 1,2,3,... Devices with lower value has higher priority.

632 633 634 635 636 637
=item B<bus>

Disk bus type. Value can be 'ide', 'sata', 'scsi', 'usb', 'virtio' or 'xen'.
The default is hypervisor dependent since not all hypervisors support all
bus types.

638 639 640 641
=item B<removable>

Sets the removable flag (/sys/block/$dev/removable on Linux). Only
used with QEMU and bus=usb. Value can be 'on' or 'off'.
642

643 644 645 646 647 648 649
=item B<readonly>

Set drive as readonly (takes 'on' or 'off')

=item B<shareable>

Set drive as shareable (takes 'on' or 'off')
650 651 652

=item B<size>

653
size (in GiB) to use if creating new storage
654 655 656

=item B<sparse>

657 658
whether to skip fully allocating newly created storage. Value is 'yes' or
'no'. Default is 'yes' (do not fully allocate) unless it isn't
659 660
supported by the underlying storage type.

661
The initial time taken to fully-allocate the guest virtual disk (sparse=no)
662 663 664 665
will be usually balanced by faster install times inside the guest. Thus
use of this option is recommended to ensure consistently high performance
and to avoid I/O errors in the guest should the host filesystem fill up.

666 667 668 669
=item B<backing_store>

Path to a disk to use as the backing store for the newly created image.

670 671 672 673
=item B<backing_format>

Disk image format of B<backing_store>

674 675 676
=item B<cache>

The cache mode to be used. The host pagecache provides cache memory.
677 678
The cache value can be 'none', 'writethrough', 'directsync', 'unsafe'
or 'writeback'.
679
'writethrough' provides read caching. 'writeback' provides
680 681 682 683 684 685 686 687 688 689
read and write caching. 'directsync' bypasses the host page
cache. 'unsafe' may cache all content and ignore flush requests from
the guest.

=item B<discard>

Whether discard (also known as "trim" or "unmap") requests are ignored
or passed to the filesystem. The value can be either "unmap" (allow
the discard request to be passed) or "ignore" (ignore the discard
request). Since 1.0.6 (QEMU and KVM only)
690 691 692

=item B<format>

693
Disk image format. For file volumes, this can be 'raw', 'qcow2', 'vmdk', etc. See format types in L<http://libvirt.org/storage.html> for possible values. This is often mapped to the B<driver_type> value as well.
694

695 696 697
If not specified when creating file images, this will default to 'qcow2'.

If creating storage, this will be the format of the new image. If using an existing image, this overrides libvirt's format auto-detection.
698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723

=item B<driver_name>

Driver name the hypervisor should use when accessing the specified
storage. Typically does not need to be set by the user.

=item B<driver_type>

Driver format/type the hypervisor should use when accessing the specified
storage. Typically does not need to be set by the user.

=item B<io>

Disk IO backend. Can be either "threads" or "native".

=item B<error_policy>

How guest should react if a write error is encountered. Can be one of
"stop", "ignore", or "enospace"

=item B<serial>

Serial number of the emulated disk device. This is used in linux guests
to set /dev/disk/by-id symlinks. An example serial number might be:
WD-WMAP9A966149

724 725 726 727 728
=item B<startup_policy>

It defines what to do with the disk if the source file is not accessible.  See
possible values in L<http://www.libvirt.org/formatdomain.html#elementsDisks>

729 730 731 732 733 734
=item B<snapshot_policy>

Defines default behavior of the disk during disk snapshots.  See possible
values in L<http://www.libvirt.org/formatdomain.html#elementsDisks>,
"snapshot" attribute of the <disk> element.

735 736
=back

737
See the examples section for some uses. This option deprecates -f/--file,
738
-s/--file-size, --nonsparse, and --nodisks.
739 740

Use --disk=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsDisks>
741

742
=item B<--filesystem>
743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777

Specifies a directory on the host to export to the guest. The most simple
invocation is:

    --filesystem /source/on/host,/target/point/in/guest

Which will work for recent QEMU and linux guest OS or LXC containers. For
QEMU, the target point is just a mounting hint in sysfs, so will not be
automatically mounted.

The following explicit options can be specified:

=over 4

=item B<type>

The type or the source directory. Valid values are 'mount' (the default) or
'template' for OpenVZ templates.

=item B<mode>

The access mode for the source directory from the guest OS. Only used with
QEMU and type=mount. Valid modes are 'passthrough' (the default), 'mapped',
or 'squash'. See libvirt domain XML documentation for more info.

=item B<source>

The directory on the host to share.

=item B<target>

The mount location to use in the guest.

=back

778 779
Use --filesystem=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsFilesystems>

780 781 782 783 784 785
=back





786
=head1 NETWORKING OPTIONS
787

788
=over 4
789

790 791 792
=item B<-w> OPTIONS

=item B<--network> OPTIONS
793 794

Connect the guest to the host network. The value for C<NETWORK> can take
795
one of 4 formats:
796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814

=over 4

=item bridge=BRIDGE

Connect to a bridge device in the host called C<BRIDGE>. Use this option if
the host has static networking config & the guest requires full outbound
and inbound connectivity  to/from the LAN. Also use this if live migration
will be used with this guest.

=item network=NAME

Connect to a virtual network in the host called C<NAME>. Virtual networks
can be listed, created, deleted using the C<virsh> command line tool. In
an unmodified install of C<libvirt> there is usually a virtual network
with a name of C<default>. Use a virtual network if the host has dynamic
networking (eg NetworkManager), or using wireless. The guest will be
NATed to the LAN by whichever connection is active.

815 816 817 818
=item type=direct,source=IFACE[,source_mode=MODE]

Direct connect to host interface IFACE using macvtap.

819 820 821 822 823
=item user

Connect to the LAN using SLIRP. Only use this if running a QEMU guest as
an unprivileged user. This provides a very limited form of NAT.

824 825 826 827
=item none

Tell virt-install not to add any default network interface.

828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852
=back

If this option is omitted a single NIC will be created in the guest. If
there is a bridge device in the host with a physical interface enslaved,
that will be used for connectivity. Failing that, the virtual network
called C<default> will be used. This option can be specified multiple
times to setup more than one NIC.

Other available options are:

=over 4

=item B<model>

Network device model as seen by the guest. Value can be any nic model supported
by the hypervisor, e.g.: 'e1000', 'rtl8139', 'virtio', ...

=item B<mac>

Fixed MAC address for the guest; If this parameter is omitted, or the value
C<RANDOM> is specified a suitable address will be randomly generated. For
Xen virtual machines it is required that the first 3 pairs in the MAC address
be the sequence '00:16:3e', while for QEMU or KVM virtual machines it must
be '52:54:00'.

853
=item B<filterref>
854

855 856 857
Controlling firewall and network filtering in libvirt. Value can be any nwfilter
defined by the C<virsh> 'nwfilter' subcommands. Available filters can be listed
by running 'virsh nwfilter-list', e.g.: 'clean-traffic', 'no-mac-spoofing', ...
858

859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943
=item B<virtualport_type>

The type of virtual port profile, one the following values

=over 4

=item C<802.Qbg>

The following additional parameters are accepted

=over 4

=item B<virtualport_managerid>


The VSI Manager ID identifies the database containing the VSI type
and instance definitions. This is an integer value and the value
0 is reserved.

=item B<virtualport_typeid>

The VSI Type ID identifies a VSI type characterizing the network
access. VSI types are typically managed by network administrator.
This is an integer value.

=item B<virtualport_typeidversion>

The VSI Type Version allows multiple versions of a VSI Type. This
is an integer value.

=item B<virtualport_instanceid>

The VSI Instance ID Identifier is generated when a VSI instance
(i.e. a virtual interface of a virtual machine) is created. This
is a globally unique identifier.

=back

=item C<802.Qbh>

The following additional parameters are accepted

=over 4

=item B<virtualport_profileid>

The profile ID contains the name of the port profile that is to
be applied to this interface. This name is resolved by the port
profile database into the network parameters from the port profile,
and those network parameters will be applied to this interface.

=back

=item C<openvswitch>

The following additional parameters are accepted

=over 4

=item B<virtualport_profileid>

The OpenVSwitch port profile for the interface

=item B<virtualport_interfaceid>

A UUID to uniquely identify the interface. If omitted one will
be generated automatically

=back

=item C<midonet>

The following additional parameters are accepted

=over 4

=item B<virtualport_interfaceid>

A UUID identifying the port in the network to which the interface
will be bound

=back

=back

944
=back
945

946
Use --network=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsNICS>
947

948
This option deprecates -m/--mac, -b/--bridge, and --nonetworks
949 950 951 952 953 954 955

=back





956
=head1 GRAPHICS OPTIONS
957

958 959 960
If no graphics option is specified, C<virt-install> will try to select
the appropriate graphics if the DISPLAY environment variable is set,
otherwise '--graphics none' is used.
961

962
=over 4
963

964
=item B<--graphics> TYPE,opt1=arg1,opt2=arg2,...
965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007

Specifies the graphical display configuration. This does not configure any
virtual hardware, just how the guest's graphical display can be accessed.
Typically the user does not need to specify this option, virt-install will
try and choose a useful default, and launch a suitable connection.

General format of a graphical string is

    --graphics TYPE,opt1=arg1,opt2=arg2,...

For example:

    --graphics vnc,password=foobar

The supported options are:

=over 4

=item B<type>

The display type. This is one of:

vnc

Setup a virtual console in the guest and export it as a VNC server in
the host. Unless the C<port> parameter is also provided, the VNC
server will run on the first free port number at 5900 or above. The
actual VNC display allocated can be obtained using the C<vncdisplay>
command to C<virsh> (or L<virt-viewer(1)> can be used which handles this
detail for the use).

spice

Export the guest's console using the Spice protocol. Spice allows advanced
features like audio and USB device streaming, as well as improved graphical
performance.

Using spice graphic type will work as if those arguments were given:

    --video qxl --channel spicevmc

none

1008 1009 1010 1011
No graphical console will be allocated for the guest. Guests will likely
need to have a text console configured on the first
serial port in the guest (this can be done via the --extra-args option). The
command 'virsh console NAME' can be used to connect to the serial device.
1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026

=item B<port>

Request a permanent, statically assigned port number for the guest
console. This is used by 'vnc' and 'spice'

=item B<tlsport>

Specify the spice tlsport.

=item B<listen>

Address to listen on for VNC/Spice connections. Default is typically 127.0.0.1
(localhost only), but some hypervisors allow changing this globally (for
example, the qemu driver default can be changed in /etc/libvirt/qemu.conf).
1027 1028 1029 1030 1031 1032 1033 1034 1035 1036
Use 0.0.0.0 to allow access from other machines.

Use 'none' to specify that the display server should not listen on any
port. The display server can be accessed only locally through
libvirt unix socket (virt-viewer with --attach for instance).

Use 'socket' to have the VM listen on a libvirt generated unix socket
path on the host filesystem.

This is used by 'vnc' and 'spice'
1037 1038 1039

=item B<keymap>

1040
Request that the virtual console be configured to run with a specific
1041 1042 1043 1044
keyboard layout. If the special value 'local' is specified, virt-install
will attempt to configure to use the same keymap as the local system. A value
of 'none' specifically defers to the hypervisor. Default behavior is
hypervisor specific, but typically is the same as 'local'. This is used
1045
by 'vnc' and 'spice'.
1046 1047 1048

=item B<password>

1049
Request a console password, required at connection time. Beware, this info may
1050 1051 1052
end up in virt-install log files, so don't use an important password. This
is used by 'vnc' and 'spice'

1053 1054 1055 1056 1057
=item B<gl>

Whether to use OpenGl accelerated rendering. Value is 'yes' or 'no'. This is
used by 'spice'.

1058 1059 1060 1061
=item B<rendernode>

DRM render node path to use. This is used when 'gl' is enabled.

1062 1063
=back

1064
Use --graphics=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsGraphics>
1065

1066
This deprecates the following options: --vnc, --vncport, --vnclisten, -k/--keymap, --sdl, --nographics
1067

1068
=item B<--noautoconsole>
1069 1070

Don't automatically try to connect to the guest console. The default behaviour
1071
is to launch L<virt-viewer(1)> to display the graphical console, or to run the
1072 1073 1074 1075 1076 1077 1078 1079
C<virsh> C<console> command to display the text console. Use of this parameter
will disable this behaviour.

=back




1080
=head1 VIRTUALIZATION OPTIONS
1081 1082 1083

Options to override the default virtualization type choices.

1084 1085 1086
=over 4

=item B<-v>
1087

1088
=item B<--hvm>
1089 1090 1091 1092 1093 1094

Request the use of full virtualization, if both para & full virtualization are
available on the host. This parameter may not be available if connecting to a
Xen hypervisor on a machine without hardware virtualization support. This
parameter is implied if connecting to a QEMU based hypervisor.

1095 1096 1097
=item B<-p>

=item B<--paravirt>
1098 1099 1100 1101 1102

This guest should be a paravirtualized guest. If the host supports both
para & full virtualization, and neither this parameter nor the C<--hvm>
are specified, this will be assumed.

1103
=item B<--container>
1104 1105 1106 1107 1108 1109

This guest should be a container type guest. This option is only required
if the hypervisor supports other guest types as well (so for example this
option is the default behavior for LXC and OpenVZ, but is provided for
completeness).

1110
=item B<--virt-type>
1111

1112
The hypervisor to install on. Example choices are kvm, qemu, or xen.
1113 1114
Available options are listed via 'virsh capabilities' in the <domain> tags.

1115
This deprecates the --accelerate option, which is now the default behavior. To install a plain QEMU guest, use '--virt-type qemu'
1116 1117 1118 1119 1120 1121 1122

=back





1123
=head1 DEVICE OPTIONS
1124

1125 1126 1127 1128
All devices have a set of B<address.*> options for configuring the
particulars of the device's address on its parent controller or bus.
See C<http://libvirt.org/formatdomain.html#elementsAddress> for details.

1129
=over 4
1130

1131
=item B<--controller> OPTIONS
1132 1133 1134 1135

Attach a controller device to the guest. TYPE is one of:
B<ide>, B<fdc>, B<scsi>, B<sata>, B<virtio-serial>, or B<usb>.

1136 1137 1138
Controller also supports the special values B<usb2> and B<usb3> to
specify which version of the USB controller should be used (version 2
or 3).
1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151

=over 4

=item B<model>

Controller model.  These may vary according to the hypervisor and its
version.  Most commonly used models are e.g. B<auto>, B<virtio-scsi>
for the B<scsi> controller, B<ehci> or B<none> for the B<usb>
controller.  For full list and further details on controllers/models,
see C<http://libvirt.org/formatdomain.html#elementsControllers>.

=item B<address>

1152 1153
Shorthand for setting a manual PCI address from an lscpi style string.
The preferred method for setting this is using the address.* parameters.
1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169

=item B<index>

A decimal integer describing in which order the bus controller is
encountered, and to reference the controller bus.

=item B<master>

Applicable to USB companion controllers, to define the master bus startport.

=back

Examples:

=over 4

1170
=item B<--controller usb,model=ich9-ehci1,address=0:0:4.0,index=0>
1171

1172
Adds a ICH9 EHCI1 USB controller on PCI address 0:0:4.0
1173 1174 1175 1176 1177 1178

=item B<--controller usb,model=ich9-uhci2,address=0:0:4.7,index=0,master=2>

Adds a ICH9 UHCI2 USB companion controller for the previous master
controller, ports start from port number 2.

1179 1180 1181
The parameter multifunction='on' will be added automatically to the
proper device (if needed).  This applies to all PCI devices.

1182 1183
=back

1184 1185
Use --controller=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsControllers>

1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196

=item B<--input> OPTIONS

Attach an input device to the guest. Example input device types are mouse, tablet, or keyboard.

Use --input=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsInput>


=item B<--hostdev> OPTIONS

=item B<--host-device> OPTIONS
1197 1198 1199

Attach a physical host device to the guest. Some example values for HOSTDEV:

1200
=over 4
1201

1202
=item B<--hostdev pci_0000_00_1b_0>
1203 1204 1205

A node device name via libvirt, as shown by 'virsh nodedev-list'

1206
=item B<--hostdev 001.003>
1207 1208 1209

USB by bus, device (via lsusb).

1210
=item B<--hostdev 0x1234:0x5678>
1211 1212 1213

USB by vendor, product (via lsusb).

1214
=item B<--hostdev 1f.01.02>
1215 1216 1217 1218 1219

PCI device (via lspci).

=back

1220
Use --hostdev=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsHostDev>
1221

1222
=item B<--sound> MODEL
1223 1224

Attach a virtual audio device to the guest. MODEL specifies the emulated
1225
sound card model. Possible values are ich6, ich9, ac97, es1370, sb16, pcspk,
1226 1227 1228
or default. 'default' will try to pick the best model that the specified
OS supports.

1229
This deprecates the old --soundhw option.
1230

1231
Use --sound=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsSound>
1232

1233
=item B<--watchdog> MODEL[,action=ACTION]
1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275

Attach a virtual hardware watchdog device to the guest. This requires a
daemon and device driver in the guest. The watchdog fires a signal when
the virtual machine appears to hung. ACTION specifies what libvirt will do
when the watchdog fires. Values are

=over 4

=item B<reset>

Forcefully reset the guest (the default)

=item B<poweroff>

Forcefully power off the guest

=item B<pause>

Pause the guest

=item B<none>

Do nothing

=item B<shutdown>

Gracefully shutdown the guest (not recommended, since a hung guest probably
won't respond to a graceful shutdown)

=back

MODEL is the emulated device model: either i6300esb (the default) or ib700.
Some examples:

Use the recommended settings:

--watchdog default

Use the i6300esb with the 'poweroff' action

--watchdog i6300esb,action=poweroff

1276 1277
Use --watchdog=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsWatchdog>

1278
=item B<--parallel> OPTIONS
1279

1280
=item B<--serial> OPTIONS
1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354

Specifies a serial device to attach to the guest, with various options. The
general format of a serial string is

    --serial type,opt1=val1,opt2=val2,...

--serial and --parallel devices share all the same options, unless otherwise
noted. Some of the types of character device redirection are:

=over 4

=item B<--serial pty>

Pseudo TTY. The allocated pty will be listed in the running guests XML
description.

=item B<--serial dev,path=HOSTPATH>

Host device. For serial devices, this could be /dev/ttyS0. For parallel
devices, this could be /dev/parport0.

=item B<--serial file,path=FILENAME>

Write output to FILENAME.

=item B<--serial pipe,path=PIPEPATH>

Named pipe (see pipe(7))

=item B<--serial tcp,host=HOST:PORT,mode=MODE,protocol=PROTOCOL>

TCP net console. MODE is either 'bind' (wait for connections on HOST:PORT)
or 'connect' (send output to HOST:PORT), default is 'bind'. HOST defaults
to '127.0.0.1', but PORT is required. PROTOCOL can be either 'raw' or 'telnet'
(default 'raw'). If 'telnet', the port acts like a telnet server or client.
Some examples:

Wait for connections on any address, port 4567:

--serial tcp,host=0.0.0.0:4567

Connect to localhost, port 1234:

--serial tcp,host=:1234,mode=connect

Wait for telnet connection on localhost, port 2222. The user could then
connect interactively to this console via 'telnet localhost 2222':

--serial tcp,host=:2222,mode=bind,protocol=telnet

=item B<--serial udp,host=CONNECT_HOST:PORT,bind_host=BIND_HOST:BIND_PORT>

UDP net console. HOST:PORT is the destination to send output to (default
HOST is '127.0.0.1', PORT is required). BIND_HOST:BIND_PORT is the optional
local address to bind to (default BIND_HOST is 127.0.0.1, but is only set if
BIND_PORT is specified). Some examples:

Send output to default syslog port (may need to edit /etc/rsyslog.conf
accordingly):

--serial udp,host=:514

Send output to remote host 192.168.10.20, port 4444 (this output can be
read on the remote host using 'nc -u -l 4444'):

--serial udp,host=192.168.10.20:4444

=item B<--serial unix,path=UNIXPATH,mode=MODE>

Unix socket, see unix(7). MODE has similar behavior and defaults as
--serial tcp,mode=MODE

=back

1355 1356
Use --serial=? or --parallel=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsCharSerial> and L<http://libvirt.org/formatdomain.html#elementsCharParallel>

1357
=item B<--channel>
1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390

Specifies a communication channel device to connect the guest and host
machine. This option uses the same options as --serial and --parallel
for specifying the host/source end of the channel. Extra 'target' options
are used to specify how the guest machine sees the channel.

Some of the types of character device redirection are:

=over 4

=item B<--channel SOURCE,target_type=guestfwd,target_address=HOST:PORT>

Communication channel using QEMU usermode networking stack. The guest can
connect to the channel using the specified HOST:PORT combination.

=item B<--channel SOURCE,target_type=virtio[,name=NAME]>

Communication channel using virtio serial (requires 2.6.34 or later host and
guest). Each instance of a virtio --channel line is exposed in the
guest as /dev/vport0p1, /dev/vport0p2, etc. NAME is optional metadata, and
can be any string, such as org.linux-kvm.virtioport1.
If specified, this will be exposed in the guest at
/sys/class/virtio-ports/vport0p1/NAME

=item B<--channel spicevmc,target_type=virtio[,name=NAME]>

Communication channel for QEMU spice agent, using virtio serial
(requires 2.6.34 or later host and guest). NAME is optional metadata,
and can be any string, such as the default com.redhat.spice.0 that
specifies how the guest will see the channel.

=back

1391 1392
Use --channel=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsCharChannel>

1393
=item B<--console>
1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412

Connect a text console between the guest and host. Certain guest and
hypervisor combinations can automatically set up a getty in the guest, so
an out of the box text login can be provided (target_type=xen for xen
paravirt guests, and possibly target_type=virtio in the future).

Example:

=over 4

=item B<--console pty,target_type=virtio>

Connect a virtio console to the guest, redirected to a PTY on the host.
For supported guests, this exposes /dev/hvc0 in the guest. See
http://fedoraproject.org/wiki/Features/VirtioSerial for more info. virtio
console requires libvirt 0.8.3 or later.

=back

1413 1414
Use --console=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsCharConsole>

1415
=item B<--video> OPTIONS
1416 1417 1418

Specify what video device model will be attached to the guest. Valid values
for VIDEO are hypervisor specific, but some options for recent kvm are
1419
cirrus, vga, qxl, virtio, or vmvga (vmware).
1420

1421 1422
Use --video=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsVideo>

1423
=item B<--smartcard> MODE[,OPTIONS]
1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449

Configure a virtual smartcard device.

Mode is one of B<host>, B<host-certificates>, or B<passthrough>. Additional
options are:

=over 4

=item B<type>

Character device type to connect to on the host. This is only applicable
for B<passthrough> mode.

=back

An example invocation:

=over 4

=item B<--smartcard passthrough,type=spicevmc>

Use the smartcard channel of a SPICE graphics device to pass smartcard info
to the guest

=back

1450
Use --smartcard=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsSmartcard>
1451

1452
=item B<--redirdev> BUS[,OPTIONS]
1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482

Add a redirected device.

=over 4

=item B<type>

The redirection type, currently supported is B<tcp> or B<spicevmc>.

=item B<server>

The TCP server connection details, of the form 'server:port'.

=back

Examples of invocation:

=over 4

=item B<--redirdev usb,type=tcp,server=localhost:4000>

Add a USB redirected device provided by the TCP server on 'localhost'
port 4000.

=item B<--redirdev usb,type=spicevmc>

Add a USB device redirected via a dedicated Spice channel.

=back

1483 1484
Use --redirdev=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsRedir>

1485
=item B<--memballoon> MODEL
1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501

Attach a virtual memory balloon device to the guest. If the memballoon device
needs to be explicitly disabled, MODEL='none' is used.

MODEL is the type of memballoon device provided. The value can be 'virtio',
'xen' or 'none'.
Some examples:

Use the recommended settings:

--memballoon virtio

Do not use memballoon device:

--memballoon none

1502 1503
Use --memballoon=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemBalloon>

1504
=item B<--tpm> TYPE[,OPTIONS]
1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534

Configure a virtual TPM device.

Type must be B<passthrough>. Additional options are:

=over 4

=item B<model>

The device model to present to the guest operating system. Model
must be B<tpm-tis>.

=back

An example invocation:

=over 4

=item B<--tpm passthrough,model=tpm-tis>

Make the host's TPM accessible to a single guest.

=item B<--tpm /dev/tpm>

Convenience option for passing through the hosts TPM.

=back

Use --tpm=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsTpm>

1535
=item B<--rng> TYPE[,OPTIONS]
1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601

Configure a virtual RNG device.

Type can be B<random> or B<egd>.

If the specified type is B<random> then these values must
be specified:

=over 4

=item B<backend_device>

The device to use as a source of entropy.

=back

Whereas, when the type is B<egd>, these values must be provided:

=over 4

=item B<backend_host>

Specify the host of the Entropy Gathering Daemon to connect to.

=item B<backend_service>

Specify the port of the Entropy Gathering Daemon to connect to.

=item B<backend_type>

Specify the type of the connection: B<tcp> or B<udp>.

=item B<backend_mode>

Specify the mode of the connection.  It is either 'bind' (wait for
connections on HOST:PORT) or 'connect' (send output to HOST:PORT).

=item B<backend_connect_host>

Specify the remote host to connect to when the specified backend_type is B<udp>
and backend_mode is B<bind>.

=item B<backend_connect_service>

Specify the remote service to connect to when the specified backend_type is
B<udp> and backend_mode is B<bind>.

=back

An example invocation:

=over 4

=item B<--rng egd,backend_host=localhost,backend_service=8000,backend_type=tcp>

Connect to localhost to the TCP port 8000 to get entropy data.

=item B<--rng /dev/random>

Use the /dev/random device to get entropy data, this form implicitly uses the
"random" model.

Use --rng=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsRng>

=back

1602
=item B<--panic> MODEL[,OPTS]
1603 1604 1605 1606 1607 1608 1609

Attach a panic notifier device to the guest. For the recommended settings, use:

--panic default

Use --panic=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsPanic>

1610 1611 1612 1613
=item B<--memdev> OPTS

Add a memory module to a guest which can be hotunplugged. To add a memdev you need
to configure hotplugmemory and NUMA for a guest.
1614

1615
Use --memdev=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemory>.
1616 1617


1618 1619
=back

1620
=head1 MISCELLANEOUS OPTIONS
1621

1622
=over 4
1623

1624
=item B<-h>
1625

1626
=item B<--help>
1627

1628
Show the help message and exit
1629

1630
=item B<--version>
1631

1632
Show program's version number and exit
1633

1634
=item B<--autostart>
1635

1636 1637 1638
Set the autostart flag for a domain. This causes the domain to be started
on host boot up.

1639 1640 1641 1642 1643 1644 1645 1646 1647
=item B<--transient>

Use --import or --boot and --transient if you want a transient libvirt
VM.  These VMs exist only until the domain is shut down or the host
server is restarted.  Libvirt forgets the XML configuration of the VM
after either of these events.  Note that the VM's disks will not be
deleted.  See:
L<http://wiki.libvirt.org/page/VM_lifecycle#Transient_guest_domains_vs_Persistent_guest_domains>

1648 1649 1650 1651 1652
=item B<--print-xml> [STEP]

Print the generated XML of the guest, instead of defining it. By default this WILL do storage creation (can be disabled with --dry-run). This option implies --quiet.

If the VM install has multiple phases, by default this will print all generated XML. If you want to print a particular step, use --print-xml 2 (for the second phase XML).
1653

1654
=item B<--noreboot>
1655 1656 1657 1658

Prevent the domain from automatically rebooting after the install has
completed.

1659
=item B<--wait> WAIT
1660 1661 1662 1663 1664 1665 1666 1667 1668

Amount of time to wait (in minutes) for a VM to complete its install.
Without this option, virt-install will wait for the console to close (not
necessarily indicating the guest has shutdown), or in the case of
--noautoconsole, simply kick off the install and exit. Any negative
value will make virt-install wait indefinitely, a value of 0 triggers the
same results as noautoconsole. If the time limit is exceeded, virt-install
simply exits, leaving the virtual machine in its current state.

1669
=item B<--dry-run>
1670 1671 1672 1673 1674 1675

Proceed through the guest creation process, but do NOT create storage devices,
change host device configuration, or actually teach libvirt about the guest.
virt-install may still fetch install media, since this is required to
properly detect the OS to install.

1676 1677 1678 1679 1680 1681 1682
=item B<--check>

Enable or disable some validation checks. Some examples are warning about using a disk that's already assigned to another VM (--check path_in_use=on|off), or warning about potentially running out of space during disk allocation (--check disk_size=on|off). Most checks are performed by default.

=item B<-q>

=item B<--quiet>
1683 1684 1685

Only print fatal error messages.

1686 1687 1688
=item B<-d>

=item B<--debug>
1689 1690

Print debugging information to the terminal when running the install process.
1691 1692
The debugging information is also stored in
C<~/.cache/virt-manager/virt-install.log> even if this parameter is omitted.
1693 1694 1695 1696 1697

=back

=head1 EXAMPLES

1698
Install a Fedora 20 KVM guest with virtio accelerated disk/network,
1699
creating a new 10GiB qcow2 file, installing from media in the hosts
1700 1701
CDROM drive. This will use Spice graphics by default, and launch autolaunch
a graphical client.
1702 1703 1704 1705 1706

  # virt-install \
       --connect qemu:///system \
       --virt-type kvm \
       --name demo \
1707
       --memory 500 \
1708
       --disk size=10 \
1709 1710 1711 1712
       --cdrom /dev/cdrom \
       --os-variant fedora13

Install a Fedora 9 plain QEMU guest, using LVM partition, virtual networking,
1713
booting from PXE, using VNC server/viewer, with virtio-scsi disk
1714 1715 1716 1717

  # virt-install \
       --connect qemu:///system \
       --name demo \
1718
       --memory 500 \
1719 1720
       --disk path=/dev/HostVG/DemoVM,bus=scsi \
       --controller virtio-scsi \
1721
       --network network=default \
1722
       --virt-type qemu \
1723 1724 1725 1726 1727 1728 1729 1730
       --graphics vnc \
       --os-variant fedora9

Run a Live CD image under Xen fullyvirt, in diskless environment

  # virt-install \
       --hvm \
       --name demo \
1731
       --memory 500 \
1732
       --disk none \
1733 1734 1735 1736 1737
       --livecd \
       --graphics vnc \
       --cdrom /root/fedora7live.iso

Run /usr/bin/httpd in a linux container guest (LXC). Resource usage is capped
1738
at 512 MiB of ram and 2 host cpus:
1739 1740 1741 1742

  # virt-install \
        --connect lxc:/// \
        --name httpd_guest \
1743
        --memory 512 \
1744 1745 1746
        --vcpus 2 \
        --init /usr/bin/httpd

1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760
Start a linux container guest(LXC) with a private root filesystem,
using /bin/sh as init.
Container's root will be under host dir /home/LXC.
The host dir "/home/test" will be mounted at
"/mnt" dir inside container:

  # virt-install \
        --connect lxc:/// \
        --name container \
        --memory 128 \
        --filesystem /home/LXC,/ \
        --filesystem /home/test,/mnt \
        --init /bin/sh

1761
Install a paravirtualized Xen guest, 500 MiB of RAM, a 5 GiB of disk, and
1762 1763 1764 1765 1766 1767
Fedora Core 6 from a web server, in text-only mode, with old style --file
options:

  # virt-install \
       --paravirt \
       --name demo \
1768
       --memory 500 \
1769
       --disk /var/lib/xen/images/demo.img,size=6 \
1770 1771 1772 1773 1774 1775 1776 1777
       --graphics none \
       --location http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/

Create a guest from an existing disk image 'mydisk.img' using defaults for
the rest of the options.

  # virt-install \
       --name demo \
1778
       --memory 512 \
1779 1780 1781
       --disk /home/user/VMs/mydisk.img \
       --import

1782
Start serial QEMU ARM VM, which requires specifying a manual kernel.
1783 1784

  # virt-install \
1785 1786 1787 1788 1789
       --name armtest \
       --memory 1024 \
       --arch armv7l --machine vexpress-a9 \
       --disk /home/user/VMs/myarmdisk.img \
       --boot kernel=/tmp/my-arm-kernel,initrd=/tmp/my-arm-initrd,dtb=/tmp/my-arm-dtb,kernel_args="console=ttyAMA0 rw root=/dev/mmcblk0p3" \
1790
       --graphics none
1791 1792 1793 1794 1795 1796 1797

=head1 BUGS

Please see http://virt-manager.org/page/BugReporting

=head1 COPYRIGHT

1798
Copyright (C) Red Hat, Inc, and various contributors.
1799 1800 1801 1802 1803 1804 1805 1806 1807
This is free software. You may redistribute copies of it under the terms of
the GNU General Public License C<http://www.gnu.org/licenses/gpl.html>. There
is NO WARRANTY, to the extent permitted by law.

=head1 SEE ALSO

C<virsh(1)>, C<virt-clone(1)>, C<virt-manager(1)>, the project website C<http://virt-manager.org>

=cut