<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>xl - Xen management tool, based on LibXenlight</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>
<body>
<ul id="index">
<li><a href="#NAME">NAME</a></li>
<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
<li><a href="#NOTES">NOTES</a></li>
<li><a href="#GLOBAL-OPTIONS">GLOBAL OPTIONS</a></li>
<li><a href="#DOMAIN-SUBCOMMANDS">DOMAIN SUBCOMMANDS</a></li>
<li><a href="#XEN-HOST-SUBCOMMANDS">XEN HOST SUBCOMMANDS</a></li>
<li><a href="#SCHEDULER-SUBCOMMANDS">SCHEDULER SUBCOMMANDS</a></li>
<li><a href="#CPUPOOLS-COMMANDS">CPUPOOLS COMMANDS</a></li>
<li><a href="#VIRTUAL-DEVICE-COMMANDS">VIRTUAL DEVICE COMMANDS</a>
<ul>
<li><a href="#BLOCK-DEVICES">BLOCK DEVICES</a></li>
<li><a href="#NETWORK-DEVICES">NETWORK DEVICES</a></li>
<li><a href="#CHANNEL-DEVICES">CHANNEL DEVICES</a></li>
<li><a href="#VIRTUAL-TRUSTED-PLATFORM-MODULE-vTPM-DEVICES">VIRTUAL TRUSTED PLATFORM MODULE (vTPM) DEVICES</a></li>
<li><a href="#VDISPL-DEVICES">VDISPL DEVICES</a></li>
<li><a href="#VSND-DEVICES">VSND DEVICES</a></li>
<li><a href="#KEYBOARD-DEVICES">KEYBOARD DEVICES</a></li>
</ul>
</li>
<li><a href="#PCI-PASS-THROUGH">PCI PASS-THROUGH</a></li>
<li><a href="#USB-PASS-THROUGH">USB PASS-THROUGH</a></li>
<li><a href="#DEVICE-MODEL-CONTROL">DEVICE-MODEL CONTROL</a></li>
<li><a href="#TRANSCENDENT-MEMORY-TMEM">TRANSCENDENT MEMORY (TMEM)</a></li>
<li><a href="#FLASK">FLASK</a></li>
<li><a href="#PLATFORM-SHARED-RESOURCE-MONITORING-CONTROL">PLATFORM SHARED RESOURCE MONITORING/CONTROL</a>
<ul>
<li><a href="#CACHE-MONITORING-TECHNOLOGY">CACHE MONITORING TECHNOLOGY</a></li>
<li><a href="#CACHE-ALLOCATION-TECHNOLOGY">CACHE ALLOCATION TECHNOLOGY</a></li>
<li><a href="#Memory-Bandwidth-Allocation">Memory Bandwidth Allocation</a></li>
</ul>
</li>
<li><a href="#IGNORED-FOR-COMPATIBILITY-WITH-XM">IGNORED FOR COMPATIBILITY WITH XM</a></li>
<li><a href="#TO-BE-DOCUMENTED">TO BE DOCUMENTED</a></li>
<li><a href="#SEE-ALSO">SEE ALSO</a></li>
<li><a href="#BUGS">BUGS</a></li>
</ul>
<h1 id="NAME">NAME</h1>
<p>xl - Xen management tool, based on LibXenlight</p>
<h1 id="SYNOPSIS">SYNOPSIS</h1>
<p><b>xl</b> <i>subcommand</i> [<i>args</i>]</p>
<h1 id="DESCRIPTION">DESCRIPTION</h1>
<p>The <b>xl</b> program is the new tool for managing Xen guest domains. The program can be used to create, pause, and shutdown domains. It can also be used to list current domains, enable or pin VCPUs, and attach or detach virtual block devices.</p>
<p>The basic structure of every <b>xl</b> command is almost always:</p>
<ul>
<p><b>xl</b> <i>subcommand</i> [<i>OPTIONS</i>] <i>domain-id</i></p>
</ul>
<p>Where <i>subcommand</i> is one of the subcommands listed below, <i>domain-id</i> is the numeric domain id, or the domain name (which will be internally translated to domain id), and <i>OPTIONS</i> are subcommand specific options. There are a few exceptions to this rule in the cases where the subcommand in question acts on all domains, the entire machine, or directly on the Xen hypervisor. Those exceptions will be clear for each of those subcommands.</p>
<h1 id="NOTES">NOTES</h1>
<dl>
<dt id="start-the-script-etc-init.d-xencommons-at-boot-time">start the script <b>/etc/init.d/xencommons</b> at boot time</dt>
<dd>
<p>Most <b>xl</b> operations rely upon <b>xenstored</b> and <b>xenconsoled</b>: make sure you start the script <b>/etc/init.d/xencommons</b> at boot time to initialize all the daemons needed by <b>xl</b>.</p>
</dd>
<dt id="setup-a-xenbr0-bridge-in-dom0">setup a <b>xenbr0</b> bridge in dom0</dt>
<dd>
<p>In the most common network configuration, you need to setup a bridge in dom0 named <b>xenbr0</b> in order to have a working network in the guest domains. Please refer to the documentation of your Linux distribution to know how to setup the bridge.</p>
</dd>
<dt id="autoballoon"><b>autoballoon</b></dt>
<dd>
<p>If you specify the amount of memory dom0 has, passing <b>dom0_mem</b> to Xen, it is highly recommended to disable <b>autoballoon</b>. Edit <b>/etc/xen/xl.conf</b> and set it to 0.</p>
</dd>
<dt id="run-xl-as-root">run xl as <b>root</b></dt>
<dd>
<p>Most <b>xl</b> commands require root privileges to run due to the communications channels used to talk to the hypervisor. Running as non root will return an error.</p>
</dd>
</dl>
<h1 id="GLOBAL-OPTIONS">GLOBAL OPTIONS</h1>
<p>Some global options are always available:</p>
<dl>
<dt id="v"><b>-v</b></dt>
<dd>
<p>Verbose.</p>
</dd>
<dt id="N"><b>-N</b></dt>
<dd>
<p>Dry run: do not actually execute the command.</p>
</dd>
<dt id="f"><b>-f</b></dt>
<dd>
<p>Force execution: xl will refuse to run some commands if it detects that xend is also running, this option will force the execution of those commands, even though it is unsafe.</p>
</dd>
<dt id="t"><b>-t</b></dt>
<dd>
<p>Always use carriage-return-based overwriting for displaying progress messages without scrolling the screen. Without -t, this is done only if stderr is a tty.</p>
</dd>
</dl>
<h1 id="DOMAIN-SUBCOMMANDS">DOMAIN SUBCOMMANDS</h1>
<p>The following subcommands manipulate domains directly. As stated previously, most commands take <i>domain-id</i> as the first parameter.</p>
<dl>
<dt id="button-press-domain-id-button"><b>button-press</b> <i>domain-id</i> <i>button</i></dt>
<dd>
<p><i>This command is deprecated. Please use <code>xl trigger</code> instead.</i></p>
<p>Indicate an ACPI button press to the domain, where <i>button</i> can be 'power' or 'sleep'. This command is only available for HVM domains.</p>
</dd>
<dt id="create-configfile-OPTIONS"><b>create</b> [<i>configfile</i>] [<i>OPTIONS</i>]</dt>
<dd>
<p>The create subcommand takes a config file as its first argument: see <a href="xl.cfg.5.html">xl.cfg(5)</a> for full details of the file format and possible options. If <i>configfile</i> is missing <b>xl</b> creates the domain assuming the default values for every option.</p>
<p><i>configfile</i> has to be an absolute path to a file.</p>
<p>Create will return <b>as soon</b> as the domain is started. This <b>does not</b> mean the guest OS in the domain has actually booted, or is available for input.</p>
<p>If the <i>-F</i> option is specified, create will start the domain and not return until its death.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="q---quiet"><b>-q</b>, <b>--quiet</b></dt>
<dd>
<p>No console output.</p>
</dd>
<dt id="f-FILE---defconfig-FILE"><b>-f=FILE</b>, <b>--defconfig=FILE</b></dt>
<dd>
<p>Use the given configuration file.</p>
</dd>
<dt id="p"><b>-p</b></dt>
<dd>
<p>Leave the domain paused after it is created.</p>
</dd>
<dt id="F"><b>-F</b></dt>
<dd>
<p>Run in foreground until death of the domain.</p>
</dd>
<dt id="V---vncviewer"><b>-V</b>, <b>--vncviewer</b></dt>
<dd>
<p>Attach to domain's VNC server, forking a vncviewer process.</p>
</dd>
<dt id="A---vncviewer-autopass"><b>-A</b>, <b>--vncviewer-autopass</b></dt>
<dd>
<p>Pass the VNC password to vncviewer via stdin.</p>
</dd>
<dt id="c"><b>-c</b></dt>
<dd>
<p>Attach console to the domain as soon as it has started. This is useful for determining issues with crashing domains and just as a general convenience since you often want to watch the domain boot.</p>
</dd>
<dt id="key-value"><b>key=value</b></dt>
<dd>
<p>It is possible to pass <i>key=value</i> pairs on the command line to provide options as if they were written in the configuration file; these override whatever is in the <i>configfile</i>.</p>
<p>NB: Many config options require characters such as quotes or brackets which are interpreted by the shell (and often discarded) before being passed to xl, resulting in xl being unable to parse the value correctly. A simple work-around is to put all extra options within a single set of quotes, separated by semicolons. (See below for an example.)</p>
</dd>
</dl>
<p><b>EXAMPLES</b></p>
<dl>
<dt id="with-config-file"><i>with config file</i></dt>
<dd>
<pre><code> xl create DebianLenny</code></pre>
<p>This creates a domain with the file /etc/xen/DebianLenny, and returns as soon as it is run.</p>
</dd>
<dt id="with-extra-parameters"><i>with extra parameters</i></dt>
<dd>
<pre><code> xl create hvm.cfg 'cpus="0-3"; pci=["01:05.1","01:05.2"]'</code></pre>
<p>This creates a domain with the file hvm.cfg, but additionally pins it to cpus 0-3, and passes through two PCI devices.</p>
</dd>
</dl>
</dd>
<dt id="config-update-domain-id-configfile-OPTIONS"><b>config-update</b> <i>domain-id</i> [<i>configfile</i>] [<i>OPTIONS</i>]</dt>
<dd>
<p>Update the saved configuration for a running domain. This has no immediate effect but will be applied when the guest is next restarted. This command is useful to ensure that runtime modifications made to the guest will be preserved when the guest is restarted.</p>
<p>Since Xen 4.5 xl has improved capabilities to handle dynamic domain configuration changes and will preserve any changes made at runtime when necessary. Therefore it should not normally be necessary to use this command any more.</p>
<p><i>configfile</i> has to be an absolute path to a file.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="f-FILE---defconfig-FILE1"><b>-f=FILE</b>, <b>--defconfig=FILE</b></dt>
<dd>
<p>Use the given configuration file.</p>
</dd>
<dt id="key-value1"><b>key=value</b></dt>
<dd>
<p>It is possible to pass <i>key=value</i> pairs on the command line to provide options as if they were written in the configuration file; these override whatever is in the <i>configfile</i>. Please see the note under <i>create</i> on handling special characters when passing <i>key=value</i> pairs on the command line.</p>
</dd>
</dl>
</dd>
<dt id="console-OPTIONS-domain-id"><b>console</b> [<i>OPTIONS</i>] <i>domain-id</i></dt>
<dd>
<p>Attach to the console of a domain specified by <i>domain-id</i>. If you've set up your domains to have a traditional login console this will look much like a normal text login screen.</p>
<p>Use the key combination Ctrl+] to detach from the domain console.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="t-pv-serial"><i>-t [pv|serial]</i></dt>
<dd>
<p>Connect to a PV console or connect to an emulated serial console. PV consoles are the only consoles available for PV domains while HVM domains can have both. If this option is not specified it defaults to emulated serial for HVM guests and PV console for PV guests.</p>
</dd>
<dt id="n-NUM"><i>-n NUM</i></dt>
<dd>
<p>Connect to console number <i>NUM</i>. Console numbers start from 0.</p>
</dd>
</dl>
</dd>
<dt id="destroy-OPTIONS-domain-id"><b>destroy</b> [<i>OPTIONS</i>] <i>domain-id</i></dt>
<dd>
<p>Immediately terminate the domain specified by <i>domain-id</i>. This doesn't give the domain OS any chance to react, and is the equivalent of ripping the power cord out on a physical machine. In most cases you will want to use the <b>shutdown</b> command instead.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="f1"><i>-f</i></dt>
<dd>
<p>Allow domain 0 to be destroyed. Because a domain cannot destroy itself, this is only possible when using a disaggregated toolstack, and is most useful when using a hardware domain separated from domain 0.</p>
</dd>
</dl>
</dd>
<dt id="domid-domain-name"><b>domid</b> <i>domain-name</i></dt>
<dd>
<p>Converts a domain name to a domain id.</p>
</dd>
<dt id="domname-domain-id"><b>domname</b> <i>domain-id</i></dt>
<dd>
<p>Converts a domain id to a domain name.</p>
</dd>
<dt id="rename-domain-id-new-name"><b>rename</b> <i>domain-id</i> <i>new-name</i></dt>
<dd>
<p>Change the domain name of a domain specified by <i>domain-id</i> to <i>new-name</i>.</p>
</dd>
<dt id="dump-core-domain-id-filename"><b>dump-core</b> <i>domain-id</i> [<i>filename</i>]</dt>
<dd>
<p>Dumps the virtual machine's memory for the specified domain to the <i>filename</i> specified, without pausing the domain. The dump file will be written to a distribution specific directory for dump files, for example: /var/lib/xen/dump/dump.</p>
</dd>
<dt id="help---long"><b>help</b> [<i>--long</i>]</dt>
<dd>
<p>Displays the short help message (i.e. common commands) by default.</p>
<p>If the <i>--long</i> option is specified, it displays the complete set of <b>xl</b> subcommands, grouped by function.</p>
</dd>
<dt id="list-OPTIONS-domain-id"><b>list</b> [<i>OPTIONS</i>] [<i>domain-id</i> ...]</dt>
<dd>
<p>Displays information about one or more domains. If no domains are specified it displays information about all domains.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="l---long"><b>-l</b>, <b>--long</b></dt>
<dd>
<p>The output for <b>xl list</b> is not the table view shown below, but instead presents the data as a JSON data structure.</p>
</dd>
<dt id="Z---context"><b>-Z</b>, <b>--context</b></dt>
<dd>
<p>Also displays the security labels.</p>
</dd>
<dt id="v---verbose"><b>-v</b>, <b>--verbose</b></dt>
<dd>
<p>Also displays the domain UUIDs, the shutdown reason and security labels.</p>
</dd>
<dt id="c---cpupool"><b>-c</b>, <b>--cpupool</b></dt>
<dd>
<p>Also displays the cpupool the domain belongs to.</p>
</dd>
<dt id="n---numa"><b>-n</b>, <b>--numa</b></dt>
<dd>
<p>Also displays the domain NUMA node affinity.</p>
</dd>
</dl>
<p><b>EXAMPLE</b></p>
<p>An example format for the list is as follows:</p>
<pre><code> Name ID Mem VCPUs State Time(s)
Domain-0 0 750 4 r----- 11794.3
win 1 1019 1 r----- 0.3
linux 2 2048 2 r----- 5624.2</code></pre>
<p>Name is the name of the domain. ID the numeric domain id. Mem is the desired amount of memory to allocate to the domain (although it may not be the currently allocated amount). VCPUs is the number of virtual CPUs allocated to the domain. State is the run state (see below). Time is the total run time of the domain as accounted for by Xen.</p>
<p><b>STATES</b></p>
<p>The State field lists 6 states for a Xen domain, and which ones the current domain is in.</p>
<dl>
<dt id="r---running"><b>r - running</b></dt>
<dd>
<p>The domain is currently running on a CPU.</p>
</dd>
<dt id="b---blocked"><b>b - blocked</b></dt>
<dd>
<p>The domain is blocked, and not running or runnable. This can be because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.</p>
</dd>
<dt id="p---paused"><b>p - paused</b></dt>
<dd>
<p>The domain has been paused, usually occurring through the administrator running <b>xl pause</b>. When in a paused state the domain will still consume allocated resources (like memory), but will not be eligible for scheduling by the Xen hypervisor.</p>
</dd>
<dt id="s---shutdown"><b>s - shutdown</b></dt>
<dd>
<p>The guest OS has shut down (SCHEDOP_shutdown has been called) but the domain is not dying yet.</p>
</dd>
<dt id="c---crashed"><b>c - crashed</b></dt>
<dd>
<p>The domain has crashed, which is always a violent ending. Usually this state only occurs if the domain has been configured not to restart on a crash. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more info.</p>
</dd>
<dt id="d---dying"><b>d - dying</b></dt>
<dd>
<p>The domain is in the process of dying, but hasn't completely shut down or crashed.</p>
</dd>
</dl>
<p><b>NOTES</b></p>
<ul>
<p>The Time column is deceptive. Virtual IO (network and block devices) used by the domains requires coordination by Domain0, which means that Domain0 is actually charged for much of the time that a DomainU is doing IO. Use of this time value to determine relative utilizations by domains is thus very unreliable, as a high IO workload may show as less utilized than a high CPU workload. Consider yourself warned.</p>
</ul>
</dd>
<dt id="mem-max-domain-id-mem"><b>mem-max</b> <i>domain-id</i> <i>mem</i></dt>
<dd>
<p>Specify the maximum amount of memory the domain is able to use, appending 't' for terabytes, 'g' for gigabytes, 'm' for megabytes, 'k' for kilobytes and 'b' for bytes.</p>
<p>The mem-max value may not correspond to the actual memory used in the domain, as it may balloon down its memory to give more back to the OS.</p>
<p>The value given just sets the memory amount the domain is allowed to allocate in the hypervisor. It can't be set lower than the current reservation, but it is allowed to be higher than the configured maximum memory size of the domain (<b>maxmem</b> parameter in the domain's configuration). Using <b>xl mem-max</b> to set the maximum memory above the initial <b>maxmem</b> value will not allow the additional memory to be used via <b>xl mem-set</b>. The initial <b>maxmem</b> value is still used as an upper limit for <b>xl mem-set</b>.</p>
<p>The domain will not receive any signal regarding the changed memory limit.</p>
</dd>
<dt id="mem-set-domain-id-mem"><b>mem-set</b> <i>domain-id</i> <i>mem</i></dt>
<dd>
<p>Set the domain's used memory using the balloon driver; append 't' for terabytes, 'g' for gigabytes, 'm' for megabytes, 'k' for kilobytes and 'b' for bytes.</p>
<p>Because this operation requires cooperation from the domain operating system, there is no guarantee that it will succeed. This command will definitely not work unless the domain has the required paravirt driver.</p>
<p><b>Warning:</b> There is no good way to know in advance how small of a mem-set will make a domain unstable and cause it to crash. Be very careful when using this command on running domains.</p>
</dd>
<dt id="migrate-OPTIONS-domain-id-host"><b>migrate</b> [<i>OPTIONS</i>] <i>domain-id</i> <i>host</i></dt>
<dd>
<p>Migrate a domain to another host machine. By default <b>xl</b> relies on ssh as a transport mechanism between the two hosts.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="s-sshcommand"><b>-s</b> <i>sshcommand</i></dt>
<dd>
<p>Use <sshcommand> instead of ssh. String will be passed to sh. If empty, run <host> instead of ssh <host> xl migrate-receive [-d -e].</p>
</dd>
<dt id="e"><b>-e</b></dt>
<dd>
<p>On the new <host>, do not wait in the background for the death of the domain. See the corresponding option of the <i>create</i> subcommand.</p>
</dd>
<dt id="C-config"><b>-C</b> <i>config</i></dt>
<dd>
<p>Send the specified <config> file instead of the file used on creation of the domain.</p>
</dd>
<dt id="debug"><b>--debug</b></dt>
<dd>
<p>Display huge (!) amount of debug information during the migration process.</p>
</dd>
<dt id="p1"><b>-p</b></dt>
<dd>
<p>Leave the domain on the receive side paused after migration.</p>
</dd>
</dl>
</dd>
<dt id="remus-OPTIONS-domain-id-host"><b>remus</b> [<i>OPTIONS</i>] <i>domain-id</i> <i>host</i></dt>
<dd>
<p>Enable Remus HA or COLO HA for domain. By default <b>xl</b> relies on ssh as a transport mechanism between the two hosts.</p>
<p><b>NOTES</b></p>
<ul>
<p>Remus support in xl is still in experimental (proof-of-concept) phase. Disk replication support is limited to DRBD disks.</p>
<p>COLO support in xl is still in experimental (proof-of-concept) phase. All options are subject to change in the future.</p>
</ul>
<p>COLO disk configuration looks like:</p>
<pre><code> disk = ['...,colo,colo-host=xxx,colo-port=xxx,colo-export=xxx,active-disk=xxx,hidden-disk=xxx...']</code></pre>
<p>The supported options are:</p>
<dl>
<dt id="colo-host-:-Secondary-hosts-ip-address"><b>colo-host</b> : Secondary host's ip address.</dt>
<dd>
</dd>
<dt id="colo-port-:-Secondary-hosts-port-we-will-run-a-nbd-server-on-the-secondary-host-and-the-nbd-server-will-listen-on-this-port"><b>colo-port</b> : Secondary host's port, we will run a nbd server on the secondary host, and the nbd server will listen on this port.</dt>
<dd>
</dd>
<dt id="colo-export-:-Nbd-servers-disk-export-name-of-the-secondary-host"><b>colo-export</b> : Nbd server's disk export name of the secondary host.</dt>
<dd>
</dd>
<dt id="active-disk-:-Secondarys-guest-write-will-be-buffered-to-this-disk-and-its-used-by-the-secondary"><b>active-disk</b> : Secondary's guest write will be buffered to this disk, and it's used by the secondary.</dt>
<dd>
</dd>
<dt id="hidden-disk-:-Primarys-modified-contents-will-be-buffered-in-this-disk-and-its-used-by-the-secondary"><b>hidden-disk</b> : Primary's modified contents will be buffered in this disk, and it's used by the secondary.</dt>
<dd>
</dd>
</dl>
<p>COLO network configuration looks like:</p>
<pre><code> vif = [ '...,forwarddev=xxx,...']</code></pre>
<p>The supported options are:</p>
<dl>
<dt id="forwarddev-:-Forward-devices-for-the-primary-and-the-secondary-they-are-directly-connected"><b>forwarddev</b> : Forward devices for the primary and the secondary, they are directly connected.</dt>
<dd>
</dd>
</dl>
<p><b>OPTIONS</b></p>
<dl>
<dt id="i-MS"><b>-i</b> <i>MS</i></dt>
<dd>
<p>Checkpoint domain memory every MS milliseconds (default 200ms).</p>
</dd>
<dt id="u"><b>-u</b></dt>
<dd>
<p>Disable memory checkpoint compression.</p>
</dd>
<dt id="s-sshcommand1"><b>-s</b> <i>sshcommand</i></dt>
<dd>
<p>Use <sshcommand> instead of ssh. String will be passed to sh. If empty, run <host> instead of ssh <host> xl migrate-receive -r [-e].</p>
</dd>
<dt id="e1"><b>-e</b></dt>
<dd>
<p>On the new <host>, do not wait in the background for the death of the domain. See the corresponding option of the <i>create</i> subcommand.</p>
</dd>
<dt id="N-netbufscript"><b>-N</b> <i>netbufscript</i></dt>
<dd>
<p>Use <netbufscript> to setup network buffering instead of the default script (/etc/xen/scripts/remus-netbuf-setup).</p>
</dd>
<dt id="F1"><b>-F</b></dt>
<dd>
<p>Run Remus in unsafe mode. Use this option with caution as failover may not work as intended.</p>
</dd>
<dt id="b"><b>-b</b></dt>
<dd>
<p>Replicate memory checkpoints to /dev/null (blackhole). Generally useful for debugging. Requires enabling unsafe mode.</p>
</dd>
<dt id="n"><b>-n</b></dt>
<dd>
<p>Disable network output buffering. Requires enabling unsafe mode.</p>
</dd>
<dt id="d"><b>-d</b></dt>
<dd>
<p>Disable disk replication. Requires enabling unsafe mode.</p>
</dd>
<dt id="c1"><b>-c</b></dt>
<dd>
<p>Enable COLO HA. This conflicts with <b>-i</b> and <b>-b</b>, and memory checkpoint compression must be disabled.</p>
</dd>
<dt id="p2"><b>-p</b></dt>
<dd>
<p>Use userspace COLO Proxy. This option must be used in conjunction with <b>-c</b>.</p>
</dd>
</dl>
</dd>
<dt id="pause-domain-id"><b>pause</b> <i>domain-id</i></dt>
<dd>
<p>Pause a domain. When in a paused state the domain will still consume allocated resources (such as memory), but will not be eligible for scheduling by the Xen hypervisor.</p>
</dd>
<dt id="reboot-OPTIONS-domain-id"><b>reboot</b> [<i>OPTIONS</i>] <i>domain-id</i></dt>
<dd>
<p>Reboot a domain. This acts just as if the domain had the <b>reboot</b> command run from the console. The command returns as soon as it has executed the reboot action, which may be significantly earlier than when the domain actually reboots.</p>
<p>For HVM domains this requires PV drivers to be installed in your guest OS. If PV drivers are not present but you have configured the guest OS to behave appropriately you may be able to use the <i>-F</i> option to trigger a reset button press.</p>
<p>The behavior of what happens to a domain when it reboots is set by the <b>on_reboot</b> parameter of the domain configuration file when the domain was created.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="F2"><b>-F</b></dt>
<dd>
<p>If the guest does not support PV reboot control then fallback to sending an ACPI power event (equivalent to the <i>reset</i> option to <i>trigger</i>).</p>
<p>You should ensure that the guest is configured to behave as expected in response to this event.</p>
</dd>
</dl>
</dd>
<dt id="restore-OPTIONS-configfile-checkpointfile"><b>restore</b> [<i>OPTIONS</i>] [<i>configfile</i>] <i>checkpointfile</i></dt>
<dd>
<p>Build a domain from an <b>xl save</b> state file. See <b>save</b> for more info.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="p3"><b>-p</b></dt>
<dd>
<p>Do not unpause the domain after restoring it.</p>
</dd>
<dt id="e2"><b>-e</b></dt>
<dd>
<p>Do not wait in the background for the death of the domain on the new host. See the corresponding option of the <i>create</i> subcommand.</p>
</dd>
<dt id="d1"><b>-d</b></dt>
<dd>
<p>Enable debug messages.</p>
</dd>
<dt id="V---vncviewer1"><b>-V</b>, <b>--vncviewer</b></dt>
<dd>
<p>Attach to the domain's VNC server, forking a vncviewer process.</p>
</dd>
<dt id="A---vncviewer-autopass1"><b>-A</b>, <b>--vncviewer-autopass</b></dt>
<dd>
<p>Pass the VNC password to vncviewer via stdin.</p>
</dd>
</dl>
</dd>
<dt id="save-OPTIONS-domain-id-checkpointfile-configfile"><b>save</b> [<i>OPTIONS</i>] <i>domain-id</i> <i>checkpointfile</i> [<i>configfile</i>]</dt>
<dd>
<p>Saves a running domain to a state file so that it can be restored later. Once saved, the domain will no longer be running on the system, unless the -c or -p options are used. <b>xl restore</b> restores from this checkpoint file. Passing a config file argument allows the user to manually select the VM config file used to create the domain.</p>
<dl>
<dt id="c2"><b>-c</b></dt>
<dd>
<p>Leave the domain running after creating the snapshot.</p>
</dd>
<dt id="p4"><b>-p</b></dt>
<dd>
<p>Leave the domain paused after creating the snapshot.</p>
</dd>
</dl>
</dd>
<dt id="sharing-domain-id"><b>sharing</b> [<i>domain-id</i>]</dt>
<dd>
<p>Display the number of shared pages for a specified domain. If no domain is specified it displays information about all domains.</p>
</dd>
<dt id="shutdown-OPTIONS--a-domain-id"><b>shutdown</b> [<i>OPTIONS</i>] <i>-a|domain-id</i></dt>
<dd>
<p>Gracefully shuts down a domain. This coordinates with the domain OS to perform graceful shutdown, so there is no guarantee that it will succeed, and may take a variable length of time depending on what services must be shut down in the domain.</p>
<p>For HVM domains this requires PV drivers to be installed in your guest OS. If PV drivers are not present but you have configured the guest OS to behave appropriately you may be able to use the <i>-F</i> option to trigger a power button press.</p>
<p>The command returns immediately after signaling the domain unless the <b>-w</b> flag is used.</p>
<p>The behavior of what happens to a domain when it reboots is set by the <b>on_shutdown</b> parameter of the domain configuration file when the domain was created.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="a---all"><b>-a</b>, <b>--all</b></dt>
<dd>
<p>Shutdown all guest domains. Often used when doing a complete shutdown of a Xen system.</p>
</dd>
<dt id="w---wait"><b>-w</b>, <b>--wait</b></dt>
<dd>
<p>Wait for the domain to complete shutdown before returning.</p>
</dd>
<dt id="F3"><b>-F</b></dt>
<dd>
<p>If the guest does not support PV shutdown control then fallback to sending an ACPI power event (equivalent to the <i>power</i> option to <i>trigger</i>).</p>
<p>You should ensure that the guest is configured to behave as expected in response to this event.</p>
</dd>
</dl>
</dd>
<dt id="sysrq-domain-id-letter"><b>sysrq</b> <i>domain-id</i> <i>letter</i></dt>
<dd>
<p>Send a <Magic System Request> to the domain, each type of request is represented by a different letter. It can be used to send SysRq requests to Linux guests, see sysrq.txt in your Linux Kernel sources for more information. It requires PV drivers to be installed in your guest OS.</p>
</dd>
<dt id="trigger-domain-id-nmi-reset-init-power-sleep-s3resume-VCPU"><b>trigger</b> <i>domain-id</i> <i>nmi|reset|init|power|sleep|s3resume</i> [<i>VCPU</i>]</dt>
<dd>
<p>Send a trigger to a domain, where the trigger can be: nmi, reset, init, power or sleep. Optionally a specific vcpu number can be passed as an argument. This command is only available for HVM domains.</p>
</dd>
<dt id="unpause-domain-id"><b>unpause</b> <i>domain-id</i></dt>
<dd>
<p>Moves a domain out of the paused state. This will allow a previously paused domain to now be eligible for scheduling by the Xen hypervisor.</p>
</dd>
<dt id="vcpu-set-domain-id-vcpu-count"><b>vcpu-set</b> <i>domain-id</i> <i>vcpu-count</i></dt>
<dd>
<p>Enables the <i>vcpu-count</i> virtual CPUs for the domain in question. Like mem-set, this command can only allocate up to the maximum virtual CPU count configured at boot for the domain.</p>
<p>If the <i>vcpu-count</i> is smaller than the current number of active VCPUs, the highest number VCPUs will be hotplug removed. This may be important for pinning purposes.</p>
<p>Attempting to set the VCPUs to a number larger than the initially configured VCPU count is an error. Trying to set VCPUs to < 1 will be quietly ignored.</p>
<p>Some guests may need to actually bring the newly added CPU online after <b>vcpu-set</b>, go to <b>SEE ALSO</b> section for information.</p>
</dd>
<dt id="vcpu-list-domain-id"><b>vcpu-list</b> [<i>domain-id</i>]</dt>
<dd>
<p>Lists VCPU information for a specific domain. If no domain is specified, VCPU information for all domains will be provided.</p>
</dd>
<dt id="vcpu-pin--f---force-domain-id-vcpu-cpus-hard-cpus-soft"><b>vcpu-pin</b> [<i>-f|--force</i>] <i>domain-id</i> <i>vcpu</i> <i>cpus hard</i> <i>cpus soft</i></dt>
<dd>
<p>Set hard and soft affinity for a <i>vcpu</i> of <domain-id>. Normally VCPUs can float between available CPUs whenever Xen deems a different run state is appropriate.</p>
<p>Hard affinity can be used to restrict this, by ensuring certain VCPUs can only run on certain physical CPUs. Soft affinity specifies a <i>preferred</i> set of CPUs. Soft affinity needs special support in the scheduler, which is only provided in credit1.</p>
<p>The keyword <b>all</b> can be used to apply the hard and soft affinity masks to all the VCPUs in the domain. The symbol '-' can be used to leave either hard or soft affinity alone.</p>
<p>For example:</p>
<pre><code> xl vcpu-pin 0 3 - 6-9</code></pre>
<p>will set soft affinity for vCPU 3 of domain 0 to pCPUs 6,7,8 and 9, leaving its hard affinity untouched. On the other hand:</p>
<pre><code> xl vcpu-pin 0 3 3,4 6-9</code></pre>
<p>will set both hard and soft affinity, the former to pCPUs 3 and 4, the latter to pCPUs 6,7,8, and 9.</p>
<p>Specifying <i>-f</i> or <i>--force</i> will remove a temporary pinning done by the operating system (normally this should be done by the operating system). In case a temporary pinning is active for a vcpu the affinity of this vcpu can't be changed without this option.</p>
</dd>
<dt id="vm-list"><b>vm-list</b></dt>
<dd>
<p>Prints information about guests. This list excludes information about service or auxiliary domains such as dom0 and stubdoms.</p>
<p><b>EXAMPLE</b></p>
<p>An example format for the list is as follows:</p>
<pre><code> UUID ID name
59e1cf6c-6ab9-4879-90e7-adc8d1c63bf5 2 win
50bc8f75-81d0-4d53-b2e6-95cb44e2682e 3 linux</code></pre>
</dd>
<dt id="vncviewer-OPTIONS-domain-id"><b>vncviewer</b> [<i>OPTIONS</i>] <i>domain-id</i></dt>
<dd>
<p>Attach to the domain's VNC server, forking a vncviewer process.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="autopass"><i>--autopass</i></dt>
<dd>
<p>Pass the VNC password to vncviewer via stdin.</p>
</dd>
</dl>
</dd>
</dl>
<h1 id="XEN-HOST-SUBCOMMANDS">XEN HOST SUBCOMMANDS</h1>
<dl>
<dt id="debug-keys-keys"><b>debug-keys</b> <i>keys</i></dt>
<dd>
<p>Send debug <i>keys</i> to Xen. It is the same as pressing the Xen "conswitch" (Ctrl-A by default) three times and then pressing "keys".</p>
</dd>
<dt id="set-parameters-params"><b>set-parameters</b> <i>params</i></dt>
<dd>
<p>Set hypervisor parameters as specified in <i>params</i>. This allows for some boot parameters of the hypervisor to be modified in the running systems.</p>
</dd>
<dt id="dmesg-OPTIONS"><b>dmesg</b> [<i>OPTIONS</i>]</dt>
<dd>
<p>Reads the Xen message buffer, similar to dmesg on a Linux system. The buffer contains informational, warning, and error messages created during Xen's boot process. If you are having problems with Xen, this is one of the first places to look as part of problem determination.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="c---clear"><b>-c</b>, <b>--clear</b></dt>
<dd>
<p>Clears Xen's message buffer.</p>
</dd>
</dl>
</dd>
<dt id="info-OPTIONS"><b>info</b> [<i>OPTIONS</i>]</dt>
<dd>
<p>Print information about the Xen host in <i>name : value</i> format. When reporting a Xen bug, please provide this information as part of the bug report. See <i>http://wiki.xen.org/xenwiki/ReportingBugs</i> on how to report Xen bugs.</p>
<p>Sample output looks as follows:</p>
<pre><code> host : scarlett
release : 3.1.0-rc4+
version : #1001 SMP Wed Oct 19 11:09:54 UTC 2011
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2266
hw_caps : bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 6141
free_memory : 4274
free_cpus : 0
outstanding_claims : 0
xen_major : 4
xen_minor : 2
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed Nov 02 17:09:09 2011 +0000 24066:54a5e994a241
xen_commandline : com1=115200,8n1 guest_loglvl=all dom0_mem=750M console=com1
cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8)
cc_compile_by : sstabellini
cc_compile_domain : uk.xensource.com
cc_compile_date : Tue Nov 8 12:03:05 UTC 2011
xend_config_format : 4</code></pre>
<p><b>FIELDS</b></p>
<p>Not all fields will be explained here, but some of the less obvious ones deserve explanation:</p>
<dl>
<dt id="hw_caps"><b>hw_caps</b></dt>
<dd>
<p>A vector showing what hardware capabilities are supported by your processor. This is equivalent to, though more cryptic, the flags field in /proc/cpuinfo on a normal Linux machine: they both derive from the feature bits returned by the cpuid command on x86 platforms.</p>
</dd>
<dt id="free_memory"><b>free_memory</b></dt>
<dd>
<p>Available memory (in MB) not allocated to Xen, or any other domains, or claimed for domains.</p>
</dd>
<dt id="outstanding_claims"><b>outstanding_claims</b></dt>
<dd>
<p>When a claim call is done (see <a href="xl.conf.5.html">xl.conf(5)</a>) a reservation for a specific amount of pages is set and also a global value is incremented. This global value (outstanding_claims) is then reduced as the domain's memory is populated and eventually reaches zero. Most of the time the value will be zero, but if you are launching multiple guests, and <b>claim_mode</b> is enabled, this value can increase/decrease. Note that the value also affects the <b>free_memory</b> - as it will reflect the free memory in the hypervisor minus the outstanding pages claimed for guests. See xl <i>info</i> <b>claims</b> parameter for detailed listing.</p>
</dd>
<dt id="xen_caps"><b>xen_caps</b></dt>
<dd>
<p>The Xen version and architecture. Architecture values can be one of: x86_32, x86_32p (i.e. PAE enabled), x86_64, ia64.</p>
</dd>
<dt id="xen_changeset"><b>xen_changeset</b></dt>
<dd>
<p>The Xen mercurial changeset id. Very useful for determining exactly what version of code your Xen system was built from.</p>
</dd>
</dl>
<p><b>OPTIONS</b></p>
<dl>
<dt id="n---numa1"><b>-n</b>, <b>--numa</b></dt>
<dd>
<p>List host NUMA topology information</p>
</dd>
</dl>
</dd>
<dt id="top"><b>top</b></dt>
<dd>
<p>Executes the <b>xentop(1)</b> command, which provides real time monitoring of domains. Xentop has a curses interface, and is reasonably self explanatory.</p>
</dd>
<dt id="uptime"><b>uptime</b></dt>
<dd>
<p>Prints the current uptime of the domains running.</p>
</dd>
<dt id="claims"><b>claims</b></dt>
<dd>
<p>Prints information about outstanding claims by the guests. This provides the outstanding claims and currently populated memory count for the guests. These values added up reflect the global outstanding claim value, which is provided via the <i>info</i> argument, <b>outstanding_claims</b> value. The <b>Mem</b> column has the cumulative value of outstanding claims and the total amount of memory that has been right now allocated to the guest.</p>
<p><b>EXAMPLE</b></p>
<p>An example format for the list is as follows:</p>
<pre><code> Name ID Mem VCPUs State Time(s) Claimed
Domain-0 0 2047 4 r----- 19.7 0
OL5 2 2048 1 --p--- 0.0 847
OL6 3 1024 4 r----- 5.9 0
Windows_XP 4 2047 1 --p--- 0.0 1989</code></pre>
<p>In which it can be seen that the OL5 guest still has 847MB of claimed memory (out of the total 2048MB where 1191MB has been allocated to the guest).</p>
</dd>
</dl>
<h1 id="SCHEDULER-SUBCOMMANDS">SCHEDULER SUBCOMMANDS</h1>
<p>Xen ships with a number of domain schedulers, which can be set at boot time with the <b>sched=</b> parameter on the Xen command line. By default <b>credit</b> is used for scheduling.</p>
<dl>
<dt id="sched-credit-OPTIONS"><b>sched-credit</b> [<i>OPTIONS</i>]</dt>
<dd>
<p>Set or get credit (aka credit1) scheduler parameters. The credit scheduler is a proportional fair share CPU scheduler built from the ground up to be work conserving on SMP hosts.</p>
<p>Each domain (including Domain0) is assigned a weight and a cap.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="d-DOMAIN---domain-DOMAIN"><b>-d DOMAIN</b>, <b>--domain=DOMAIN</b></dt>
<dd>
<p>Specify domain for which scheduler parameters are to be modified or retrieved. Mandatory for modifying scheduler parameters.</p>
</dd>
<dt id="w-WEIGHT---weight-WEIGHT"><b>-w WEIGHT</b>, <b>--weight=WEIGHT</b></dt>
<dd>
<p>A domain with a weight of 512 will get twice as much CPU as a domain with a weight of 256 on a contended host. Legal weights range from 1 to 65535 and the default is 256.</p>
</dd>
<dt id="c-CAP---cap-CAP"><b>-c CAP</b>, <b>--cap=CAP</b></dt>
<dd>
<p>The cap optionally fixes the maximum amount of CPU a domain will be able to consume, even if the host system has idle CPU cycles. The cap is expressed in percentage of one physical CPU: 100 is 1 physical CPU, 50 is half a CPU, 400 is 4 CPUs, etc. The default, 0, means there is no upper cap.</p>
<p>NB: Many systems have features that will scale down the computing power of a cpu that is not 100% utilized. This can be in the operating system, but can also sometimes be below the operating system in the BIOS. If you set a cap such that individual cores are running at less than 100%, this may have an impact on the performance of your workload over and above the impact of the cap. For example, if your processor runs at 2GHz, and you cap a vm at 50%, the power management system may also reduce the clock speed to 1GHz; the effect will be that your VM gets 25% of the available power (50% of 1GHz) rather than 50% (50% of 2GHz). If you are not getting the performance you expect, look at performance and cpufreq options in your operating system and your BIOS.</p>
</dd>
<dt id="p-CPUPOOL---cpupool-CPUPOOL"><b>-p CPUPOOL</b>, <b>--cpupool=CPUPOOL</b></dt>
<dd>
<p>Restrict output to domains in the specified cpupool.</p>
</dd>
<dt id="s---schedparam"><b>-s</b>, <b>--schedparam</b></dt>
<dd>
<p>Specify to list or set pool-wide scheduler parameters.</p>
</dd>
<dt id="t-TSLICE---tslice_ms-TSLICE"><b>-t TSLICE</b>, <b>--tslice_ms=TSLICE</b></dt>
<dd>
<p>Timeslice tells the scheduler how long to allow VMs to run before pre-empting. The default is 30ms. Valid ranges are 1ms to 1000ms. The length of the timeslice (in ms) must be higher than the length of the ratelimit (see below).</p>
</dd>
<dt id="r-RLIMIT---ratelimit_us-RLIMIT"><b>-r RLIMIT</b>, <b>--ratelimit_us=RLIMIT</b></dt>
<dd>
<p>Ratelimit attempts to limit the number of schedules per second. It sets a minimum amount of time (in microseconds) a VM must run before we will allow a higher-priority VM to pre-empt it. The default value is 1000 microseconds (1ms). Valid range is 100 to 500000 (500ms). The ratelimit length must be lower than the timeslice length.</p>
</dd>
<dt id="m-DELAY---migration_delay_us-DELAY"><b>-m DELAY</b>, <b>--migration_delay_us=DELAY</b></dt>
<dd>
<p>Migration delay specifies for how long a vCPU, after it stopped running should be considered "cache-hot". Basically, if less than DELAY us passed since when the vCPU was executing on a CPU, it is likely that most of the vCPU's working set is still in the CPU's cache, and therefore the vCPU is not migrated.</p>
<p>Default is 0. Maximum is 100 ms. This can be effective at preventing vCPUs to bounce among CPUs too quickly, but, at the same time, the scheduler stops being fully work-conserving.</p>
</dd>
</dl>
<p><b>COMBINATION</b></p>
<p>The following is the effect of combining the above options:</p>
<dl>
<dt id="nothing-:-List-all-domain-params-and-sched-params-from-all-pools"><b><nothing></b> : List all domain params and sched params from all pools</dt>
<dd>
</dd>
<dt id="d-domid-:-List-domain-params-for-domain-domid"><b>-d [domid]</b> : List domain params for domain [domid]</dt>
<dd>
</dd>
<dt id="d-domid-params-:-Set-domain-params-for-domain-domid"><b>-d [domid] [params]</b> : Set domain params for domain [domid]</dt>
<dd>
</dd>
<dt id="p-pool-:-list-all-domains-and-sched-params-for-pool"><b>-p [pool]</b> : list all domains and sched params for [pool]</dt>
<dd>
</dd>
<dt id="s-:-List-sched-params-for-poolid-0"><b>-s</b> : List sched params for poolid 0</dt>
<dd>
</dd>
<dt id="s-params-:-Set-sched-params-for-poolid-0"><b>-s [params]</b> : Set sched params for poolid 0</dt>
<dd>
</dd>
<dt id="p-pool--s-:-List-sched-params-for-pool"><b>-p [pool] -s</b> : List sched params for [pool]</dt>
<dd>
</dd>
<dt id="p-pool--s-params-:-Set-sched-params-for-pool"><b>-p [pool] -s [params]</b> : Set sched params for [pool]</dt>
<dd>
</dd>
<dt id="p-pool--d...-:-Illegal"><b>-p [pool] -d</b>... : Illegal</dt>
<dd>
</dd>
</dl>
</dd>
<dt id="sched-credit2-OPTIONS"><b>sched-credit2</b> [<i>OPTIONS</i>]</dt>
<dd>
<p>Set or get credit2 scheduler parameters. The credit2 scheduler is a proportional fair share CPU scheduler built from the ground up to be work conserving on SMP hosts.</p>
<p>Each domain (including Domain0) is assigned a weight.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="d-DOMAIN---domain-DOMAIN1"><b>-d DOMAIN</b>, <b>--domain=DOMAIN</b></dt>
<dd>
<p>Specify domain for which scheduler parameters are to be modified or retrieved. Mandatory for modifying scheduler parameters.</p>
</dd>
<dt id="w-WEIGHT---weight-WEIGHT1"><b>-w WEIGHT</b>, <b>--weight=WEIGHT</b></dt>
<dd>
<p>A domain with a weight of 512 will get twice as much CPU as a domain with a weight of 256 on a contended host. Legal weights range from 1 to 65535 and the default is 256.</p>
</dd>
<dt id="p-CPUPOOL---cpupool-CPUPOOL1"><b>-p CPUPOOL</b>, <b>--cpupool=CPUPOOL</b></dt>
<dd>
<p>Restrict output to domains in the specified cpupool.</p>
</dd>
<dt id="s---schedparam1"><b>-s</b>, <b>--schedparam</b></dt>
<dd>
<p>Specify to list or set pool-wide scheduler parameters.</p>
</dd>
<dt id="r-RLIMIT---ratelimit_us-RLIMIT1"><b>-r RLIMIT</b>, <b>--ratelimit_us=RLIMIT</b></dt>
<dd>
<p>Attempts to limit the rate of context switching. It is basically the same as <b>--ratelimit_us</b> in <b>sched-credit</b></p>
</dd>
</dl>
</dd>
<dt id="sched-rtds-OPTIONS"><b>sched-rtds</b> [<i>OPTIONS</i>]</dt>
<dd>
<p>Set or get rtds (Real Time Deferrable Server) scheduler parameters. This rt scheduler applies Preemptive Global Earliest Deadline First real-time scheduling algorithm to schedule VCPUs in the system. Each VCPU has a dedicated period, budget and extratime. While scheduled, a VCPU burns its budget. A VCPU has its budget replenished at the beginning of each period; Unused budget is discarded at the end of each period. A VCPU with extratime set gets extra time from the unreserved system resource.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="d-DOMAIN---domain-DOMAIN2"><b>-d DOMAIN</b>, <b>--domain=DOMAIN</b></dt>
<dd>
<p>Specify domain for which scheduler parameters are to be modified or retrieved. Mandatory for modifying scheduler parameters.</p>
</dd>
<dt id="v-VCPUID-all---vcpuid-VCPUID-all"><b>-v VCPUID/all</b>, <b>--vcpuid=VCPUID/all</b></dt>
<dd>
<p>Specify vcpu for which scheduler parameters are to be modified or retrieved.</p>
</dd>
<dt id="p-PERIOD---period-PERIOD"><b>-p PERIOD</b>, <b>--period=PERIOD</b></dt>
<dd>
<p>Period of time, in microseconds, over which to replenish the budget.</p>
</dd>
<dt id="b-BUDGET---budget-BUDGET"><b>-b BUDGET</b>, <b>--budget=BUDGET</b></dt>
<dd>
<p>Amount of time, in microseconds, that the VCPU will be allowed to run every period.</p>
</dd>
<dt id="e-Extratime---extratime-Extratime"><b>-e Extratime</b>, <b>--extratime=Extratime</b></dt>
<dd>
<p>Binary flag to decide if the VCPU will be allowed to get extra time from the unreserved system resource.</p>
</dd>
<dt id="c-CPUPOOL---cpupool-CPUPOOL"><b>-c CPUPOOL</b>, <b>--cpupool=CPUPOOL</b></dt>
<dd>
<p>Restrict output to domains in the specified cpupool.</p>
</dd>
</dl>
<p><b>EXAMPLE</b></p>
<ul>
<p>1) Use <b>-v all</b> to see the budget and period of all the VCPUs of all the domains:</p>
<pre><code> xl sched-rtds -v all
Cpupool Pool-0: sched=RTDS
Name ID VCPU Period Budget Extratime
Domain-0 0 0 10000 4000 yes
vm1 2 0 300 150 yes
vm1 2 1 400 200 yes
vm1 2 2 10000 4000 yes
vm1 2 3 1000 500 yes
vm2 4 0 10000 4000 yes
vm2 4 1 10000 4000 yes</code></pre>
<p>Without any arguments, it will output the default scheduling parameters for each domain:</p>
<pre><code> xl sched-rtds
Cpupool Pool-0: sched=RTDS
Name ID Period Budget Extratime
Domain-0 0 10000 4000 yes
vm1 2 10000 4000 yes
vm2 4 10000 4000 yes</code></pre>
<p>2) Use, for instance, <b>-d vm1, -v all</b> to see the budget and period of all VCPUs of a specific domain (<b>vm1</b>):</p>
<pre><code> xl sched-rtds -d vm1 -v all
Name ID VCPU Period Budget Extratime
vm1 2 0 300 150 yes
vm1 2 1 400 200 yes
vm1 2 2 10000 4000 yes
vm1 2 3 1000 500 yes</code></pre>
<p>To see the parameters of a subset of the VCPUs of a domain, use:</p>
<pre><code> xl sched-rtds -d vm1 -v 0 -v 3
Name ID VCPU Period Budget Extratime
vm1 2 0 300 150 yes
vm1 2 3 1000 500 yes</code></pre>
<p>If no <b>-v</b> is specified, the default scheduling parameters for the domain are shown:</p>
<pre><code> xl sched-rtds -d vm1
Name ID Period Budget Extratime
vm1 2 10000 4000 yes</code></pre>
<p>3) Users can set the budget and period of multiple VCPUs of a specific domain with only one command, e.g., "xl sched-rtds -d vm1 -v 0 -p 100 -b 50 -e 1 -v 3 -p 300 -b 150 -e 0".</p>
<p>To change the parameters of all the VCPUs of a domain, use <b>-v all</b>, e.g., "xl sched-rtds -d vm1 -v all -p 500 -b 250 -e 1".</p>
</ul>
</dd>
</dl>
<h1 id="CPUPOOLS-COMMANDS">CPUPOOLS COMMANDS</h1>
<p>Xen can group the physical cpus of a server in cpu-pools. Each physical CPU is assigned at most to one cpu-pool. Domains are each restricted to a single cpu-pool. Scheduling does not cross cpu-pool boundaries, so each cpu-pool has its own scheduler. Physical cpus and domains can be moved from one cpu-pool to another only by an explicit command. Cpu-pools can be specified either by name or by id.</p>
<dl>
<dt id="cpupool-create-OPTIONS-configfile-variable-value"><b>cpupool-create</b> [<i>OPTIONS</i>] [<i>configfile</i>] [<i>variable=value</i> ...]</dt>
<dd>
<p>Create a cpu pool based an config from a <i>configfile</i> or command-line parameters. Variable settings from the <i>configfile</i> may be altered by specifying new or additional assignments on the command line.</p>
<p>See the <a href="xlcpupool.cfg.5.html">xlcpupool.cfg(5)</a> manpage for more information.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="f-FILE---defconfig-FILE2"><b>-f=FILE</b>, <b>--defconfig=FILE</b></dt>
<dd>
<p>Use the given configuration file.</p>
</dd>
</dl>
</dd>
<dt id="cpupool-list-OPTIONS-cpu-pool"><b>cpupool-list</b> [<i>OPTIONS</i>] [<i>cpu-pool</i>]</dt>
<dd>
<p>List CPU pools on the host.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="c---cpus"><b>-c</b>, <b>--cpus</b></dt>
<dd>
<p>If this option is specified, <b>xl</b> prints a list of CPUs used by <i>cpu-pool</i>.</p>
</dd>
</dl>
</dd>
<dt id="cpupool-destroy-cpu-pool"><b>cpupool-destroy</b> <i>cpu-pool</i></dt>
<dd>
<p>Deactivates a cpu pool. This is possible only if no domain is active in the cpu-pool.</p>
</dd>
<dt id="cpupool-rename-cpu-pool-newname"><b>cpupool-rename</b> <i>cpu-pool</i> <newname></dt>
<dd>
<p>Renames a cpu-pool to <i>newname</i>.</p>
</dd>
<dt id="cpupool-cpu-add-cpu-pool-cpus-node:nodes"><b>cpupool-cpu-add</b> <i>cpu-pool</i> <i>cpus|node:nodes</i></dt>
<dd>
<p>Adds one or more CPUs or NUMA nodes to <i>cpu-pool</i>. CPUs and NUMA nodes can be specified as single CPU/node IDs or as ranges.</p>
<p>For example:</p>
<pre><code> (a) xl cpupool-cpu-add mypool 4
(b) xl cpupool-cpu-add mypool 1,5,10-16,^13
(c) xl cpupool-cpu-add mypool node:0,nodes:2-3,^10-12,8</code></pre>
<p>means adding CPU 4 to mypool, in (a); adding CPUs 1,5,10,11,12,14,15 and 16, in (b); and adding all the CPUs of NUMA nodes 0, 2 and 3, plus CPU 8, but keeping out CPUs 10,11,12, in (c).</p>
<p>All the specified CPUs that can be added to the cpupool will be added to it. If some CPU can't (e.g., because they're already part of another cpupool), an error is reported about each one of them.</p>
</dd>
<dt id="cpupool-cpu-remove-cpus-node:nodes"><b>cpupool-cpu-remove</b> <i>cpus|node:nodes</i></dt>
<dd>
<p>Removes one or more CPUs or NUMA nodes from <i>cpu-pool</i>. CPUs and NUMA nodes can be specified as single CPU/node IDs or as ranges, using the exact same syntax as in <b>cpupool-cpu-add</b> above.</p>
</dd>
<dt id="cpupool-migrate-domain-id-cpu-pool"><b>cpupool-migrate</b> <i>domain-id</i> <i>cpu-pool</i></dt>
<dd>
<p>Moves a domain specified by domain-id or domain-name into a cpu-pool. Domain-0 can't be moved to another cpu-pool.</p>
</dd>
<dt id="cpupool-numa-split"><b>cpupool-numa-split</b></dt>
<dd>
<p>Splits up the machine into one cpu-pool per numa node.</p>
</dd>
</dl>
<h1 id="VIRTUAL-DEVICE-COMMANDS">VIRTUAL DEVICE COMMANDS</h1>
<p>Most virtual devices can be added and removed while guests are running, assuming that the necessary support exists in the guest OS. The effect to the guest OS is much the same as any hotplug event.</p>
<h2 id="BLOCK-DEVICES">BLOCK DEVICES</h2>
<dl>
<dt id="block-attach-domain-id-disc-spec-component-s"><b>block-attach</b> <i>domain-id</i> <i>disc-spec-component(s)</i> ...</dt>
<dd>
<p>Create a new virtual block device and attach it to the specified domain. A disc specification is in the same format used for the <b>disk</b> variable in the domain config file. See <a href="xl-disk-configuration.5.html">xl-disk-configuration(5)</a>. This will trigger a hotplug event for the guest.</p>
<p>Note that only PV block devices are supported by block-attach. Requests to attach emulated devices (eg, vdev=hdc) will result in only the PV view being available to the guest.</p>
</dd>
<dt id="block-detach-domain-id-devid-OPTIONS"><b>block-detach</b> <i>domain-id</i> <i>devid</i> [<i>OPTIONS</i>]</dt>
<dd>
<p>Detach a domain's virtual block device. <i>devid</i> may be the symbolic name or the numeric device id given to the device by domain 0. You will need to run <b>xl block-list</b> to determine that number.</p>
<p>Detaching the device requires the cooperation of the domain. If the domain fails to release the device (perhaps because the domain is hung or is still using the device), the detach will fail.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="force"><b>--force</b></dt>
<dd>
<p>If this parameter is specified the device will be forcefully detached, which may cause IO errors in the domain.</p>
</dd>
</dl>
</dd>
<dt id="block-list-domain-id"><b>block-list</b> <i>domain-id</i></dt>
<dd>
<p>List virtual block devices for a domain.</p>
</dd>
<dt id="cd-insert-domain-id-virtualdevice-target"><b>cd-insert</b> <i>domain-id</i> <i>virtualdevice</i> <i>target</i></dt>
<dd>
<p>Insert a cdrom into a guest domain's existing virtual cd drive. The virtual drive must already exist but can be empty. How the device should be presented to the guest domain is specified by the <i>virtualdevice</i> parameter; for example "hdc". Parameter <i>target</i> is the target path in the backend domain (usually domain 0) to be exported; can be a block device or a file etc. See <b>target</b> in <a href="xl-disk-configuration.5.html">xl-disk-configuration(5)</a>.</p>
<p>Only works with HVM domains.</p>
</dd>
<dt id="cd-eject-domain-id-virtualdevice"><b>cd-eject</b> <i>domain-id</i> <i>virtualdevice</i></dt>
<dd>
<p>Eject a cdrom from a guest domain's virtual cd drive, specified by <i>virtualdevice</i>. Only works with HVM domains.</p>
</dd>
</dl>
<h2 id="NETWORK-DEVICES">NETWORK DEVICES</h2>
<dl>
<dt id="network-attach-domain-id-network-device"><b>network-attach</b> <i>domain-id</i> <i>network-device</i></dt>
<dd>
<p>Creates a new network device in the domain specified by <i>domain-id</i>. <i>network-device</i> describes the device to attach, using the same format as the <b>vif</b> string in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> and <a href="xl-network-configuration.5.html">xl-network-configuration(5)</a> for more information.</p>
<p>Note that only attaching PV network interfaces is supported.</p>
</dd>
<dt id="network-detach-domain-id-devid-mac"><b>network-detach</b> <i>domain-id</i> <i>devid|mac</i></dt>
<dd>
<p>Removes the network device from the domain specified by <i>domain-id</i>. <i>devid</i> is the virtual interface device number within the domain (i.e. the 3 in vif22.3). Alternatively, the <i>mac</i> address can be used to select the virtual interface to detach.</p>
</dd>
<dt id="network-list-domain-id"><b>network-list</b> <i>domain-id</i></dt>
<dd>
<p>List virtual network interfaces for a domain.</p>
</dd>
</dl>
<h2 id="CHANNEL-DEVICES">CHANNEL DEVICES</h2>
<dl>
<dt id="channel-list-domain-id"><b>channel-list</b> <i>domain-id</i></dt>
<dd>
<p>List virtual channel interfaces for a domain.</p>
</dd>
</dl>
<h2 id="VIRTUAL-TRUSTED-PLATFORM-MODULE-vTPM-DEVICES">VIRTUAL TRUSTED PLATFORM MODULE (vTPM) DEVICES</h2>
<dl>
<dt id="vtpm-attach-domain-id-vtpm-device"><b>vtpm-attach</b> <i>domain-id</i> <i>vtpm-device</i></dt>
<dd>
<p>Creates a new vtpm (virtual Trusted Platform Module) device in the domain specified by <i>domain-id</i>. <i>vtpm-device</i> describes the device to attach, using the same format as the <b>vtpm</b> string in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more information.</p>
</dd>
<dt id="vtpm-detach-domain-id-devid-uuid"><b>vtpm-detach</b> <i>domain-id</i> <i>devid|uuid</i></dt>
<dd>
<p>Removes the vtpm device from the domain specified by <i>domain-id</i>. <i>devid</i> is the numeric device id given to the virtual Trusted Platform Module device. You will need to run <b>xl vtpm-list</b> to determine that number. Alternatively, the <i>uuid</i> of the vtpm can be used to select the virtual device to detach.</p>
</dd>
<dt id="vtpm-list-domain-id"><b>vtpm-list</b> <i>domain-id</i></dt>
<dd>
<p>List virtual Trusted Platform Modules for a domain.</p>
</dd>
</dl>
<h2 id="VDISPL-DEVICES">VDISPL DEVICES</h2>
<dl>
<dt id="vdispl-attach-domain-id-vdispl-device"><b>vdispl-attach</b> <i>domain-id</i> <i>vdispl-device</i></dt>
<dd>
<p>Creates a new vdispl device in the domain specified by <i>domain-id</i>. <i>vdispl-device</i> describes the device to attach, using the same format as the <b>vdispl</b> string in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more information.</p>
<p><b>NOTES</b></p>
<ul>
<p>As in <i>vdispl-device</i> string semicolon is used then put quotes or escaping when using from the shell.</p>
<p><b>EXAMPLE</b></p>
<ul>
<p>xl vdispl-attach DomU connectors='id0:1920x1080;id1:800x600;id2:640x480'</p>
<p>or</p>
<p>xl vdispl-attach DomU connectors=id0:1920x1080\;id1:800x600\;id2:640x480</p>
</ul>
</ul>
</dd>
<dt id="vdispl-detach-domain-id-dev-id"><b>vdispl-detach</b> <i>domain-id</i> <i>dev-id</i></dt>
<dd>
<p>Removes the vdispl device specified by <i>dev-id</i> from the domain specified by <i>domain-id</i>.</p>
</dd>
<dt id="vdispl-list-domain-id"><b>vdispl-list</b> <i>domain-id</i></dt>
<dd>
<p>List virtual displays for a domain.</p>
</dd>
</dl>
<h2 id="VSND-DEVICES">VSND DEVICES</h2>
<dl>
<dt id="vsnd-attach-domain-id-vsnd-item-vsnd-item"><b>vsnd-attach</b> <i>domain-id</i> <i>vsnd-item</i> <i>vsnd-item</i> ...</dt>
<dd>
<p>Creates a new vsnd device in the domain specified by <i>domain-id</i>. <i>vsnd-item</i>'s describe the vsnd device to attach, using the same format as the <b>VSND_ITEM_SPEC</b> string in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more information.</p>
<p><b>EXAMPLE</b></p>
<ul>
<p>xl vsnd-attach DomU 'CARD, short-name=Main, sample-formats=s16_le;s8;u32_be' 'PCM, name=Main' 'STREAM, id=0, type=p' 'STREAM, id=1, type=c, channels-max=2'</p>
</ul>
</dd>
<dt id="vsnd-detach-domain-id-dev-id"><b>vsnd-detach</b> <i>domain-id</i> <i>dev-id</i></dt>
<dd>
<p>Removes the vsnd device specified by <i>dev-id</i> from the domain specified by <i>domain-id</i>.</p>
</dd>
<dt id="vsnd-list-domain-id"><b>vsnd-list</b> <i>domain-id</i></dt>
<dd>
<p>List vsnd devices for a domain.</p>
</dd>
</dl>
<h2 id="KEYBOARD-DEVICES">KEYBOARD DEVICES</h2>
<dl>
<dt id="vkb-attach-domain-id-vkb-device"><b>vkb-attach</b> <i>domain-id</i> <i>vkb-device</i></dt>
<dd>
<p>Creates a new keyboard device in the domain specified by <i>domain-id</i>. <i>vkb-device</i> describes the device to attach, using the same format as the <b>VKB_SPEC_STRING</b> string in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more informations.</p>
</dd>
<dt id="vkb-detach-domain-id-devid"><b>vkb-detach</b> <i>domain-id</i> <i>devid</i></dt>
<dd>
<p>Removes the keyboard device from the domain specified by <i>domain-id</i>. <i>devid</i> is the virtual interface device number within the domain</p>
</dd>
<dt id="vkb-list-domain-id"><b>vkb-list</b> <i>domain-id</i></dt>
<dd>
<p>List virtual network interfaces for a domain.</p>
</dd>
</dl>
<h1 id="PCI-PASS-THROUGH">PCI PASS-THROUGH</h1>
<dl>
<dt id="pci-assignable-list"><b>pci-assignable-list</b></dt>
<dd>
<p>List all the assignable PCI devices. These are devices in the system which are configured to be available for passthrough and are bound to a suitable PCI backend driver in domain 0 rather than a real driver.</p>
</dd>
<dt id="pci-assignable-add-BDF"><b>pci-assignable-add</b> <i>BDF</i></dt>
<dd>
<p>Make the device at PCI Bus/Device/Function BDF assignable to guests. This will bind the device to the pciback driver. If it is already bound to a driver, it will first be unbound, and the original driver stored so that it can be re-bound to the same driver later if desired. If the device is already bound, it will return success.</p>
<p>CAUTION: This will make the device unusable by Domain 0 until it is returned with pci-assignable-remove. Care should therefore be taken not to do this on a device critical to domain 0's operation, such as storage controllers, network interfaces, or GPUs that are currently being used.</p>
</dd>
<dt id="pci-assignable-remove--r-BDF"><b>pci-assignable-remove</b> [<i>-r</i>] <i>BDF</i></dt>
<dd>
<p>Make the device at PCI Bus/Device/Function BDF not assignable to guests. This will at least unbind the device from pciback. If the -r option is specified, it will also attempt to re-bind the device to its original driver, making it usable by Domain 0 again. If the device is not bound to pciback, it will return success.</p>
</dd>
<dt id="pci-attach-domain-id-BDF"><b>pci-attach</b> <i>domain-id</i> <i>BDF</i></dt>
<dd>
<p>Hot-plug a new pass-through pci device to the specified domain. <b>BDF</b> is the PCI Bus/Device/Function of the physical device to pass-through.</p>
</dd>
<dt id="pci-detach-OPTIONS-domain-id-BDF"><b>pci-detach</b> [<i>OPTIONS</i>] <i>domain-id</i> <i>BDF</i></dt>
<dd>
<p>Hot-unplug a previously assigned pci device from a domain. <b>BDF</b> is the PCI Bus/Device/Function of the physical device to be removed from the guest domain.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="f2"><b>-f</b></dt>
<dd>
<p>If this parameter is specified, <b>xl</b> is going to forcefully remove the device even without guest domain's collaboration.</p>
</dd>
</dl>
</dd>
<dt id="pci-list-domain-id"><b>pci-list</b> <i>domain-id</i></dt>
<dd>
<p>List pass-through pci devices for a domain.</p>
</dd>
</dl>
<h1 id="USB-PASS-THROUGH">USB PASS-THROUGH</h1>
<dl>
<dt id="usbctrl-attach-domain-id-usbctrl-device"><b>usbctrl-attach</b> <i>domain-id</i> <i>usbctrl-device</i></dt>
<dd>
<p>Create a new USB controller in the domain specified by <i>domain-id</i>, <i>usbctrl-device</i> describes the device to attach, using form <code>KEY=VALUE KEY=VALUE ...</code> where <b>KEY=VALUE</b> has the same meaning as the <b>usbctrl</b> description in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more information.</p>
</dd>
<dt id="usbctrl-detach-domain-id-devid"><b>usbctrl-detach</b> <i>domain-id</i> <i>devid</i></dt>
<dd>
<p>Destroy a USB controller from the specified domain. <b>devid</b> is devid of the USB controller.</p>
</dd>
<dt id="usbdev-attach-domain-id-usbdev-device"><b>usbdev-attach</b> <i>domain-id</i> <i>usbdev-device</i></dt>
<dd>
<p>Hot-plug a new pass-through USB device to the domain specified by <i>domain-id</i>, <i>usbdev-device</i> describes the device to attach, using form <code>KEY=VALUE KEY=VALUE ...</code> where <b>KEY=VALUE</b> has the same meaning as the <b>usbdev</b> description in the domain config file. See <a href="xl.cfg.5.html">xl.cfg(5)</a> for more information.</p>
</dd>
<dt id="usbdev-detach-domain-id-controller-devid-port-number"><b>usbdev-detach</b> <i>domain-id</i> <i>controller=devid</i> <i>port=number</i></dt>
<dd>
<p>Hot-unplug a previously assigned USB device from a domain. <b>controller=devid</b> and <b>port=number</b> is USB controller:port in the guest domain the USB device is attached to.</p>
</dd>
<dt id="usb-list-domain-id"><b>usb-list</b> <i>domain-id</i></dt>
<dd>
<p>List pass-through usb devices for a domain.</p>
</dd>
</dl>
<h1 id="DEVICE-MODEL-CONTROL">DEVICE-MODEL CONTROL</h1>
<dl>
<dt id="qemu-monitor-command-domain-id-command"><b>qemu-monitor-command</b> <i>domain-id</i> <i>command</i></dt>
<dd>
<p>Issue a monitor command to the device model of the domain specified by <i>domain-id</i>. <i>command</i> can be any valid command qemu understands. This can be e.g. used to add non-standard devices or devices with non-standard parameters to a domain. The output of the command is printed to stdout.</p>
<p><b>Warning:</b> This qemu monitor access is provided for convenience when debugging, troubleshooting, and experimenting. Its use is not supported by the Xen Project.</p>
<p>Specifically, not all information displayed by the qemu monitor will necessarily be accurate or complete, because in a Xen system qemu does not have a complete view of the guest.</p>
<p>Furthermore, modifying the guest's setup via the qemu monitor may conflict with the Xen toolstack's assumptions. Resulting problems may include, but are not limited to: guest crashes; toolstack error messages; inability to migrate the guest; and security vulnerabilities which are not covered by the Xen Project security response policy.</p>
<p><b>EXAMPLE</b></p>
<p>Obtain information of USB devices connected as such via the device model (only!) to a domain:</p>
<pre><code> xl qemu-monitor-command vm1 'info usb'
Device 0.2, Port 5, Speed 480 Mb/s, Product Mass Storage</code></pre>
</dd>
</dl>
<h1 id="TRANSCENDENT-MEMORY-TMEM">TRANSCENDENT MEMORY (TMEM)</h1>
<dl>
<dt id="tmem-list-OPTIONS-domain-id"><b>tmem-list</b> <i>[OPTIONS]</i> <i>domain-id</i></dt>
<dd>
<p>List tmem pools.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="l"><b>-l</b></dt>
<dd>
<p>If this parameter is specified, also list tmem stats.</p>
</dd>
</dl>
</dd>
<dt id="tmem-freeze-domain-id"><b>tmem-freeze</b> <i>domain-id</i></dt>
<dd>
<p>Freeze tmem pools.</p>
</dd>
<dt id="tmem-thaw-domain-id"><b>tmem-thaw</b> <i>domain-id</i></dt>
<dd>
<p>Thaw tmem pools.</p>
</dd>
<dt id="tmem-set-domain-id-OPTIONS"><b>tmem-set</b> <i>domain-id</i> [<i>OPTIONS</i>]</dt>
<dd>
<p>Change tmem settings.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="w-WEIGHT"><b>-w</b> <i>WEIGHT</i></dt>
<dd>
<p>Weight (int)</p>
</dd>
<dt id="p-COMPRESS"><b>-p</b> <i>COMPRESS</i></dt>
<dd>
<p>Compress (int)</p>
</dd>
</dl>
</dd>
<dt id="tmem-shared-auth-domain-id-OPTIONS"><b>tmem-shared-auth</b> <i>domain-id</i> [<i>OPTIONS</i>]</dt>
<dd>
<p>De/authenticate shared tmem pool.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="u-UUID"><b>-u</b> <i>UUID</i></dt>
<dd>
<p>Specify uuid (abcdef01-2345-6789-1234-567890abcdef)</p>
</dd>
<dt id="a-AUTH"><b>-a</b> <i>AUTH</i></dt>
<dd>
<p>0=auth,1=deauth</p>
</dd>
</dl>
</dd>
<dt id="tmem-freeable"><b>tmem-freeable</b></dt>
<dd>
<p>Get information about how much freeable memory (MB) is in-use by tmem.</p>
</dd>
</dl>
<h1 id="FLASK">FLASK</h1>
<p><b>FLASK</b> is a security framework that defines a mandatory access control policy providing fine-grained controls over Xen domains, allowing the policy writer to define what interactions between domains, devices, and the hypervisor are permitted. Some example of what you can do using XSM/FLASK: - Prevent two domains from communicating via event channels or grants - Control which domains can use device passthrough (and which devices) - Restrict or audit operations performed by privileged domains - Prevent a privileged domain from arbitrarily mapping pages from other domains.</p>
<p>You can find more details on how to use FLASK and an example security policy here: <a href="http://xenbits.xen.org/docs/unstable/misc/xsm-flask.txt">http://xenbits.xen.org/docs/unstable/misc/xsm-flask.txt</a></p>
<dl>
<dt id="getenforce"><b>getenforce</b></dt>
<dd>
<p>Determine if the FLASK security module is loaded and enforcing its policy.</p>
</dd>
<dt id="setenforce-1-0-Enforcing-Permissive"><b>setenforce</b> <i>1|0|Enforcing|Permissive</i></dt>
<dd>
<p>Enable or disable enforcing of the FLASK access controls. The default is permissive, but this can be changed to enforcing by specifying "flask=enforcing" or "flask=late" on the hypervisor's command line.</p>
</dd>
<dt id="loadpolicy-policy-file"><b>loadpolicy</b> <i>policy-file</i></dt>
<dd>
<p>Load FLASK policy from the given policy file. The initial policy is provided to the hypervisor as a multiboot module; this command allows runtime updates to the policy. Loading new security policy will reset runtime changes to device labels.</p>
</dd>
</dl>
<h1 id="PLATFORM-SHARED-RESOURCE-MONITORING-CONTROL">PLATFORM SHARED RESOURCE MONITORING/CONTROL</h1>
<p>Intel Haswell and later server platforms offer shared resource monitoring and control technologies. The availability of these technologies and the hardware capabilities can be shown with <b>psr-hwinfo</b>.</p>
<p>See <a href="http://xenbits.xen.org/docs/unstable/misc/xl-psr.html">http://xenbits.xen.org/docs/unstable/misc/xl-psr.html</a> for more information.</p>
<dl>
<dt id="psr-hwinfo-OPTIONS"><b>psr-hwinfo</b> [<i>OPTIONS</i>]</dt>
<dd>
<p>Show Platform Shared Resource (PSR) hardware information.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="m---cmt"><b>-m</b>, <b>--cmt</b></dt>
<dd>
<p>Show Cache Monitoring Technology (CMT) hardware information.</p>
</dd>
<dt id="a---cat"><b>-a</b>, <b>--cat</b></dt>
<dd>
<p>Show Cache Allocation Technology (CAT) hardware information.</p>
</dd>
</dl>
</dd>
</dl>
<h2 id="CACHE-MONITORING-TECHNOLOGY">CACHE MONITORING TECHNOLOGY</h2>
<p>Intel Haswell and later server platforms offer monitoring capability in each logical processor to measure specific platform shared resource metric, for example, L3 cache occupancy. In the Xen implementation, the monitoring granularity is domain level. To monitor a specific domain, just attach the domain id with the monitoring service. When the domain doesn't need to be monitored any more, detach the domain id from the monitoring service.</p>
<p>Intel Broadwell and later server platforms also offer total/local memory bandwidth monitoring. Xen supports per-domain monitoring for these two additional monitoring types. Both memory bandwidth monitoring and L3 cache occupancy monitoring share the same set of underlying monitoring service. Once a domain is attached to the monitoring service, monitoring data can be shown for any of these monitoring types.</p>
<p>There is no cache monitoring and memory bandwidth monitoring on L2 cache so far.</p>
<dl>
<dt id="psr-cmt-attach-domain-id"><b>psr-cmt-attach</b> <i>domain-id</i></dt>
<dd>
<p>attach: Attach the platform shared resource monitoring service to a domain.</p>
</dd>
<dt id="psr-cmt-detach-domain-id"><b>psr-cmt-detach</b> <i>domain-id</i></dt>
<dd>
<p>detach: Detach the platform shared resource monitoring service from a domain.</p>
</dd>
<dt id="psr-cmt-show-psr-monitor-type-domain-id"><b>psr-cmt-show</b> <i>psr-monitor-type</i> [<i>domain-id</i>]</dt>
<dd>
<p>Show monitoring data for a certain domain or all domains. Current supported monitor types are: - "cache-occupancy": showing the L3 cache occupancy(KB). - "total-mem-bandwidth": showing the total memory bandwidth(KB/s). - "local-mem-bandwidth": showing the local memory bandwidth(KB/s).</p>
</dd>
</dl>
<h2 id="CACHE-ALLOCATION-TECHNOLOGY">CACHE ALLOCATION TECHNOLOGY</h2>
<p>Intel Broadwell and later server platforms offer capabilities to configure and make use of the Cache Allocation Technology (CAT) mechanisms, which enable more cache resources (i.e. L3/L2 cache) to be made available for high priority applications. In the Xen implementation, CAT is used to control cache allocation on VM basis. To enforce cache on a specific domain, just set capacity bitmasks (CBM) for the domain.</p>
<p>Intel Broadwell and later server platforms also offer Code/Data Prioritization (CDP) for cache allocations, which support specifying code or data cache for applications. CDP is used on a per VM basis in the Xen implementation. To specify code or data CBM for the domain, CDP feature must be enabled and CBM type options need to be specified when setting CBM, and the type options (code and data) are mutually exclusive. There is no CDP support on L2 so far.</p>
<dl>
<dt id="psr-cat-set-OPTIONS-domain-id-cbm"><b>psr-cat-set</b> [<i>OPTIONS</i>] <i>domain-id</i> <i>cbm</i></dt>
<dd>
<p>Set cache capacity bitmasks(CBM) for a domain. For how to specify <i>cbm</i> please refer to <a href="http://xenbits.xen.org/docs/unstable/misc/xl-psr.html">http://xenbits.xen.org/docs/unstable/misc/xl-psr.html</a>.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="s-SOCKET---socket-SOCKET"><b>-s SOCKET</b>, <b>--socket=SOCKET</b></dt>
<dd>
<p>Specify the socket to process, otherwise all sockets are processed.</p>
</dd>
<dt id="l-LEVEL---level-LEVEL"><b>-l LEVEL</b>, <b>--level=LEVEL</b></dt>
<dd>
<p>Specify the cache level to process, otherwise the last level cache (L3) is processed.</p>
</dd>
<dt id="c---code"><b>-c</b>, <b>--code</b></dt>
<dd>
<p>Set code CBM when CDP is enabled.</p>
</dd>
<dt id="d---data"><b>-d</b>, <b>--data</b></dt>
<dd>
<p>Set data CBM when CDP is enabled.</p>
</dd>
</dl>
</dd>
<dt id="psr-cat-show-OPTIONS-domain-id"><b>psr-cat-show</b> [<i>OPTIONS</i>] [<i>domain-id</i>]</dt>
<dd>
<p>Show CAT settings for a certain domain or all domains.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="l-LEVEL---level-LEVEL1"><b>-l LEVEL</b>, <b>--level=LEVEL</b></dt>
<dd>
<p>Specify the cache level to process, otherwise the last level cache (L3) is processed.</p>
</dd>
</dl>
</dd>
</dl>
<h2 id="Memory-Bandwidth-Allocation">Memory Bandwidth Allocation</h2>
<p>Intel Skylake and later server platforms offer capabilities to configure and make use of the Memory Bandwidth Allocation (MBA) mechanisms, which provides OS/VMMs the ability to slow misbehaving apps/VMs by using a credit-based throttling mechanism. In the Xen implementation, MBA is used to control memory bandwidth on VM basis. To enforce bandwidth on a specific domain, just set throttling value (THRTL) for the domain.</p>
<dl>
<dt id="psr-mba-set-OPTIONS-domain-id-thrtl"><b>psr-mba-set</b> [<i>OPTIONS</i>] <i>domain-id</i> <i>thrtl</i></dt>
<dd>
<p>Set throttling value (THRTL) for a domain. For how to specify <i>thrtl</i> please refer to <a href="http://xenbits.xen.org/docs/unstable/misc/xl-psr.html">http://xenbits.xen.org/docs/unstable/misc/xl-psr.html</a>.</p>
<p><b>OPTIONS</b></p>
<dl>
<dt id="s-SOCKET---socket-SOCKET1"><b>-s SOCKET</b>, <b>--socket=SOCKET</b></dt>
<dd>
<p>Specify the socket to process, otherwise all sockets are processed.</p>
</dd>
</dl>
</dd>
<dt id="psr-mba-show-domain-id"><b>psr-mba-show</b> [<i>domain-id</i>]</dt>
<dd>
<p>Show MBA settings for a certain domain or all domains. For linear mode, it shows the decimal value. For non-linear mode, it shows hexadecimal value.</p>
</dd>
</dl>
<h1 id="IGNORED-FOR-COMPATIBILITY-WITH-XM">IGNORED FOR COMPATIBILITY WITH XM</h1>
<p>xl is mostly command-line compatible with the old xm utility used with the old Python xend. For compatibility, the following options are ignored:</p>
<dl>
<dt id="xl-migrate---live"><b>xl migrate --live</b></dt>
<dd>
</dd>
</dl>
<h1 id="TO-BE-DOCUMENTED">TO BE DOCUMENTED</h1>
<p>We need better documentation for:</p>
<dl>
<dt id="tmem"><b>tmem</b></dt>
<dd>
<p>Transcendent Memory.</p>
</dd>
</dl>
<h1 id="SEE-ALSO">SEE ALSO</h1>
<p>The following man pages:</p>
<p><a href="xl.cfg.5.html">xl.cfg(5)</a>, <a href="xlcpupool.cfg.5.html">xlcpupool.cfg(5)</a>, <a href="xentop.1.html">xentop(1)</a>, <a href="xl-disk-configuration.5.html">xl-disk-configuration(5)</a> <a href="xl-network-configuration.5.html">xl-network-configuration(5)</a></p>
<p>And the following documents on the xen.org website:</p>
<p><a href="http://xenbits.xen.org/docs/unstable/misc/xsm-flask.txt">http://xenbits.xen.org/docs/unstable/misc/xsm-flask.txt</a> <a href="http://xenbits.xen.org/docs/unstable/misc/xl-psr.html">http://xenbits.xen.org/docs/unstable/misc/xl-psr.html</a></p>
<p>For systems that don't automatically bring the CPU online:</p>
<p><a href="http://wiki.xen.org/wiki/Paravirt_Linux_CPU_Hotplug">http://wiki.xen.org/wiki/Paravirt_Linux_CPU_Hotplug</a></p>
<h1 id="BUGS">BUGS</h1>
<p>Send bugs to xen-devel@lists.xen.org, see http://wiki.xen.org/xenwiki/ReportingBugs on how to send bug reports.</p>
</body>
</html>
