2009-03-28 07:44:27 +01:00
|
|
|
HXCOMM Use DEFHEADING() to define headings in both help text and texi
|
|
|
|
HXCOMM Text between STEXI and ETEXI are copied to texi version and
|
|
|
|
HXCOMM discarded from C version
|
2010-03-29 21:23:52 +02:00
|
|
|
HXCOMM DEF(option, HAS_ARG/0, opt_enum, opt_help, arch_mask) is used to
|
|
|
|
HXCOMM construct option structures, enums and help message for specified
|
|
|
|
HXCOMM architectures.
|
2009-03-28 07:44:27 +01:00
|
|
|
HXCOMM HXCOMM can be used for comments, discarded from both texi and C
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Standard options:)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("help", 0, QEMU_OPTION_h,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-h or -help display this help and exit\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -h
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -h
|
2009-03-28 07:44:27 +01:00
|
|
|
Display help and exit
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-08 00:58:45 +02:00
|
|
|
DEF("version", 0, QEMU_OPTION_version,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-version display version information and exit\n", QEMU_ARCH_ALL)
|
2009-04-08 00:58:45 +02:00
|
|
|
STEXI
|
|
|
|
@item -version
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -version
|
2009-04-08 00:58:45 +02:00
|
|
|
Display version information and exit
|
|
|
|
ETEXI
|
|
|
|
|
2011-07-23 12:39:46 +02:00
|
|
|
DEF("machine", HAS_ARG, QEMU_OPTION_machine, \
|
|
|
|
"-machine [type=]name[,prop[=value][,...]]\n"
|
2012-10-04 17:22:01 +02:00
|
|
|
" selects emulated machine ('-machine help' for list)\n"
|
2011-07-23 12:39:46 +02:00
|
|
|
" property accel=accel1[:accel2[:...]] selects accelerator\n"
|
2018-01-22 22:07:46 +01:00
|
|
|
" supported accelerators are kvm, xen, hax, hvf, whpx or tcg (default: tcg)\n"
|
2015-11-16 19:03:06 +01:00
|
|
|
" kernel_irqchip=on|off|split controls accelerated irqchip support (default=off)\n"
|
2014-11-21 17:18:52 +01:00
|
|
|
" vmport=on|off|auto controls emulation of vmport (default: auto)\n"
|
2016-05-10 17:49:29 +02:00
|
|
|
" kvm_shadow_mem=size of KVM shadow MMU in bytes\n"
|
2012-09-05 21:50:16 +02:00
|
|
|
" dump-guest-core=on|off include guest memory in a core dump (default=on)\n"
|
2014-08-16 07:55:40 +02:00
|
|
|
" mem-merge=on|off controls memory merge support (default: on)\n"
|
2015-07-15 07:37:45 +02:00
|
|
|
" igd-passthru=on|off controls IGD GFX passthrough support (default=off)\n"
|
2015-03-12 13:53:51 +01:00
|
|
|
" aes-key-wrap=on|off controls support for AES key wrapping (default=on)\n"
|
2015-02-23 13:56:42 +01:00
|
|
|
" dea-key-wrap=on|off controls support for DEA key wrapping (default=on)\n"
|
nvdimm acpi: build ACPI NFIT table
NFIT is defined in ACPI 6.0: 5.2.25 NVDIMM Firmware Interface Table (NFIT)
Currently, we only support PMEM mode. Each device has 3 structures:
- SPA structure, defines the PMEM region info
- MEM DEV structure, it has the @handle which is used to associate specified
ACPI NVDIMM device we will introduce in later patch.
Also we can happily ignored the memory device's interleave, the real
nvdimm hardware access is hidden behind host
- DCR structure, it defines vendor ID used to associate specified vendor
nvdimm driver. Since we only implement PMEM mode this time, Command
window and Data window are not needed
The NVDIMM functionality is controlled by the parameter, 'nvdimm', which
is introduced for the machine, there is a example to enable it:
-machine pc,nvdimm -m 8G,maxmem=100G,slots=100 -object \
memory-backend-file,id=mem1,share,mem-path=/tmp/nvdimm1,size=10G -device \
nvdimm,memdev=mem1,id=nv1
It is disabled on default
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-12-02 08:20:58 +01:00
|
|
|
" suppress-vmdesc=on|off disables self-describing migration (default=off)\n"
|
2016-02-18 12:32:25 +01:00
|
|
|
" nvdimm=on|off controls NVDIMM support (default=off)\n"
|
2017-05-17 02:48:03 +02:00
|
|
|
" enforce-config-section=on|off enforce configuration section migration (default=off)\n"
|
2018-03-08 13:48:38 +01:00
|
|
|
" memory-encryption=@var{} memory encryption object to use (default=none)\n",
|
2011-07-23 12:39:46 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2011-07-23 12:39:46 +02:00
|
|
|
@item -machine [type=]@var{name}[,prop=@var{value}[,...]]
|
|
|
|
@findex -machine
|
2012-10-04 17:22:01 +02:00
|
|
|
Select the emulated machine by @var{name}. Use @code{-machine help} to list
|
2017-07-25 16:10:41 +02:00
|
|
|
available machines.
|
|
|
|
|
|
|
|
For architectures which aim to support live migration compatibility
|
|
|
|
across releases, each release will introduce a new versioned machine
|
|
|
|
type. For example, the 2.8.0 release introduced machine types
|
|
|
|
``pc-i440fx-2.8'' and ``pc-q35-2.8'' for the x86_64/i686 architectures.
|
|
|
|
|
|
|
|
To allow live migration of guests from QEMU version 2.8.0, to QEMU
|
|
|
|
version 2.9.0, the 2.9.0 version must support the ``pc-i440fx-2.8''
|
|
|
|
and ``pc-q35-2.8'' machines too. To allow users live migrating VMs
|
|
|
|
to skip multiple intermediate releases when upgrading, new releases
|
|
|
|
of QEMU will support machine types from many previous versions.
|
|
|
|
|
|
|
|
Supported machine properties are:
|
2011-07-23 12:39:46 +02:00
|
|
|
@table @option
|
|
|
|
@item accel=@var{accels1}[:@var{accels2}[:...]]
|
|
|
|
This is used to enable an accelerator. Depending on the target architecture,
|
2018-01-22 22:07:46 +01:00
|
|
|
kvm, xen, hax, hvf, whpx or tcg can be available. By default, tcg is used. If there is
|
2017-05-04 07:24:41 +02:00
|
|
|
more than one accelerator specified, the next one is used if the previous one
|
|
|
|
fails to initialize.
|
2011-10-15 13:43:48 +02:00
|
|
|
@item kernel_irqchip=on|off
|
2015-11-16 19:03:06 +01:00
|
|
|
Controls in-kernel irqchip support for the chosen accelerator when available.
|
2015-07-15 07:37:45 +02:00
|
|
|
@item gfx_passthru=on|off
|
|
|
|
Enables IGD GFX passthrough support for the chosen machine when available.
|
2014-11-21 17:18:52 +01:00
|
|
|
@item vmport=on|off|auto
|
|
|
|
Enables emulation of VMWare IO port, for vmmouse etc. auto says to select the
|
|
|
|
value based on accel. For accel=xen the default is off otherwise the default
|
|
|
|
is on.
|
2012-01-25 18:14:15 +01:00
|
|
|
@item kvm_shadow_mem=size
|
|
|
|
Defines the size of the KVM shadow MMU.
|
2012-08-02 21:44:16 +02:00
|
|
|
@item dump-guest-core=on|off
|
|
|
|
Include guest memory in a core dump. The default is on.
|
2012-09-05 21:50:16 +02:00
|
|
|
@item mem-merge=on|off
|
|
|
|
Enables or disables memory merge support. This feature, when supported by
|
|
|
|
the host, de-duplicates identical memory pages among VMs instances
|
|
|
|
(enabled by default).
|
2015-03-12 13:53:51 +01:00
|
|
|
@item aes-key-wrap=on|off
|
|
|
|
Enables or disables AES key wrapping support on s390-ccw hosts. This feature
|
|
|
|
controls whether AES wrapping keys will be created to allow
|
|
|
|
execution of AES cryptographic functions. The default is on.
|
|
|
|
@item dea-key-wrap=on|off
|
|
|
|
Enables or disables DEA key wrapping support on s390-ccw hosts. This feature
|
|
|
|
controls whether DEA wrapping keys will be created to allow
|
|
|
|
execution of DEA cryptographic functions. The default is on.
|
nvdimm acpi: build ACPI NFIT table
NFIT is defined in ACPI 6.0: 5.2.25 NVDIMM Firmware Interface Table (NFIT)
Currently, we only support PMEM mode. Each device has 3 structures:
- SPA structure, defines the PMEM region info
- MEM DEV structure, it has the @handle which is used to associate specified
ACPI NVDIMM device we will introduce in later patch.
Also we can happily ignored the memory device's interleave, the real
nvdimm hardware access is hidden behind host
- DCR structure, it defines vendor ID used to associate specified vendor
nvdimm driver. Since we only implement PMEM mode this time, Command
window and Data window are not needed
The NVDIMM functionality is controlled by the parameter, 'nvdimm', which
is introduced for the machine, there is a example to enable it:
-machine pc,nvdimm -m 8G,maxmem=100G,slots=100 -object \
memory-backend-file,id=mem1,share,mem-path=/tmp/nvdimm1,size=10G -device \
nvdimm,memdev=mem1,id=nv1
It is disabled on default
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-12-02 08:20:58 +01:00
|
|
|
@item nvdimm=on|off
|
|
|
|
Enables or disables NVDIMM support. The default is off.
|
2017-07-07 04:54:08 +02:00
|
|
|
@item enforce-config-section=on|off
|
|
|
|
If @option{enforce-config-section} is set to @var{on}, force migration
|
|
|
|
code to send configuration section even if the machine-type sets the
|
|
|
|
@option{migration.send-configuration} property to @var{off}.
|
|
|
|
NOTE: this parameter is deprecated. Please use @option{-global}
|
|
|
|
@option{migration.send-configuration}=@var{on|off} instead.
|
2018-03-08 13:48:38 +01:00
|
|
|
@item memory-encryption=@var{}
|
|
|
|
Memory encryption object to use. The default is none.
|
2011-07-23 12:39:46 +02:00
|
|
|
@end table
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2011-07-23 12:39:46 +02:00
|
|
|
HXCOMM Deprecated by -machine
|
|
|
|
DEF("M", HAS_ARG, QEMU_OPTION_M, "", QEMU_ARCH_ALL)
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("cpu", HAS_ARG, QEMU_OPTION_cpu,
|
2012-10-04 17:22:01 +02:00
|
|
|
"-cpu cpu select CPU ('-cpu help' for list)\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -cpu @var{model}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -cpu
|
2012-10-04 17:22:01 +02:00
|
|
|
Select CPU model (@code{-cpu help} for list and additional feature selection)
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2017-02-23 19:29:08 +01:00
|
|
|
DEF("accel", HAS_ARG, QEMU_OPTION_accel,
|
|
|
|
"-accel [accel=]accelerator[,thread=single|multi]\n"
|
2018-01-22 22:07:46 +01:00
|
|
|
" select accelerator (kvm, xen, hax, hvf, whpx or tcg; use 'help' for a list)\n"
|
2018-06-11 21:56:07 +02:00
|
|
|
" thread=single|multi (enable multi-threaded TCG)\n", QEMU_ARCH_ALL)
|
2017-02-23 19:29:08 +01:00
|
|
|
STEXI
|
|
|
|
@item -accel @var{name}[,prop=@var{value}[,...]]
|
|
|
|
@findex -accel
|
|
|
|
This is used to enable an accelerator. Depending on the target architecture,
|
2018-01-22 22:07:46 +01:00
|
|
|
kvm, xen, hax, hvf, whpx or tcg can be available. By default, tcg is used. If there is
|
2017-05-04 07:24:41 +02:00
|
|
|
more than one accelerator specified, the next one is used if the previous one
|
|
|
|
fails to initialize.
|
2017-02-23 19:29:08 +01:00
|
|
|
@table @option
|
|
|
|
@item thread=single|multi
|
|
|
|
Controls number of TCG threads. When the TCG is multi-threaded there will be one
|
|
|
|
thread per vCPU therefor taking advantage of additional host cores. The default
|
|
|
|
is to enable multi-threading where both the back-end and front-ends support it and
|
|
|
|
no incompatible TCG features have been enabled (e.g. icount/replay).
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("smp", HAS_ARG, QEMU_OPTION_smp,
|
2019-06-20 07:45:25 +02:00
|
|
|
"-smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads][,dies=dies][,sockets=sockets]\n"
|
2009-07-23 17:03:42 +02:00
|
|
|
" set the number of CPUs to 'n' [default=1]\n"
|
|
|
|
" maxcpus= maximum number of total cpus, including\n"
|
2010-01-06 20:33:57 +01:00
|
|
|
" offline CPUs for hotplug, etc\n"
|
2019-06-20 07:45:25 +02:00
|
|
|
" cores= number of CPU cores on one socket (for PC, it's on one die)\n"
|
2009-08-28 10:49:57 +02:00
|
|
|
" threads= number of threads on one CPU core\n"
|
2019-06-20 07:45:25 +02:00
|
|
|
" dies= number of CPU dies on one socket (for PC only)\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" sockets= number of discrete sockets in the system\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2019-06-20 07:45:25 +02:00
|
|
|
@item -smp [cpus=]@var{n}[,cores=@var{cores}][,threads=@var{threads}][,dies=dies][,sockets=@var{sockets}][,maxcpus=@var{maxcpus}]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -smp
|
2009-03-28 07:44:27 +01:00
|
|
|
Simulate an SMP system with @var{n} CPUs. On the PC target, up to 255
|
|
|
|
CPUs are supported. On Sparc32 target, Linux limits the number of usable CPUs
|
|
|
|
to 4.
|
2019-06-20 07:45:25 +02:00
|
|
|
For the PC target, the number of @var{cores} per die, the number of @var{threads}
|
|
|
|
per cores, the number of @var{dies} per packages and the total number of
|
|
|
|
@var{sockets} can be specified. Missing values will be computed.
|
|
|
|
If any on the three values is given, the total number of CPUs @var{n} can be omitted.
|
|
|
|
@var{maxcpus} specifies the maximum number of hotpluggable CPUs.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2009-04-22 00:30:27 +02:00
|
|
|
DEF("numa", HAS_ARG, QEMU_OPTION_numa,
|
2017-01-23 19:06:31 +01:00
|
|
|
"-numa node[,mem=size][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n"
|
numa: Allow setting NUMA distance for different NUMA nodes
This patch is going to add SLIT table support in QEMU, and provides
additional option `dist` for command `-numa` to allow user set vNUMA
distance by QEMU command.
With this patch, when a user wants to create a guest that contains
several vNUMA nodes and also wants to set distance among those nodes,
the QEMU command would like:
```
-numa node,nodeid=0,cpus=0 \
-numa node,nodeid=1,cpus=1 \
-numa node,nodeid=2,cpus=2 \
-numa node,nodeid=3,cpus=3 \
-numa dist,src=0,dst=1,val=21 \
-numa dist,src=0,dst=2,val=31 \
-numa dist,src=0,dst=3,val=41 \
-numa dist,src=1,dst=2,val=21 \
-numa dist,src=1,dst=3,val=31 \
-numa dist,src=2,dst=3,val=21 \
```
Signed-off-by: He Chen <he.chen@linux.intel.com>
Message-Id: <1493260558-20728-1-git-send-email-he.chen@linux.intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-04-27 04:35:58 +02:00
|
|
|
"-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n"
|
2017-11-28 15:53:58 +01:00
|
|
|
"-numa dist,src=source,dst=destination,val=distance\n"
|
|
|
|
"-numa cpu,node-id=node[,socket-id=x][,core-id=y][,thread-id=z]\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-04-22 00:30:27 +02:00
|
|
|
STEXI
|
2017-01-23 19:06:31 +01:00
|
|
|
@item -numa node[,mem=@var{size}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}]
|
|
|
|
@itemx -numa node[,memdev=@var{id}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}]
|
numa: Allow setting NUMA distance for different NUMA nodes
This patch is going to add SLIT table support in QEMU, and provides
additional option `dist` for command `-numa` to allow user set vNUMA
distance by QEMU command.
With this patch, when a user wants to create a guest that contains
several vNUMA nodes and also wants to set distance among those nodes,
the QEMU command would like:
```
-numa node,nodeid=0,cpus=0 \
-numa node,nodeid=1,cpus=1 \
-numa node,nodeid=2,cpus=2 \
-numa node,nodeid=3,cpus=3 \
-numa dist,src=0,dst=1,val=21 \
-numa dist,src=0,dst=2,val=31 \
-numa dist,src=0,dst=3,val=41 \
-numa dist,src=1,dst=2,val=21 \
-numa dist,src=1,dst=3,val=31 \
-numa dist,src=2,dst=3,val=21 \
```
Signed-off-by: He Chen <he.chen@linux.intel.com>
Message-Id: <1493260558-20728-1-git-send-email-he.chen@linux.intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-04-27 04:35:58 +02:00
|
|
|
@itemx -numa dist,src=@var{source},dst=@var{destination},val=@var{distance}
|
numa: add '-numa cpu,...' option for property based node mapping
legacy cpu to node mapping is using cpu index values to map
VCPU to node with help of '-numa node,nodeid=node,cpus=x[-y]'
option. However cpu index is internal concept and QEMU users
have to guess /reimplement qemu's logic/ to map it to
a concrete cpu socket/core/thread to make sane CPUs
placement across numa nodes.
This patch allows to map cpu objects to numa nodes using
the same properties as used for cpus with -device/device_add
(socket-id/core-id/thread-id/node-id).
At present valid properties/values to address CPUs could be
fetched using hotpluggable-cpus monitor/qmp command, it will
require user to start qemu twice when creating domain to fetch
possible CPUs for a machine type/-smp layout first and
then the second time with numa explicit mapping for actual
usage. The first step results could be saved and reused to
set/change mapping later as far as machine type/-smp stays
the same.
Proposed impl. supports exact and wildcard matching to
simplify CLI and allow to set mapping for a specific cpu
or group of cpu objects specified by matched properties.
For example:
# exact mapping x86
-numa cpu,node-id=x,socket-id=y,core-id=z,thread-id=n
# exact mapping SPAPR
-numa cpu,node-id=x,core-id=y
# wildcard mapping, all cpu objects that match socket-id=y
# are mapped to node-id=x
-numa cpu,node-id=x,socket-id=y
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <1494415802-227633-18-git-send-email-imammedo@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-05-10 13:30:01 +02:00
|
|
|
@itemx -numa cpu,node-id=@var{node}[,socket-id=@var{x}][,core-id=@var{y}][,thread-id=@var{z}]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -numa
|
2017-01-23 19:06:32 +01:00
|
|
|
Define a NUMA node and assign RAM and VCPUs to it.
|
numa: Allow setting NUMA distance for different NUMA nodes
This patch is going to add SLIT table support in QEMU, and provides
additional option `dist` for command `-numa` to allow user set vNUMA
distance by QEMU command.
With this patch, when a user wants to create a guest that contains
several vNUMA nodes and also wants to set distance among those nodes,
the QEMU command would like:
```
-numa node,nodeid=0,cpus=0 \
-numa node,nodeid=1,cpus=1 \
-numa node,nodeid=2,cpus=2 \
-numa node,nodeid=3,cpus=3 \
-numa dist,src=0,dst=1,val=21 \
-numa dist,src=0,dst=2,val=31 \
-numa dist,src=0,dst=3,val=41 \
-numa dist,src=1,dst=2,val=21 \
-numa dist,src=1,dst=3,val=31 \
-numa dist,src=2,dst=3,val=21 \
```
Signed-off-by: He Chen <he.chen@linux.intel.com>
Message-Id: <1493260558-20728-1-git-send-email-he.chen@linux.intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-04-27 04:35:58 +02:00
|
|
|
Set the NUMA distance from a source node to a destination node.
|
2017-01-23 19:06:32 +01:00
|
|
|
|
numa: add '-numa cpu,...' option for property based node mapping
legacy cpu to node mapping is using cpu index values to map
VCPU to node with help of '-numa node,nodeid=node,cpus=x[-y]'
option. However cpu index is internal concept and QEMU users
have to guess /reimplement qemu's logic/ to map it to
a concrete cpu socket/core/thread to make sane CPUs
placement across numa nodes.
This patch allows to map cpu objects to numa nodes using
the same properties as used for cpus with -device/device_add
(socket-id/core-id/thread-id/node-id).
At present valid properties/values to address CPUs could be
fetched using hotpluggable-cpus monitor/qmp command, it will
require user to start qemu twice when creating domain to fetch
possible CPUs for a machine type/-smp layout first and
then the second time with numa explicit mapping for actual
usage. The first step results could be saved and reused to
set/change mapping later as far as machine type/-smp stays
the same.
Proposed impl. supports exact and wildcard matching to
simplify CLI and allow to set mapping for a specific cpu
or group of cpu objects specified by matched properties.
For example:
# exact mapping x86
-numa cpu,node-id=x,socket-id=y,core-id=z,thread-id=n
# exact mapping SPAPR
-numa cpu,node-id=x,core-id=y
# wildcard mapping, all cpu objects that match socket-id=y
# are mapped to node-id=x
-numa cpu,node-id=x,socket-id=y
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <1494415802-227633-18-git-send-email-imammedo@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-05-10 13:30:01 +02:00
|
|
|
Legacy VCPU assignment uses @samp{cpus} option where
|
2017-01-23 19:06:32 +01:00
|
|
|
@var{firstcpu} and @var{lastcpu} are CPU indexes. Each
|
|
|
|
@samp{cpus} option represent a contiguous range of CPU indexes
|
|
|
|
(or a single VCPU if @var{lastcpu} is omitted). A non-contiguous
|
|
|
|
set of VCPUs can be represented by providing multiple @samp{cpus}
|
|
|
|
options. If @samp{cpus} is omitted on all nodes, VCPUs are automatically
|
|
|
|
split between them.
|
|
|
|
|
|
|
|
For example, the following option assigns VCPUs 0, 1, 2 and 5 to
|
|
|
|
a NUMA node:
|
|
|
|
@example
|
|
|
|
-numa node,cpus=0-2,cpus=5
|
|
|
|
@end example
|
|
|
|
|
numa: add '-numa cpu,...' option for property based node mapping
legacy cpu to node mapping is using cpu index values to map
VCPU to node with help of '-numa node,nodeid=node,cpus=x[-y]'
option. However cpu index is internal concept and QEMU users
have to guess /reimplement qemu's logic/ to map it to
a concrete cpu socket/core/thread to make sane CPUs
placement across numa nodes.
This patch allows to map cpu objects to numa nodes using
the same properties as used for cpus with -device/device_add
(socket-id/core-id/thread-id/node-id).
At present valid properties/values to address CPUs could be
fetched using hotpluggable-cpus monitor/qmp command, it will
require user to start qemu twice when creating domain to fetch
possible CPUs for a machine type/-smp layout first and
then the second time with numa explicit mapping for actual
usage. The first step results could be saved and reused to
set/change mapping later as far as machine type/-smp stays
the same.
Proposed impl. supports exact and wildcard matching to
simplify CLI and allow to set mapping for a specific cpu
or group of cpu objects specified by matched properties.
For example:
# exact mapping x86
-numa cpu,node-id=x,socket-id=y,core-id=z,thread-id=n
# exact mapping SPAPR
-numa cpu,node-id=x,core-id=y
# wildcard mapping, all cpu objects that match socket-id=y
# are mapped to node-id=x
-numa cpu,node-id=x,socket-id=y
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <1494415802-227633-18-git-send-email-imammedo@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-05-10 13:30:01 +02:00
|
|
|
@samp{cpu} option is a new alternative to @samp{cpus} option
|
|
|
|
which uses @samp{socket-id|core-id|thread-id} properties to assign
|
|
|
|
CPU objects to a @var{node} using topology layout properties of CPU.
|
|
|
|
The set of properties is machine specific, and depends on used
|
|
|
|
machine type/@samp{smp} options. It could be queried with
|
|
|
|
@samp{hotpluggable-cpus} monitor command.
|
|
|
|
@samp{node-id} property specifies @var{node} to which CPU object
|
|
|
|
will be assigned, it's required for @var{node} to be declared
|
|
|
|
with @samp{node} option before it's used with @samp{cpu} option.
|
|
|
|
|
|
|
|
For example:
|
|
|
|
@example
|
|
|
|
-M pc \
|
|
|
|
-smp 1,sockets=2,maxcpus=2 \
|
|
|
|
-numa node,nodeid=0 -numa node,nodeid=1 \
|
|
|
|
-numa cpu,node-id=0,socket-id=0 -numa cpu,node-id=1,socket-id=1
|
|
|
|
@end example
|
|
|
|
|
2017-01-23 19:06:32 +01:00
|
|
|
@samp{mem} assigns a given RAM amount to a node. @samp{memdev}
|
|
|
|
assigns RAM from a given memory backend device to a node. If
|
|
|
|
@samp{mem} and @samp{memdev} are omitted in all nodes, RAM is
|
|
|
|
split equally between them.
|
|
|
|
|
|
|
|
@samp{mem} and @samp{memdev} are mutually exclusive. Furthermore,
|
|
|
|
if one node uses @samp{memdev}, all of them have to use it.
|
|
|
|
|
numa: Allow setting NUMA distance for different NUMA nodes
This patch is going to add SLIT table support in QEMU, and provides
additional option `dist` for command `-numa` to allow user set vNUMA
distance by QEMU command.
With this patch, when a user wants to create a guest that contains
several vNUMA nodes and also wants to set distance among those nodes,
the QEMU command would like:
```
-numa node,nodeid=0,cpus=0 \
-numa node,nodeid=1,cpus=1 \
-numa node,nodeid=2,cpus=2 \
-numa node,nodeid=3,cpus=3 \
-numa dist,src=0,dst=1,val=21 \
-numa dist,src=0,dst=2,val=31 \
-numa dist,src=0,dst=3,val=41 \
-numa dist,src=1,dst=2,val=21 \
-numa dist,src=1,dst=3,val=31 \
-numa dist,src=2,dst=3,val=21 \
```
Signed-off-by: He Chen <he.chen@linux.intel.com>
Message-Id: <1493260558-20728-1-git-send-email-he.chen@linux.intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-04-27 04:35:58 +02:00
|
|
|
@var{source} and @var{destination} are NUMA node IDs.
|
|
|
|
@var{distance} is the NUMA distance from @var{source} to @var{destination}.
|
|
|
|
The distance from a node to itself is always 10. If any pair of nodes is
|
|
|
|
given a distance, then all pairs must be given distances. Although, when
|
|
|
|
distances are only given in one direction for each pair of nodes, then
|
|
|
|
the distances in the opposite directions are assumed to be the same. If,
|
|
|
|
however, an asymmetrical pair of distances is given for even one node
|
|
|
|
pair, then all node pairs must be provided distance values for both
|
|
|
|
directions, even when they are symmetrical. When a node is unreachable
|
|
|
|
from another node, set the pair's distance to 255.
|
|
|
|
|
2017-01-23 19:06:32 +01:00
|
|
|
Note that the -@option{numa} option doesn't allocate any of the
|
|
|
|
specified resources, it just assigns existing resources to NUMA
|
|
|
|
nodes. This means that one still has to use the @option{-m},
|
|
|
|
@option{-smp} options to allocate RAM and VCPUs respectively.
|
|
|
|
|
2009-04-22 00:30:27 +02:00
|
|
|
ETEXI
|
|
|
|
|
2012-10-18 21:19:34 +02:00
|
|
|
DEF("add-fd", HAS_ARG, QEMU_OPTION_add_fd,
|
|
|
|
"-add-fd fd=fd,set=set[,opaque=opaque]\n"
|
|
|
|
" Add 'fd' to fd 'set'\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -add-fd fd=@var{fd},set=@var{set}[,opaque=@var{opaque}]
|
|
|
|
@findex -add-fd
|
|
|
|
|
|
|
|
Add a file descriptor to an fd set. Valid options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item fd=@var{fd}
|
|
|
|
This option defines the file descriptor of which a duplicate is added to fd set.
|
|
|
|
The file descriptor cannot be stdin, stdout, or stderr.
|
|
|
|
@item set=@var{set}
|
|
|
|
This option defines the ID of the fd set to add the file descriptor to.
|
|
|
|
@item opaque=@var{opaque}
|
|
|
|
This option defines a free-form string that can be used to describe @var{fd}.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
You can open an image using pre-opened file descriptors from an fd set:
|
|
|
|
@example
|
|
|
|
qemu-system-i386
|
|
|
|
-add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
|
|
|
|
-add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
|
|
|
|
-drive file=/dev/fdset/2,index=0,media=disk
|
|
|
|
@end example
|
|
|
|
ETEXI
|
|
|
|
|
2010-02-05 23:52:05 +01:00
|
|
|
DEF("set", HAS_ARG, QEMU_OPTION_set,
|
|
|
|
"-set group.id.arg=value\n"
|
|
|
|
" set <arg> parameter for item <id> of type <group>\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" i.e. -set drive.$id.file=/path/to/image\n", QEMU_ARCH_ALL)
|
2010-02-05 23:52:05 +01:00
|
|
|
STEXI
|
2013-02-13 19:49:39 +01:00
|
|
|
@item -set @var{group}.@var{id}.@var{arg}=@var{value}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -set
|
2016-10-16 16:21:37 +02:00
|
|
|
Set parameter @var{arg} for item @var{id} of type @var{group}
|
2010-02-05 23:52:05 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("global", HAS_ARG, QEMU_OPTION_global,
|
2015-04-09 14:16:19 +02:00
|
|
|
"-global driver.property=value\n"
|
|
|
|
"-global driver=driver,property=property,value=value\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" set a global default for a driver property\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-02-05 23:52:05 +01:00
|
|
|
STEXI
|
2012-03-21 13:46:54 +01:00
|
|
|
@item -global @var{driver}.@var{prop}=@var{value}
|
2015-04-09 14:16:19 +02:00
|
|
|
@itemx -global driver=@var{driver},property=@var{property},value=@var{value}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -global
|
2012-03-21 13:46:54 +01:00
|
|
|
Set default value of @var{driver}'s property @var{prop} to @var{value}, e.g.:
|
|
|
|
|
|
|
|
@example
|
2017-05-09 11:41:15 +02:00
|
|
|
qemu-system-i386 -global ide-hd.physical_block_size=4096 disk-image.img
|
2012-03-21 13:46:54 +01:00
|
|
|
@end example
|
|
|
|
|
2017-09-23 18:31:59 +02:00
|
|
|
In particular, you can use this to set driver properties for devices which are
|
|
|
|
created automatically by the machine model. To create a device which is not
|
2012-03-21 13:46:54 +01:00
|
|
|
created automatically and set properties on it, use -@option{device}.
|
2015-04-09 14:16:19 +02:00
|
|
|
|
2015-06-15 14:35:58 +02:00
|
|
|
-global @var{driver}.@var{prop}=@var{value} is shorthand for -global
|
|
|
|
driver=@var{driver},property=@var{prop},value=@var{value}. The
|
|
|
|
longhand syntax works even when @var{driver} contains a dot.
|
2010-02-05 23:52:05 +01:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("boot", HAS_ARG, QEMU_OPTION_boot,
|
2009-07-02 00:19:02 +02:00
|
|
|
"-boot [order=drives][,once=drives][,menu=on|off]\n"
|
2013-03-19 07:23:27 +01:00
|
|
|
" [,splash=sp_name][,splash-time=sp_time][,reboot-timeout=rb_time][,strict=on|off]\n"
|
2011-07-27 12:04:55 +02:00
|
|
|
" 'drives': floppy (a), hard disk (c), CD-ROM (d), network (n)\n"
|
|
|
|
" 'sp_name': the file's name that would be passed to bios as logo picture, if menu=on\n"
|
add a boot parameter to set reboot timeout
Added an option to let qemu transfer a configuration file to bios,
"etc/boot-fail-wait", which could be specified by command
-boot reboot-timeout=T
T have a max value of 0xffff, unit is ms.
With this option, guest will wait for a given time if not find
bootabled device, then reboot. If reboot-timeout is '-1', guest
will not reboot, qemu passes '-1' to bios by default.
This feature need the new seabios's support.
Seabios pulls the value from the fwcfg "file" interface, this
interface is used because SeaBIOS needs a reliable way of
obtaining a name, value size, and value. It in no way requires
that there be a real file on the user's host machine.
Signed-off-by: Amos Kong <akong@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-09-07 05:11:03 +02:00
|
|
|
" 'sp_time': the period that splash picture last if menu=on, unit is ms\n"
|
|
|
|
" 'rb_timeout': the timeout before guest reboot when boot failed, unit is ms\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2013-03-19 07:23:27 +01:00
|
|
|
@item -boot [order=@var{drives}][,once=@var{drives}][,menu=on|off][,splash=@var{sp_name}][,splash-time=@var{sp_time}][,reboot-timeout=@var{rb_timeout}][,strict=on|off]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -boot
|
2009-07-02 00:19:02 +02:00
|
|
|
Specify boot order @var{drives} as a string of drive letters. Valid
|
2015-07-03 11:50:57 +02:00
|
|
|
drive letters depend on the target architecture. The x86 PC uses: a, b
|
2009-07-02 00:19:02 +02:00
|
|
|
(floppy 1 and 2), c (first hard disk), d (first CD-ROM), n-p (Etherboot
|
|
|
|
from network adapter 1-4), hard disk boot is the default. To apply a
|
|
|
|
particular boot order only on the first startup, specify it via
|
2017-02-28 18:40:01 +01:00
|
|
|
@option{once}. Note that the @option{order} or @option{once} parameter
|
|
|
|
should not be used together with the @option{bootindex} property of
|
|
|
|
devices, since the firmware implementations normally do not support both
|
|
|
|
at the same time.
|
2009-07-02 00:19:02 +02:00
|
|
|
|
|
|
|
Interactive boot menus/prompts can be enabled via @option{menu=on} as far
|
|
|
|
as firmware/BIOS supports them. The default is non-interactive boot.
|
|
|
|
|
2011-07-27 12:04:55 +02:00
|
|
|
A splash picture could be passed to bios, enabling user to show it as logo,
|
|
|
|
when option splash=@var{sp_name} is given and menu=on, If firmware/BIOS
|
|
|
|
supports them. Currently Seabios for X86 system support it.
|
|
|
|
limitation: The splash file could be a jpeg file or a BMP file in 24 BPP
|
|
|
|
format(true color). The resolution should be supported by the SVGA mode, so
|
|
|
|
the recommended is 320x240, 640x480, 800x640.
|
|
|
|
|
add a boot parameter to set reboot timeout
Added an option to let qemu transfer a configuration file to bios,
"etc/boot-fail-wait", which could be specified by command
-boot reboot-timeout=T
T have a max value of 0xffff, unit is ms.
With this option, guest will wait for a given time if not find
bootabled device, then reboot. If reboot-timeout is '-1', guest
will not reboot, qemu passes '-1' to bios by default.
This feature need the new seabios's support.
Seabios pulls the value from the fwcfg "file" interface, this
interface is used because SeaBIOS needs a reliable way of
obtaining a name, value size, and value. It in no way requires
that there be a real file on the user's host machine.
Signed-off-by: Amos Kong <akong@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-09-07 05:11:03 +02:00
|
|
|
A timeout could be passed to bios, guest will pause for @var{rb_timeout} ms
|
|
|
|
when boot failed, then reboot. If @var{rb_timeout} is '-1', guest will not
|
|
|
|
reboot, qemu passes '-1' to bios by default. Currently Seabios for X86
|
|
|
|
system support it.
|
|
|
|
|
2013-03-19 07:23:27 +01:00
|
|
|
Do strict boot via @option{strict=on} as far as firmware/BIOS
|
|
|
|
supports it. This only effects when boot priority is changed by
|
|
|
|
bootindex options. The default is non-strict boot.
|
|
|
|
|
2009-07-02 00:19:02 +02:00
|
|
|
@example
|
|
|
|
# try to boot from network first, then from hard disk
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 -boot order=nc
|
2009-07-02 00:19:02 +02:00
|
|
|
# boot from CD-ROM first, switch back to default order after reboot
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 -boot once=d
|
2011-07-27 12:04:55 +02:00
|
|
|
# boot with a splash picture for 5 seconds.
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 -boot menu=on,splash=/root/boot.bmp,splash-time=5000
|
2009-07-02 00:19:02 +02:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Note: The legacy format '-boot @var{drives}' is still supported but its
|
|
|
|
use is discouraged as it may be removed from future versions.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("m", HAS_ARG, QEMU_OPTION_m,
|
2016-11-10 15:51:32 +01:00
|
|
|
"-m [size=]megs[,slots=n,maxmem=size]\n"
|
2013-11-27 01:27:35 +01:00
|
|
|
" configure guest RAM\n"
|
2015-06-05 11:05:03 +02:00
|
|
|
" size: initial amount of guest memory\n"
|
2014-06-02 15:25:02 +02:00
|
|
|
" slots: number of hotplug slots (default: none)\n"
|
2014-08-28 17:25:33 +02:00
|
|
|
" maxmem: maximum amount of guest memory (default: none)\n"
|
|
|
|
"NOTE: Some architectures might enforce a specific granularity\n",
|
2013-11-27 01:27:35 +01:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2015-02-26 20:35:45 +01:00
|
|
|
@item -m [size=]@var{megs}[,slots=n,maxmem=size]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -m
|
2015-02-26 20:35:45 +01:00
|
|
|
Sets guest startup RAM size to @var{megs} megabytes. Default is 128 MiB.
|
|
|
|
Optionally, a suffix of ``M'' or ``G'' can be used to signify a value in
|
|
|
|
megabytes or gigabytes respectively. Optional pair @var{slots}, @var{maxmem}
|
|
|
|
could be used to set amount of hotpluggable memory slots and maximum amount of
|
|
|
|
memory. Note that @var{maxmem} must be aligned to the page size.
|
|
|
|
|
|
|
|
For example, the following command-line sets the guest startup RAM size to
|
|
|
|
1GB, creates 3 slots to hotplug additional memory and sets the maximum
|
|
|
|
memory the guest can reach to 4GB:
|
|
|
|
|
|
|
|
@example
|
|
|
|
qemu-system-x86_64 -m 1G,slots=3,maxmem=4G
|
|
|
|
@end example
|
|
|
|
|
|
|
|
If @var{slots} and @var{maxmem} are not specified, memory hotplug won't
|
|
|
|
be enabled and the guest startup RAM will never increase.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2010-03-02 00:25:08 +01:00
|
|
|
DEF("mem-path", HAS_ARG, QEMU_OPTION_mempath,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-mem-path FILE provide backing storage for guest RAM\n", QEMU_ARCH_ALL)
|
2010-03-02 00:25:08 +01:00
|
|
|
STEXI
|
|
|
|
@item -mem-path @var{path}
|
2013-02-13 19:49:38 +01:00
|
|
|
@findex -mem-path
|
2010-03-02 00:25:08 +01:00
|
|
|
Allocate guest RAM from a temporarily created file in @var{path}.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("mem-prealloc", 0, QEMU_OPTION_mem_prealloc,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-mem-prealloc preallocate guest memory (use with -mem-path)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-03-02 00:25:08 +01:00
|
|
|
STEXI
|
|
|
|
@item -mem-prealloc
|
2013-02-13 19:49:38 +01:00
|
|
|
@findex -mem-prealloc
|
2010-03-02 00:25:08 +01:00
|
|
|
Preallocate memory when using -mem-path.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("k", HAS_ARG, QEMU_OPTION_k,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-k language use keyboard layout (for example 'fr' for French)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -k @var{language}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -k
|
2009-03-28 07:44:27 +01:00
|
|
|
Use keyboard layout @var{language} (for example @code{fr} for
|
|
|
|
French). This option is only needed where it is not easy to get raw PC
|
2016-06-22 17:48:31 +02:00
|
|
|
keycodes (e.g. on Macs, with some X11 servers or with a VNC or curses
|
2009-03-28 07:44:27 +01:00
|
|
|
display). You don't normally need to use it on PC/Linux or PC/Windows
|
|
|
|
hosts.
|
|
|
|
|
|
|
|
The available layouts are:
|
|
|
|
@example
|
|
|
|
ar de-ch es fo fr-ca hu ja mk no pt-br sv
|
|
|
|
da en-gb et fr fr-ch is lt nl pl ru th
|
|
|
|
de en-us fi fr-be hr it lv nl-be pt sl tr
|
|
|
|
@end example
|
|
|
|
|
|
|
|
The default is @code{en-us}.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
|
2019-03-08 23:34:14 +01:00
|
|
|
HXCOMM Deprecated by -audiodev
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("audio-help", 0, QEMU_OPTION_audio_help,
|
2019-03-08 23:34:14 +01:00
|
|
|
"-audio-help show -audiodev equivalent of the currently specified audio settings\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -audio-help
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -audio-help
|
2019-03-08 23:34:14 +01:00
|
|
|
Will show the -audiodev equivalent of the currently specified
|
|
|
|
(deprecated) environment variables.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("audiodev", HAS_ARG, QEMU_OPTION_audiodev,
|
|
|
|
"-audiodev [driver=]driver,id=id[,prop[=value][,...]]\n"
|
|
|
|
" specifies the audio backend to use\n"
|
|
|
|
" id= identifier of the backend\n"
|
|
|
|
" timer-period= timer period in microseconds\n"
|
|
|
|
" in|out.fixed-settings= use fixed settings for host audio\n"
|
|
|
|
" in|out.frequency= frequency to use with fixed settings\n"
|
|
|
|
" in|out.channels= number of channels to use with fixed settings\n"
|
|
|
|
" in|out.format= sample format to use with fixed settings\n"
|
|
|
|
" valid values: s8, s16, s32, u8, u16, u32\n"
|
|
|
|
" in|out.voices= number of voices to use\n"
|
|
|
|
" in|out.buffer-len= length of buffer in microseconds\n"
|
|
|
|
"-audiodev none,id=id,[,prop[=value][,...]]\n"
|
|
|
|
" dummy driver that discards all output\n"
|
|
|
|
#ifdef CONFIG_AUDIO_ALSA
|
|
|
|
"-audiodev alsa,id=id[,prop[=value][,...]]\n"
|
|
|
|
" in|out.dev= name of the audio device to use\n"
|
|
|
|
" in|out.period-len= length of period in microseconds\n"
|
|
|
|
" in|out.try-poll= attempt to use poll mode\n"
|
|
|
|
" threshold= threshold (in microseconds) when playback starts\n"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_AUDIO_COREAUDIO
|
|
|
|
"-audiodev coreaudio,id=id[,prop[=value][,...]]\n"
|
|
|
|
" in|out.buffer-count= number of buffers\n"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_AUDIO_DSOUND
|
|
|
|
"-audiodev dsound,id=id[,prop[=value][,...]]\n"
|
|
|
|
" latency= add extra latency to playback in microseconds\n"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_AUDIO_OSS
|
|
|
|
"-audiodev oss,id=id[,prop[=value][,...]]\n"
|
|
|
|
" in|out.dev= path of the audio device to use\n"
|
|
|
|
" in|out.buffer-count= number of buffers\n"
|
|
|
|
" in|out.try-poll= attempt to use poll mode\n"
|
|
|
|
" try-mmap= try using memory mapped access\n"
|
|
|
|
" exclusive= open device in exclusive mode\n"
|
|
|
|
" dsp-policy= set timing policy (0..10), -1 to use fragment mode\n"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_AUDIO_PA
|
|
|
|
"-audiodev pa,id=id[,prop[=value][,...]]\n"
|
|
|
|
" server= PulseAudio server address\n"
|
|
|
|
" in|out.name= source/sink device name\n"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_AUDIO_SDL
|
|
|
|
"-audiodev sdl,id=id[,prop[=value][,...]]\n"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_SPICE
|
|
|
|
"-audiodev spice,id=id[,prop[=value][,...]]\n"
|
|
|
|
#endif
|
|
|
|
"-audiodev wav,id=id[,prop[=value][,...]]\n"
|
|
|
|
" path= path of wav file to record\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -audiodev [driver=]@var{driver},id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
@findex -audiodev
|
|
|
|
Adds a new audio backend @var{driver} identified by @var{id}. There are
|
|
|
|
global and driver specific properties. Some values can be set
|
|
|
|
differently for input and output, they're marked with @code{in|out.}.
|
|
|
|
You can set the input's property with @code{in.@var{prop}} and the
|
|
|
|
output's property with @code{out.@var{prop}}. For example:
|
|
|
|
@example
|
|
|
|
-audiodev alsa,id=example,in.frequency=44110,out.frequency=8000
|
|
|
|
-audiodev alsa,id=example,out.channels=1 # leaves in.channels unspecified
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Valid global options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item id=@var{identifier}
|
|
|
|
Identifies the audio backend.
|
|
|
|
|
|
|
|
@item timer-period=@var{period}
|
|
|
|
Sets the timer @var{period} used by the audio subsystem in microseconds.
|
|
|
|
Default is 10000 (10 ms).
|
|
|
|
|
|
|
|
@item in|out.fixed-settings=on|off
|
|
|
|
Use fixed settings for host audio. When off, it will change based on
|
|
|
|
how the guest opens the sound card. In this case you must not specify
|
|
|
|
@var{frequency}, @var{channels} or @var{format}. Default is on.
|
|
|
|
|
|
|
|
@item in|out.frequency=@var{frequency}
|
|
|
|
Specify the @var{frequency} to use when using @var{fixed-settings}.
|
|
|
|
Default is 44100Hz.
|
|
|
|
|
|
|
|
@item in|out.channels=@var{channels}
|
|
|
|
Specify the number of @var{channels} to use when using
|
|
|
|
@var{fixed-settings}. Default is 2 (stereo).
|
|
|
|
|
|
|
|
@item in|out.format=@var{format}
|
|
|
|
Specify the sample @var{format} to use when using @var{fixed-settings}.
|
|
|
|
Valid values are: @code{s8}, @code{s16}, @code{s32}, @code{u8},
|
|
|
|
@code{u16}, @code{u32}. Default is @code{s16}.
|
|
|
|
|
|
|
|
@item in|out.voices=@var{voices}
|
|
|
|
Specify the number of @var{voices} to use. Default is 1.
|
|
|
|
|
|
|
|
@item in|out.buffer=@var{usecs}
|
|
|
|
Sets the size of the buffer in microseconds.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -audiodev none,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a dummy backend that discards all outputs. This backend has no
|
|
|
|
backend specific properties.
|
|
|
|
|
|
|
|
@item -audiodev alsa,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates backend using the ALSA. This backend is only available on
|
|
|
|
Linux.
|
|
|
|
|
|
|
|
ALSA specific options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item in|out.dev=@var{device}
|
|
|
|
Specify the ALSA @var{device} to use for input and/or output. Default
|
|
|
|
is @code{default}.
|
|
|
|
|
|
|
|
@item in|out.period-len=@var{usecs}
|
|
|
|
Sets the period length in microseconds.
|
|
|
|
|
|
|
|
@item in|out.try-poll=on|off
|
|
|
|
Attempt to use poll mode with the device. Default is on.
|
|
|
|
|
|
|
|
@item threshold=@var{threshold}
|
|
|
|
Threshold (in microseconds) when playback starts. Default is 0.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -audiodev coreaudio,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend using Apple's Core Audio. This backend is only
|
|
|
|
available on Mac OS and only supports playback.
|
|
|
|
|
|
|
|
Core Audio specific options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item in|out.buffer-count=@var{count}
|
|
|
|
Sets the @var{count} of the buffers.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -audiodev dsound,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend using Microsoft's DirectSound. This backend is only
|
|
|
|
available on Windows and only supports playback.
|
|
|
|
|
|
|
|
DirectSound specific options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item latency=@var{usecs}
|
|
|
|
Add extra @var{usecs} microseconds latency to playback. Default is
|
|
|
|
10000 (10 ms).
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -audiodev oss,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend using OSS. This backend is available on most
|
|
|
|
Unix-like systems.
|
|
|
|
|
|
|
|
OSS specific options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item in|out.dev=@var{device}
|
|
|
|
Specify the file name of the OSS @var{device} to use. Default is
|
|
|
|
@code{/dev/dsp}.
|
|
|
|
|
|
|
|
@item in|out.buffer-count=@var{count}
|
|
|
|
Sets the @var{count} of the buffers.
|
|
|
|
|
|
|
|
@item in|out.try-poll=on|of
|
|
|
|
Attempt to use poll mode with the device. Default is on.
|
|
|
|
|
|
|
|
@item try-mmap=on|off
|
|
|
|
Try using memory mapped device access. Default is off.
|
|
|
|
|
|
|
|
@item exclusive=on|off
|
|
|
|
Open the device in exclusive mode (vmix won't work in this case).
|
|
|
|
Default is off.
|
|
|
|
|
|
|
|
@item dsp-policy=@var{policy}
|
|
|
|
Sets the timing policy (between 0 and 10, where smaller number means
|
|
|
|
smaller latency but higher CPU usage). Use -1 to use buffer sizes
|
|
|
|
specified by @code{buffer} and @code{buffer-count}. This option is
|
|
|
|
ignored if you do not have OSS 4. Default is 5.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -audiodev pa,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend using PulseAudio. This backend is available on most
|
|
|
|
systems.
|
|
|
|
|
|
|
|
PulseAudio specific options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item server=@var{server}
|
|
|
|
Sets the PulseAudio @var{server} to connect to.
|
|
|
|
|
|
|
|
@item in|out.name=@var{sink}
|
|
|
|
Use the specified source/sink for recording/playback.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -audiodev sdl,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend using SDL. This backend is available on most systems,
|
|
|
|
but you should use your platform's native backend if possible. This
|
|
|
|
backend has no backend specific properties.
|
|
|
|
|
|
|
|
@item -audiodev spice,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend that sends audio through SPICE. This backend requires
|
|
|
|
@code{-spice} and automatically selected in that case, so usually you
|
|
|
|
can ignore this option. This backend has no backend specific
|
|
|
|
properties.
|
|
|
|
|
|
|
|
@item -audiodev wav,id=@var{id}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
Creates a backend that writes audio to a WAV file.
|
|
|
|
|
|
|
|
Backend specific options are:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item path=@var{path}
|
|
|
|
Write recorded audio into the specified file. Default is
|
|
|
|
@code{qemu.wav}.
|
|
|
|
|
|
|
|
@end table
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("soundhw", HAS_ARG, QEMU_OPTION_soundhw,
|
|
|
|
"-soundhw c1,... enable audio support\n"
|
|
|
|
" and only specified sound cards (comma separated list)\n"
|
2012-10-04 17:22:01 +02:00
|
|
|
" use '-soundhw help' to get the list of supported cards\n"
|
|
|
|
" use '-soundhw all' to enable all of them\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -soundhw @var{card1}[,@var{card2},...] or -soundhw all
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -soundhw
|
2012-10-04 17:22:01 +02:00
|
|
|
Enable audio and selected sound hardware. Use 'help' to print all
|
2009-03-28 07:44:27 +01:00
|
|
|
available sound hardware.
|
|
|
|
|
|
|
|
@example
|
2013-02-13 19:49:43 +01:00
|
|
|
qemu-system-i386 -soundhw sb16,adlib disk.img
|
|
|
|
qemu-system-i386 -soundhw es1370 disk.img
|
|
|
|
qemu-system-i386 -soundhw ac97 disk.img
|
|
|
|
qemu-system-i386 -soundhw hda disk.img
|
|
|
|
qemu-system-i386 -soundhw all disk.img
|
|
|
|
qemu-system-i386 -soundhw help
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Note that Linux's i810_audio OSS kernel (for AC97) module might
|
|
|
|
require manually specifying clocking.
|
|
|
|
|
|
|
|
@example
|
|
|
|
modprobe i810_audio clocking=48000
|
|
|
|
@end example
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("device", HAS_ARG, QEMU_OPTION_device,
|
|
|
|
"-device driver[,prop[=value][,...]]\n"
|
|
|
|
" add device (based on driver)\n"
|
|
|
|
" prop=value,... sets driver properties\n"
|
|
|
|
" use '-device help' to print all possible drivers\n"
|
|
|
|
" use '-device driver,help' to print all possible properties\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -device @var{driver}[,@var{prop}[=@var{value}][,...]]
|
|
|
|
@findex -device
|
|
|
|
Add device @var{driver}. @var{prop}=@var{value} sets driver
|
|
|
|
properties. Valid properties depend on the driver. To get help on
|
|
|
|
possible drivers and properties, use @code{-device help} and
|
|
|
|
@code{-device @var{driver},help}.
|
2015-12-17 19:50:10 +01:00
|
|
|
|
|
|
|
Some drivers are:
|
2017-04-05 14:41:32 +02:00
|
|
|
@item -device ipmi-bmc-sim,id=@var{id}[,slave_addr=@var{val}][,sdrfile=@var{file}][,furareasize=@var{val}][,furdatafile=@var{file}]
|
2015-12-17 19:50:10 +01:00
|
|
|
|
|
|
|
Add an IPMI BMC. This is a simulation of a hardware management
|
|
|
|
interface processor that normally sits on a system. It provides
|
|
|
|
a watchdog and the ability to reset and power control the system.
|
|
|
|
You need to connect this to an IPMI interface to make it useful
|
|
|
|
|
|
|
|
The IPMI slave address to use for the BMC. The default is 0x20.
|
|
|
|
This address is the BMC's address on the I2C network of management
|
|
|
|
controllers. If you don't know what this means, it is safe to ignore
|
|
|
|
it.
|
|
|
|
|
2017-04-05 14:41:31 +02:00
|
|
|
@table @option
|
|
|
|
@item bmc=@var{id}
|
|
|
|
The BMC to connect to, one of ipmi-bmc-sim or ipmi-bmc-extern above.
|
|
|
|
@item slave_addr=@var{val}
|
|
|
|
Define slave address to use for the BMC. The default is 0x20.
|
|
|
|
@item sdrfile=@var{file}
|
2017-04-05 14:41:32 +02:00
|
|
|
file containing raw Sensor Data Records (SDR) data. The default is none.
|
|
|
|
@item fruareasize=@var{val}
|
|
|
|
size of a Field Replaceable Unit (FRU) area. The default is 1024.
|
|
|
|
@item frudatafile=@var{file}
|
|
|
|
file containing raw Field Replaceable Unit (FRU) inventory data. The default is none.
|
2017-04-05 14:41:31 +02:00
|
|
|
@end table
|
|
|
|
|
2015-12-17 19:50:10 +01:00
|
|
|
@item -device ipmi-bmc-extern,id=@var{id},chardev=@var{id}[,slave_addr=@var{val}]
|
|
|
|
|
|
|
|
Add a connection to an external IPMI BMC simulator. Instead of
|
|
|
|
locally emulating the BMC like the above item, instead connect
|
|
|
|
to an external entity that provides the IPMI services.
|
|
|
|
|
|
|
|
A connection is made to an external BMC simulator. If you do this, it
|
|
|
|
is strongly recommended that you use the "reconnect=" chardev option
|
|
|
|
to reconnect to the simulator if the connection is lost. Note that if
|
|
|
|
this is not used carefully, it can be a security issue, as the
|
|
|
|
interface has the ability to send resets, NMIs, and power off the VM.
|
|
|
|
It's best if QEMU makes a connection to an external simulator running
|
|
|
|
on a secure port on localhost, so neither the simulator nor QEMU is
|
|
|
|
exposed to any outside network.
|
|
|
|
|
|
|
|
See the "lanserv/README.vm" file in the OpenIPMI library for more
|
|
|
|
details on the external interface.
|
|
|
|
|
|
|
|
@item -device isa-ipmi-kcs,bmc=@var{id}[,ioport=@var{val}][,irq=@var{val}]
|
|
|
|
|
|
|
|
Add a KCS IPMI interafce on the ISA bus. This also adds a
|
|
|
|
corresponding ACPI and SMBIOS entries, if appropriate.
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item bmc=@var{id}
|
|
|
|
The BMC to connect to, one of ipmi-bmc-sim or ipmi-bmc-extern above.
|
|
|
|
@item ioport=@var{val}
|
|
|
|
Define the I/O address of the interface. The default is 0xca0 for KCS.
|
|
|
|
@item irq=@var{val}
|
|
|
|
Define the interrupt to use. The default is 5. To disable interrupts,
|
|
|
|
set this to 0.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -device isa-ipmi-bt,bmc=@var{id}[,ioport=@var{val}][,irq=@var{val}]
|
|
|
|
|
|
|
|
Like the KCS interface, but defines a BT interface. The default port is
|
|
|
|
0xe4 and the default interrupt is 5.
|
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("name", HAS_ARG, QEMU_OPTION_name,
|
2014-01-30 11:20:31 +01:00
|
|
|
"-name string1[,process=string2][,debug-threads=on|off]\n"
|
2013-02-13 19:49:43 +01:00
|
|
|
" set the name of the guest\n"
|
2018-12-17 21:26:01 +01:00
|
|
|
" string1 sets the window title and string2 the process name\n"
|
|
|
|
" When debug-threads is enabled, individual threads are given a separate name\n"
|
2014-01-30 11:20:31 +01:00
|
|
|
" NOTE: The thread names are for debugging and not a stable API.\n",
|
2013-02-13 19:49:43 +01:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -name @var{name}
|
|
|
|
@findex -name
|
|
|
|
Sets the @var{name} of the guest.
|
|
|
|
This name will be displayed in the SDL window caption.
|
|
|
|
The @var{name} will also be used for the VNC server.
|
|
|
|
Also optionally set the top visible process name in Linux.
|
2014-01-30 11:20:31 +01:00
|
|
|
Naming of individual threads can also be enabled on Linux to aid debugging.
|
2013-02-13 19:49:43 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("uuid", HAS_ARG, QEMU_OPTION_uuid,
|
|
|
|
"-uuid %08x-%04x-%04x-%04x-%012x\n"
|
|
|
|
" specify machine UUID\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -uuid @var{uuid}
|
|
|
|
@findex -uuid
|
|
|
|
Set system UUID.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Block device options:)
|
2013-02-13 19:49:43 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("fda", HAS_ARG, QEMU_OPTION_fda,
|
|
|
|
"-fda/-fdb file use 'file' as floppy disk 0/1 image\n", QEMU_ARCH_ALL)
|
|
|
|
DEF("fdb", HAS_ARG, QEMU_OPTION_fdb, "", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -fda @var{file}
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx -fdb @var{file}
|
2013-02-13 19:49:43 +01:00
|
|
|
@findex -fda
|
|
|
|
@findex -fdb
|
2015-03-17 17:02:20 +01:00
|
|
|
Use @var{file} as floppy disk 0/1 image (@pxref{disk_images}).
|
2013-02-13 19:49:43 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("hda", HAS_ARG, QEMU_OPTION_hda,
|
|
|
|
"-hda/-hdb file use 'file' as IDE hard disk 0/1 image\n", QEMU_ARCH_ALL)
|
|
|
|
DEF("hdb", HAS_ARG, QEMU_OPTION_hdb, "", QEMU_ARCH_ALL)
|
|
|
|
DEF("hdc", HAS_ARG, QEMU_OPTION_hdc,
|
|
|
|
"-hdc/-hdd file use 'file' as IDE hard disk 2/3 image\n", QEMU_ARCH_ALL)
|
|
|
|
DEF("hdd", HAS_ARG, QEMU_OPTION_hdd, "", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -hda @var{file}
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx -hdb @var{file}
|
|
|
|
@itemx -hdc @var{file}
|
|
|
|
@itemx -hdd @var{file}
|
2013-02-13 19:49:43 +01:00
|
|
|
@findex -hda
|
|
|
|
@findex -hdb
|
|
|
|
@findex -hdc
|
|
|
|
@findex -hdd
|
|
|
|
Use @var{file} as hard disk 0, 1, 2 or 3 image (@pxref{disk_images}).
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("cdrom", HAS_ARG, QEMU_OPTION_cdrom,
|
|
|
|
"-cdrom file use 'file' as IDE cdrom image (cdrom is ide1 master)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -cdrom @var{file}
|
|
|
|
@findex -cdrom
|
|
|
|
Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and
|
|
|
|
@option{-cdrom} at the same time). You can use the host CD-ROM by
|
|
|
|
using @file{/dev/cdrom} as filename (@pxref{host_drives}).
|
|
|
|
ETEXI
|
|
|
|
|
block: Initial implementation of -blockdev
The new command line option -blockdev works like QMP command
blockdev-add.
The option argument may be given in JSON syntax, exactly as in QMP.
Example usage:
-blockdev '{"node-name": "foo", "driver": "raw", "file": {"driver": "file", "filename": "foo.img"} }'
The JSON argument doesn't exactly blend into the existing option
syntax, so the traditional KEY=VALUE,... syntax is also supported,
using dotted keys to do the nesting:
-blockdev node-name=foo,driver=raw,file.driver=file,file.filename=foo.img
This does not yet support lists, but that will be addressed shortly.
Note that calling qmp_blockdev_add() (say via qmp_marshal_block_add())
right away would crash. We need to stash the configuration for later
instead. This is crudely done, and bypasses QemuOpts, even though
storing configuration is what QemuOpts is for. Need to revamp option
infrastructure to support QAPI types like BlockdevOptions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <1488317230-26248-22-git-send-email-armbru@redhat.com>
2017-02-28 22:27:07 +01:00
|
|
|
DEF("blockdev", HAS_ARG, QEMU_OPTION_blockdev,
|
|
|
|
"-blockdev [driver=]driver[,node-name=N][,discard=ignore|unmap]\n"
|
|
|
|
" [,cache.direct=on|off][,cache.no-flush=on|off]\n"
|
|
|
|
" [,read-only=on|off][,detect-zeroes=on|off|unmap]\n"
|
|
|
|
" [,driver specific parameters...]\n"
|
|
|
|
" configure a block backend\n", QEMU_ARCH_ALL)
|
2016-09-22 16:53:24 +02:00
|
|
|
STEXI
|
|
|
|
@item -blockdev @var{option}[,@var{option}[,@var{option}[,...]]]
|
|
|
|
@findex -blockdev
|
|
|
|
|
2016-09-22 17:24:38 +02:00
|
|
|
Define a new block driver node. Some of the options apply to all block drivers,
|
|
|
|
other options are only accepted for a specific block driver. See below for a
|
|
|
|
list of generic options and options for the most common block drivers.
|
|
|
|
|
|
|
|
Options that expect a reference to another node (e.g. @code{file}) can be
|
|
|
|
given in two ways. Either you specify the node name of an already existing node
|
|
|
|
(file=@var{node-name}), or you define a new node inline, adding options
|
|
|
|
for the referenced node after a dot (file.filename=@var{path},file.aio=native).
|
|
|
|
|
|
|
|
A block driver node created with @option{-blockdev} can be used for a guest
|
|
|
|
device by specifying its node name for the @code{drive} property in a
|
|
|
|
@option{-device} argument that defines a block device.
|
2016-09-22 16:53:24 +02:00
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item Valid options for any block driver node:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item driver
|
|
|
|
Specifies the block driver to use for the given node.
|
|
|
|
@item node-name
|
|
|
|
This defines the name of the block driver node by which it will be referenced
|
|
|
|
later. The name must be unique, i.e. it must not match the name of a different
|
|
|
|
block driver node, or (if you use @option{-drive} as well) the ID of a drive.
|
|
|
|
|
|
|
|
If no node name is specified, it is automatically generated. The generated node
|
|
|
|
name is not intended to be predictable and changes between QEMU invocations.
|
|
|
|
For the top level, an explicit node name must be specified.
|
|
|
|
@item read-only
|
|
|
|
Open the node read-only. Guest write attempts will fail.
|
|
|
|
@item cache.direct
|
|
|
|
The host page cache can be avoided with @option{cache.direct=on}. This will
|
|
|
|
attempt to do disk IO directly to the guest's memory. QEMU may still perform an
|
|
|
|
internal copy of the data.
|
|
|
|
@item cache.no-flush
|
|
|
|
In case you don't care about data integrity over host failures, you can use
|
|
|
|
@option{cache.no-flush=on}. This option tells QEMU that it never needs to write
|
|
|
|
any data to the disk but can instead keep things in cache. If anything goes
|
|
|
|
wrong, like your host losing power, the disk storage getting disconnected
|
|
|
|
accidentally, etc. your image will most probably be rendered unusable.
|
|
|
|
@item discard=@var{discard}
|
|
|
|
@var{discard} is one of "ignore" (or "off") or "unmap" (or "on") and controls
|
|
|
|
whether @code{discard} (also known as @code{trim} or @code{unmap}) requests are
|
|
|
|
ignored or passed to the filesystem. Some machine types may not support
|
|
|
|
discard requests.
|
|
|
|
@item detect-zeroes=@var{detect-zeroes}
|
|
|
|
@var{detect-zeroes} is "off", "on" or "unmap" and enables the automatic
|
|
|
|
conversion of plain zero writes by the OS to driver specific optimized
|
|
|
|
zero write commands. You may even choose "unmap" if @var{discard} is set
|
|
|
|
to "unmap" to allow a zero write to be converted to an @code{unmap} operation.
|
|
|
|
@end table
|
|
|
|
|
2016-09-22 17:24:38 +02:00
|
|
|
@item Driver-specific options for @code{file}
|
|
|
|
|
|
|
|
This is the protocol-level block driver for accessing regular files.
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item filename
|
|
|
|
The path to the image file in the local filesystem
|
|
|
|
@item aio
|
|
|
|
Specifies the AIO backend (threads/native, default: threads)
|
2017-11-24 09:53:51 +01:00
|
|
|
@item locking
|
|
|
|
Specifies whether the image file is protected with Linux OFD / POSIX locks. The
|
|
|
|
default is to use the Linux Open File Descriptor API if available, otherwise no
|
|
|
|
lock is applied. (auto/on/off, default: auto)
|
2016-09-22 17:24:38 +02:00
|
|
|
@end table
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
-blockdev driver=file,node-name=disk,filename=disk.img
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@item Driver-specific options for @code{raw}
|
|
|
|
|
|
|
|
This is the image format block driver for raw images. It is usually
|
|
|
|
stacked on top of a protocol level block driver such as @code{file}.
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item file
|
|
|
|
Reference to or definition of the data source block driver node
|
|
|
|
(e.g. a @code{file} driver node)
|
|
|
|
@end table
|
|
|
|
Example 1:
|
|
|
|
@example
|
|
|
|
-blockdev driver=file,node-name=disk_file,filename=disk.img
|
|
|
|
-blockdev driver=raw,node-name=disk,file=disk_file
|
|
|
|
@end example
|
|
|
|
Example 2:
|
|
|
|
@example
|
|
|
|
-blockdev driver=raw,node-name=disk,file.driver=file,file.filename=disk.img
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@item Driver-specific options for @code{qcow2}
|
|
|
|
|
|
|
|
This is the image format block driver for qcow2 images. It is usually
|
|
|
|
stacked on top of a protocol level block driver such as @code{file}.
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item file
|
|
|
|
Reference to or definition of the data source block driver node
|
|
|
|
(e.g. a @code{file} driver node)
|
|
|
|
|
|
|
|
@item backing
|
|
|
|
Reference to or definition of the backing file block device (default is taken
|
2018-02-24 16:40:33 +01:00
|
|
|
from the image file). It is allowed to pass @code{null} here in order to disable
|
|
|
|
the default backing file.
|
2016-09-22 17:24:38 +02:00
|
|
|
|
|
|
|
@item lazy-refcounts
|
|
|
|
Whether to enable the lazy refcounts feature (on/off; default is taken from the
|
|
|
|
image file)
|
|
|
|
|
|
|
|
@item cache-size
|
|
|
|
The maximum total size of the L2 table and refcount block caches in bytes
|
2018-09-26 18:04:39 +02:00
|
|
|
(default: the sum of l2-cache-size and refcount-cache-size)
|
2016-09-22 17:24:38 +02:00
|
|
|
|
|
|
|
@item l2-cache-size
|
|
|
|
The maximum size of the L2 table cache in bytes
|
2018-09-26 18:04:44 +02:00
|
|
|
(default: if cache-size is not specified - 32M on Linux platforms, and 8M on
|
|
|
|
non-Linux platforms; otherwise, as large as possible within the cache-size,
|
|
|
|
while permitting the requested or the minimal refcount cache size)
|
2016-09-22 17:24:38 +02:00
|
|
|
|
|
|
|
@item refcount-cache-size
|
|
|
|
The maximum size of the refcount block cache in bytes
|
2018-09-26 18:04:39 +02:00
|
|
|
(default: 4 times the cluster size; or if cache-size is specified, the part of
|
|
|
|
it which is not used for the L2 cache)
|
2016-09-22 17:24:38 +02:00
|
|
|
|
|
|
|
@item cache-clean-interval
|
|
|
|
Clean unused entries in the L2 and refcount caches. The interval is in seconds.
|
2018-09-29 11:54:54 +02:00
|
|
|
The default value is 600 on supporting platforms, and 0 on other platforms.
|
|
|
|
Setting it to 0 disables this feature.
|
2016-09-22 17:24:38 +02:00
|
|
|
|
|
|
|
@item pass-discard-request
|
|
|
|
Whether discard requests to the qcow2 device should be forwarded to the data
|
|
|
|
source (on/off; default: on if discard=unmap is specified, off otherwise)
|
|
|
|
|
|
|
|
@item pass-discard-snapshot
|
|
|
|
Whether discard requests for the data source should be issued when a snapshot
|
|
|
|
operation (e.g. deleting a snapshot) frees clusters in the qcow2 file (on/off;
|
|
|
|
default: on)
|
|
|
|
|
|
|
|
@item pass-discard-other
|
|
|
|
Whether discard requests for the data source should be issued on other
|
|
|
|
occasions where a cluster gets freed (on/off; default: off)
|
|
|
|
|
|
|
|
@item overlap-check
|
|
|
|
Which overlap checks to perform for writes to the image
|
|
|
|
(none/constant/cached/all; default: cached). For details or finer
|
|
|
|
granularity control refer to the QAPI documentation of @code{blockdev-add}.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
Example 1:
|
|
|
|
@example
|
|
|
|
-blockdev driver=file,node-name=my_file,filename=/tmp/disk.qcow2
|
|
|
|
-blockdev driver=qcow2,node-name=hda,file=my_file,overlap-check=none,cache-size=16777216
|
|
|
|
@end example
|
|
|
|
Example 2:
|
|
|
|
@example
|
|
|
|
-blockdev driver=qcow2,node-name=disk,file.driver=http,file.filename=http://example.com/image.qcow2
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@item Driver-specific options for other drivers
|
|
|
|
Please refer to the QAPI documentation of the @code{blockdev-add} QMP command.
|
|
|
|
|
2016-09-22 16:53:24 +02:00
|
|
|
@end table
|
|
|
|
|
|
|
|
ETEXI
|
block: Initial implementation of -blockdev
The new command line option -blockdev works like QMP command
blockdev-add.
The option argument may be given in JSON syntax, exactly as in QMP.
Example usage:
-blockdev '{"node-name": "foo", "driver": "raw", "file": {"driver": "file", "filename": "foo.img"} }'
The JSON argument doesn't exactly blend into the existing option
syntax, so the traditional KEY=VALUE,... syntax is also supported,
using dotted keys to do the nesting:
-blockdev node-name=foo,driver=raw,file.driver=file,file.filename=foo.img
This does not yet support lists, but that will be addressed shortly.
Note that calling qmp_blockdev_add() (say via qmp_marshal_block_add())
right away would crash. We need to stash the configuration for later
instead. This is crudely done, and bypasses QemuOpts, even though
storing configuration is what QemuOpts is for. Need to revamp option
infrastructure to support QAPI types like BlockdevOptions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <1488317230-26248-22-git-send-email-armbru@redhat.com>
2017-02-28 22:27:07 +01:00
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
DEF("drive", HAS_ARG, QEMU_OPTION_drive,
|
|
|
|
"-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]\n"
|
|
|
|
" [,cache=writethrough|writeback|none|directsync|unsafe][,format=f]\n"
|
2018-06-13 11:01:30 +02:00
|
|
|
" [,snapshot=on|off][,rerror=ignore|stop|report]\n"
|
2014-04-23 13:55:37 +02:00
|
|
|
" [,werror=ignore|stop|report|enospc][,id=name][,aio=threads|native]\n"
|
2013-02-13 19:49:43 +01:00
|
|
|
" [,readonly=on|off][,copy-on-read=on|off]\n"
|
2014-07-28 21:53:02 +02:00
|
|
|
" [,discard=ignore|unmap][,detect-zeroes=on|off|unmap]\n"
|
2013-09-02 14:14:40 +02:00
|
|
|
" [[,bps=b]|[[,bps_rd=r][,bps_wr=w]]]\n"
|
|
|
|
" [[,iops=i]|[[,iops_rd=r][,iops_wr=w]]]\n"
|
|
|
|
" [[,bps_max=bm]|[[,bps_rd_max=rm][,bps_wr_max=wm]]]\n"
|
|
|
|
" [[,iops_max=im]|[[,iops_rd_max=irm][,iops_wr_max=iwm]]]\n"
|
2013-09-02 14:14:41 +02:00
|
|
|
" [[,iops_size=is]]\n"
|
2015-06-08 18:17:44 +02:00
|
|
|
" [[,group=g]]\n"
|
2013-02-13 19:49:43 +01:00
|
|
|
" use 'file' as a drive image\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -drive @var{option}[,@var{option}[,@var{option}[,...]]]
|
|
|
|
@findex -drive
|
|
|
|
|
2016-09-22 16:53:24 +02:00
|
|
|
Define a new drive. This includes creating a block driver node (the backend) as
|
|
|
|
well as a guest device, and is mostly a shortcut for defining the corresponding
|
|
|
|
@option{-blockdev} and @option{-device} options.
|
|
|
|
|
|
|
|
@option{-drive} accepts all options that are accepted by @option{-blockdev}. In
|
|
|
|
addition, it knows the following options:
|
2013-02-13 19:49:43 +01:00
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item file=@var{file}
|
|
|
|
This option defines which disk image (@pxref{disk_images}) to use with
|
|
|
|
this drive. If the filename contains comma, you must double it
|
|
|
|
(for instance, "file=my,,file" to use file "my,file").
|
|
|
|
|
|
|
|
Special files such as iSCSI devices can be specified using protocol
|
|
|
|
specific URLs. See the section for "Device URL Syntax" for more information.
|
|
|
|
@item if=@var{interface}
|
|
|
|
This option defines on which type on interface the drive is connected.
|
2017-03-17 16:49:55 +01:00
|
|
|
Available types are: ide, scsi, sd, mtd, floppy, pflash, virtio, none.
|
2013-02-13 19:49:43 +01:00
|
|
|
@item bus=@var{bus},unit=@var{unit}
|
|
|
|
These options define where is connected the drive by defining the bus number and
|
|
|
|
the unit id.
|
|
|
|
@item index=@var{index}
|
|
|
|
This option defines where is connected the drive by using an index in the list
|
|
|
|
of available connectors of a given interface type.
|
|
|
|
@item media=@var{media}
|
|
|
|
This option defines the type of the media: disk or cdrom.
|
|
|
|
@item snapshot=@var{snapshot}
|
2014-04-07 11:34:58 +02:00
|
|
|
@var{snapshot} is "on" or "off" and controls snapshot mode for the given drive
|
|
|
|
(see @option{-snapshot}).
|
2013-02-13 19:49:43 +01:00
|
|
|
@item cache=@var{cache}
|
2016-09-22 16:53:24 +02:00
|
|
|
@var{cache} is "none", "writeback", "unsafe", "directsync" or "writethrough"
|
|
|
|
and controls how the host cache is used to access block data. This is a
|
|
|
|
shortcut that sets the @option{cache.direct} and @option{cache.no-flush}
|
|
|
|
options (as in @option{-blockdev}), and additionally @option{cache.writeback},
|
|
|
|
which provides a default for the @option{write-cache} option of block guest
|
|
|
|
devices (as in @option{-device}). The modes correspond to the following
|
|
|
|
settings:
|
|
|
|
|
|
|
|
@c Our texi2pod.pl script doesn't support @multitable, so fall back to using
|
|
|
|
@c plain ASCII art (well, UTF-8 art really). This looks okay both in the manpage
|
|
|
|
@c and the HTML output.
|
|
|
|
@example
|
|
|
|
@ │ cache.writeback cache.direct cache.no-flush
|
|
|
|
─────────────┼─────────────────────────────────────────────────
|
|
|
|
writeback │ on off off
|
|
|
|
none │ on on off
|
|
|
|
writethrough │ off off off
|
|
|
|
directsync │ off on off
|
|
|
|
unsafe │ on off on
|
|
|
|
@end example
|
|
|
|
|
|
|
|
The default mode is @option{cache=writeback}.
|
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
@item aio=@var{aio}
|
|
|
|
@var{aio} is "threads", or "native" and selects between pthread based disk I/O and native Linux AIO.
|
|
|
|
@item format=@var{format}
|
|
|
|
Specify which disk @var{format} will be used rather than detecting
|
2016-05-18 14:47:53 +02:00
|
|
|
the format. Can be used to specify format=raw to avoid interpreting
|
2013-02-13 19:49:43 +01:00
|
|
|
an untrusted format header.
|
|
|
|
@item werror=@var{action},rerror=@var{action}
|
|
|
|
Specify which @var{action} to take on write and read errors. Valid actions are:
|
|
|
|
"ignore" (ignore the error and try to continue), "stop" (pause QEMU),
|
|
|
|
"report" (report the error to the guest), "enospc" (pause QEMU only if the
|
|
|
|
host disk is full; report the error to the guest otherwise).
|
|
|
|
The default setting is @option{werror=enospc} and @option{rerror=report}.
|
|
|
|
@item copy-on-read=@var{copy-on-read}
|
|
|
|
@var{copy-on-read} is "on" or "off" and enables whether to copy read backing
|
|
|
|
file sectors into the image file.
|
2017-03-01 12:50:24 +01:00
|
|
|
@item bps=@var{b},bps_rd=@var{r},bps_wr=@var{w}
|
|
|
|
Specify bandwidth throttling limits in bytes per second, either for all request
|
|
|
|
types or for reads or writes only. Small values can lead to timeouts or hangs
|
|
|
|
inside the guest. A safe minimum for disks is 2 MB/s.
|
|
|
|
@item bps_max=@var{bm},bps_rd_max=@var{rm},bps_wr_max=@var{wm}
|
|
|
|
Specify bursts in bytes per second, either for all request types or for reads
|
|
|
|
or writes only. Bursts allow the guest I/O to spike above the limit
|
|
|
|
temporarily.
|
|
|
|
@item iops=@var{i},iops_rd=@var{r},iops_wr=@var{w}
|
|
|
|
Specify request rate limits in requests per second, either for all request
|
|
|
|
types or for reads or writes only.
|
|
|
|
@item iops_max=@var{bm},iops_rd_max=@var{rm},iops_wr_max=@var{wm}
|
|
|
|
Specify bursts in requests per second, either for all request types or for reads
|
|
|
|
or writes only. Bursts allow the guest I/O to spike above the limit
|
|
|
|
temporarily.
|
|
|
|
@item iops_size=@var{is}
|
|
|
|
Let every @var{is} bytes of a request count as a new request for iops
|
|
|
|
throttling purposes. Use this option to prevent guests from circumventing iops
|
|
|
|
limits by sending fewer but larger requests.
|
|
|
|
@item group=@var{g}
|
|
|
|
Join a throttling quota group with given name @var{g}. All drives that are
|
|
|
|
members of the same group are accounted for together. Use this option to
|
|
|
|
prevent guests from circumventing throttling limits by using many small disks
|
|
|
|
instead of a single larger disk.
|
2013-02-13 19:49:43 +01:00
|
|
|
@end table
|
|
|
|
|
2016-09-22 16:53:24 +02:00
|
|
|
By default, the @option{cache.writeback=on} mode is used. It will report data
|
2013-02-13 19:49:43 +01:00
|
|
|
writes as completed as soon as the data is present in the host page cache.
|
|
|
|
This is safe as long as your guest OS makes sure to correctly flush disk caches
|
|
|
|
where needed. If your guest OS does not handle volatile disk write caches
|
|
|
|
correctly and your host crashes or loses power, then the guest may experience
|
|
|
|
data corruption.
|
|
|
|
|
2016-09-22 16:53:24 +02:00
|
|
|
For such guests, you should consider using @option{cache.writeback=off}. This
|
2013-02-13 19:49:43 +01:00
|
|
|
means that the host page cache will be used to read and write data, but write
|
|
|
|
notification will be sent to the guest only after QEMU has made sure to flush
|
|
|
|
each write to the disk. Be aware that this has a major impact on performance.
|
|
|
|
|
2016-09-22 16:53:24 +02:00
|
|
|
When using the @option{-snapshot} option, unsafe caching is always used.
|
2013-02-13 19:49:43 +01:00
|
|
|
|
|
|
|
Copy-on-read avoids accessing the same backing file sectors repeatedly and is
|
|
|
|
useful when the backing file is over a slow network. By default copy-on-read
|
|
|
|
is off.
|
|
|
|
|
|
|
|
Instead of @option{-cdrom} you can use:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive file=file,index=2,media=cdrom
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Instead of @option{-hda}, @option{-hdb}, @option{-hdc}, @option{-hdd}, you can
|
|
|
|
use:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive file=file,index=0,media=disk
|
|
|
|
qemu-system-i386 -drive file=file,index=1,media=disk
|
|
|
|
qemu-system-i386 -drive file=file,index=2,media=disk
|
|
|
|
qemu-system-i386 -drive file=file,index=3,media=disk
|
|
|
|
@end example
|
|
|
|
|
|
|
|
You can open an image using pre-opened file descriptors from an fd set:
|
|
|
|
@example
|
|
|
|
qemu-system-i386
|
|
|
|
-add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
|
|
|
|
-add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
|
|
|
|
-drive file=/dev/fdset/2,index=0,media=disk
|
|
|
|
@end example
|
|
|
|
|
|
|
|
You can connect a CDROM to the slave of ide0:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive file=file,if=ide,index=1,media=cdrom
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
If you don't specify the "file=" argument, you define an empty drive:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive if=ide,index=1,media=cdrom
|
|
|
|
@end example
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
Instead of @option{-fda}, @option{-fdb}, you can use:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive file=file,index=0,if=floppy
|
|
|
|
qemu-system-i386 -drive file=file,index=1,if=floppy
|
|
|
|
@end example
|
2011-12-19 07:19:32 +01:00
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
By default, @var{interface} is "ide" and @var{index} is automatically
|
|
|
|
incremented:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive file=a -drive file=b"
|
|
|
|
@end example
|
|
|
|
is interpreted like:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -hda a -hdb b
|
|
|
|
@end example
|
2013-02-13 19:49:42 +01:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
DEF("mtdblock", HAS_ARG, QEMU_OPTION_mtdblock,
|
|
|
|
"-mtdblock file use 'file' as on-board Flash memory image\n",
|
2013-02-13 19:49:42 +01:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2013-02-13 19:49:43 +01:00
|
|
|
@item -mtdblock @var{file}
|
|
|
|
@findex -mtdblock
|
|
|
|
Use @var{file} as on-board Flash memory image.
|
2013-02-13 19:49:42 +01:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
DEF("sd", HAS_ARG, QEMU_OPTION_sd,
|
|
|
|
"-sd file use 'file' as SecureDigital card image\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2013-02-13 19:49:43 +01:00
|
|
|
@item -sd @var{file}
|
|
|
|
@findex -sd
|
|
|
|
Use @var{file} as SecureDigital card image.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
DEF("pflash", HAS_ARG, QEMU_OPTION_pflash,
|
|
|
|
"-pflash file use 'file' as a parallel flash image\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2013-02-13 19:49:43 +01:00
|
|
|
@item -pflash @var{file}
|
|
|
|
@findex -pflash
|
|
|
|
Use @var{file} as a parallel flash image.
|
2013-02-13 19:49:40 +01:00
|
|
|
ETEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2013-02-13 19:49:43 +01:00
|
|
|
DEF("snapshot", 0, QEMU_OPTION_snapshot,
|
|
|
|
"-snapshot write to temporary files instead of disk image files\n",
|
2013-02-13 19:49:40 +01:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2013-02-13 19:49:43 +01:00
|
|
|
@item -snapshot
|
|
|
|
@findex -snapshot
|
|
|
|
Write to temporary files instead of disk image files. In this case,
|
|
|
|
the raw disk image you use is not written back. You can however force
|
|
|
|
the write back by pressing @key{C-a s} (@pxref{disk_images}).
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2010-04-29 14:14:43 +02:00
|
|
|
DEF("fsdev", HAS_ARG, QEMU_OPTION_fsdev,
|
2019-05-17 17:34:49 +02:00
|
|
|
"-fsdev local,id=id,path=path,security_model=mapped-xattr|mapped-file|passthrough|none\n"
|
|
|
|
" [,writeout=immediate][,readonly][,fmode=fmode][,dmode=dmode]\n"
|
2017-02-28 10:31:46 +01:00
|
|
|
" [[,throttling.bps-total=b]|[[,throttling.bps-read=r][,throttling.bps-write=w]]]\n"
|
|
|
|
" [[,throttling.iops-total=i]|[[,throttling.iops-read=r][,throttling.iops-write=w]]]\n"
|
|
|
|
" [[,throttling.bps-total-max=bm]|[[,throttling.bps-read-max=rm][,throttling.bps-write-max=wm]]]\n"
|
|
|
|
" [[,throttling.iops-total-max=im]|[[,throttling.iops-read-max=irm][,throttling.iops-write-max=iwm]]]\n"
|
2019-05-17 17:34:49 +02:00
|
|
|
" [[,throttling.iops-size=is]]\n"
|
|
|
|
"-fsdev proxy,id=id,socket=socket[,writeout=immediate][,readonly]\n"
|
|
|
|
"-fsdev proxy,id=id,sock_fd=sock_fd[,writeout=immediate][,readonly]\n"
|
|
|
|
"-fsdev synth,id=id\n",
|
2010-04-29 14:14:43 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
|
2019-05-17 17:34:49 +02:00
|
|
|
@item -fsdev local,id=@var{id},path=@var{path},security_model=@var{security_model} [,writeout=@var{writeout}][,readonly][,fmode=@var{fmode}][,dmode=@var{dmode}] [,throttling.@var{option}=@var{value}[,throttling.@var{option}=@var{value}[,...]]]
|
|
|
|
@itemx -fsdev proxy,id=@var{id},socket=@var{socket}[,writeout=@var{writeout}][,readonly]
|
|
|
|
@itemx -fsdev proxy,id=@var{id},sock_fd=@var{sock_fd}[,writeout=@var{writeout}][,readonly]
|
|
|
|
@itemx -fsdev synth,id=@var{id}[,readonly]
|
2010-04-29 14:14:43 +02:00
|
|
|
@findex -fsdev
|
2011-10-12 15:41:24 +02:00
|
|
|
Define a new file system device. Valid options are:
|
|
|
|
@table @option
|
2019-05-17 17:34:49 +02:00
|
|
|
@item local
|
|
|
|
Accesses to the filesystem are done by QEMU.
|
|
|
|
@item proxy
|
|
|
|
Accesses to the filesystem are done by virtfs-proxy-helper(1).
|
|
|
|
@item synth
|
|
|
|
Synthetic filesystem, only used by QTests.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item id=@var{id}
|
2019-05-17 17:34:49 +02:00
|
|
|
Specifies identifier for this device.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item path=@var{path}
|
|
|
|
Specifies the export path for the file system device. Files under
|
|
|
|
this path will be available to the 9p client on the guest.
|
|
|
|
@item security_model=@var{security_model}
|
|
|
|
Specifies the security model to be used for this export path.
|
2012-01-19 07:51:11 +01:00
|
|
|
Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
|
2011-10-12 15:41:24 +02:00
|
|
|
In "passthrough" security model, files are stored using the same
|
2012-05-11 22:25:50 +02:00
|
|
|
credentials as they are created on the guest. This requires QEMU
|
2012-01-19 07:51:11 +01:00
|
|
|
to run as root. In "mapped-xattr" security model, some of the file
|
2011-10-12 15:41:24 +02:00
|
|
|
attributes like uid, gid, mode bits and link target are stored as
|
2012-01-19 07:51:11 +01:00
|
|
|
file attributes. For "mapped-file" these attributes are stored in the
|
|
|
|
hidden .virtfs_metadata directory. Directories exported by this security model cannot
|
2011-10-12 15:41:24 +02:00
|
|
|
interact with other unix tools. "none" security model is same as
|
|
|
|
passthrough except the sever won't report failures if it fails to
|
2011-10-14 09:29:37 +02:00
|
|
|
set file attributes like ownership. Security model is mandatory
|
2018-12-12 14:18:10 +01:00
|
|
|
only for local fsdriver. Other fsdrivers (like proxy) don't take
|
2011-10-14 09:29:37 +02:00
|
|
|
security model as a parameter.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item writeout=@var{writeout}
|
|
|
|
This is an optional argument. The only supported value is "immediate".
|
|
|
|
This means that host page cache will be used to read and write data but
|
|
|
|
write notification will be sent to the guest only when the data has been
|
|
|
|
reported as written by the storage subsystem.
|
2011-10-25 08:40:39 +02:00
|
|
|
@item readonly
|
|
|
|
Enables exporting 9p share as a readonly mount for guests. By default
|
|
|
|
read-write access is given.
|
2011-12-14 09:28:47 +01:00
|
|
|
@item socket=@var{socket}
|
|
|
|
Enables proxy filesystem driver to use passed socket file for communicating
|
2019-05-17 17:34:49 +02:00
|
|
|
with virtfs-proxy-helper(1).
|
2011-12-14 09:28:46 +01:00
|
|
|
@item sock_fd=@var{sock_fd}
|
|
|
|
Enables proxy filesystem driver to use passed socket descriptor for
|
2019-05-17 17:34:49 +02:00
|
|
|
communicating with virtfs-proxy-helper(1). Usually a helper like libvirt
|
|
|
|
will create socketpair and pass one of the fds as sock_fd.
|
2017-06-29 15:11:50 +02:00
|
|
|
@item fmode=@var{fmode}
|
|
|
|
Specifies the default mode for newly created files on the host. Works only
|
|
|
|
with security models "mapped-xattr" and "mapped-file".
|
|
|
|
@item dmode=@var{dmode}
|
|
|
|
Specifies the default mode for newly created directories on the host. Works
|
|
|
|
only with security models "mapped-xattr" and "mapped-file".
|
2019-05-17 17:34:49 +02:00
|
|
|
@item throttling.bps-total=@var{b},throttling.bps-read=@var{r},throttling.bps-write=@var{w}
|
|
|
|
Specify bandwidth throttling limits in bytes per second, either for all request
|
|
|
|
types or for reads or writes only.
|
|
|
|
@item throttling.bps-total-max=@var{bm},bps-read-max=@var{rm},bps-write-max=@var{wm}
|
|
|
|
Specify bursts in bytes per second, either for all request types or for reads
|
|
|
|
or writes only. Bursts allow the guest I/O to spike above the limit
|
|
|
|
temporarily.
|
|
|
|
@item throttling.iops-total=@var{i},throttling.iops-read=@var{r}, throttling.iops-write=@var{w}
|
|
|
|
Specify request rate limits in requests per second, either for all request
|
|
|
|
types or for reads or writes only.
|
|
|
|
@item throttling.iops-total-max=@var{im},throttling.iops-read-max=@var{irm}, throttling.iops-write-max=@var{iwm}
|
|
|
|
Specify bursts in requests per second, either for all request types or for reads
|
|
|
|
or writes only. Bursts allow the guest I/O to spike above the limit temporarily.
|
|
|
|
@item throttling.iops-size=@var{is}
|
|
|
|
Let every @var{is} bytes of a request count as a new request for iops
|
|
|
|
throttling purposes.
|
2011-10-12 15:41:24 +02:00
|
|
|
@end table
|
2010-06-14 22:34:40 +02:00
|
|
|
|
2019-05-17 17:34:49 +02:00
|
|
|
-fsdev option is used along with -device driver "virtio-9p-...".
|
|
|
|
@item -device virtio-9p-@var{type},fsdev=@var{id},mount_tag=@var{mount_tag}
|
|
|
|
Options for virtio-9p-... driver are:
|
2011-10-12 15:41:24 +02:00
|
|
|
@table @option
|
2019-05-17 17:34:49 +02:00
|
|
|
@item @var{type}
|
|
|
|
Specifies the variant to be used. Supported values are "pci", "ccw" or "device",
|
|
|
|
depending on the machine type.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item fsdev=@var{id}
|
2019-05-17 17:34:49 +02:00
|
|
|
Specifies the id value specified along with -fsdev option.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item mount_tag=@var{mount_tag}
|
2019-05-17 17:34:49 +02:00
|
|
|
Specifies the tag name to be used by the guest to mount this export point.
|
2010-04-29 14:14:43 +02:00
|
|
|
@end table
|
2011-10-12 15:41:24 +02:00
|
|
|
|
2010-04-29 14:14:43 +02:00
|
|
|
ETEXI
|
|
|
|
|
virtio-9p: Create a syntactic shortcut for the file-system pass-thru
Currently the commandline to create a virtual-filesystem pass-through between
the guest and the host is as follows:
#qemu -fsdev fstype,id=ID,path=path/to/share \
-device virtio-9p-pci,fsdev=ID,mount_tag=tag \
This patch provides a syntactic short-cut to achieve the same as follows:
#qemu -virtfs fstype,path=path/to/share,mount_tag=tag
This will be internally expanded as:
#qemu -fsdev fstype,id=tag,path=path/to/share, \
-device virtio-9p-pci,fsdev=tag,mount_tag=tag \
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-04-29 14:15:03 +02:00
|
|
|
DEF("virtfs", HAS_ARG, QEMU_OPTION_virtfs,
|
2019-05-17 17:34:49 +02:00
|
|
|
"-virtfs local,path=path,mount_tag=tag,security_model=mapped-xattr|mapped-file|passthrough|none\n"
|
|
|
|
" [,id=id][,writeout=immediate][,readonly][,fmode=fmode][,dmode=dmode]\n"
|
|
|
|
"-virtfs proxy,mount_tag=tag,socket=socket[,id=id][,writeout=immediate][,readonly]\n"
|
|
|
|
"-virtfs proxy,mount_tag=tag,sock_fd=sock_fd[,id=id][,writeout=immediate][,readonly]\n"
|
|
|
|
"-virtfs synth,mount_tag=tag[,id=id][,readonly]\n",
|
virtio-9p: Create a syntactic shortcut for the file-system pass-thru
Currently the commandline to create a virtual-filesystem pass-through between
the guest and the host is as follows:
#qemu -fsdev fstype,id=ID,path=path/to/share \
-device virtio-9p-pci,fsdev=ID,mount_tag=tag \
This patch provides a syntactic short-cut to achieve the same as follows:
#qemu -virtfs fstype,path=path/to/share,mount_tag=tag
This will be internally expanded as:
#qemu -fsdev fstype,id=tag,path=path/to/share, \
-device virtio-9p-pci,fsdev=tag,mount_tag=tag \
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-04-29 14:15:03 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
|
2019-05-17 17:34:49 +02:00
|
|
|
@item -virtfs local,path=@var{path},mount_tag=@var{mount_tag} ,security_model=@var{security_model}[,writeout=@var{writeout}][,readonly] [,fmode=@var{fmode}][,dmode=@var{dmode}]
|
|
|
|
@itemx -virtfs proxy,socket=@var{socket},mount_tag=@var{mount_tag} [,writeout=@var{writeout}][,readonly]
|
|
|
|
@itemx -virtfs proxy,sock_fd=@var{sock_fd},mount_tag=@var{mount_tag} [,writeout=@var{writeout}][,readonly]
|
|
|
|
@itemx -virtfs synth,mount_tag=@var{mount_tag}
|
virtio-9p: Create a syntactic shortcut for the file-system pass-thru
Currently the commandline to create a virtual-filesystem pass-through between
the guest and the host is as follows:
#qemu -fsdev fstype,id=ID,path=path/to/share \
-device virtio-9p-pci,fsdev=ID,mount_tag=tag \
This patch provides a syntactic short-cut to achieve the same as follows:
#qemu -virtfs fstype,path=path/to/share,mount_tag=tag
This will be internally expanded as:
#qemu -fsdev fstype,id=tag,path=path/to/share, \
-device virtio-9p-pci,fsdev=tag,mount_tag=tag \
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-04-29 14:15:03 +02:00
|
|
|
@findex -virtfs
|
|
|
|
|
2019-05-17 17:34:49 +02:00
|
|
|
Define a new filesystem device and expose it to the guest using a virtio-9p-device. The general form of a Virtual File system pass-through options are:
|
2011-10-12 15:41:24 +02:00
|
|
|
@table @option
|
2019-05-17 17:34:49 +02:00
|
|
|
@item local
|
|
|
|
Accesses to the filesystem are done by QEMU.
|
|
|
|
@item proxy
|
|
|
|
Accesses to the filesystem are done by virtfs-proxy-helper(1).
|
|
|
|
@item synth
|
|
|
|
Synthetic filesystem, only used by QTests.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item id=@var{id}
|
2019-05-17 17:34:49 +02:00
|
|
|
Specifies identifier for the filesystem device
|
2011-10-12 15:41:24 +02:00
|
|
|
@item path=@var{path}
|
|
|
|
Specifies the export path for the file system device. Files under
|
|
|
|
this path will be available to the 9p client on the guest.
|
|
|
|
@item security_model=@var{security_model}
|
|
|
|
Specifies the security model to be used for this export path.
|
2012-01-19 07:51:11 +01:00
|
|
|
Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
|
2011-10-12 15:41:24 +02:00
|
|
|
In "passthrough" security model, files are stored using the same
|
2012-05-11 22:25:50 +02:00
|
|
|
credentials as they are created on the guest. This requires QEMU
|
2012-01-19 07:51:11 +01:00
|
|
|
to run as root. In "mapped-xattr" security model, some of the file
|
2011-10-12 15:41:24 +02:00
|
|
|
attributes like uid, gid, mode bits and link target are stored as
|
2012-01-19 07:51:11 +01:00
|
|
|
file attributes. For "mapped-file" these attributes are stored in the
|
|
|
|
hidden .virtfs_metadata directory. Directories exported by this security model cannot
|
2011-10-12 15:41:24 +02:00
|
|
|
interact with other unix tools. "none" security model is same as
|
|
|
|
passthrough except the sever won't report failures if it fails to
|
2011-10-14 09:29:37 +02:00
|
|
|
set file attributes like ownership. Security model is mandatory only
|
2018-12-12 14:18:10 +01:00
|
|
|
for local fsdriver. Other fsdrivers (like proxy) don't take security
|
2011-10-14 09:29:37 +02:00
|
|
|
model as a parameter.
|
2011-10-12 15:41:24 +02:00
|
|
|
@item writeout=@var{writeout}
|
|
|
|
This is an optional argument. The only supported value is "immediate".
|
|
|
|
This means that host page cache will be used to read and write data but
|
|
|
|
write notification will be sent to the guest only when the data has been
|
|
|
|
reported as written by the storage subsystem.
|
2011-10-25 08:40:39 +02:00
|
|
|
@item readonly
|
|
|
|
Enables exporting 9p share as a readonly mount for guests. By default
|
|
|
|
read-write access is given.
|
2011-12-14 09:28:47 +01:00
|
|
|
@item socket=@var{socket}
|
|
|
|
Enables proxy filesystem driver to use passed socket file for
|
2019-05-17 17:34:49 +02:00
|
|
|
communicating with virtfs-proxy-helper(1). Usually a helper like libvirt
|
|
|
|
will create socketpair and pass one of the fds as sock_fd.
|
2011-12-14 09:28:46 +01:00
|
|
|
@item sock_fd
|
|
|
|
Enables proxy filesystem driver to use passed 'sock_fd' as the socket
|
2019-05-17 17:34:49 +02:00
|
|
|
descriptor for interfacing with virtfs-proxy-helper(1).
|
2017-06-29 15:11:50 +02:00
|
|
|
@item fmode=@var{fmode}
|
|
|
|
Specifies the default mode for newly created files on the host. Works only
|
|
|
|
with security models "mapped-xattr" and "mapped-file".
|
|
|
|
@item dmode=@var{dmode}
|
|
|
|
Specifies the default mode for newly created directories on the host. Works
|
|
|
|
only with security models "mapped-xattr" and "mapped-file".
|
2019-05-17 17:34:49 +02:00
|
|
|
@item mount_tag=@var{mount_tag}
|
|
|
|
Specifies the tag name to be used by the guest to mount this export point.
|
virtio-9p: Create a syntactic shortcut for the file-system pass-thru
Currently the commandline to create a virtual-filesystem pass-through between
the guest and the host is as follows:
#qemu -fsdev fstype,id=ID,path=path/to/share \
-device virtio-9p-pci,fsdev=ID,mount_tag=tag \
This patch provides a syntactic short-cut to achieve the same as follows:
#qemu -virtfs fstype,path=path/to/share,mount_tag=tag
This will be internally expanded as:
#qemu -fsdev fstype,id=tag,path=path/to/share, \
-device virtio-9p-pci,fsdev=tag,mount_tag=tag \
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-04-29 14:15:03 +02:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2011-10-25 08:40:40 +02:00
|
|
|
DEF("virtfs_synth", 0, QEMU_OPTION_virtfs_synth,
|
|
|
|
"-virtfs_synth Create synthetic file system image\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -virtfs_synth
|
|
|
|
@findex -virtfs_synth
|
2019-05-17 17:34:48 +02:00
|
|
|
Create synthetic file system image. Note that this option is now deprecated.
|
|
|
|
Please use @code{-fsdev synth} and @code{-device virtio-9p-...} instead.
|
2011-10-25 08:40:40 +02:00
|
|
|
ETEXI
|
|
|
|
|
2017-10-02 16:03:03 +02:00
|
|
|
DEF("iscsi", HAS_ARG, QEMU_OPTION_iscsi,
|
|
|
|
"-iscsi [user=user][,password=password]\n"
|
|
|
|
" [,header-digest=CRC32C|CR32C-NONE|NONE-CRC32C|NONE\n"
|
|
|
|
" [,initiator-name=initiator-iqn][,id=target-iqn]\n"
|
|
|
|
" [,timeout=timeout]\n"
|
|
|
|
" iSCSI session parameters\n", QEMU_ARCH_ALL)
|
|
|
|
|
2017-10-02 16:03:04 +02:00
|
|
|
STEXI
|
|
|
|
@item -iscsi
|
|
|
|
@findex -iscsi
|
|
|
|
Configure iSCSI session parameters.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(USB options:)
|
2013-02-13 19:49:43 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("usb", 0, QEMU_OPTION_usb,
|
2017-05-19 08:35:16 +02:00
|
|
|
"-usb enable the USB driver (if it is not used by default yet)\n",
|
2013-02-13 19:49:43 +01:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -usb
|
|
|
|
@findex -usb
|
2017-05-19 08:35:16 +02:00
|
|
|
Enable the USB driver (if it is not used by default yet).
|
2013-02-13 19:49:43 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("usbdevice", HAS_ARG, QEMU_OPTION_usbdevice,
|
|
|
|
"-usbdevice name add the host or guest USB device 'name'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
|
|
|
|
@item -usbdevice @var{devname}
|
|
|
|
@findex -usbdevice
|
2017-05-19 08:35:16 +02:00
|
|
|
Add the USB device @var{devname}. Note that this option is deprecated,
|
|
|
|
please use @code{-device usb-...} instead. @xref{usb_devices}.
|
2013-02-13 19:49:43 +01:00
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item mouse
|
|
|
|
Virtual Mouse. This will override the PS/2 mouse emulation when activated.
|
|
|
|
|
|
|
|
@item tablet
|
|
|
|
Pointer device that uses absolute coordinates (like a touchscreen). This
|
|
|
|
means QEMU is able to report the mouse position without having to grab the
|
|
|
|
mouse. Also overrides the PS/2 mouse emulation when activated.
|
|
|
|
|
|
|
|
@item braille
|
|
|
|
Braille device. This will use BrlAPI to display the braille output on a real
|
|
|
|
or fake device.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Display options:)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
2011-03-16 13:33:31 +01:00
|
|
|
DEF("display", HAS_ARG, QEMU_OPTION_display,
|
2019-02-21 12:07:03 +01:00
|
|
|
"-display spice-app[,gl=on|off]\n"
|
2011-03-16 13:33:31 +01:00
|
|
|
"-display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]\n"
|
2018-04-13 15:58:42 +02:00
|
|
|
" [,window_close=on|off][,gl=on|core|es|off]\n"
|
2016-07-26 12:17:11 +02:00
|
|
|
"-display gtk[,grab_on_hover=on|off][,gl=on|off]|\n"
|
|
|
|
"-display vnc=<display>[,<optargs>]\n"
|
2019-03-11 14:51:27 +01:00
|
|
|
"-display curses[,charset=<encoding>]\n"
|
2018-11-16 11:14:44 +01:00
|
|
|
"-display none\n"
|
|
|
|
"-display egl-headless[,rendernode=<file>]"
|
2016-07-26 12:17:11 +02:00
|
|
|
" select display type\n"
|
|
|
|
"The default display is equivalent to\n"
|
|
|
|
#if defined(CONFIG_GTK)
|
|
|
|
"\t\"-display gtk\"\n"
|
|
|
|
#elif defined(CONFIG_SDL)
|
|
|
|
"\t\"-display sdl\"\n"
|
|
|
|
#elif defined(CONFIG_COCOA)
|
|
|
|
"\t\"-display cocoa\"\n"
|
|
|
|
#elif defined(CONFIG_VNC)
|
|
|
|
"\t\"-vnc localhost:0,to=99,id=default\"\n"
|
|
|
|
#else
|
|
|
|
"\t\"-display none\"\n"
|
|
|
|
#endif
|
|
|
|
, QEMU_ARCH_ALL)
|
2011-03-16 13:33:31 +01:00
|
|
|
STEXI
|
|
|
|
@item -display @var{type}
|
|
|
|
@findex -display
|
|
|
|
Select type of display to use. This option is a replacement for the
|
|
|
|
old style -sdl/-curses/... options. Valid values for @var{type} are
|
|
|
|
@table @option
|
|
|
|
@item sdl
|
|
|
|
Display video output via SDL (usually in a separate graphics
|
|
|
|
window; see the SDL documentation for other possibilities).
|
|
|
|
@item curses
|
|
|
|
Display video output via curses. For graphics device models which
|
|
|
|
support a text mode, QEMU can display this output using a
|
|
|
|
curses/ncurses interface. Nothing is displayed when the graphics
|
|
|
|
device is in graphical mode or if the graphics device does not support
|
|
|
|
a text mode. Generally only the VGA device models support text mode.
|
2019-03-11 14:51:27 +01:00
|
|
|
The font charset used by the guest can be specified with the
|
|
|
|
@code{charset} option, for example @code{charset=CP850} for IBM CP850
|
|
|
|
encoding. The default is @code{CP437}.
|
2011-03-16 13:33:32 +01:00
|
|
|
@item none
|
|
|
|
Do not display video output. The guest will still see an emulated
|
|
|
|
graphics card, but its output will not be displayed to the QEMU
|
|
|
|
user. This option differs from the -nographic option in that it
|
|
|
|
only affects what is done with video output; -nographic also changes
|
|
|
|
the destination of the serial and parallel port data.
|
2014-03-12 08:33:50 +01:00
|
|
|
@item gtk
|
|
|
|
Display video output in a GTK window. This interface provides drop-down
|
|
|
|
menus and other UI elements to configure and control the VM during
|
|
|
|
runtime.
|
2011-03-16 13:33:33 +01:00
|
|
|
@item vnc
|
|
|
|
Start a VNC server on display <arg>
|
2018-11-16 11:14:44 +01:00
|
|
|
@item egl-headless
|
|
|
|
Offload all OpenGL operations to a local DRI device. For any graphical display,
|
|
|
|
this display needs to be paired with either VNC or SPICE displays.
|
2019-02-21 12:07:03 +01:00
|
|
|
@item spice-app
|
|
|
|
Start QEMU as a Spice server and launch the default Spice client
|
|
|
|
application. The Spice server will redirect the serial consoles and
|
|
|
|
QEMU monitors. (Since 4.0)
|
2011-03-16 13:33:31 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("nographic", 0, QEMU_OPTION_nographic,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-nographic disable graphical output and redirect serial I/Os to console\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -nographic
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -nographic
|
2016-08-12 21:30:48 +02:00
|
|
|
Normally, if QEMU is compiled with graphical window support, it displays
|
|
|
|
output such as guest graphics, guest console, and the QEMU monitor in a
|
|
|
|
window. With this option, you can totally disable graphical output so
|
|
|
|
that QEMU is a simple command line application. The emulated serial port
|
|
|
|
is redirected on the console and muxed with the monitor (unless
|
|
|
|
redirected elsewhere explicitly). Therefore, you can still use QEMU to
|
|
|
|
debug a Linux kernel with a serial console. Use @key{C-a h} for help on
|
|
|
|
switching between the console and monitor.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("curses", 0, QEMU_OPTION_curses,
|
2016-07-26 12:17:11 +02:00
|
|
|
"-curses shorthand for -display curses\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -curses
|
2013-02-13 19:49:38 +01:00
|
|
|
@findex -curses
|
2016-08-12 21:30:48 +02:00
|
|
|
Normally, if QEMU is compiled with graphical window support, it displays
|
|
|
|
output such as guest graphics, guest console, and the QEMU monitor in a
|
|
|
|
window. With this option, QEMU can display the VGA output when in text
|
|
|
|
mode using a curses/ncurses interface. Nothing is displayed in graphical
|
|
|
|
mode.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("alt-grab", 0, QEMU_OPTION_alt_grab,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -alt-grab
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -alt-grab
|
2011-04-29 13:46:12 +02:00
|
|
|
Use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt). Note that this also
|
|
|
|
affects the special keys (for fullscreen, monitor-mode switching, etc).
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2009-09-17 22:48:04 +02:00
|
|
|
DEF("ctrl-grab", 0, QEMU_OPTION_ctrl_grab,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-09-17 22:48:04 +02:00
|
|
|
STEXI
|
|
|
|
@item -ctrl-grab
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -ctrl-grab
|
2011-04-29 13:46:12 +02:00
|
|
|
Use Right-Ctrl to grab mouse (instead of Ctrl-Alt). Note that this also
|
|
|
|
affects the special keys (for fullscreen, monitor-mode switching, etc).
|
2009-09-17 22:48:04 +02:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("no-quit", 0, QEMU_OPTION_no_quit,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-no-quit disable SDL window close capability\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -no-quit
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -no-quit
|
2009-03-28 07:44:27 +01:00
|
|
|
Disable SDL window close capability.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("sdl", 0, QEMU_OPTION_sdl,
|
2016-07-26 12:17:11 +02:00
|
|
|
"-sdl shorthand for -display sdl\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -sdl
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -sdl
|
2009-03-28 07:44:27 +01:00
|
|
|
Enable SDL.
|
|
|
|
ETEXI
|
|
|
|
|
2010-03-11 15:13:27 +01:00
|
|
|
DEF("spice", HAS_ARG, QEMU_OPTION_spice,
|
2012-08-21 12:54:20 +02:00
|
|
|
"-spice [port=port][,tls-port=secured-port][,x509-dir=<dir>]\n"
|
|
|
|
" [,x509-key-file=<file>][,x509-key-password=<file>]\n"
|
|
|
|
" [,x509-cert-file=<file>][,x509-cacert-file=<file>]\n"
|
2015-01-13 17:57:51 +01:00
|
|
|
" [,x509-dh-key-file=<file>][,addr=addr][,ipv4|ipv6|unix]\n"
|
2012-08-21 12:54:20 +02:00
|
|
|
" [,tls-ciphers=<list>]\n"
|
|
|
|
" [,tls-channel=[main|display|cursor|inputs|record|playback]]\n"
|
|
|
|
" [,plaintext-channel=[main|display|cursor|inputs|record|playback]]\n"
|
|
|
|
" [,sasl][,password=<secret>][,disable-ticketing]\n"
|
|
|
|
" [,image-compression=[auto_glz|auto_lz|quic|glz|lz|off]]\n"
|
|
|
|
" [,jpeg-wan-compression=[auto|never|always]]\n"
|
|
|
|
" [,zlib-glz-wan-compression=[auto|never|always]]\n"
|
|
|
|
" [,streaming-video=[off|all|filter]][,disable-copy-paste]\n"
|
2013-06-08 15:37:27 +02:00
|
|
|
" [,disable-agent-file-xfer][,agent-mouse=[on|off]]\n"
|
|
|
|
" [,playback-compression=[on|off]][,seamless-migration=[on|off]]\n"
|
2017-02-12 12:21:18 +01:00
|
|
|
" [,gl=[on|off]][,rendernode=<file>]\n"
|
2012-08-21 12:54:20 +02:00
|
|
|
" enable spice\n"
|
|
|
|
" at least one of {port, tls-port} is mandatory\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-03-11 15:13:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -spice @var{option}[,@var{option}[,...]]
|
|
|
|
@findex -spice
|
|
|
|
Enable the spice remote desktop protocol. Valid options are
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item port=<nr>
|
2010-03-11 15:13:32 +01:00
|
|
|
Set the TCP port spice is listening on for plaintext channels.
|
2010-03-11 15:13:27 +01:00
|
|
|
|
2010-08-27 14:29:16 +02:00
|
|
|
@item addr=<addr>
|
|
|
|
Set the IP address spice is listening on. Default is any address.
|
|
|
|
|
|
|
|
@item ipv4
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx ipv6
|
|
|
|
@itemx unix
|
2010-08-27 14:29:16 +02:00
|
|
|
Force using the specified IP version.
|
|
|
|
|
2010-03-11 15:13:27 +01:00
|
|
|
@item password=<secret>
|
|
|
|
Set the password you need to authenticate.
|
|
|
|
|
2011-05-17 10:40:33 +02:00
|
|
|
@item sasl
|
|
|
|
Require that the client use SASL to authenticate with the spice.
|
|
|
|
The exact choice of authentication method used is controlled from the
|
|
|
|
system / user's SASL configuration file for the 'qemu' service. This
|
|
|
|
is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
|
|
|
|
unprivileged user, an environment variable SASL_CONF_PATH can be used
|
|
|
|
to make it search alternate locations for the service config.
|
|
|
|
While some SASL auth methods can also provide data encryption (eg GSSAPI),
|
|
|
|
it is recommended that SASL always be combined with the 'tls' and
|
|
|
|
'x509' settings to enable use of SSL and server certificates. This
|
|
|
|
ensures a data encryption preventing compromise of authentication
|
|
|
|
credentials.
|
|
|
|
|
2010-03-11 15:13:27 +01:00
|
|
|
@item disable-ticketing
|
|
|
|
Allow client connects without authentication.
|
|
|
|
|
2011-03-27 16:43:54 +02:00
|
|
|
@item disable-copy-paste
|
|
|
|
Disable copy paste between the client and the guest.
|
|
|
|
|
2013-06-08 15:37:27 +02:00
|
|
|
@item disable-agent-file-xfer
|
|
|
|
Disable spice-vdagent based file-xfer between the client and the guest.
|
|
|
|
|
2010-03-11 15:13:32 +01:00
|
|
|
@item tls-port=<nr>
|
|
|
|
Set the TCP port spice is listening on for encrypted channels.
|
|
|
|
|
|
|
|
@item x509-dir=<dir>
|
|
|
|
Set the x509 file directory. Expects same filenames as -vnc $display,x509=$dir
|
|
|
|
|
|
|
|
@item x509-key-file=<file>
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx x509-key-password=<file>
|
|
|
|
@itemx x509-cert-file=<file>
|
|
|
|
@itemx x509-cacert-file=<file>
|
|
|
|
@itemx x509-dh-key-file=<file>
|
2010-03-11 15:13:32 +01:00
|
|
|
The x509 file names can also be configured individually.
|
|
|
|
|
|
|
|
@item tls-ciphers=<list>
|
|
|
|
Specify which ciphers to use.
|
|
|
|
|
2011-12-20 12:05:18 +01:00
|
|
|
@item tls-channel=[main|display|cursor|inputs|record|playback]
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx plaintext-channel=[main|display|cursor|inputs|record|playback]
|
2010-08-27 14:09:56 +02:00
|
|
|
Force specific channel to be used with or without TLS encryption. The
|
|
|
|
options can be specified multiple times to configure multiple
|
|
|
|
channels. The special name "default" can be used to set the default
|
|
|
|
mode. For channels which are not explicitly forced into one mode the
|
|
|
|
spice client is allowed to pick tls/plaintext as he pleases.
|
|
|
|
|
2010-07-14 12:26:34 +02:00
|
|
|
@item image-compression=[auto_glz|auto_lz|quic|glz|lz|off]
|
|
|
|
Configure image compression (lossless).
|
|
|
|
Default is auto_glz.
|
|
|
|
|
|
|
|
@item jpeg-wan-compression=[auto|never|always]
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx zlib-glz-wan-compression=[auto|never|always]
|
2010-07-14 12:26:34 +02:00
|
|
|
Configure wan image compression (lossy for slow links).
|
|
|
|
Default is auto.
|
|
|
|
|
2010-08-30 16:36:53 +02:00
|
|
|
@item streaming-video=[off|all|filter]
|
2016-08-01 06:06:59 +02:00
|
|
|
Configure video stream detection. Default is off.
|
2010-08-30 16:36:53 +02:00
|
|
|
|
|
|
|
@item agent-mouse=[on|off]
|
|
|
|
Enable/disable passing mouse events via vdagent. Default is on.
|
|
|
|
|
|
|
|
@item playback-compression=[on|off]
|
|
|
|
Enable/disable audio stream compression (using celt 0.5.1). Default is on.
|
|
|
|
|
2012-08-21 10:51:59 +02:00
|
|
|
@item seamless-migration=[on|off]
|
|
|
|
Enable/disable spice seamless migration. Default is off.
|
|
|
|
|
2015-10-13 15:39:34 +02:00
|
|
|
@item gl=[on|off]
|
|
|
|
Enable/disable OpenGL context. Default is off.
|
|
|
|
|
2017-02-12 12:21:18 +01:00
|
|
|
@item rendernode=<file>
|
|
|
|
DRM render node for OpenGL rendering. If not specified, it will pick
|
|
|
|
the first available. (Since 2.9)
|
|
|
|
|
2010-03-11 15:13:27 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("portrait", 0, QEMU_OPTION_portrait,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-portrait rotate graphical output 90 deg left (only PXA LCD)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -portrait
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -portrait
|
2009-03-28 07:44:27 +01:00
|
|
|
Rotate graphical output 90 deg left (only PXA LCD).
|
|
|
|
ETEXI
|
|
|
|
|
2011-06-17 12:04:36 +02:00
|
|
|
DEF("rotate", HAS_ARG, QEMU_OPTION_rotate,
|
|
|
|
"-rotate <deg> rotate graphical output some deg left (only PXA LCD)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2013-02-13 19:49:39 +01:00
|
|
|
@item -rotate @var{deg}
|
2011-06-17 12:04:36 +02:00
|
|
|
@findex -rotate
|
|
|
|
Rotate graphical output some deg left (only PXA LCD).
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("vga", HAS_ARG, QEMU_OPTION_vga,
|
2014-09-10 14:28:48 +02:00
|
|
|
"-vga [std|cirrus|vmware|qxl|xenfb|tcx|cg3|virtio|none]\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" select video card type\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2012-08-27 16:33:21 +02:00
|
|
|
@item -vga @var{type}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -vga
|
2009-03-28 07:44:27 +01:00
|
|
|
Select type of VGA card to emulate. Valid values for @var{type} are
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2009-03-28 07:44:27 +01:00
|
|
|
@item cirrus
|
|
|
|
Cirrus Logic GD5446 Video card. All Windows versions starting from
|
|
|
|
Windows 95 should recognize and use this graphic card. For optimal
|
|
|
|
performances, use 16 bit color depth in the guest and the host OS.
|
2017-01-27 10:41:54 +01:00
|
|
|
(This card was the default before QEMU 2.2)
|
2009-03-28 07:44:27 +01:00
|
|
|
@item std
|
|
|
|
Standard VGA card with Bochs VBE extensions. If your guest OS
|
|
|
|
supports the VESA 2.0 VBE extensions (e.g. Windows XP) and if you want
|
|
|
|
to use high resolution modes (>= 1280x1024x16) then you should use
|
2017-01-27 10:41:54 +01:00
|
|
|
this option. (This card is the default since QEMU 2.2)
|
2009-03-28 07:44:27 +01:00
|
|
|
@item vmware
|
|
|
|
VMWare SVGA-II compatible adapter. Use it if you have sufficiently
|
|
|
|
recent XFree86/XOrg server or Windows guest with a driver for this
|
|
|
|
card.
|
2010-04-27 11:50:11 +02:00
|
|
|
@item qxl
|
|
|
|
QXL paravirtual graphic card. It is VGA compatible (including VESA
|
|
|
|
2.0 VBE support). Works best with qxl guest drivers installed though.
|
|
|
|
Recommended choice when using the spice protocol.
|
2014-03-17 22:46:25 +01:00
|
|
|
@item tcx
|
|
|
|
(sun4m only) Sun TCX framebuffer. This is the default framebuffer for
|
|
|
|
sun4m machines and offers both 8-bit and 24-bit colour depths at a
|
|
|
|
fixed resolution of 1024x768.
|
|
|
|
@item cg3
|
|
|
|
(sun4m only) Sun cgthree framebuffer. This is a simple 8-bit framebuffer
|
|
|
|
for sun4m machines available in both 1024x768 (OpenBIOS) and 1152x900 (OBP)
|
|
|
|
resolutions aimed at people wishing to run older Solaris versions.
|
2014-09-10 14:28:48 +02:00
|
|
|
@item virtio
|
|
|
|
Virtio VGA card.
|
2009-03-28 07:44:27 +01:00
|
|
|
@item none
|
|
|
|
Disable VGA card.
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("full-screen", 0, QEMU_OPTION_full_screen,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-full-screen start in full screen\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -full-screen
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -full-screen
|
2009-03-28 07:44:27 +01:00
|
|
|
Start in full screen.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("g", 1, QEMU_OPTION_g ,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-g WxH[xDEPTH] Set the initial graphical resolution and depth\n",
|
|
|
|
QEMU_ARCH_PPC | QEMU_ARCH_SPARC)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2010-01-20 22:25:27 +01:00
|
|
|
@item -g @var{width}x@var{height}[x@var{depth}]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -g
|
2010-01-20 22:25:27 +01:00
|
|
|
Set the initial graphical resolution and depth (PPC, SPARC only).
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("vnc", HAS_ARG, QEMU_OPTION_vnc ,
|
2016-07-26 12:17:11 +02:00
|
|
|
"-vnc <display> shorthand for -display vnc=<display>\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -vnc @var{display}[,@var{option}[,@var{option}[,...]]]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -vnc
|
2016-08-12 21:30:48 +02:00
|
|
|
Normally, if QEMU is compiled with graphical window support, it displays
|
|
|
|
output such as guest graphics, guest console, and the QEMU monitor in a
|
|
|
|
window. With this option, you can have QEMU listen on VNC display
|
|
|
|
@var{display} and redirect the VGA display over the VNC session. It is
|
|
|
|
very useful to enable the usb tablet device when using this option
|
2017-05-19 08:35:16 +02:00
|
|
|
(option @option{-device usb-tablet}). When using the VNC display, you
|
2016-08-12 21:30:48 +02:00
|
|
|
must use the @option{-k} parameter to set the keyboard layout if you are
|
|
|
|
not using en-us. Valid syntax for the @var{display} is
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2016-05-31 09:03:09 +02:00
|
|
|
@item to=@var{L}
|
|
|
|
|
|
|
|
With this option, QEMU will try next available VNC @var{display}s, until the
|
|
|
|
number @var{L}, if the origianlly defined "-vnc @var{display}" is not
|
|
|
|
available, e.g. port 5900+@var{display} is already used by another
|
|
|
|
application. By default, to=0.
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
@item @var{host}:@var{d}
|
|
|
|
|
|
|
|
TCP connections will only be allowed from @var{host} on display @var{d}.
|
|
|
|
By convention the TCP port is 5900+@var{d}. Optionally, @var{host} can
|
|
|
|
be omitted in which case the server will accept connections from any host.
|
|
|
|
|
2009-10-09 10:58:36 +02:00
|
|
|
@item unix:@var{path}
|
2009-03-28 07:44:27 +01:00
|
|
|
|
|
|
|
Connections will be allowed over UNIX domain sockets where @var{path} is the
|
|
|
|
location of a unix socket to listen for connections on.
|
|
|
|
|
|
|
|
@item none
|
|
|
|
|
|
|
|
VNC is initialized but not started. The monitor @code{change} command
|
|
|
|
can be used to later start the VNC server.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
Following the @var{display} value there may be one or more @var{option} flags
|
|
|
|
separated by commas. Valid options are
|
|
|
|
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2009-03-28 07:44:27 +01:00
|
|
|
|
|
|
|
@item reverse
|
|
|
|
|
|
|
|
Connect to a listening VNC client via a ``reverse'' connection. The
|
|
|
|
client is specified by the @var{display}. For reverse network
|
|
|
|
connections (@var{host}:@var{d},@code{reverse}), the @var{d} argument
|
|
|
|
is a TCP port number, not a display number.
|
|
|
|
|
2013-01-21 11:04:44 +01:00
|
|
|
@item websocket
|
|
|
|
|
|
|
|
Opens an additional TCP listening port dedicated to VNC Websocket connections.
|
2017-02-03 13:06:45 +01:00
|
|
|
If a bare @var{websocket} option is given, the Websocket port is
|
|
|
|
5700+@var{display}. An alternative port can be specified with the
|
|
|
|
syntax @code{websocket}=@var{port}.
|
|
|
|
|
|
|
|
If @var{host} is specified connections will only be allowed from this host.
|
|
|
|
It is possible to control the websocket listen address independently, using
|
|
|
|
the syntax @code{websocket}=@var{host}:@var{port}.
|
|
|
|
|
ui: convert VNC server to use QCryptoTLSSession
Switch VNC server over to using the QCryptoTLSSession object
for the TLS session. This removes the direct use of gnutls
from the VNC server code. It also removes most knowledge
about TLS certificate handling from the VNC server code.
This has the nice effect that all the CONFIG_VNC_TLS
conditionals go away and the user gets an actual error
message when requesting TLS instead of it being silently
ignored.
With this change, the existing configuration options for
enabling TLS with -vnc are deprecated.
Old syntax for anon-DH credentials:
-vnc hostname:0,tls
New syntax:
-object tls-creds-anon,id=tls0,endpoint=server \
-vnc hostname:0,tls-creds=tls0
Old syntax for x509 credentials, no client certs:
-vnc hostname:0,tls,x509=/path/to/certs
New syntax:
-object tls-creds-x509,id=tls0,dir=/path/to/certs,endpoint=server,verify-peer=no \
-vnc hostname:0,tls-creds=tls0
Old syntax for x509 credentials, requiring client certs:
-vnc hostname:0,tls,x509verify=/path/to/certs
New syntax:
-object tls-creds-x509,id=tls0,dir=/path/to/certs,endpoint=server,verify-peer=yes \
-vnc hostname:0,tls-creds=tls0
This aligns VNC with the way TLS credentials are to be
configured in the future for chardev, nbd and migration
backends. It also has the benefit that the same TLS
credentials can be shared across multiple VNC server
instances, if desired.
If someone uses the deprecated syntax, it will internally
result in the creation of a 'tls-creds' object with an ID
based on the VNC server ID. This allows backwards compat
with the CLI syntax, while still deleting all the original
TLS code from the VNC server.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-08-06 15:39:32 +02:00
|
|
|
If no TLS credentials are provided, the websocket connection runs in
|
|
|
|
unencrypted mode. If TLS credentials are provided, the websocket connection
|
|
|
|
requires encrypted client connections.
|
2013-01-21 11:04:44 +01:00
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
@item password
|
|
|
|
|
|
|
|
Require that password based authentication is used for client connections.
|
2012-07-16 15:54:38 +02:00
|
|
|
|
|
|
|
The password must be set separately using the @code{set_password} command in
|
|
|
|
the @ref{pcsys_monitor}. The syntax to change your password is:
|
|
|
|
@code{set_password <protocol> <password>} where <protocol> could be either
|
|
|
|
"vnc" or "spice".
|
|
|
|
|
|
|
|
If you would like to change <protocol> password expiration, you should use
|
|
|
|
@code{expire_password <protocol> <expiration-time>} where expiration time could
|
|
|
|
be one of the following options: now, never, +seconds or UNIX time of
|
|
|
|
expiration, e.g. +60 to make password expire in 60 seconds, or 1335196800
|
|
|
|
to make password expire on "Mon Apr 23 12:00:00 EDT 2012" (UNIX time for this
|
|
|
|
date and time).
|
|
|
|
|
|
|
|
You can also use keywords "now" or "never" for the expiration time to
|
|
|
|
allow <protocol> password to expire immediately or never expire.
|
2009-03-28 07:44:27 +01:00
|
|
|
|
ui: convert VNC server to use QCryptoTLSSession
Switch VNC server over to using the QCryptoTLSSession object
for the TLS session. This removes the direct use of gnutls
from the VNC server code. It also removes most knowledge
about TLS certificate handling from the VNC server code.
This has the nice effect that all the CONFIG_VNC_TLS
conditionals go away and the user gets an actual error
message when requesting TLS instead of it being silently
ignored.
With this change, the existing configuration options for
enabling TLS with -vnc are deprecated.
Old syntax for anon-DH credentials:
-vnc hostname:0,tls
New syntax:
-object tls-creds-anon,id=tls0,endpoint=server \
-vnc hostname:0,tls-creds=tls0
Old syntax for x509 credentials, no client certs:
-vnc hostname:0,tls,x509=/path/to/certs
New syntax:
-object tls-creds-x509,id=tls0,dir=/path/to/certs,endpoint=server,verify-peer=no \
-vnc hostname:0,tls-creds=tls0
Old syntax for x509 credentials, requiring client certs:
-vnc hostname:0,tls,x509verify=/path/to/certs
New syntax:
-object tls-creds-x509,id=tls0,dir=/path/to/certs,endpoint=server,verify-peer=yes \
-vnc hostname:0,tls-creds=tls0
This aligns VNC with the way TLS credentials are to be
configured in the future for chardev, nbd and migration
backends. It also has the benefit that the same TLS
credentials can be shared across multiple VNC server
instances, if desired.
If someone uses the deprecated syntax, it will internally
result in the creation of a 'tls-creds' object with an ID
based on the VNC server ID. This allows backwards compat
with the CLI syntax, while still deleting all the original
TLS code from the VNC server.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-08-06 15:39:32 +02:00
|
|
|
@item tls-creds=@var{ID}
|
|
|
|
|
|
|
|
Provides the ID of a set of TLS credentials to use to secure the
|
|
|
|
VNC server. They will apply to both the normal VNC server socket
|
|
|
|
and the websocket socket (if enabled). Setting TLS credentials
|
|
|
|
will cause the VNC server socket to enable the VeNCrypt auth
|
|
|
|
mechanism. The credentials should have been previously created
|
|
|
|
using the @option{-object tls-creds} argument.
|
|
|
|
|
vnc: allow specifying a custom authorization object name
The VNC server has historically had support for ACLs to check both the
SASL username and the TLS x509 distinguished name. The VNC server was
responsible for creating the initial ACL, and the client app was then
responsible for populating it with rules using the HMP 'acl_add' command.
This is not satisfactory for a variety of reasons. There is no way to
populate the ACLs from the command line, users are forced to use the
HMP. With multiple network services all supporting TLS and ACLs now, it
is desirable to be able to define a single ACL that is referenced by all
services.
To address these limitations, two new options are added to the VNC
server CLI. The 'tls-authz' option takes the ID of a QAuthZ object to
use for checking TLS x509 distinguished names, and the 'sasl-authz'
option takes the ID of another object to use for checking SASL usernames.
In this example, we setup two authorization rules. The first allows any
client with a certificate issued by the 'RedHat' organization in the
'London' locality. The second ACL allows clients with either the
'joe@REDHAT.COM' or 'fred@REDHAT.COM' kerberos usernames. Both checks
must pass for the user to be allowed.
$QEMU -object tls-creds-x509,id=tls0,dir=/home/berrange/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-simple,id=authz0,policy=deny,\
rules.0.match=O=RedHat,,L=London,rules.0.policy=allow \
-object authz-simple,id=authz1,policy=deny,\
rules.0.match=fred@REDHAT.COM,rules.0.policy=allow \
rules.0.match=joe@REDHAT.COM,rules.0.policy=allow \
-vnc 0.0.0.0:1,tls-creds=tls0,tls-authz=authz0,
sasl,sasl-authz=authz1 \
...other QEMU args...
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20190227145755.26556-2-berrange@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2019-02-27 15:57:54 +01:00
|
|
|
@item tls-authz=@var{ID}
|
|
|
|
|
|
|
|
Provides the ID of the QAuthZ authorization object against which
|
|
|
|
the client's x509 distinguished name will validated. This object is
|
|
|
|
only resolved at time of use, so can be deleted and recreated on the
|
|
|
|
fly while the VNC server is active. If missing, it will default
|
|
|
|
to denying access.
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
@item sasl
|
|
|
|
|
|
|
|
Require that the client use SASL to authenticate with the VNC server.
|
|
|
|
The exact choice of authentication method used is controlled from the
|
|
|
|
system / user's SASL configuration file for the 'qemu' service. This
|
|
|
|
is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
|
|
|
|
unprivileged user, an environment variable SASL_CONF_PATH can be used
|
|
|
|
to make it search alternate locations for the service config.
|
|
|
|
While some SASL auth methods can also provide data encryption (eg GSSAPI),
|
|
|
|
it is recommended that SASL always be combined with the 'tls' and
|
|
|
|
'x509' settings to enable use of SSL and server certificates. This
|
|
|
|
ensures a data encryption preventing compromise of authentication
|
|
|
|
credentials. See the @ref{vnc_security} section for details on using
|
|
|
|
SASL authentication.
|
|
|
|
|
vnc: allow specifying a custom authorization object name
The VNC server has historically had support for ACLs to check both the
SASL username and the TLS x509 distinguished name. The VNC server was
responsible for creating the initial ACL, and the client app was then
responsible for populating it with rules using the HMP 'acl_add' command.
This is not satisfactory for a variety of reasons. There is no way to
populate the ACLs from the command line, users are forced to use the
HMP. With multiple network services all supporting TLS and ACLs now, it
is desirable to be able to define a single ACL that is referenced by all
services.
To address these limitations, two new options are added to the VNC
server CLI. The 'tls-authz' option takes the ID of a QAuthZ object to
use for checking TLS x509 distinguished names, and the 'sasl-authz'
option takes the ID of another object to use for checking SASL usernames.
In this example, we setup two authorization rules. The first allows any
client with a certificate issued by the 'RedHat' organization in the
'London' locality. The second ACL allows clients with either the
'joe@REDHAT.COM' or 'fred@REDHAT.COM' kerberos usernames. Both checks
must pass for the user to be allowed.
$QEMU -object tls-creds-x509,id=tls0,dir=/home/berrange/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-simple,id=authz0,policy=deny,\
rules.0.match=O=RedHat,,L=London,rules.0.policy=allow \
-object authz-simple,id=authz1,policy=deny,\
rules.0.match=fred@REDHAT.COM,rules.0.policy=allow \
rules.0.match=joe@REDHAT.COM,rules.0.policy=allow \
-vnc 0.0.0.0:1,tls-creds=tls0,tls-authz=authz0,
sasl,sasl-authz=authz1 \
...other QEMU args...
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20190227145755.26556-2-berrange@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2019-02-27 15:57:54 +01:00
|
|
|
@item sasl-authz=@var{ID}
|
|
|
|
|
|
|
|
Provides the ID of the QAuthZ authorization object against which
|
|
|
|
the client's SASL username will validated. This object is
|
|
|
|
only resolved at time of use, so can be deleted and recreated on the
|
|
|
|
fly while the VNC server is active. If missing, it will default
|
|
|
|
to denying access.
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
@item acl
|
|
|
|
|
vnc: allow specifying a custom authorization object name
The VNC server has historically had support for ACLs to check both the
SASL username and the TLS x509 distinguished name. The VNC server was
responsible for creating the initial ACL, and the client app was then
responsible for populating it with rules using the HMP 'acl_add' command.
This is not satisfactory for a variety of reasons. There is no way to
populate the ACLs from the command line, users are forced to use the
HMP. With multiple network services all supporting TLS and ACLs now, it
is desirable to be able to define a single ACL that is referenced by all
services.
To address these limitations, two new options are added to the VNC
server CLI. The 'tls-authz' option takes the ID of a QAuthZ object to
use for checking TLS x509 distinguished names, and the 'sasl-authz'
option takes the ID of another object to use for checking SASL usernames.
In this example, we setup two authorization rules. The first allows any
client with a certificate issued by the 'RedHat' organization in the
'London' locality. The second ACL allows clients with either the
'joe@REDHAT.COM' or 'fred@REDHAT.COM' kerberos usernames. Both checks
must pass for the user to be allowed.
$QEMU -object tls-creds-x509,id=tls0,dir=/home/berrange/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-simple,id=authz0,policy=deny,\
rules.0.match=O=RedHat,,L=London,rules.0.policy=allow \
-object authz-simple,id=authz1,policy=deny,\
rules.0.match=fred@REDHAT.COM,rules.0.policy=allow \
rules.0.match=joe@REDHAT.COM,rules.0.policy=allow \
-vnc 0.0.0.0:1,tls-creds=tls0,tls-authz=authz0,
sasl,sasl-authz=authz1 \
...other QEMU args...
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20190227145755.26556-2-berrange@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2019-02-27 15:57:54 +01:00
|
|
|
Legacy method for enabling authorization of clients against the
|
|
|
|
x509 distinguished name and SASL username. It results in the creation
|
|
|
|
of two @code{authz-list} objects with IDs of @code{vnc.username} and
|
|
|
|
@code{vnc.x509dname}. The rules for these objects must be configured
|
|
|
|
with the HMP ACL commands.
|
|
|
|
|
|
|
|
This option is deprecated and should no longer be used. The new
|
|
|
|
@option{sasl-authz} and @option{tls-authz} options are a
|
|
|
|
replacement.
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2010-07-07 20:57:51 +02:00
|
|
|
@item lossy
|
|
|
|
|
|
|
|
Enable lossy compression methods (gradient, JPEG, ...). If this
|
|
|
|
option is set, VNC client may receive lossy framebuffer updates
|
|
|
|
depending on its encoding settings. Enabling this option can save
|
|
|
|
a lot of bandwidth at the expense of quality.
|
|
|
|
|
2011-02-04 09:06:08 +01:00
|
|
|
@item non-adaptive
|
|
|
|
|
|
|
|
Disable adaptive encodings. Adaptive encodings are enabled by default.
|
|
|
|
An adaptive encoding will try to detect frequently updated screen regions,
|
|
|
|
and send updates in these regions using a lossy encoding (like JPEG).
|
2011-04-13 22:45:22 +02:00
|
|
|
This can be really helpful to save bandwidth when playing videos. Disabling
|
2014-04-07 11:34:58 +02:00
|
|
|
adaptive encodings restores the original static behavior of encodings
|
2011-02-04 09:06:08 +01:00
|
|
|
like Tight.
|
|
|
|
|
2011-11-24 18:10:49 +01:00
|
|
|
@item share=[allow-exclusive|force-shared|ignore]
|
|
|
|
|
|
|
|
Set display sharing policy. 'allow-exclusive' allows clients to ask
|
|
|
|
for exclusive access. As suggested by the rfb spec this is
|
|
|
|
implemented by dropping other connections. Connecting multiple
|
|
|
|
clients in parallel requires all clients asking for a shared session
|
|
|
|
(vncviewer: -shared switch). This is the default. 'force-shared'
|
|
|
|
disables exclusive client access. Useful for shared desktop sessions,
|
|
|
|
where you don't want someone forgetting specify -shared disconnect
|
|
|
|
everybody else. 'ignore' completely ignores the shared flag and
|
|
|
|
allows everybody connect unconditionally. Doesn't conform to the rfb
|
2012-05-11 22:25:50 +02:00
|
|
|
spec but is traditional QEMU behavior.
|
2011-11-24 18:10:49 +01:00
|
|
|
|
2016-06-01 08:22:30 +02:00
|
|
|
@item key-delay-ms
|
|
|
|
|
|
|
|
Set keyboard delay, for key down and key up events, in milliseconds.
|
2017-07-12 14:43:45 +02:00
|
|
|
Default is 10. Keyboards are low-bandwidth devices, so this slowdown
|
2016-06-01 08:22:30 +02:00
|
|
|
can help the device and guest to keep up and not lose events in case
|
|
|
|
events are arriving in bulk. Possible causes for the latter are flaky
|
|
|
|
network connections, or scripts for automated testing.
|
|
|
|
|
2019-08-19 01:06:48 +02:00
|
|
|
@item audiodev=@var{audiodev}
|
|
|
|
|
|
|
|
Use the specified @var{audiodev} when the VNC client requests audio
|
|
|
|
transmission. When not using an -audiodev argument, this option must
|
|
|
|
be omitted, otherwise is must be present and specify a valid audiodev.
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
2011-12-19 07:19:31 +01:00
|
|
|
ARCHHEADING(, QEMU_ARCH_I386)
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
ARCHHEADING(i386 target only:, QEMU_ARCH_I386)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("win2k-hack", 0, QEMU_OPTION_win2k_hack,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-win2k-hack use it when installing Windows 2000 to avoid a disk full bug\n",
|
|
|
|
QEMU_ARCH_I386)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -win2k-hack
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -win2k-hack
|
2009-03-28 07:44:27 +01:00
|
|
|
Use it when installing Windows 2000 to avoid a disk full bug. After
|
|
|
|
Windows 2000 is installed, you no longer need this option (this option
|
|
|
|
slows down the IDE transfers).
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-fd-bootchk", 0, QEMU_OPTION_no_fd_bootchk,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-no-fd-bootchk disable boot signature checking for floppy disks\n",
|
|
|
|
QEMU_ARCH_I386)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -no-fd-bootchk
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -no-fd-bootchk
|
2013-06-14 13:15:06 +02:00
|
|
|
Disable boot signature checking for floppy disks in BIOS. May
|
2009-03-28 07:44:27 +01:00
|
|
|
be needed to boot from old floppy disks.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-acpi", 0, QEMU_OPTION_no_acpi,
|
2015-05-29 12:28:54 +02:00
|
|
|
"-no-acpi disable ACPI\n", QEMU_ARCH_I386 | QEMU_ARCH_ARM)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -no-acpi
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -no-acpi
|
2009-03-28 07:44:27 +01:00
|
|
|
Disable ACPI (Advanced Configuration and Power Interface) support. Use
|
|
|
|
it if your guest OS complains about ACPI problems (PC target machine
|
|
|
|
only).
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-hpet", 0, QEMU_OPTION_no_hpet,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-no-hpet disable HPET\n", QEMU_ARCH_I386)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -no-hpet
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -no-hpet
|
2009-03-28 07:44:27 +01:00
|
|
|
Disable HPET support.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("acpitable", HAS_ARG, QEMU_OPTION_acpitable,
|
2011-05-12 16:44:17 +02:00
|
|
|
"-acpitable [sig=str][,rev=n][,oem_id=str][,oem_table_id=str][,oem_rev=n][,asl_compiler_id=str][,asl_compiler_rev=n][,{data|file}=file1[:file2]...]\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" ACPI table description\n", QEMU_ARCH_I386)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -acpitable [sig=@var{str}][,rev=@var{n}][,oem_id=@var{str}][,oem_table_id=@var{str}][,oem_rev=@var{n}] [,asl_compiler_id=@var{str}][,asl_compiler_rev=@var{n}][,data=@var{file1}[:@var{file2}]...]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -acpitable
|
2009-03-28 07:44:27 +01:00
|
|
|
Add ACPI table with specified header fields and context from specified files.
|
2011-05-12 16:44:17 +02:00
|
|
|
For file=, take whole ACPI table from the specified files, including all
|
|
|
|
ACPI headers (possible overridden by other options).
|
|
|
|
For data=, only data
|
|
|
|
portion of the table is used, all header information is specified in the
|
|
|
|
command line.
|
2016-01-18 15:12:13 +01:00
|
|
|
If a SLIC table is supplied to QEMU, then the SLIC's oem_id and oem_table_id
|
|
|
|
fields will override the same in the RSDT and the FADT (a.k.a. FACP), in order
|
|
|
|
to ensure the field matches required by the Microsoft SLIC spec and the ACPI
|
|
|
|
spec.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
DEF("smbios", HAS_ARG, QEMU_OPTION_smbios,
|
|
|
|
"-smbios file=binary\n"
|
2010-01-06 20:33:57 +01:00
|
|
|
" load SMBIOS entry from binary file\n"
|
2015-02-05 17:45:30 +01:00
|
|
|
"-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]\n"
|
|
|
|
" [,uefi=on|off]\n"
|
2010-01-06 20:33:57 +01:00
|
|
|
" specify SMBIOS type 0 fields\n"
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
"-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]\n"
|
|
|
|
" [,uuid=uuid][,sku=str][,family=str]\n"
|
2015-02-05 17:45:30 +01:00
|
|
|
" specify SMBIOS type 1 fields\n"
|
|
|
|
"-smbios type=2[,manufacturer=str][,product=str][,version=str][,serial=str]\n"
|
|
|
|
" [,asset=str][,location=str]\n"
|
|
|
|
" specify SMBIOS type 2 fields\n"
|
|
|
|
"-smbios type=3[,manufacturer=str][,version=str][,serial=str][,asset=str]\n"
|
|
|
|
" [,sku=str]\n"
|
|
|
|
" specify SMBIOS type 3 fields\n"
|
|
|
|
"-smbios type=4[,sock_pfx=str][,manufacturer=str][,version=str][,serial=str]\n"
|
|
|
|
" [,asset=str][,part=str]\n"
|
|
|
|
" specify SMBIOS type 4 fields\n"
|
|
|
|
"-smbios type=17[,loc_pfx=str][,bank=str][,manufacturer=str][,serial=str]\n"
|
2015-03-11 18:58:01 +01:00
|
|
|
" [,asset=str][,part=str][,speed=%d]\n"
|
2015-02-05 17:45:30 +01:00
|
|
|
" specify SMBIOS type 17 fields\n",
|
2015-09-07 11:39:29 +02:00
|
|
|
QEMU_ARCH_I386 | QEMU_ARCH_ARM)
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
STEXI
|
|
|
|
@item -smbios file=@var{binary}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -smbios
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
Load SMBIOS entry from binary file.
|
|
|
|
|
2014-05-19 16:09:54 +02:00
|
|
|
@item -smbios type=0[,vendor=@var{str}][,version=@var{str}][,date=@var{str}][,release=@var{%d.%d}][,uefi=on|off]
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
Specify SMBIOS type 0 fields
|
|
|
|
|
2015-02-05 17:45:30 +01:00
|
|
|
@item -smbios type=1[,manufacturer=@var{str}][,product=@var{str}][,version=@var{str}][,serial=@var{str}][,uuid=@var{uuid}][,sku=@var{str}][,family=@var{str}]
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
Specify SMBIOS type 1 fields
|
2015-02-05 17:45:30 +01:00
|
|
|
|
2019-05-21 16:23:31 +02:00
|
|
|
@item -smbios type=2[,manufacturer=@var{str}][,product=@var{str}][,version=@var{str}][,serial=@var{str}][,asset=@var{str}][,location=@var{str}]
|
2015-02-05 17:45:30 +01:00
|
|
|
Specify SMBIOS type 2 fields
|
|
|
|
|
|
|
|
@item -smbios type=3[,manufacturer=@var{str}][,version=@var{str}][,serial=@var{str}][,asset=@var{str}][,sku=@var{str}]
|
|
|
|
Specify SMBIOS type 3 fields
|
|
|
|
|
|
|
|
@item -smbios type=4[,sock_pfx=@var{str}][,manufacturer=@var{str}][,version=@var{str}][,serial=@var{str}][,asset=@var{str}][,part=@var{str}]
|
|
|
|
Specify SMBIOS type 4 fields
|
|
|
|
|
2015-03-11 18:58:01 +01:00
|
|
|
@item -smbios type=17[,loc_pfx=@var{str}][,bank=@var{str}][,manufacturer=@var{str}][,serial=@var{str}][,asset=@var{str}][,part=@var{str}][,speed=@var{%d}]
|
2015-02-05 17:45:30 +01:00
|
|
|
Specify SMBIOS type 17 fields
|
qemu: Add support for SMBIOS command line otions (Alex Williamson)
Create a new -smbios option (x86-only) to allow binary SMBIOS entries
to be passed through to the BIOS or modify the default values of
individual fields of type 0 and 1 entries on the command line.
Binary SMBIOS entries can be generated as follows:
dmidecode -t 1 -u | grep $'^\t\t[^"]' | xargs -n1 | \
perl -lne 'printf "%c", hex($_)' > smbios_type_1.bin
These can then be passed to the BIOS using this switch:
-smbios file=smbios_type_1.bin
Command line generation supports the following syntax:
-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
[,uuid=$(uuidgen)][,sku=str][,family=str]
For instance, to add a serial number to the type 1 table:
-smbios type=1,serial=0123456789
Interface is extensible to support more fields/tables as needed.
aliguori: remove texi formatting from help output
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@7163 c046a42c-6fe2-441c-8c8c-71466251a162
2009-04-17 20:59:56 +02:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
2013-02-13 19:49:40 +01:00
|
|
|
DEFHEADING()
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Network options:)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
2015-05-15 16:58:24 +02:00
|
|
|
DEF("netdev", HAS_ARG, QEMU_OPTION_netdev,
|
2009-03-28 07:44:27 +01:00
|
|
|
#ifdef CONFIG_SLIRP
|
2016-03-20 12:29:54 +01:00
|
|
|
"-netdev user,id=str[,ipv4[=on|off]][,net=addr[/mask]][,host=addr]\n"
|
|
|
|
" [,ipv6[=on|off]][,ipv6-net=addr[/int]][,ipv6-host=addr]\n"
|
|
|
|
" [,restrict=on|off][,hostname=host][,dhcpstart=addr]\n"
|
2018-02-27 17:06:01 +01:00
|
|
|
" [,dns=addr][,ipv6-dns=addr][,dnssearch=domain][,domainname=domain]\n"
|
2018-09-14 09:26:16 +02:00
|
|
|
" [,tftp=dir][,tftp-server-name=name][,bootfile=f][,hostfwd=rule][,guestfwd=rule]"
|
2009-06-24 14:42:28 +02:00
|
|
|
#ifndef _WIN32
|
2009-06-24 14:42:28 +02:00
|
|
|
"[,smb=dir[,smbserver=addr]]\n"
|
2009-06-24 14:42:28 +02:00
|
|
|
#endif
|
2015-05-15 16:58:24 +02:00
|
|
|
" configure a user mode network backend with ID 'str',\n"
|
|
|
|
" its DHCP server and optional services\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
#endif
|
|
|
|
#ifdef _WIN32
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev tap,id=str,ifname=name\n"
|
|
|
|
" configure a host TAP network backend with ID 'str'\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
#else
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev tap,id=str[,fd=h][,fds=x:y:...:z][,ifname=name][,script=file][,downscript=dfile]\n"
|
2016-09-13 09:11:54 +02:00
|
|
|
" [,br=bridge][,helper=helper][,sndbuf=nbytes][,vnet_hdr=on|off][,vhost=on|off]\n"
|
2015-05-15 16:58:24 +02:00
|
|
|
" [,vhostfd=h][,vhostfds=x:y:...:z][,vhostforce=on|off][,queues=n]\n"
|
2016-07-06 03:57:55 +02:00
|
|
|
" [,poll-us=n]\n"
|
2015-05-15 16:58:24 +02:00
|
|
|
" configure a host TAP network backend with ID 'str'\n"
|
2016-09-13 09:11:54 +02:00
|
|
|
" connected to a bridge (default=" DEFAULT_BRIDGE_INTERFACE ")\n"
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
" use network scripts 'file' (default=" DEFAULT_NETWORK_SCRIPT ")\n"
|
|
|
|
" to configure it and 'dfile' (default=" DEFAULT_NETWORK_DOWN_SCRIPT ")\n"
|
|
|
|
" to deconfigure it\n"
|
2010-01-06 20:33:57 +01:00
|
|
|
" use '[down]script=no' to disable script execution\n"
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
" use network helper 'helper' (default=" DEFAULT_BRIDGE_HELPER ") to\n"
|
|
|
|
" configure it\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
" use 'fd=h' to connect to an already opened TAP interface\n"
|
2013-02-20 11:04:01 +01:00
|
|
|
" use 'fds=x:y:...:z' to connect to already opened multiqueue capable TAP interfaces\n"
|
2010-01-06 20:33:57 +01:00
|
|
|
" use 'sndbuf=nbytes' to limit the size of the send buffer (the\n"
|
2011-02-01 13:25:40 +01:00
|
|
|
" default is disabled 'sndbuf=0' to enable flow control set 'sndbuf=1048576')\n"
|
2010-01-06 20:33:57 +01:00
|
|
|
" use vnet_hdr=off to avoid enabling the IFF_VNET_HDR tap flag\n"
|
|
|
|
" use vnet_hdr=on to make the lack of IFF_VNET_HDR support an error condition\n"
|
2010-03-17 12:08:24 +01:00
|
|
|
" use vhost=on to enable experimental in kernel accelerator\n"
|
2011-02-01 21:13:42 +01:00
|
|
|
" (only has effect for virtio guests which use MSIX)\n"
|
|
|
|
" use vhostforce=on to force vhost on for non-MSIX virtio guests\n"
|
2010-03-17 12:08:24 +01:00
|
|
|
" use 'vhostfd=h' to connect to an already opened vhost net device\n"
|
2013-02-20 11:04:01 +01:00
|
|
|
" use 'vhostfds=x:y:...:z to connect to multiple already opened vhost net devices\n"
|
2013-02-22 15:57:52 +01:00
|
|
|
" use 'queues=n' to specify the number of queues to be created for multiqueue TAP\n"
|
2016-07-06 03:57:55 +02:00
|
|
|
" use 'poll-us=n' to speciy the maximum number of microseconds that could be\n"
|
|
|
|
" spent on busy polling for vhost net\n"
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev bridge,id=str[,br=bridge][,helper=helper]\n"
|
|
|
|
" configure a host TAP network backend with ID 'str' that is\n"
|
|
|
|
" connected to a bridge (default=" DEFAULT_BRIDGE_INTERFACE ")\n"
|
|
|
|
" using the program 'helper (default=" DEFAULT_BRIDGE_HELPER ")\n"
|
2014-06-20 11:34:41 +02:00
|
|
|
#endif
|
|
|
|
#ifdef __linux__
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev l2tpv3,id=str,src=srcaddr,dst=dstaddr[,srcport=srcport][,dstport=dstport]\n"
|
|
|
|
" [,rxsession=rxsession],txsession=txsession[,ipv6=on/off][,udp=on/off]\n"
|
|
|
|
" [,cookie64=on/off][,counter][,pincounter][,txcookie=txcookie]\n"
|
|
|
|
" [,rxcookie=rxcookie][,offset=offset]\n"
|
|
|
|
" configure a network backend with ID 'str' connected to\n"
|
|
|
|
" an Ethernet over L2TPv3 pseudowire.\n"
|
2014-06-20 11:34:41 +02:00
|
|
|
" Linux kernel 3.3+ as well as most routers can talk\n"
|
2014-07-24 18:10:17 +02:00
|
|
|
" L2TPv3. This transport allows connecting a VM to a VM,\n"
|
2014-06-20 11:34:41 +02:00
|
|
|
" VM to a router and even VM to Host. It is a nearly-universal\n"
|
|
|
|
" standard (RFC3391). Note - this implementation uses static\n"
|
|
|
|
" pre-configured tunnels (same as the Linux kernel).\n"
|
|
|
|
" use 'src=' to specify source address\n"
|
|
|
|
" use 'dst=' to specify destination address\n"
|
|
|
|
" use 'udp=on' to specify udp encapsulation\n"
|
2014-08-14 08:35:48 +02:00
|
|
|
" use 'srcport=' to specify source udp port\n"
|
2014-06-20 11:34:41 +02:00
|
|
|
" use 'dstport=' to specify destination udp port\n"
|
|
|
|
" use 'ipv6=on' to force v6\n"
|
|
|
|
" L2TPv3 uses cookies to prevent misconfiguration as\n"
|
|
|
|
" well as a weak security measure\n"
|
|
|
|
" use 'rxcookie=0x012345678' to specify a rxcookie\n"
|
|
|
|
" use 'txcookie=0x012345678' to specify a txcookie\n"
|
|
|
|
" use 'cookie64=on' to set cookie size to 64 bit, otherwise 32\n"
|
|
|
|
" use 'counter=off' to force a 'cut-down' L2TPv3 with no counter\n"
|
|
|
|
" use 'pincounter=on' to work around broken counter handling in peer\n"
|
|
|
|
" use 'offset=X' to add an extra offset between header and data\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
#endif
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev socket,id=str[,fd=h][,listen=[host]:port][,connect=host:port]\n"
|
|
|
|
" configure a network backend to connect to another network\n"
|
|
|
|
" using a socket connection\n"
|
|
|
|
"-netdev socket,id=str[,fd=h][,mcast=maddr:port[,localaddr=addr]]\n"
|
|
|
|
" configure a network backend to connect to a multicast maddr and port\n"
|
2010-12-01 20:16:47 +01:00
|
|
|
" use 'localaddr=addr' to specify the host address to send packets from\n"
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev socket,id=str[,fd=h][,udp=host:port][,localaddr=host:port]\n"
|
|
|
|
" configure a network backend to connect to another network\n"
|
|
|
|
" using an UDP tunnel\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
#ifdef CONFIG_VDE
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev vde,id=str[,sock=socketpath][,port=n][,group=groupname][,mode=octalmode]\n"
|
|
|
|
" configure a network backend to connect to port 'n' of a vde switch\n"
|
|
|
|
" running on host and listening for incoming connections on 'socketpath'.\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
" Use group 'groupname' and mode 'octalmode' to change default\n"
|
|
|
|
" ownership and permissions for communication port.\n"
|
2013-11-06 11:44:06 +01:00
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_NETMAP
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev netmap,id=str,ifname=name[,devname=nmname]\n"
|
2013-11-06 11:44:06 +01:00
|
|
|
" attach to the existing netmap-enabled network interface 'name', or to a\n"
|
|
|
|
" VALE port (created on the fly) called 'name' ('nmname' is name of the \n"
|
|
|
|
" netmap device, defaults to '/dev/netmap')\n"
|
2009-03-28 07:44:27 +01:00
|
|
|
#endif
|
2018-02-21 11:18:32 +01:00
|
|
|
#ifdef CONFIG_POSIX
|
2015-05-15 16:58:24 +02:00
|
|
|
"-netdev vhost-user,id=str,chardev=dev[,vhostforce=on|off]\n"
|
|
|
|
" configure a vhost-user network, backed by a chardev 'dev'\n"
|
2018-02-21 11:18:32 +01:00
|
|
|
#endif
|
net: Allow hubports to connect to other netdevs
QEMU can emulate hubs to connect NICs and netdevs. This is currently
primarily used for the mis-named 'vlan' feature of the networking
subsystem. Now the 'vlan' feature has been marked as deprecated, since
its name is rather confusing and the users often rather mis-configure
their network when trying to use it. But while the 'vlan' parameter
should be removed at one point in time, the basic idea of emulating
a hub in QEMU is still good: It's useful for bundling up the output of
multiple NICs into one single l2tp netdev for example.
Now to be able to use the hubport feature without 'vlan's, there is one
missing piece: The possibility to connect a hubport to a netdev, too.
This patch adds this possibility by introducing a new "netdev=..."
parameter to the hubports.
To bundle up the output of multiple NICs into one socket netdev, you can
now run QEMU with these parameters for example:
qemu-system-ppc64 ... -netdev socket,id=s1,connect=:11122 \
-netdev hubport,hubid=1,id=h1,netdev=s1 \
-netdev hubport,hubid=1,id=h2 -device e1000,netdev=h2 \
-netdev hubport,hubid=1,id=h3 -device virtio-net-pci,netdev=h3
For using the socket netdev, you have got to start another QEMU as the
receiving side first, for example with network dumping enabled:
qemu-system-x86_64 -M isapc -netdev socket,id=s0,listen=:11122 \
-device ne2k_isa,netdev=s0 \
-object filter-dump,id=f1,netdev=s0,file=/tmp/dump.dat
After the ppc64 guest tried to boot from both NICs, you can see in the
dump file (using Wireshark, for example), that the output of both NICs
(the e1000 and the virtio-net-pci) has been successfully transfered
via the socket netdev in this case.
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2018-01-15 20:50:55 +01:00
|
|
|
"-netdev hubport,id=str,hubid=n[,netdev=nd]\n"
|
2018-04-30 20:02:23 +02:00
|
|
|
" configure a hub port on the hub with ID 'n'\n", QEMU_ARCH_ALL)
|
2018-02-21 11:18:36 +01:00
|
|
|
DEF("nic", HAS_ARG, QEMU_OPTION_nic,
|
2018-07-16 21:12:08 +02:00
|
|
|
"-nic [tap|bridge|"
|
2018-02-21 11:18:36 +01:00
|
|
|
#ifdef CONFIG_SLIRP
|
|
|
|
"user|"
|
|
|
|
#endif
|
|
|
|
#ifdef __linux__
|
|
|
|
"l2tpv3|"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_VDE
|
|
|
|
"vde|"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_NETMAP
|
|
|
|
"netmap|"
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_POSIX
|
|
|
|
"vhost-user|"
|
|
|
|
#endif
|
|
|
|
"socket][,option][,...][mac=macaddr]\n"
|
|
|
|
" initialize an on-board / default host NIC (using MAC address\n"
|
|
|
|
" macaddr) and connect it to the given host network backend\n"
|
2018-07-16 21:12:08 +02:00
|
|
|
"-nic none use it alone to have zero network devices (the default is to\n"
|
2018-02-21 11:18:36 +01:00
|
|
|
" provided a 'user' network connection)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2015-05-15 16:58:24 +02:00
|
|
|
DEF("net", HAS_ARG, QEMU_OPTION_net,
|
2018-04-30 20:02:23 +02:00
|
|
|
"-net nic[,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]\n"
|
2017-12-19 16:28:55 +01:00
|
|
|
" configure or create an on-board (or machine default) NIC and\n"
|
2018-04-30 20:02:23 +02:00
|
|
|
" connect it to hub 0 (please use -nic unless you need a hub)\n"
|
2015-05-15 16:58:24 +02:00
|
|
|
"-net ["
|
2009-10-08 20:58:26 +02:00
|
|
|
#ifdef CONFIG_SLIRP
|
|
|
|
"user|"
|
|
|
|
#endif
|
|
|
|
"tap|"
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
"bridge|"
|
2009-10-08 20:58:26 +02:00
|
|
|
#ifdef CONFIG_VDE
|
|
|
|
"vde|"
|
2013-11-06 11:44:06 +01:00
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_NETMAP
|
|
|
|
"netmap|"
|
2009-10-08 20:58:26 +02:00
|
|
|
#endif
|
2018-04-30 20:02:23 +02:00
|
|
|
"socket][,option][,option][,...]\n"
|
2015-05-15 16:58:24 +02:00
|
|
|
" old way to initialize a host network interface\n"
|
|
|
|
" (use the -netdev option if possible instead)\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2018-03-12 13:20:50 +01:00
|
|
|
@item -nic [tap|bridge|user|l2tpv3|vde|netmap|vhost-user|socket][,...][,mac=macaddr][,model=mn]
|
|
|
|
@findex -nic
|
|
|
|
This option is a shortcut for configuring both the on-board (default) guest
|
|
|
|
NIC hardware and the host network backend in one go. The host backend options
|
|
|
|
are the same as with the corresponding @option{-netdev} options below.
|
|
|
|
The guest NIC model can be set with @option{model=@var{modelname}}.
|
|
|
|
Use @option{model=help} to list the available device types.
|
|
|
|
The hardware MAC address can be set with @option{mac=@var{macaddr}}.
|
|
|
|
|
|
|
|
The following two example do exactly the same, to show how @option{-nic} can
|
|
|
|
be used to shorten the command line length (note that the e1000 is the default
|
|
|
|
on i386, so the @option{model=e1000} parameter could even be omitted here, too):
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -netdev user,id=n1,ipv6=off -device e1000,netdev=n1,mac=52:54:98:76:54:32
|
|
|
|
qemu-system-i386 -nic user,ipv6=off,model=e1000,mac=52:54:98:76:54:32
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@item -nic none
|
|
|
|
Indicate that no network devices should be configured. It is used to override
|
|
|
|
the default configuration (default NIC with ``user'' host network backend)
|
|
|
|
which is activated if no other networking options are provided.
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2012-08-14 15:14:27 +02:00
|
|
|
@item -netdev user,id=@var{id}[,@var{option}][,@var{option}][,...]
|
2013-02-13 19:49:38 +01:00
|
|
|
@findex -netdev
|
2018-03-12 13:20:50 +01:00
|
|
|
Configure user mode host network backend which requires no administrator
|
2009-06-24 14:42:28 +02:00
|
|
|
privilege to run. Valid options are:
|
|
|
|
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2012-08-14 15:14:27 +02:00
|
|
|
@item id=@var{id}
|
2009-06-24 14:42:28 +02:00
|
|
|
Assign symbolic name for use in monitor commands.
|
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
@item ipv4=on|off and ipv6=on|off
|
|
|
|
Specify that either IPv4 or IPv6 must be enabled. If neither is specified
|
|
|
|
both protocols are enabled.
|
2016-03-20 12:29:54 +01:00
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item net=@var{addr}[/@var{mask}]
|
|
|
|
Set IP network address the guest will see. Optionally specify the netmask,
|
|
|
|
either in the form a.b.c.d or as number of valid top-most bits. Default is
|
2011-04-24 09:19:56 +02:00
|
|
|
10.0.2.0/24.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
|
|
|
@item host=@var{addr}
|
|
|
|
Specify the guest-visible address of the host. Default is the 2nd IP in the
|
|
|
|
guest network, i.e. x.x.x.2.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
2016-03-25 00:02:58 +01:00
|
|
|
@item ipv6-net=@var{addr}[/@var{int}]
|
|
|
|
Set IPv6 network address the guest will see (default is fec0::/64). The
|
|
|
|
network prefix is given in the usual hexadecimal IPv6 address
|
|
|
|
notation. The prefix size is optional, and is given as the number of
|
|
|
|
valid top-most bits (default is 64).
|
2016-03-15 10:31:22 +01:00
|
|
|
|
2016-03-25 00:02:58 +01:00
|
|
|
@item ipv6-host=@var{addr}
|
2016-03-15 10:31:22 +01:00
|
|
|
Specify the guest-visible IPv6 address of the host. Default is the 2nd IPv6 in
|
|
|
|
the guest network, i.e. xxxx::2.
|
|
|
|
|
2011-07-20 12:20:14 +02:00
|
|
|
@item restrict=on|off
|
2011-06-08 23:50:43 +02:00
|
|
|
If this option is enabled, the guest will be isolated, i.e. it will not be
|
2009-06-24 14:42:28 +02:00
|
|
|
able to contact the host and no guest IP packets will be routed over the host
|
2011-06-08 23:50:43 +02:00
|
|
|
to the outside. This option does not affect any explicitly set forwarding rules.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
|
|
|
@item hostname=@var{name}
|
2012-10-27 19:53:39 +02:00
|
|
|
Specifies the client hostname reported by the built-in DHCP server.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item dhcpstart=@var{addr}
|
|
|
|
Specify the first of the 16 IPs the built-in DHCP server can assign. Default
|
2011-04-24 09:19:56 +02:00
|
|
|
is the 15th to 31st IP in the guest network, i.e. x.x.x.15 to x.x.x.31.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
|
|
|
@item dns=@var{addr}
|
|
|
|
Specify the guest-visible address of the virtual nameserver. The address must
|
|
|
|
be different from the host address. Default is the 3rd IP in the guest network,
|
|
|
|
i.e. x.x.x.3.
|
2016-03-15 10:31:22 +01:00
|
|
|
|
2016-03-25 00:02:58 +01:00
|
|
|
@item ipv6-dns=@var{addr}
|
2016-03-15 10:31:22 +01:00
|
|
|
Specify the guest-visible address of the IPv6 virtual nameserver. The address
|
|
|
|
must be different from the host address. Default is the 3rd IP in the guest
|
|
|
|
network, i.e. xxxx::3.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
2012-10-27 19:53:39 +02:00
|
|
|
@item dnssearch=@var{domain}
|
|
|
|
Provides an entry for the domain-search list sent by the built-in
|
|
|
|
DHCP server. More than one domain suffix can be transmitted by specifying
|
|
|
|
this option multiple times. If supported, this will cause the guest to
|
|
|
|
automatically try to append the given domain suffix(es) in case a domain name
|
|
|
|
can not be resolved.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 -nic user,dnssearch=mgmt.example.org,dnssearch=example.org
|
2012-10-27 19:53:39 +02:00
|
|
|
@end example
|
|
|
|
|
2018-02-27 17:06:01 +01:00
|
|
|
@item domainname=@var{domain}
|
|
|
|
Specifies the client domain name reported by the built-in DHCP server.
|
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item tftp=@var{dir}
|
|
|
|
When using the user mode network stack, activate a built-in TFTP
|
|
|
|
server. The files in @var{dir} will be exposed as the root of a TFTP server.
|
|
|
|
The TFTP client on the guest must be configured in binary mode (use the command
|
2009-06-24 14:42:28 +02:00
|
|
|
@code{bin} of the Unix TFTP client).
|
2009-06-24 14:42:28 +02:00
|
|
|
|
2018-09-14 09:26:16 +02:00
|
|
|
@item tftp-server-name=@var{name}
|
|
|
|
In BOOTP reply, broadcast @var{name} as the "TFTP server name" (RFC2132 option
|
|
|
|
66). This can be used to advise the guest to load boot files or configurations
|
|
|
|
from a different server than the host address.
|
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item bootfile=@var{file}
|
|
|
|
When using the user mode network stack, broadcast @var{file} as the BOOTP
|
|
|
|
filename. In conjunction with @option{tftp}, this can be used to network boot
|
|
|
|
a guest from a local directory.
|
|
|
|
|
|
|
|
Example (using pxelinux):
|
|
|
|
@example
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 -hda linux.img -boot n -device e1000,netdev=n1 \
|
|
|
|
-netdev user,id=n1,tftp=/path/to/tftp/files,bootfile=/pxelinux.0
|
2009-06-24 14:42:28 +02:00
|
|
|
@end example
|
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item smb=@var{dir}[,smbserver=@var{addr}]
|
2009-06-24 14:42:28 +02:00
|
|
|
When using the user mode network stack, activate a built-in SMB
|
|
|
|
server so that Windows OSes can access to the host files in @file{@var{dir}}
|
2009-06-24 14:42:28 +02:00
|
|
|
transparently. The IP address of the SMB server can be set to @var{addr}. By
|
|
|
|
default the 4th IP in the guest network is used, i.e. x.x.x.4.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
|
|
|
In the guest Windows OS, the line:
|
|
|
|
@example
|
|
|
|
10.0.2.4 smbserver
|
|
|
|
@end example
|
|
|
|
must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me)
|
|
|
|
or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000).
|
|
|
|
|
|
|
|
Then @file{@var{dir}} can be accessed in @file{\\smbserver\qemu}.
|
|
|
|
|
2011-09-02 22:53:28 +02:00
|
|
|
Note that a SAMBA server must be installed on the host OS.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item hostfwd=[tcp|udp]:[@var{hostaddr}]:@var{hostport}-[@var{guestaddr}]:@var{guestport}
|
2009-06-24 14:42:28 +02:00
|
|
|
Redirect incoming TCP or UDP connections to the host port @var{hostport} to
|
|
|
|
the guest IP address @var{guestaddr} on guest port @var{guestport}. If
|
|
|
|
@var{guestaddr} is not specified, its value is x.x.x.15 (default first address
|
2009-06-24 14:42:28 +02:00
|
|
|
given by the built-in DHCP server). By specifying @var{hostaddr}, the rule can
|
|
|
|
be bound to a specific host interface. If no connection type is set, TCP is
|
2009-06-24 14:42:28 +02:00
|
|
|
used. This option can be given multiple times.
|
2009-06-24 14:42:28 +02:00
|
|
|
|
|
|
|
For example, to redirect host X11 connection from screen 1 to guest
|
|
|
|
screen 0, use the following:
|
|
|
|
|
|
|
|
@example
|
|
|
|
# on the host
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 -nic user,hostfwd=tcp:127.0.0.1:6001-:6000
|
2009-06-24 14:42:28 +02:00
|
|
|
# this host xterm should open in the guest X11 server
|
|
|
|
xterm -display :1
|
|
|
|
@end example
|
|
|
|
|
|
|
|
To redirect telnet connections from host port 5555 to telnet port on
|
|
|
|
the guest, use the following:
|
|
|
|
|
|
|
|
@example
|
|
|
|
# on the host
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 -nic user,hostfwd=tcp::5555-:23
|
2009-06-24 14:42:28 +02:00
|
|
|
telnet localhost 5555
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Then when you use on the host @code{telnet localhost 5555}, you
|
|
|
|
connect to the guest telnet server.
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2009-06-24 14:42:28 +02:00
|
|
|
@item guestfwd=[tcp]:@var{server}:@var{port}-@var{dev}
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx guestfwd=[tcp]:@var{server}:@var{port}-@var{cmd:command}
|
2009-06-24 14:42:28 +02:00
|
|
|
Forward guest TCP connections to the IP address @var{server} on port @var{port}
|
2012-06-03 09:45:01 +02:00
|
|
|
to the character device @var{dev} or to a program executed by @var{cmd:command}
|
|
|
|
which gets spawned for each connection. This option can be given multiple times.
|
|
|
|
|
2012-07-20 23:26:02 +02:00
|
|
|
You can either use a chardev directly and have that one used throughout QEMU's
|
2012-06-03 09:45:01 +02:00
|
|
|
lifetime, like in the following example:
|
|
|
|
|
|
|
|
@example
|
|
|
|
# open 10.10.1.1:4321 on bootup, connect 10.0.2.100:1234 to it whenever
|
|
|
|
# the guest accesses it
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 -nic user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321
|
2012-06-03 09:45:01 +02:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Or you can execute a command on every TCP connection established by the guest,
|
2012-07-20 23:26:02 +02:00
|
|
|
so that QEMU behaves similar to an inetd process for that virtual server:
|
2012-06-03 09:45:01 +02:00
|
|
|
|
|
|
|
@example
|
|
|
|
# call "netcat 10.10.1.1 4321" on every TCP connection to 10.0.2.100:1234
|
|
|
|
# and connect the TCP stream to its stdin/stdout
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 -nic 'user,id=n1,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321'
|
2012-06-03 09:45:01 +02:00
|
|
|
@end example
|
2009-06-24 14:42:28 +02:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2016-09-13 09:11:54 +02:00
|
|
|
@item -netdev tap,id=@var{id}[,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,br=@var{bridge}][,helper=@var{helper}]
|
2018-03-12 13:20:50 +01:00
|
|
|
Configure a host TAP network backend with ID @var{id}.
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
|
|
|
|
Use the network script @var{file} to configure it and the network script
|
2009-03-28 07:44:27 +01:00
|
|
|
@var{dfile} to deconfigure it. If @var{name} is not provided, the OS
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
automatically provides one. The default network configure script is
|
|
|
|
@file{/etc/qemu-ifup} and the default network deconfigure script is
|
|
|
|
@file{/etc/qemu-ifdown}. Use @option{script=no} or @option{downscript=no}
|
|
|
|
to disable script execution.
|
|
|
|
|
|
|
|
If running QEMU as an unprivileged user, use the network helper
|
2016-09-13 09:11:54 +02:00
|
|
|
@var{helper} to configure the TAP interface and attach it to the bridge.
|
|
|
|
The default network helper executable is @file{/path/to/qemu-bridge-helper}
|
|
|
|
and the default bridge device is @file{br0}.
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
|
|
|
|
@option{fd}=@var{h} can be used to specify the handle of an already
|
|
|
|
opened host TAP interface.
|
|
|
|
|
|
|
|
Examples:
|
2009-03-28 07:44:27 +01:00
|
|
|
|
|
|
|
@example
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
#launch a QEMU instance with the default network script
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 linux.img -nic tap
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
|
|
|
@example
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
#launch a QEMU instance with two NICs, each one connected
|
|
|
|
#to a TAP device
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-01-15 08:40:17 +01:00
|
|
|
-netdev tap,id=nd0,ifname=tap0 -device e1000,netdev=nd0 \
|
|
|
|
-netdev tap,id=nd1,ifname=tap1 -device rtl8139,netdev=nd1
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
@example
|
|
|
|
#launch a QEMU instance with the default network helper to
|
|
|
|
#connect a TAP device to bridge br0
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 linux.img -device virtio-net-pci,netdev=n1 \
|
|
|
|
-netdev tap,id=n1,"helper=/path/to/qemu-bridge-helper"
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 15:14:27 +02:00
|
|
|
@item -netdev bridge,id=@var{id}[,br=@var{bridge}][,helper=@var{helper}]
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
Connect a host TAP network interface to a host bridge device.
|
|
|
|
|
|
|
|
Use the network helper @var{helper} to configure the TAP interface and
|
|
|
|
attach it to the bridge. The default network helper executable is
|
2013-10-22 22:49:28 +02:00
|
|
|
@file{/path/to/qemu-bridge-helper} and the default bridge
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
device is @file{br0}.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
@example
|
|
|
|
#launch a QEMU instance with the default network helper to
|
|
|
|
#connect a TAP device to bridge br0
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 linux.img -netdev bridge,id=n1 -device virtio-net,netdev=n1
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
@end example
|
|
|
|
|
|
|
|
@example
|
|
|
|
#launch a QEMU instance with the default network helper to
|
|
|
|
#connect a TAP device to bridge qemubr0
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 linux.img -netdev bridge,br=qemubr0,id=n1 -device virtio-net,netdev=n1
|
Add support for net bridge
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's incredibly
difficult to eliminate the need to run qemu as root. The only really viable
mechanism is to use tunctl to create a tap device, attach it to a bridge as
root, and then hand that tap device to qemu. The problem with this mechanism
is that it requires administrator intervention whenever a user wants to create
a guest.
By essentially writing a helper that implements the most common qemu-ifup
script that can be safely given cap_net_admin, we can dramatically simplify
things for non-privileged users. We still support existing -net tap options
as a mechanism for advanced users and backwards compatibility.
Currently, this is very Linux centric but there's really no reason why it
couldn't be extended for other Unixes.
A typical invocation would be similar to one of the following:
qemu linux.img -net bridge -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper"
-net nic,model=virtio
qemu linux.img -netdev bridge,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
The default bridge that we attach to is br0. The thinking is that a distro
could preconfigure such an interface to allow out-of-the-box bridged networking.
Alternatively, if a user wants to use a different bridge, a typical invocation
would be simliar to one of the following:
qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
qemu linux.img -net tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0"
-net nic,model=virtio
qemu linux.img -netdev bridge,br=qemubr0,id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
qemu linux.img -netdev tap,helper="/usr/local/libexec/qemu-bridge-helper --br=qemubr0",id=hn0
-device virtio-net-pci,netdev=hn0,id=nic1
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by: Richa Marwaha <rmarwah@linux.vnet.ibm.com>
Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-01-26 15:42:27 +01:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 15:14:27 +02:00
|
|
|
@item -netdev socket,id=@var{id}[,fd=@var{h}][,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}]
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
This host network backend can be used to connect the guest's network to
|
|
|
|
another QEMU virtual machine using a TCP socket connection. If @option{listen}
|
|
|
|
is specified, QEMU waits for incoming connections on @var{port}
|
2009-03-28 07:44:27 +01:00
|
|
|
(@var{host} is optional). @option{connect} is used to connect to
|
|
|
|
another QEMU instance using the @option{listen} option. @option{fd}=@var{h}
|
|
|
|
specifies an already opened TCP socket.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
# launch a first QEMU instance
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-03-12 13:20:50 +01:00
|
|
|
-device e1000,netdev=n1,mac=52:54:00:12:34:56 \
|
|
|
|
-netdev socket,id=n1,listen=:1234
|
|
|
|
# connect the network of this instance to the network of the first instance
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-03-12 13:20:50 +01:00
|
|
|
-device e1000,netdev=n2,mac=52:54:00:12:34:57 \
|
|
|
|
-netdev socket,id=n2,connect=127.0.0.1:1234
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 15:14:27 +02:00
|
|
|
@item -netdev socket,id=@var{id}[,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]]
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
Configure a socket host network backend to share the guest's network traffic
|
|
|
|
with another QEMU virtual machines using a UDP multicast socket, effectively
|
|
|
|
making a bus for every QEMU with same multicast address @var{maddr} and @var{port}.
|
2009-03-28 07:44:27 +01:00
|
|
|
NOTES:
|
|
|
|
@enumerate
|
|
|
|
@item
|
|
|
|
Several QEMU can be running on different hosts and share same bus (assuming
|
|
|
|
correct multicast setup for these hosts).
|
|
|
|
@item
|
|
|
|
mcast support is compatible with User Mode Linux (argument @option{eth@var{N}=mcast}), see
|
|
|
|
@url{http://user-mode-linux.sf.net}.
|
|
|
|
@item
|
|
|
|
Use @option{fd=h} to specify an already opened UDP multicast socket.
|
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
# launch one QEMU instance
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-03-12 13:20:50 +01:00
|
|
|
-device e1000,netdev=n1,mac=52:54:00:12:34:56 \
|
|
|
|
-netdev socket,id=n1,mcast=230.0.0.1:1234
|
2009-03-28 07:44:27 +01:00
|
|
|
# launch another QEMU instance on same "bus"
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-03-12 13:20:50 +01:00
|
|
|
-device e1000,netdev=n2,mac=52:54:00:12:34:57 \
|
|
|
|
-netdev socket,id=n2,mcast=230.0.0.1:1234
|
2009-03-28 07:44:27 +01:00
|
|
|
# launch yet another QEMU instance on same "bus"
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-08-13 13:51:44 +02:00
|
|
|
-device e1000,netdev=n3,mac=52:54:00:12:34:58 \
|
2018-03-12 13:20:50 +01:00
|
|
|
-netdev socket,id=n3,mcast=230.0.0.1:1234
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Example (User Mode Linux compat.):
|
|
|
|
@example
|
2018-03-12 13:20:50 +01:00
|
|
|
# launch QEMU instance (note mcast address selected is UML's default)
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-03-12 13:20:50 +01:00
|
|
|
-device e1000,netdev=n1,mac=52:54:00:12:34:56 \
|
|
|
|
-netdev socket,id=n1,mcast=239.192.168.1:1102
|
2009-03-28 07:44:27 +01:00
|
|
|
# launch UML
|
|
|
|
/path/to/linux ubd0=/path/to/root_fs eth0=mcast
|
|
|
|
@end example
|
|
|
|
|
2010-12-01 20:16:47 +01:00
|
|
|
Example (send packets from host's 1.2.3.4):
|
|
|
|
@example
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 linux.img \
|
2018-03-12 13:20:50 +01:00
|
|
|
-device e1000,netdev=n1,mac=52:54:00:12:34:56 \
|
|
|
|
-netdev socket,id=n1,mcast=239.192.168.1:1102,localaddr=1.2.3.4
|
2010-12-01 20:16:47 +01:00
|
|
|
@end example
|
|
|
|
|
2014-06-20 11:34:41 +02:00
|
|
|
@item -netdev l2tpv3,id=@var{id},src=@var{srcaddr},dst=@var{dstaddr}[,srcport=@var{srcport}][,dstport=@var{dstport}],txsession=@var{txsession}[,rxsession=@var{rxsession}][,ipv6][,udp][,cookie64][,counter][,pincounter][,txcookie=@var{txcookie}][,rxcookie=@var{rxcookie}][,offset=@var{offset}]
|
2018-03-12 13:20:50 +01:00
|
|
|
Configure a L2TPv3 pseudowire host network backend. L2TPv3 (RFC3391) is a
|
|
|
|
popular protocol to transport Ethernet (and other Layer 2) data frames between
|
2014-06-20 11:34:41 +02:00
|
|
|
two systems. It is present in routers, firewalls and the Linux kernel
|
|
|
|
(from version 3.3 onwards).
|
|
|
|
|
|
|
|
This transport allows a VM to communicate to another VM, router or firewall directly.
|
|
|
|
|
2017-10-02 16:03:01 +02:00
|
|
|
@table @option
|
2014-06-20 11:34:41 +02:00
|
|
|
@item src=@var{srcaddr}
|
|
|
|
source address (mandatory)
|
|
|
|
@item dst=@var{dstaddr}
|
|
|
|
destination address (mandatory)
|
|
|
|
@item udp
|
|
|
|
select udp encapsulation (default is ip).
|
|
|
|
@item srcport=@var{srcport}
|
|
|
|
source udp port.
|
|
|
|
@item dstport=@var{dstport}
|
|
|
|
destination udp port.
|
|
|
|
@item ipv6
|
|
|
|
force v6, otherwise defaults to v4.
|
|
|
|
@item rxcookie=@var{rxcookie}
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx txcookie=@var{txcookie}
|
2014-06-20 11:34:41 +02:00
|
|
|
Cookies are a weak form of security in the l2tpv3 specification.
|
|
|
|
Their function is mostly to prevent misconfiguration. By default they are 32
|
|
|
|
bit.
|
|
|
|
@item cookie64
|
|
|
|
Set cookie size to 64 bit instead of the default 32
|
|
|
|
@item counter=off
|
|
|
|
Force a 'cut-down' L2TPv3 with no counter as in
|
|
|
|
draft-mkonstan-l2tpext-keyed-ipv6-tunnel-00
|
|
|
|
@item pincounter=on
|
|
|
|
Work around broken counter handling in peer. This may also help on
|
|
|
|
networks which have packet reorder.
|
|
|
|
@item offset=@var{offset}
|
|
|
|
Add an extra offset between header and data
|
2017-10-02 16:03:01 +02:00
|
|
|
@end table
|
2014-06-20 11:34:41 +02:00
|
|
|
|
|
|
|
For example, to attach a VM running on host 4.3.2.1 via L2TPv3 to the bridge br-lan
|
|
|
|
on the remote Linux host 1.2.3.4:
|
|
|
|
@example
|
|
|
|
# Setup tunnel on linux host using raw ip as encapsulation
|
|
|
|
# on 1.2.3.4
|
|
|
|
ip l2tp add tunnel remote 4.3.2.1 local 1.2.3.4 tunnel_id 1 peer_tunnel_id 1 \
|
|
|
|
encap udp udp_sport 16384 udp_dport 16384
|
|
|
|
ip l2tp add session tunnel_id 1 name vmtunnel0 session_id \
|
|
|
|
0xFFFFFFFF peer_session_id 0xFFFFFFFF
|
|
|
|
ifconfig vmtunnel0 mtu 1500
|
|
|
|
ifconfig vmtunnel0 up
|
|
|
|
brctl addif br-lan vmtunnel0
|
|
|
|
|
|
|
|
|
|
|
|
# on 4.3.2.1
|
|
|
|
# launch QEMU instance - if your network has reorder or is very lossy add ,pincounter
|
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 linux.img -device e1000,netdev=n1 \
|
|
|
|
-netdev l2tpv3,id=n1,src=4.2.3.1,dst=1.2.3.4,udp,srcport=16384,dstport=16384,rxsession=0xffffffff,txsession=0xffffffff,counter
|
2014-06-20 11:34:41 +02:00
|
|
|
|
|
|
|
@end example
|
|
|
|
|
2012-08-14 15:14:27 +02:00
|
|
|
@item -netdev vde,id=@var{id}[,sock=@var{socketpath}][,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}]
|
2018-03-12 13:20:50 +01:00
|
|
|
Configure VDE backend to connect to PORT @var{n} of a vde switch running on host and
|
2009-03-28 07:44:27 +01:00
|
|
|
listening for incoming connections on @var{socketpath}. Use GROUP @var{groupname}
|
|
|
|
and MODE @var{octalmode} to change default ownership and permissions for
|
2011-09-05 18:13:03 +02:00
|
|
|
communication port. This option is only available if QEMU has been compiled
|
2009-03-28 07:44:27 +01:00
|
|
|
with vde support enabled.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
# launch vde switch
|
|
|
|
vde_switch -F -sock /tmp/myswitch
|
|
|
|
# launch QEMU instance
|
2018-03-12 13:20:50 +01:00
|
|
|
qemu-system-i386 linux.img -nic vde,sock=/tmp/myswitch
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
vhost-user: add multiple queue support
This patch is initially based a patch from Nikolay Nikolaev.
This patch adds vhost-user multiple queue support, by creating a nc
and vhost_net pair for each queue.
Qemu exits if find that the backend can't support the number of requested
queues (by providing queues=# option). The max number is queried by a
new message, VHOST_USER_GET_QUEUE_NUM, and is sent only when protocol
feature VHOST_USER_PROTOCOL_F_MQ is present first.
The max queue check is done at vhost-user initiation stage. We initiate
one queue first, which, in the meantime, also gets the max_queues the
backend supports.
In older version, it was reported that some messages are sent more times
than necessary. Here we came an agreement with Michael that we could
categorize vhost user messages to 2 types: non-vring specific messages,
which should be sent only once, and vring specific messages, which should
be sent per queue.
Here I introduced a helper function vhost_user_one_time_request(), which
lists following messages as non-vring specific messages:
VHOST_USER_SET_OWNER
VHOST_USER_RESET_DEVICE
VHOST_USER_SET_MEM_TABLE
VHOST_USER_GET_QUEUE_NUM
For above messages, we simply ignore them when they are not sent the first
time.
Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Signed-off-by: Changchun Ouyang <changchun.ouyang@intel.com>
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Reviewed-by: Jason Wang <jasowang@redhat.com>
Tested-by: Marcel Apfelbaum <marcel@redhat.com>
2015-09-23 06:20:00 +02:00
|
|
|
@item -netdev vhost-user,chardev=@var{id}[,vhostforce=on|off][,queues=n]
|
2014-06-10 12:02:16 +02:00
|
|
|
|
|
|
|
Establish a vhost-user netdev, backed by a chardev @var{id}. The chardev should
|
|
|
|
be a unix domain socket backed one. The vhost-user uses a specifically defined
|
|
|
|
protocol to pass vhost ioctl replacement messages to an application on the other
|
|
|
|
end of the socket. On non-MSIX guests, the feature can be forced with
|
vhost-user: add multiple queue support
This patch is initially based a patch from Nikolay Nikolaev.
This patch adds vhost-user multiple queue support, by creating a nc
and vhost_net pair for each queue.
Qemu exits if find that the backend can't support the number of requested
queues (by providing queues=# option). The max number is queried by a
new message, VHOST_USER_GET_QUEUE_NUM, and is sent only when protocol
feature VHOST_USER_PROTOCOL_F_MQ is present first.
The max queue check is done at vhost-user initiation stage. We initiate
one queue first, which, in the meantime, also gets the max_queues the
backend supports.
In older version, it was reported that some messages are sent more times
than necessary. Here we came an agreement with Michael that we could
categorize vhost user messages to 2 types: non-vring specific messages,
which should be sent only once, and vring specific messages, which should
be sent per queue.
Here I introduced a helper function vhost_user_one_time_request(), which
lists following messages as non-vring specific messages:
VHOST_USER_SET_OWNER
VHOST_USER_RESET_DEVICE
VHOST_USER_SET_MEM_TABLE
VHOST_USER_GET_QUEUE_NUM
For above messages, we simply ignore them when they are not sent the first
time.
Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Signed-off-by: Changchun Ouyang <changchun.ouyang@intel.com>
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Reviewed-by: Jason Wang <jasowang@redhat.com>
Tested-by: Marcel Apfelbaum <marcel@redhat.com>
2015-09-23 06:20:00 +02:00
|
|
|
@var{vhostforce}. Use 'queues=@var{n}' to specify the number of queues to
|
|
|
|
be created for multiqueue vhost-user.
|
2014-06-10 12:02:16 +02:00
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
qemu -m 512 -object memory-backend-file,id=mem,size=512M,mem-path=/hugetlbfs,share=on \
|
|
|
|
-numa node,memdev=mem \
|
2017-02-20 17:45:09 +01:00
|
|
|
-chardev socket,id=chr0,path=/path/to/socket \
|
2014-06-10 12:02:16 +02:00
|
|
|
-netdev type=vhost-user,id=net0,chardev=chr0 \
|
|
|
|
-device virtio-net-pci,netdev=net0
|
|
|
|
@end example
|
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
@item -netdev hubport,id=@var{id},hubid=@var{hubid}[,netdev=@var{nd}]
|
2018-02-21 11:18:36 +01:00
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
Create a hub port on the emulated hub with ID @var{hubid}.
|
2018-02-21 11:18:36 +01:00
|
|
|
|
2018-03-12 13:20:50 +01:00
|
|
|
The hubport netdev lets you connect a NIC to a QEMU emulated hub instead of a
|
2018-04-30 20:02:23 +02:00
|
|
|
single netdev. Alternatively, you can also connect the hubport to another
|
|
|
|
netdev with ID @var{nd} by using the @option{netdev=@var{nd}} option.
|
2018-03-12 13:20:50 +01:00
|
|
|
|
2018-04-30 20:02:23 +02:00
|
|
|
@item -net nic[,netdev=@var{nd}][,macaddr=@var{mac}][,model=@var{type}] [,name=@var{name}][,addr=@var{addr}][,vectors=@var{v}]
|
2018-03-12 13:20:50 +01:00
|
|
|
@findex -net
|
|
|
|
Legacy option to configure or create an on-board (or machine default) Network
|
2018-04-30 20:02:23 +02:00
|
|
|
Interface Card(NIC) and connect it either to the emulated hub with ID 0 (i.e.
|
|
|
|
the default hub), or to the netdev @var{nd}.
|
2018-03-12 13:20:50 +01:00
|
|
|
The NIC is an e1000 by default on the PC target. Optionally, the MAC address
|
|
|
|
can be changed to @var{mac}, the device address set to @var{addr} (PCI cards
|
|
|
|
only), and a @var{name} can be assigned for use in monitor commands.
|
|
|
|
Optionally, for PCI cards, you can specify the number @var{v} of MSI-X vectors
|
|
|
|
that the card should have; this option currently only affects virtio cards; set
|
|
|
|
@var{v} = 0 to disable MSI-X. If no @option{-net} option is specified, a single
|
|
|
|
NIC is created. QEMU can emulate several different models of network card.
|
|
|
|
Use @code{-net nic,model=help} for a list of available devices for your target.
|
|
|
|
|
2018-04-30 20:02:23 +02:00
|
|
|
@item -net user|tap|bridge|socket|l2tpv3|vde[,...][,name=@var{name}]
|
2018-03-12 13:20:50 +01:00
|
|
|
Configure a host network backend (with the options corresponding to the same
|
2018-04-30 20:02:23 +02:00
|
|
|
@option{-netdev} option) and connect it to the emulated hub 0 (the default
|
|
|
|
hub). Use @var{name} to specify the name of the hub port.
|
2013-02-13 19:49:40 +01:00
|
|
|
ETEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2013-02-13 19:49:40 +01:00
|
|
|
STEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
2009-10-30 14:41:12 +01:00
|
|
|
DEFHEADING()
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Character device options:)
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
DEF("chardev", HAS_ARG, QEMU_OPTION_chardev,
|
2016-08-16 19:13:52 +02:00
|
|
|
"-chardev help\n"
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev null,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2014-10-02 18:17:37 +02:00
|
|
|
"-chardev socket,id=id[,host=host],port=port[,to=to][,ipv4][,ipv6][,nodelay][,reconnect=seconds]\n"
|
2018-10-19 00:35:00 +02:00
|
|
|
" [,server][,nowait][,telnet][,websocket][,reconnect=seconds][,mux=on|off]\n"
|
chardev: add support for authorization for TLS clients
Currently any client which can complete the TLS handshake is able to use
a chardev server. The server admin can turn on the 'verify-peer' option
for the x509 creds to require the client to provide a x509
certificate. This means the client will have to acquire a certificate
from the CA before they are permitted to use the chardev server. This is
still a fairly low bar.
This adds a 'tls-authz=OBJECT-ID' option to the socket chardev backend
which takes the ID of a previously added 'QAuthZ' object instance. This
will be used to validate the client's x509 distinguished name. Clients
failing the check will not be permitted to use the chardev server.
For example to setup authorization that only allows connection from a
client whose x509 certificate distinguished name contains 'CN=fred', you
would use:
$QEMU -object tls-creds-x509,id=tls0,dir=/home/berrange/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-simple,id=authz0,identity=CN=laptop.example.com,,\
O=Example Org,,L=London,,ST=London,,C=GB \
-chardev socket,host=127.0.0.1,port=9000,server,\
tls-creds=tls0,tls-authz=authz0 \
...other qemu args...
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2019-03-08 16:21:50 +01:00
|
|
|
" [,logfile=PATH][,logappend=on|off][,tls-creds=ID][,tls-authz=ID] (tcp)\n"
|
2018-10-19 00:35:00 +02:00
|
|
|
"-chardev socket,id=id,path=path[,server][,nowait][,telnet][,websocket][,reconnect=seconds]\n"
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
" [,mux=on|off][,logfile=PATH][,logappend=on|off] (unix)\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
"-chardev udp,id=id[,host=host],port=port[,localaddr=localaddr]\n"
|
2010-04-06 16:55:54 +02:00
|
|
|
" [,localport=localport][,ipv4][,ipv6][,mux=on|off]\n"
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
" [,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev msmouse,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
"-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]\n"
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
" [,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev ringbuf,id=id[,size=size][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev file,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev pipe,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
#ifdef _WIN32
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev console,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev serial,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
#else
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev pty,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev stdio,id=id[,mux=on|off][,signal=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_BRLAPI
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev braille,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
#endif
|
|
|
|
#if defined(__linux__) || defined(__sun__) || defined(__FreeBSD__) \
|
|
|
|
|| defined(__NetBSD__) || defined(__OpenBSD__) || defined(__DragonFly__)
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev serial,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev tty,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
#endif
|
|
|
|
#if defined(__linux__) || defined(__FreeBSD__) || defined(__DragonFly__)
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev parallel,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev parport,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n"
|
2011-01-19 09:49:50 +01:00
|
|
|
#endif
|
|
|
|
#if defined(CONFIG_SPICE)
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
"-chardev spicevmc,id=id,name=name[,debug=debug][,logfile=PATH][,logappend=on|off]\n"
|
|
|
|
"-chardev spiceport,id=id,name=name[,debug=debug][,logfile=PATH][,logappend=on|off]\n"
|
2009-10-30 14:41:12 +01:00
|
|
|
#endif
|
2010-03-29 21:23:52 +02:00
|
|
|
, QEMU_ARCH_ALL
|
2009-10-30 14:41:12 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
STEXI
|
2017-10-02 16:03:06 +02:00
|
|
|
|
|
|
|
The general form of a character device option is:
|
|
|
|
@table @option
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev @var{backend},id=@var{id}[,mux=on|off][,@var{options}]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -chardev
|
2009-10-30 14:41:12 +01:00
|
|
|
Backend is one of:
|
|
|
|
@option{null},
|
|
|
|
@option{socket},
|
|
|
|
@option{udp},
|
|
|
|
@option{msmouse},
|
|
|
|
@option{vc},
|
Revert "chardev: Make the name of memory device consistent"
This reverts commit 6a85e60cb994bd95d1537aafbff65816f3de4637.
Commit 51767e7 "qemu-char: Add new char backend CirMemCharDriver"
introduced a memory ring buffer character device driver named
"memory". Commit 3949e59 "qemu-char: Saner naming of memchar stuff &
doc fixes" changed the driver name to "ringbuf", along with a whole
bunch of other names, with the following rationale:
Naming is a mess. The code calls the device driver
CirMemCharDriver, the public API calls it "memory", "memchardev",
or "memchar", and the special commands are named like
"memchar-FOO". "memory" is a particularly unfortunate choice,
because there's another character device driver called
MemoryDriver. Moreover, the device's distinctive property is that
it's a ring buffer, not that's in memory.
This is what we released in 1.4.0.
Unfortunately, the rename missed a critical instance of "memory": the
actual driver name. Thus, the new device could be used only by an
entirely undocumented name. The documented name did not work.
Bummer.
Commit 6a85e60 fixes this by changing the documentation to match the
code. It also changes some, but not all related occurences of
"ringbuf" to "memory". Left alone are identifiers in C code, HMP and
QMP commands. The latter are external interface, so they can't be
changed.
The result is an inconsistent mess. Moreover, "memory" is a rotten
name. The device's distinctive property is that it's a ring buffer,
not that's in memory. User's don't care whether it's in RAM, flash,
or carved into chocolate tablets by Oompa Loompas.
Revert the commit. Next commit will fix just the bug.
Cc: qemu-stable@nongnu.org
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1374849874-25531-2-git-send-email-armbru@redhat.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-07-26 16:44:32 +02:00
|
|
|
@option{ringbuf},
|
2009-10-30 14:41:12 +01:00
|
|
|
@option{file},
|
|
|
|
@option{pipe},
|
|
|
|
@option{console},
|
|
|
|
@option{serial},
|
|
|
|
@option{pty},
|
|
|
|
@option{stdio},
|
|
|
|
@option{braille},
|
|
|
|
@option{tty},
|
2013-01-10 14:20:58 +01:00
|
|
|
@option{parallel},
|
2011-01-19 09:49:50 +01:00
|
|
|
@option{parport},
|
2018-01-30 10:36:21 +01:00
|
|
|
@option{spicevmc},
|
2012-12-05 16:15:34 +01:00
|
|
|
@option{spiceport}.
|
2009-10-30 14:41:12 +01:00
|
|
|
The specific backend will determine the applicable options.
|
|
|
|
|
2017-10-02 16:03:06 +02:00
|
|
|
Use @code{-chardev help} to print all available chardev backend types.
|
2016-08-16 19:13:52 +02:00
|
|
|
|
2009-10-30 14:41:12 +01:00
|
|
|
All devices must have an id, which can be any string up to 127 characters long.
|
|
|
|
It is used to uniquely identify this device in other command line directives.
|
|
|
|
|
2010-04-06 16:55:54 +02:00
|
|
|
A character device may be used in multiplexing mode by multiple front-ends.
|
2016-02-16 18:28:58 +01:00
|
|
|
Specify @option{mux=on} to enable this mode.
|
|
|
|
A multiplexer is a "1:N" device, and here the "1" end is your specified chardev
|
|
|
|
backend, and the "N" end is the various parts of QEMU that can talk to a chardev.
|
|
|
|
If you create a chardev with @option{id=myid} and @option{mux=on}, QEMU will
|
|
|
|
create a multiplexer with your specified ID, and you can then configure multiple
|
|
|
|
front ends to use that chardev ID for their input/output. Up to four different
|
|
|
|
front ends can be connected to a single multiplexed chardev. (Without
|
|
|
|
multiplexing enabled, a chardev can only be used by a single front end.)
|
|
|
|
For instance you could use this to allow a single stdio chardev to be used by
|
|
|
|
two serial ports and the QEMU monitor:
|
|
|
|
|
|
|
|
@example
|
|
|
|
-chardev stdio,mux=on,id=char0 \
|
2016-10-11 19:41:21 +02:00
|
|
|
-mon chardev=char0,mode=readline \
|
2016-02-16 18:28:58 +01:00
|
|
|
-serial chardev:char0 \
|
|
|
|
-serial chardev:char0
|
|
|
|
@end example
|
|
|
|
|
|
|
|
You can have more than one multiplexer in a system configuration; for instance
|
|
|
|
you could have a TCP port multiplexed between UART 0 and UART 1, and stdio
|
|
|
|
multiplexed between the QEMU monitor and a parallel port:
|
|
|
|
|
|
|
|
@example
|
|
|
|
-chardev stdio,mux=on,id=char0 \
|
2016-10-11 19:41:21 +02:00
|
|
|
-mon chardev=char0,mode=readline \
|
2016-02-16 18:28:58 +01:00
|
|
|
-parallel chardev:char0 \
|
|
|
|
-chardev tcp,...,mux=on,id=char1 \
|
|
|
|
-serial chardev:char1 \
|
|
|
|
-serial chardev:char1
|
|
|
|
@end example
|
|
|
|
|
|
|
|
When you're using a multiplexed character device, some escape sequences are
|
|
|
|
interpreted in the input. @xref{mux_keys, Keys in the character backend
|
|
|
|
multiplexer}.
|
|
|
|
|
|
|
|
Note that some other command line options may implicitly create multiplexed
|
|
|
|
character backends; for instance @option{-serial mon:stdio} creates a
|
|
|
|
multiplexed stdio backend connected to the serial port and the QEMU monitor,
|
|
|
|
and @option{-nographic} also multiplexes the console and the monitor to
|
|
|
|
stdio.
|
|
|
|
|
|
|
|
There is currently no support for multiplexing in the other direction
|
|
|
|
(where a single QEMU front end takes input and output from multiple chardevs).
|
2010-04-06 16:55:54 +02:00
|
|
|
|
qemu-char: add logfile facility to all chardev backends
Typically a UNIX guest OS will log boot messages to a serial
port in addition to any graphical console. An admin user
may also wish to use the serial port for an interactive
console. A virtualization management system may wish to
collect system boot messages by logging the serial port,
but also wish to allow admins interactive access.
Currently providing such a feature forces the mgmt app
to either provide 2 separate serial ports, one for
logging boot messages and one for interactive console
login, or to proxy all output via a separate service
that can multiplex the two needs onto one serial port.
While both are valid approaches, they each have their
own downsides. The former causes confusion and extra
setup work for VM admins creating disk images. The latter
places an extra burden to re-implement much of the QEMU
chardev backends logic in libvirt or even higher level
mgmt apps and adds extra hops in the data transfer path.
A simpler approach that is satisfactory for many use
cases is to allow the QEMU chardev backends to have a
"logfile" property associated with them.
$QEMU -chardev socket,host=localhost,port=9000,\
server=on,nowait,id-charserial0,\
logfile=/var/log/libvirt/qemu/test-serial0.log
-device isa-serial,chardev=charserial0,id=serial0
This patch introduces a 'ChardevCommon' struct which
is setup as a base for all the ChardevBackend types.
Ideally this would be registered directly as a base
against ChardevBackend, rather than each type, but
the QAPI generator doesn't allow that since the
ChardevBackend is a non-discriminated union. The
ChardevCommon struct provides the optional 'logfile'
parameter, as well as 'logappend' which controls
whether QEMU truncates or appends (default truncate).
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1452516281-27519-1-git-send-email-berrange@redhat.com>
[Call qemu_chr_parse_common if cd->parse is NULL. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-11 13:44:41 +01:00
|
|
|
Every backend supports the @option{logfile} option, which supplies the path
|
|
|
|
to a file to record all data transmitted via the backend. The @option{logappend}
|
|
|
|
option controls whether the log file will be truncated or appended to when
|
|
|
|
opened.
|
|
|
|
|
2017-10-02 16:03:06 +02:00
|
|
|
@end table
|
2009-10-30 14:41:12 +01:00
|
|
|
|
2017-10-02 16:03:06 +02:00
|
|
|
The available backends are:
|
|
|
|
|
|
|
|
@table @option
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev null,id=@var{id}
|
2009-10-30 14:41:12 +01:00
|
|
|
A void device. This device will not emit any data, and will drop any data it
|
|
|
|
receives. The null backend does not take any options.
|
|
|
|
|
chardev: add support for authorization for TLS clients
Currently any client which can complete the TLS handshake is able to use
a chardev server. The server admin can turn on the 'verify-peer' option
for the x509 creds to require the client to provide a x509
certificate. This means the client will have to acquire a certificate
from the CA before they are permitted to use the chardev server. This is
still a fairly low bar.
This adds a 'tls-authz=OBJECT-ID' option to the socket chardev backend
which takes the ID of a previously added 'QAuthZ' object instance. This
will be used to validate the client's x509 distinguished name. Clients
failing the check will not be permitted to use the chardev server.
For example to setup authorization that only allows connection from a
client whose x509 certificate distinguished name contains 'CN=fred', you
would use:
$QEMU -object tls-creds-x509,id=tls0,dir=/home/berrange/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-simple,id=authz0,identity=CN=laptop.example.com,,\
O=Example Org,,L=London,,ST=London,,C=GB \
-chardev socket,host=127.0.0.1,port=9000,server,\
tls-creds=tls0,tls-authz=authz0 \
...other qemu args...
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2019-03-08 16:21:50 +01:00
|
|
|
@item -chardev socket,id=@var{id}[,@var{TCP options} or @var{unix options}][,server][,nowait][,telnet][,websocket][,reconnect=@var{seconds}][,tls-creds=@var{id}][,tls-authz=@var{id}]
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Create a two-way stream socket, which can be either a TCP or a unix socket. A
|
|
|
|
unix socket will be created if @option{path} is specified. Behaviour is
|
|
|
|
undefined if TCP options are specified for a unix socket.
|
|
|
|
|
|
|
|
@option{server} specifies that the socket shall be a listening socket.
|
|
|
|
|
|
|
|
@option{nowait} specifies that QEMU should not block waiting for a client to
|
|
|
|
connect to a listening socket.
|
|
|
|
|
|
|
|
@option{telnet} specifies that traffic on the socket should interpret telnet
|
|
|
|
escape sequences.
|
|
|
|
|
2018-10-19 00:35:00 +02:00
|
|
|
@option{websocket} specifies that the socket uses WebSocket protocol for
|
|
|
|
communication.
|
|
|
|
|
2014-10-02 18:17:37 +02:00
|
|
|
@option{reconnect} sets the timeout for reconnecting on non-server sockets when
|
|
|
|
the remote end goes away. qemu will delay this many seconds and then attempt
|
|
|
|
to reconnect. Zero disables reconnecting, and is the default.
|
|
|
|
|
char: introduce support for TLS encrypted TCP chardev backend
This integrates support for QIOChannelTLS object in the TCP
chardev backend. If the 'tls-creds=NAME' option is passed with
the '-chardev tcp' argument, then it will setup the chardev
such that the client is required to establish a TLS handshake
when connecting. There is no support for checking the client
certificate against ACLs in this initial patch. This is pending
work to QOM-ify the ACL object code.
A complete invocation to run QEMU as the server for a TLS
encrypted serial dev might be
$ qemu-system-x86_64 \
-nodefconfig -nodefaults -device sga -display none \
-chardev socket,id=s0,host=127.0.0.1,port=9000,tls-creds=tls0,server \
-device isa-serial,chardev=s0 \
-object tls-creds-x509,id=tls0,endpoint=server,verify-peer=off,\
dir=/home/berrange/security/qemutls
To test with the gnutls-cli tool as the client:
$ gnutls-cli --priority=NORMAL -p 9000 \
--x509cafile=/home/berrange/security/qemutls/ca-cert.pem \
127.0.0.1
If QEMU was told to use 'anon' credential type, then use the
priority string 'NORMAL:+ANON-DH' with gnutls-cli
Alternatively, if setting up a chardev to operate as a client,
then the TLS credentials registered must be for the client
endpoint. First a TLS server must be setup, which can be done
with the gnutls-serv tool
$ gnutls-serv --priority=NORMAL -p 9000 --echo \
--x509cafile=/home/berrange/security/qemutls/ca-cert.pem \
--x509certfile=/home/berrange/security/qemutls/server-cert.pem \
--x509keyfile=/home/berrange/security/qemutls/server-key.pem
Then QEMU can connect with
$ qemu-system-x86_64 \
-nodefconfig -nodefaults -device sga -display none \
-chardev socket,id=s0,host=127.0.0.1,port=9000,tls-creds=tls0 \
-device isa-serial,chardev=s0 \
-object tls-creds-x509,id=tls0,endpoint=client,\
dir=/home/berrange/security/qemutls
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1453202071-10289-5-git-send-email-berrange@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-01-19 12:14:31 +01:00
|
|
|
@option{tls-creds} requests enablement of the TLS protocol for encryption,
|
|
|
|
and specifies the id of the TLS credentials to use for the handshake. The
|
|
|
|
credentials must be previously created with the @option{-object tls-creds}
|
|
|
|
argument.
|
|
|
|
|
chardev: add support for authorization for TLS clients
Currently any client which can complete the TLS handshake is able to use
a chardev server. The server admin can turn on the 'verify-peer' option
for the x509 creds to require the client to provide a x509
certificate. This means the client will have to acquire a certificate
from the CA before they are permitted to use the chardev server. This is
still a fairly low bar.
This adds a 'tls-authz=OBJECT-ID' option to the socket chardev backend
which takes the ID of a previously added 'QAuthZ' object instance. This
will be used to validate the client's x509 distinguished name. Clients
failing the check will not be permitted to use the chardev server.
For example to setup authorization that only allows connection from a
client whose x509 certificate distinguished name contains 'CN=fred', you
would use:
$QEMU -object tls-creds-x509,id=tls0,dir=/home/berrange/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-simple,id=authz0,identity=CN=laptop.example.com,,\
O=Example Org,,L=London,,ST=London,,C=GB \
-chardev socket,host=127.0.0.1,port=9000,server,\
tls-creds=tls0,tls-authz=authz0 \
...other qemu args...
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2019-03-08 16:21:50 +01:00
|
|
|
@option{tls-auth} provides the ID of the QAuthZ authorization object against
|
|
|
|
which the client's x509 distinguished name will be validated. This object is
|
|
|
|
only resolved at time of use, so can be deleted and recreated on the fly
|
|
|
|
while the chardev server is active. If missing, it will default to denying
|
|
|
|
access.
|
|
|
|
|
2009-10-30 14:41:12 +01:00
|
|
|
TCP and unix socket options are given below:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item TCP options: port=@var{port}[,host=@var{host}][,to=@var{to}][,ipv4][,ipv6][,nodelay]
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
@option{host} for a listening socket specifies the local address to be bound.
|
|
|
|
For a connecting socket species the remote host to connect to. @option{host} is
|
|
|
|
optional for listening sockets. If not specified it defaults to @code{0.0.0.0}.
|
|
|
|
|
|
|
|
@option{port} for a listening socket specifies the local port to be bound. For a
|
|
|
|
connecting socket specifies the port on the remote host to connect to.
|
|
|
|
@option{port} can be given as either a port number or a service name.
|
|
|
|
@option{port} is required.
|
|
|
|
|
|
|
|
@option{to} is only relevant to listening sockets. If it is specified, and
|
|
|
|
@option{port} cannot be bound, QEMU will attempt to bind to subsequent ports up
|
|
|
|
to and including @option{to} until it succeeds. @option{to} must be specified
|
|
|
|
as a port number.
|
|
|
|
|
|
|
|
@option{ipv4} and @option{ipv6} specify that either IPv4 or IPv6 must be used.
|
|
|
|
If neither is specified the socket may use either protocol.
|
|
|
|
|
|
|
|
@option{nodelay} disables the Nagle algorithm.
|
|
|
|
|
|
|
|
@item unix options: path=@var{path}
|
|
|
|
|
|
|
|
@option{path} specifies the local path of the unix socket. @option{path} is
|
|
|
|
required.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev udp,id=@var{id}[,host=@var{host}],port=@var{port}[,localaddr=@var{localaddr}][,localport=@var{localport}][,ipv4][,ipv6]
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Sends all traffic from the guest to a remote host over UDP.
|
|
|
|
|
|
|
|
@option{host} specifies the remote host to connect to. If not specified it
|
|
|
|
defaults to @code{localhost}.
|
|
|
|
|
|
|
|
@option{port} specifies the port on the remote host to connect to. @option{port}
|
|
|
|
is required.
|
|
|
|
|
|
|
|
@option{localaddr} specifies the local address to bind to. If not specified it
|
|
|
|
defaults to @code{0.0.0.0}.
|
|
|
|
|
|
|
|
@option{localport} specifies the local port to bind to. If not specified any
|
|
|
|
available local port will be used.
|
|
|
|
|
|
|
|
@option{ipv4} and @option{ipv6} specify that either IPv4 or IPv6 must be used.
|
|
|
|
If neither is specified the device may use either protocol.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev msmouse,id=@var{id}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Forward QEMU's emulated msmouse events to the guest. @option{msmouse} does not
|
|
|
|
take any options.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev vc,id=@var{id}[[,width=@var{width}][,height=@var{height}]][[,cols=@var{cols}][,rows=@var{rows}]]
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Connect to a QEMU text console. @option{vc} may optionally be given a specific
|
|
|
|
size.
|
|
|
|
|
|
|
|
@option{width} and @option{height} specify the width and height respectively of
|
|
|
|
the console, in pixels.
|
|
|
|
|
|
|
|
@option{cols} and @option{rows} specify that the console be sized to fit a text
|
|
|
|
console with the given dimensions.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev ringbuf,id=@var{id}[,size=@var{size}]
|
2013-01-24 17:03:19 +01:00
|
|
|
|
qemu-char: Saner naming of memchar stuff & doc fixes
New device, has never been released, so we can still improve things
without worrying about compatibility.
Naming is a mess. The code calls the device driver CirMemCharDriver,
the public API calls it "memory", "memchardev", or "memchar", and the
special commands are named like "memchar-FOO". "memory" is a
particularly unfortunate choice, because there's another character
device driver called MemoryDriver. Moreover, the device's distinctive
property is that it's a ring buffer, not that's in memory. Therefore:
* Rename CirMemCharDriver to RingBufCharDriver, and call the thing a
"ringbuf" in the API.
* Rename QMP and HMP commands from memchar-FOO to ringbuf-FOO.
* Rename device parameter from maxcapacity to size (simple words are
good for you).
* Clearly mark the parameter as optional in documentation.
* Fix error reporting so that chardev-add reports to current monitor,
not stderr.
* Replace cirmem in C identifiers by ringbuf.
* Rework documentation. Document the impact of our crappy UTF-8
handling on reading.
* QMP examples that even work.
I could split this up into multiple commits, but they'd change the
same documentation lines multiple times. Not worth it.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-06 21:27:24 +01:00
|
|
|
Create a ring buffer with fixed size @option{size}.
|
2016-09-19 12:56:26 +02:00
|
|
|
@var{size} must be a power of two and defaults to @code{64K}.
|
2013-01-24 17:03:19 +01:00
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev file,id=@var{id},path=@var{path}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Log all traffic received from the guest to a file.
|
|
|
|
|
|
|
|
@option{path} specifies the path of the file to be opened. This file will be
|
|
|
|
created if it does not already exist, and overwritten if it does. @option{path}
|
|
|
|
is required.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev pipe,id=@var{id},path=@var{path}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Create a two-way connection to the guest. The behaviour differs slightly between
|
|
|
|
Windows hosts and other hosts:
|
|
|
|
|
|
|
|
On Windows, a single duplex pipe will be created at
|
|
|
|
@file{\\.pipe\@option{path}}.
|
|
|
|
|
|
|
|
On other hosts, 2 pipes will be created called @file{@option{path}.in} and
|
|
|
|
@file{@option{path}.out}. Data written to @file{@option{path}.in} will be
|
|
|
|
received by the guest. Data written by the guest can be read from
|
|
|
|
@file{@option{path}.out}. QEMU will not create these fifos, and requires them to
|
|
|
|
be present.
|
|
|
|
|
|
|
|
@option{path} forms part of the pipe path as described above. @option{path} is
|
|
|
|
required.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev console,id=@var{id}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Send traffic from the guest to QEMU's standard output. @option{console} does not
|
|
|
|
take any options.
|
|
|
|
|
|
|
|
@option{console} is only available on Windows hosts.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev serial,id=@var{id},path=@option{path}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Send traffic from the guest to a serial device on the host.
|
|
|
|
|
2012-12-19 13:50:29 +01:00
|
|
|
On Unix hosts serial will actually accept any tty device,
|
|
|
|
not only serial lines.
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
@option{path} specifies the name of the serial device to open.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev pty,id=@var{id}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Create a new pseudo-terminal on the host and connect to it. @option{pty} does
|
|
|
|
not take any options.
|
|
|
|
|
|
|
|
@option{pty} is not available on Windows hosts.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev stdio,id=@var{id}[,signal=on|off]
|
2012-05-11 22:25:50 +02:00
|
|
|
Connect to standard input and standard output of the QEMU process.
|
2010-07-13 21:13:12 +02:00
|
|
|
|
|
|
|
@option{signal} controls if signals are enabled on the terminal, that includes
|
|
|
|
exiting QEMU with the key sequence @key{Control-c}. This option is enabled by
|
|
|
|
default, use @option{signal=off} to disable it.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev braille,id=@var{id}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Connect to a local BrlAPI server. @option{braille} does not take any options.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev tty,id=@var{id},path=@var{path}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
@option{tty} is only available on Linux, Sun, FreeBSD, NetBSD, OpenBSD and
|
2013-02-13 15:54:15 +01:00
|
|
|
DragonFlyBSD hosts. It is an alias for @option{serial}.
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
@option{path} specifies the path to the tty. @option{path} is required.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev parallel,id=@var{id},path=@var{path}
|
|
|
|
@itemx -chardev parport,id=@var{id},path=@var{path}
|
2009-10-30 14:41:12 +01:00
|
|
|
|
2013-01-10 14:20:58 +01:00
|
|
|
@option{parallel} is only available on Linux, FreeBSD and DragonFlyBSD hosts.
|
2009-10-30 14:41:12 +01:00
|
|
|
|
|
|
|
Connect to a local parallel port.
|
|
|
|
|
|
|
|
@option{path} specifies the path to the parallel port device. @option{path} is
|
|
|
|
required.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev spicevmc,id=@var{id},debug=@var{debug},name=@var{name}
|
2011-01-19 09:49:50 +01:00
|
|
|
|
2011-10-06 12:24:12 +02:00
|
|
|
@option{spicevmc} is only available when spice support is built in.
|
|
|
|
|
2011-01-19 09:49:50 +01:00
|
|
|
@option{debug} debug level for spicevmc
|
|
|
|
|
|
|
|
@option{name} name of spice channel to connect to
|
|
|
|
|
|
|
|
Connect to a spice virtual machine channel, such as vdiport.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -chardev spiceport,id=@var{id},debug=@var{debug},name=@var{name}
|
2012-12-05 16:15:34 +01:00
|
|
|
|
|
|
|
@option{spiceport} is only available when spice support is built in.
|
|
|
|
|
|
|
|
@option{debug} debug level for spicevmc
|
|
|
|
|
|
|
|
@option{name} name of spice port to connect to
|
|
|
|
|
|
|
|
Connect to a spice port, allowing a Spice client to handle the traffic
|
|
|
|
identified by a name (preferably a fqdn).
|
2013-02-13 19:49:40 +01:00
|
|
|
ETEXI
|
2012-12-05 16:15:34 +01:00
|
|
|
|
2013-02-13 19:49:40 +01:00
|
|
|
STEXI
|
2009-10-30 14:41:12 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Bluetooth(R) options:)
|
2013-02-13 19:49:40 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
2009-10-30 14:41:12 +01:00
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("bt", HAS_ARG, QEMU_OPTION_bt, \
|
|
|
|
"-bt hci,null dumb bluetooth HCI - doesn't respond to commands\n" \
|
|
|
|
"-bt hci,host[:id]\n" \
|
|
|
|
" use host's HCI with the given name\n" \
|
|
|
|
"-bt hci[,vlan=n]\n" \
|
|
|
|
" emulate a standard HCI in virtual scatternet 'n'\n" \
|
|
|
|
"-bt vhci[,vlan=n]\n" \
|
|
|
|
" add host computer to virtual scatternet 'n' using VHCI\n" \
|
|
|
|
"-bt device:dev[,vlan=n]\n" \
|
2010-03-29 21:23:52 +02:00
|
|
|
" emulate a bluetooth device 'dev' in scatternet 'n'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -bt hci[...]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -bt
|
2009-03-28 07:44:27 +01:00
|
|
|
Defines the function of the corresponding Bluetooth HCI. -bt options
|
|
|
|
are matched with the HCIs present in the chosen machine type. For
|
|
|
|
example when emulating a machine with only one HCI built into it, only
|
|
|
|
the first @code{-bt hci[...]} option is valid and defines the HCI's
|
|
|
|
logic. The Transport Layer is decided by the machine type. Currently
|
|
|
|
the machines @code{n800} and @code{n810} have one HCI and all other
|
|
|
|
machines have none.
|
|
|
|
|
2018-11-12 11:00:30 +01:00
|
|
|
Note: This option and the whole bluetooth subsystem is considered as deprecated.
|
|
|
|
If you still use it, please send a mail to @email{qemu-devel@@nongnu.org} where
|
|
|
|
you describe your usecase.
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
@anchor{bt-hcis}
|
|
|
|
The following three types are recognized:
|
|
|
|
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2009-03-28 07:44:27 +01:00
|
|
|
@item -bt hci,null
|
|
|
|
(default) The corresponding Bluetooth HCI assumes no internal logic
|
|
|
|
and will not respond to any HCI commands or emit events.
|
|
|
|
|
|
|
|
@item -bt hci,host[:@var{id}]
|
|
|
|
(@code{bluez} only) The corresponding HCI passes commands / events
|
|
|
|
to / from the physical HCI identified by the name @var{id} (default:
|
|
|
|
@code{hci0}) on the computer running QEMU. Only available on @code{bluez}
|
|
|
|
capable systems like Linux.
|
|
|
|
|
|
|
|
@item -bt hci[,vlan=@var{n}]
|
|
|
|
Add a virtual, standard HCI that will participate in the Bluetooth
|
|
|
|
scatternet @var{n} (default @code{0}). Similarly to @option{-net}
|
|
|
|
VLANs, devices inside a bluetooth network @var{n} can only communicate
|
|
|
|
with other devices in the same network (scatternet).
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item -bt vhci[,vlan=@var{n}]
|
|
|
|
(Linux-host only) Create a HCI in scatternet @var{n} (default 0) attached
|
|
|
|
to the host bluetooth stack instead of to the emulated target. This
|
|
|
|
allows the host and target machines to participate in a common scatternet
|
|
|
|
and communicate. Requires the Linux @code{vhci} driver installed. Can
|
|
|
|
be used as following:
|
|
|
|
|
|
|
|
@example
|
2012-05-11 22:21:50 +02:00
|
|
|
qemu-system-i386 [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5
|
2009-03-28 07:44:27 +01:00
|
|
|
@end example
|
|
|
|
|
|
|
|
@item -bt device:@var{dev}[,vlan=@var{n}]
|
|
|
|
Emulate a bluetooth device @var{dev} and place it in network @var{n}
|
|
|
|
(default @code{0}). QEMU can only emulate one type of bluetooth devices
|
|
|
|
currently:
|
|
|
|
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2009-03-28 07:44:27 +01:00
|
|
|
@item keyboard
|
|
|
|
Virtual wireless keyboard implementing the HIDP bluetooth profile.
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 19:49:40 +01:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
DEFHEADING()
|
|
|
|
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
#ifdef CONFIG_TPM
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(TPM device options:)
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
|
|
|
|
DEF("tpmdev", HAS_ARG, QEMU_OPTION_tpmdev, \
|
2013-02-27 18:47:54 +01:00
|
|
|
"-tpmdev passthrough,id=id[,path=path][,cancel-path=path]\n"
|
|
|
|
" use path to provide path to a character device; default is /dev/tpm0\n"
|
|
|
|
" use cancel-path to provide path to TPM's cancel sysfs entry; if\n"
|
2017-09-29 13:10:20 +02:00
|
|
|
" not provided it will be searched for in /sys/class/misc/tpm?/device\n"
|
|
|
|
"-tpmdev emulator,id=id,chardev=dev\n"
|
|
|
|
" configure the TPM device using chardev backend\n",
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
|
|
|
|
The general form of a TPM device option is:
|
|
|
|
@table @option
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -tpmdev @var{backend},id=@var{id}[,@var{options}]
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
@findex -tpmdev
|
|
|
|
|
|
|
|
The specific backend type will determine the applicable options.
|
2013-03-20 17:34:49 +01:00
|
|
|
The @code{-tpmdev} option creates the TPM backend and requires a
|
|
|
|
@code{-device} option that specifies the TPM frontend interface model.
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
|
2017-10-02 16:03:05 +02:00
|
|
|
Use @code{-tpmdev help} to print all available TPM backend types.
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
|
2017-10-02 16:03:05 +02:00
|
|
|
@end table
|
|
|
|
|
|
|
|
The available backends are:
|
|
|
|
|
|
|
|
@table @option
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -tpmdev passthrough,id=@var{id},path=@var{path},cancel-path=@var{cancel-path}
|
2013-02-27 18:47:53 +01:00
|
|
|
|
|
|
|
(Linux-host only) Enable access to the host's TPM using the passthrough
|
|
|
|
driver.
|
|
|
|
|
|
|
|
@option{path} specifies the path to the host's TPM device, i.e., on
|
|
|
|
a Linux host this would be @code{/dev/tpm0}.
|
|
|
|
@option{path} is optional and by default @code{/dev/tpm0} is used.
|
|
|
|
|
2013-02-27 18:47:54 +01:00
|
|
|
@option{cancel-path} specifies the path to the host TPM device's sysfs
|
|
|
|
entry allowing for cancellation of an ongoing TPM command.
|
|
|
|
@option{cancel-path} is optional and by default QEMU will search for the
|
|
|
|
sysfs entry to use.
|
|
|
|
|
2013-02-27 18:47:53 +01:00
|
|
|
Some notes about using the host's TPM with the passthrough driver:
|
|
|
|
|
|
|
|
The TPM device accessed by the passthrough driver must not be
|
|
|
|
used by any other application on the host.
|
|
|
|
|
|
|
|
Since the host's firmware (BIOS/UEFI) has already initialized the TPM,
|
|
|
|
the VM's firmware (BIOS/UEFI) will not be able to initialize the
|
|
|
|
TPM again and may therefore not show a TPM-specific menu that would
|
|
|
|
otherwise allow the user to configure the TPM, e.g., allow the user to
|
|
|
|
enable/disable or activate/deactivate the TPM.
|
|
|
|
Further, if TPM ownership is released from within a VM then the host's TPM
|
|
|
|
will get disabled and deactivated. To enable and activate the
|
|
|
|
TPM again afterwards, the host has to be rebooted and the user is
|
|
|
|
required to enter the firmware's menu to enable and activate the TPM.
|
|
|
|
If the TPM is left disabled and/or deactivated most TPM commands will fail.
|
|
|
|
|
|
|
|
To create a passthrough TPM use the following two options:
|
|
|
|
@example
|
|
|
|
-tpmdev passthrough,id=tpm0 -device tpm-tis,tpmdev=tpm0
|
|
|
|
@end example
|
|
|
|
Note that the @code{-tpmdev} id is @code{tpm0} and is referenced by
|
|
|
|
@code{tpmdev=tpm0} in the device option.
|
|
|
|
|
2018-01-30 10:36:21 +01:00
|
|
|
@item -tpmdev emulator,id=@var{id},chardev=@var{dev}
|
2017-09-29 13:10:20 +02:00
|
|
|
|
|
|
|
(Linux-host only) Enable access to a TPM emulator using Unix domain socket based
|
|
|
|
chardev backend.
|
|
|
|
|
|
|
|
@option{chardev} specifies the unique ID of a character device backend that provides connection to the software TPM server.
|
|
|
|
|
|
|
|
To create a TPM emulator backend device with chardev socket backend:
|
|
|
|
@example
|
|
|
|
|
|
|
|
-chardev socket,id=chrtpm,path=/tmp/swtpm-sock -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0
|
|
|
|
|
|
|
|
@end example
|
|
|
|
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
ETEXI
|
|
|
|
|
2017-10-02 16:03:05 +02:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
Support for TPM command line options
This patch adds support for TPM command line options.
The command line options supported here are
./qemu-... -tpmdev passthrough,path=<path to TPM device>,id=<id>
-device tpm-tis,tpmdev=<id>,id=<other id>
and
./qemu-... -tpmdev help
where the latter works similar to -soundhw help and shows a list of
available TPM backends (for example 'passthrough').
Using the type parameter, the backend is chosen, i.e., 'passthrough' for the
passthrough driver. The interpretation of the other parameters along
with determining whether enough parameters were provided is pushed into
the backend driver, which needs to implement the interface function
'create' and return a TPMDriverOpts structure if the VM can be started or
'NULL' if not enough or bad parameters were provided.
Monitor support for 'info tpm' has been added. It for example prints the
following:
(qemu) info tpm
TPM devices:
tpm0: model=tpm-tis
\ tpm0: type=passthrough,path=/dev/tpm0,cancel-path=/sys/devices/pnp0/00:09/cancel
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
Reviewed-by: Joel Schopp <jschopp@linux.vnet.ibm.com>
Message-id: 1361987275-26289-2-git-send-email-stefanb@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-02-27 18:47:49 +01:00
|
|
|
DEFHEADING()
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Linux/Multiboot boot specific:)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2009-06-28 16:55:55 +02:00
|
|
|
|
|
|
|
When using these options, you can use a given Linux or Multiboot
|
|
|
|
kernel without installing it in the disk image. It can be useful
|
2009-03-28 07:44:27 +01:00
|
|
|
for easier testing of various kernels.
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("kernel", HAS_ARG, QEMU_OPTION_kernel, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-kernel bzImage use 'bzImage' as kernel image\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -kernel @var{bzImage}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -kernel
|
2009-06-28 16:55:55 +02:00
|
|
|
Use @var{bzImage} as kernel image. The kernel can be either a Linux kernel
|
|
|
|
or in multiboot format.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("append", HAS_ARG, QEMU_OPTION_append, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-append cmdline use 'cmdline' as kernel command line\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -append @var{cmdline}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -append
|
2009-03-28 07:44:27 +01:00
|
|
|
Use @var{cmdline} as kernel command line
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("initrd", HAS_ARG, QEMU_OPTION_initrd, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-initrd file use 'file' as initial ram disk\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -initrd @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -initrd
|
2009-03-28 07:44:27 +01:00
|
|
|
Use @var{file} as initial ram disk.
|
2009-06-28 16:55:55 +02:00
|
|
|
|
|
|
|
@item -initrd "@var{file1} arg=foo,@var{file2}"
|
|
|
|
|
|
|
|
This syntax is only available with multiboot.
|
|
|
|
|
|
|
|
Use @var{file1} and @var{file2} as modules and pass arg=foo as parameter to the
|
|
|
|
first module.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2012-03-02 12:56:38 +01:00
|
|
|
DEF("dtb", HAS_ARG, QEMU_OPTION_dtb, \
|
2012-03-04 12:03:54 +01:00
|
|
|
"-dtb file use 'file' as device tree image\n", QEMU_ARCH_ALL)
|
2012-03-02 12:56:38 +01:00
|
|
|
STEXI
|
|
|
|
@item -dtb @var{file}
|
|
|
|
@findex -dtb
|
|
|
|
Use @var{file} as a device tree binary (dtb) image and pass it to the kernel
|
|
|
|
on boot.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2017-10-02 16:03:00 +02:00
|
|
|
DEFHEADING(Debug/Expert options:)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
2015-04-29 17:21:53 +02:00
|
|
|
DEF("fw_cfg", HAS_ARG, QEMU_OPTION_fwcfg,
|
|
|
|
"-fw_cfg [name=]<name>,file=<file>\n"
|
2016-04-18 18:29:50 +02:00
|
|
|
" add named fw_cfg entry with contents from file\n"
|
2015-09-29 18:29:01 +02:00
|
|
|
"-fw_cfg [name=]<name>,string=<str>\n"
|
2016-04-18 18:29:50 +02:00
|
|
|
" add named fw_cfg entry with contents from string\n",
|
2015-04-29 17:21:53 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2016-04-18 18:29:50 +02:00
|
|
|
|
2015-04-29 17:21:53 +02:00
|
|
|
@item -fw_cfg [name=]@var{name},file=@var{file}
|
|
|
|
@findex -fw_cfg
|
2016-04-18 18:29:50 +02:00
|
|
|
Add named fw_cfg entry with contents from file @var{file}.
|
2015-09-29 18:29:01 +02:00
|
|
|
|
|
|
|
@item -fw_cfg [name=]@var{name},string=@var{str}
|
2016-04-18 18:29:50 +02:00
|
|
|
Add named fw_cfg entry with contents from string @var{str}.
|
|
|
|
|
|
|
|
The terminating NUL character of the contents of @var{str} will not be
|
|
|
|
included as part of the fw_cfg item data. To insert contents with
|
|
|
|
embedded NUL characters, you have to use the @var{file} parameter.
|
|
|
|
|
|
|
|
The fw_cfg entries are passed by QEMU through to the guest.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
-fw_cfg name=opt/com.mycompany/blob,file=./my_blob.bin
|
|
|
|
@end example
|
|
|
|
creates an fw_cfg entry named opt/com.mycompany/blob with contents
|
|
|
|
from ./my_blob.bin.
|
|
|
|
|
2015-04-29 17:21:53 +02:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("serial", HAS_ARG, QEMU_OPTION_serial, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-serial dev redirect the serial port to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -serial @var{dev}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -serial
|
2009-03-28 07:44:27 +01:00
|
|
|
Redirect the virtual serial port to host character device
|
|
|
|
@var{dev}. The default device is @code{vc} in graphical mode and
|
|
|
|
@code{stdio} in non graphical mode.
|
|
|
|
|
|
|
|
This option can be used several times to simulate up to 4 serial
|
|
|
|
ports.
|
|
|
|
|
|
|
|
Use @code{-serial none} to disable all serial ports.
|
|
|
|
|
|
|
|
Available character devices are:
|
2009-10-09 10:58:35 +02:00
|
|
|
@table @option
|
2009-10-09 10:58:36 +02:00
|
|
|
@item vc[:@var{W}x@var{H}]
|
2009-03-28 07:44:27 +01:00
|
|
|
Virtual console. Optionally, a width and height can be given in pixel with
|
|
|
|
@example
|
|
|
|
vc:800x600
|
|
|
|
@end example
|
|
|
|
It is also possible to specify width or height in characters:
|
|
|
|
@example
|
|
|
|
vc:80Cx24C
|
|
|
|
@end example
|
|
|
|
@item pty
|
|
|
|
[Linux only] Pseudo TTY (a new PTY is automatically allocated)
|
|
|
|
@item none
|
|
|
|
No device is allocated.
|
|
|
|
@item null
|
|
|
|
void device
|
2013-12-20 14:44:53 +01:00
|
|
|
@item chardev:@var{id}
|
|
|
|
Use a named character device defined with the @code{-chardev} option.
|
2009-03-28 07:44:27 +01:00
|
|
|
@item /dev/XXX
|
|
|
|
[Linux only] Use host tty, e.g. @file{/dev/ttyS0}. The host serial port
|
|
|
|
parameters are set according to the emulated ones.
|
|
|
|
@item /dev/parport@var{N}
|
|
|
|
[Linux only, parallel port only] Use host parallel port
|
|
|
|
@var{N}. Currently SPP and EPP parallel port features can be used.
|
|
|
|
@item file:@var{filename}
|
|
|
|
Write output to @var{filename}. No character can be read.
|
|
|
|
@item stdio
|
|
|
|
[Unix only] standard input/output
|
|
|
|
@item pipe:@var{filename}
|
|
|
|
name pipe @var{filename}
|
|
|
|
@item COM@var{n}
|
|
|
|
[Windows only] Use host serial port @var{n}
|
|
|
|
@item udp:[@var{remote_host}]:@var{remote_port}[@@[@var{src_ip}]:@var{src_port}]
|
|
|
|
This implements UDP Net Console.
|
|
|
|
When @var{remote_host} or @var{src_ip} are not specified
|
|
|
|
they default to @code{0.0.0.0}.
|
|
|
|
When not using a specified @var{src_port} a random port is automatically chosen.
|
|
|
|
|
|
|
|
If you just want a simple readonly console you can use @code{netcat} or
|
2012-05-11 22:25:50 +02:00
|
|
|
@code{nc}, by starting QEMU with: @code{-serial udp::4555} and nc as:
|
|
|
|
@code{nc -u -l -p 4555}. Any time QEMU writes something to that port it
|
2009-03-28 07:44:27 +01:00
|
|
|
will appear in the netconsole session.
|
|
|
|
|
|
|
|
If you plan to send characters back via netconsole or you want to stop
|
2012-05-11 22:25:50 +02:00
|
|
|
and start QEMU a lot of times, you should have QEMU use the same
|
2009-03-28 07:44:27 +01:00
|
|
|
source port each time by using something like @code{-serial
|
2012-05-11 22:25:50 +02:00
|
|
|
udp::4555@@:4556} to QEMU. Another approach is to use a patched
|
2009-03-28 07:44:27 +01:00
|
|
|
version of netcat which can listen to a TCP port and send and receive
|
|
|
|
characters via udp. If you have a patched version of netcat which
|
|
|
|
activates telnet remote echo and single char transfer, then you can
|
2016-12-22 15:56:38 +01:00
|
|
|
use the following options to set up a netcat redirector to allow
|
2012-05-11 22:25:50 +02:00
|
|
|
telnet on port 5555 to access the QEMU port.
|
2009-03-28 07:44:27 +01:00
|
|
|
@table @code
|
2012-04-07 09:23:36 +02:00
|
|
|
@item QEMU Options:
|
2009-03-28 07:44:27 +01:00
|
|
|
-serial udp::4555@@:4556
|
|
|
|
@item netcat options:
|
|
|
|
-u -P 4555 -L 0.0.0.0:4556 -t -p 5555 -I -T
|
|
|
|
@item telnet options:
|
|
|
|
localhost 5555
|
|
|
|
@end table
|
|
|
|
|
2014-10-02 18:17:37 +02:00
|
|
|
@item tcp:[@var{host}]:@var{port}[,@var{server}][,nowait][,nodelay][,reconnect=@var{seconds}]
|
2009-03-28 07:44:27 +01:00
|
|
|
The TCP Net Console has two modes of operation. It can send the serial
|
|
|
|
I/O to a location or wait for a connection from a location. By default
|
|
|
|
the TCP Net Console is sent to @var{host} at the @var{port}. If you use
|
|
|
|
the @var{server} option QEMU will wait for a client socket application
|
|
|
|
to connect to the port before continuing, unless the @code{nowait}
|
|
|
|
option was specified. The @code{nodelay} option disables the Nagle buffering
|
2014-10-02 18:17:37 +02:00
|
|
|
algorithm. The @code{reconnect} option only applies if @var{noserver} is
|
|
|
|
set, if the connection goes down it will attempt to reconnect at the
|
|
|
|
given interval. If @var{host} is omitted, 0.0.0.0 is assumed. Only
|
2009-03-28 07:44:27 +01:00
|
|
|
one TCP connection at a time is accepted. You can use @code{telnet} to
|
|
|
|
connect to the corresponding character device.
|
|
|
|
@table @code
|
|
|
|
@item Example to send tcp console to 192.168.0.2 port 4444
|
|
|
|
-serial tcp:192.168.0.2:4444
|
|
|
|
@item Example to listen and wait on port 4444 for connection
|
|
|
|
-serial tcp::4444,server
|
|
|
|
@item Example to not wait and listen on ip 192.168.0.100 port 4444
|
|
|
|
-serial tcp:192.168.0.100:4444,server,nowait
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item telnet:@var{host}:@var{port}[,server][,nowait][,nodelay]
|
|
|
|
The telnet protocol is used instead of raw tcp sockets. The options
|
|
|
|
work the same as if you had specified @code{-serial tcp}. The
|
|
|
|
difference is that the port acts like a telnet server or client using
|
|
|
|
telnet option negotiation. This will also allow you to send the
|
|
|
|
MAGIC_SYSRQ sequence if you use a telnet that supports sending the break
|
|
|
|
sequence. Typically in unix telnet you do it with Control-] and then
|
|
|
|
type "send break" followed by pressing the enter key.
|
|
|
|
|
2018-10-19 00:35:00 +02:00
|
|
|
@item websocket:@var{host}:@var{port},server[,nowait][,nodelay]
|
|
|
|
The WebSocket protocol is used instead of raw tcp socket. The port acts as
|
|
|
|
a WebSocket server. Client mode is not supported.
|
|
|
|
|
2014-10-02 18:17:37 +02:00
|
|
|
@item unix:@var{path}[,server][,nowait][,reconnect=@var{seconds}]
|
2009-03-28 07:44:27 +01:00
|
|
|
A unix domain socket is used instead of a tcp socket. The option works the
|
|
|
|
same as if you had specified @code{-serial tcp} except the unix domain socket
|
|
|
|
@var{path} is used for connections.
|
|
|
|
|
|
|
|
@item mon:@var{dev_string}
|
|
|
|
This is a special option to allow the monitor to be multiplexed onto
|
|
|
|
another serial port. The monitor is accessed with key sequence of
|
2013-07-03 18:29:45 +02:00
|
|
|
@key{Control-a} and then pressing @key{c}.
|
2009-03-28 07:44:27 +01:00
|
|
|
@var{dev_string} should be any one of the serial devices specified
|
|
|
|
above. An example to multiplex the monitor onto a telnet server
|
|
|
|
listening on port 4444 would be:
|
|
|
|
@table @code
|
|
|
|
@item -serial mon:telnet::4444,server,nowait
|
|
|
|
@end table
|
2013-07-11 10:55:50 +02:00
|
|
|
When the monitor is multiplexed to stdio in this way, Ctrl+C will not terminate
|
|
|
|
QEMU any more but will be passed to the guest instead.
|
2009-03-28 07:44:27 +01:00
|
|
|
|
|
|
|
@item braille
|
|
|
|
Braille device. This will use BrlAPI to display the braille output on a real
|
|
|
|
or fake device.
|
|
|
|
|
2009-10-09 10:58:37 +02:00
|
|
|
@item msmouse
|
|
|
|
Three button serial mouse. Configure the guest to use Microsoft protocol.
|
2009-03-28 07:44:27 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("parallel", HAS_ARG, QEMU_OPTION_parallel, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-parallel dev redirect the parallel port to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -parallel @var{dev}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -parallel
|
2009-03-28 07:44:27 +01:00
|
|
|
Redirect the virtual parallel port to host device @var{dev} (same
|
|
|
|
devices as the serial port). On Linux hosts, @file{/dev/parportN} can
|
|
|
|
be used to use hardware devices connected on the corresponding host
|
|
|
|
parallel port.
|
|
|
|
|
|
|
|
This option can be used several times to simulate up to 3 parallel
|
|
|
|
ports.
|
|
|
|
|
|
|
|
Use @code{-parallel none} to disable all parallel ports.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("monitor", HAS_ARG, QEMU_OPTION_monitor, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-monitor dev redirect the monitor to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2009-12-08 13:11:37 +01:00
|
|
|
@item -monitor @var{dev}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -monitor
|
2009-03-28 07:44:27 +01:00
|
|
|
Redirect the monitor to host device @var{dev} (same devices as the
|
|
|
|
serial port).
|
|
|
|
The default device is @code{vc} in graphical mode and @code{stdio} in
|
|
|
|
non graphical mode.
|
2013-05-16 18:02:55 +02:00
|
|
|
Use @code{-monitor none} to disable the default monitor.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
2009-12-08 13:11:52 +01:00
|
|
|
DEF("qmp", HAS_ARG, QEMU_OPTION_qmp, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-qmp dev like -monitor but opens in 'control' mode\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-01-20 22:25:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -qmp @var{dev}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -qmp
|
2010-01-20 22:25:27 +01:00
|
|
|
Like -monitor but opens in 'control' mode.
|
|
|
|
ETEXI
|
2014-11-17 13:31:04 +01:00
|
|
|
DEF("qmp-pretty", HAS_ARG, QEMU_OPTION_qmp_pretty, \
|
|
|
|
"-qmp-pretty dev like -qmp but uses pretty JSON formatting\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -qmp-pretty @var{dev}
|
|
|
|
@findex -qmp-pretty
|
|
|
|
Like -qmp but uses pretty JSON formatting.
|
|
|
|
ETEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
|
2009-12-08 13:11:51 +01:00
|
|
|
DEF("mon", HAS_ARG, QEMU_OPTION_mon, \
|
2017-11-14 09:11:27 +01:00
|
|
|
"-mon [chardev=]name[,mode=readline|control][,pretty[=on|off]]\n", QEMU_ARCH_ALL)
|
2009-12-08 13:11:51 +01:00
|
|
|
STEXI
|
2017-11-14 09:11:27 +01:00
|
|
|
@item -mon [chardev=]name[,mode=readline|control][,pretty[=on|off]]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -mon
|
2017-11-14 09:11:27 +01:00
|
|
|
Setup monitor on chardev @var{name}. @code{pretty} turns on JSON pretty printing
|
|
|
|
easing human reading and debugging.
|
2009-12-08 13:11:51 +01:00
|
|
|
ETEXI
|
|
|
|
|
debugcon: support for debugging consoles (e.g. Bochs port 0xe9)
Add generic support for debugging consoles (simple I/O ports which
when written to cause debugging output to be written to a target.)
The current implementation matches Bochs' port 0xe9, allowing the same
debugging code to be used for both Bochs and Qemu.
There is no vm state associated with the debugging port, simply
because it has none -- the entire interface is a single, stateless,
write-only port.
Most of the code was cribbed from the serial port driver.
v2: removed non-ISA variants (they can be introduced when/if someone
wants them, using code from the serial port); added configurable
readback (Bochs returns 0xe9 on a read from this register, mimic that
by default) This retains the apparently somewhat controversial user
friendly option, however.
v3: reimplemented the user friendly option as a synthetic option
("-debugcon foo" basically ends up being a parser-level shorthand for
"-chardev stdio,id=debugcon -device isa-debugcon,chardev=debugcon") --
this dramatically reduced the complexity while keeping the same level
of user friendliness.
v4: spaces, not tabs.
v5: update to match current top of tree. Calling qemu_chr_open()
already during parsing no longer works; defer until we are parsing the
other console-like devices.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2009-12-29 22:51:36 +01:00
|
|
|
DEF("debugcon", HAS_ARG, QEMU_OPTION_debugcon, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-debugcon dev redirect the debug console to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
debugcon: support for debugging consoles (e.g. Bochs port 0xe9)
Add generic support for debugging consoles (simple I/O ports which
when written to cause debugging output to be written to a target.)
The current implementation matches Bochs' port 0xe9, allowing the same
debugging code to be used for both Bochs and Qemu.
There is no vm state associated with the debugging port, simply
because it has none -- the entire interface is a single, stateless,
write-only port.
Most of the code was cribbed from the serial port driver.
v2: removed non-ISA variants (they can be introduced when/if someone
wants them, using code from the serial port); added configurable
readback (Bochs returns 0xe9 on a read from this register, mimic that
by default) This retains the apparently somewhat controversial user
friendly option, however.
v3: reimplemented the user friendly option as a synthetic option
("-debugcon foo" basically ends up being a parser-level shorthand for
"-chardev stdio,id=debugcon -device isa-debugcon,chardev=debugcon") --
this dramatically reduced the complexity while keeping the same level
of user friendliness.
v4: spaces, not tabs.
v5: update to match current top of tree. Calling qemu_chr_open()
already during parsing no longer works; defer until we are parsing the
other console-like devices.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2009-12-29 22:51:36 +01:00
|
|
|
STEXI
|
|
|
|
@item -debugcon @var{dev}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -debugcon
|
debugcon: support for debugging consoles (e.g. Bochs port 0xe9)
Add generic support for debugging consoles (simple I/O ports which
when written to cause debugging output to be written to a target.)
The current implementation matches Bochs' port 0xe9, allowing the same
debugging code to be used for both Bochs and Qemu.
There is no vm state associated with the debugging port, simply
because it has none -- the entire interface is a single, stateless,
write-only port.
Most of the code was cribbed from the serial port driver.
v2: removed non-ISA variants (they can be introduced when/if someone
wants them, using code from the serial port); added configurable
readback (Bochs returns 0xe9 on a read from this register, mimic that
by default) This retains the apparently somewhat controversial user
friendly option, however.
v3: reimplemented the user friendly option as a synthetic option
("-debugcon foo" basically ends up being a parser-level shorthand for
"-chardev stdio,id=debugcon -device isa-debugcon,chardev=debugcon") --
this dramatically reduced the complexity while keeping the same level
of user friendliness.
v4: spaces, not tabs.
v5: update to match current top of tree. Calling qemu_chr_open()
already during parsing no longer works; defer until we are parsing the
other console-like devices.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2009-12-29 22:51:36 +01:00
|
|
|
Redirect the debug console to host device @var{dev} (same devices as the
|
|
|
|
serial port). The debug console is an I/O port which is typically port
|
|
|
|
0xe9; writing to that I/O port sends output to this device.
|
|
|
|
The default device is @code{vc} in graphical mode and @code{stdio} in
|
|
|
|
non graphical mode.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("pidfile", HAS_ARG, QEMU_OPTION_pidfile, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-pidfile file write PID to 'file'\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -pidfile @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -pidfile
|
2009-03-28 07:44:27 +01:00
|
|
|
Store the QEMU process PID in @var{file}. It is useful if you launch QEMU
|
|
|
|
from a script.
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-05 22:08:59 +02:00
|
|
|
DEF("singlestep", 0, QEMU_OPTION_singlestep, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-singlestep always run in singlestep mode\n", QEMU_ARCH_ALL)
|
2009-04-05 22:08:59 +02:00
|
|
|
STEXI
|
|
|
|
@item -singlestep
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -singlestep
|
2009-04-05 22:08:59 +02:00
|
|
|
Run the emulation in single step mode.
|
|
|
|
ETEXI
|
|
|
|
|
2018-05-11 19:24:43 +02:00
|
|
|
DEF("preconfig", 0, QEMU_OPTION_preconfig, \
|
2018-07-05 11:14:02 +02:00
|
|
|
"--preconfig pause QEMU before machine is initialized (experimental)\n",
|
2018-05-11 19:24:43 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item --preconfig
|
|
|
|
@findex --preconfig
|
|
|
|
Pause QEMU for interactive configuration before the machine is created,
|
|
|
|
which allows querying and configuring properties that will affect
|
2018-07-05 11:14:02 +02:00
|
|
|
machine initialization. Use QMP command 'x-exit-preconfig' to exit
|
|
|
|
the preconfig state and move to the next state (i.e. run guest if -S
|
|
|
|
isn't used or pause the second time if -S is used). This option is
|
|
|
|
experimental.
|
2018-05-11 19:24:43 +02:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("S", 0, QEMU_OPTION_S, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-S freeze CPU at startup (use 'c' to start execution)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -S
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -S
|
2009-03-28 07:44:27 +01:00
|
|
|
Do not start CPU at startup (you must type 'c' in the monitor).
|
|
|
|
ETEXI
|
|
|
|
|
2013-04-19 16:42:06 +02:00
|
|
|
DEF("realtime", HAS_ARG, QEMU_OPTION_realtime,
|
|
|
|
"-realtime [mlock=on|off]\n"
|
|
|
|
" run qemu with realtime features\n"
|
|
|
|
" mlock=on|off controls mlock support (default: on)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -realtime mlock=on|off
|
|
|
|
@findex -realtime
|
|
|
|
Run qemu with realtime features.
|
|
|
|
mlocking qemu and guest memory can be enabled via @option{mlock=on}
|
|
|
|
(enabled by default).
|
|
|
|
ETEXI
|
|
|
|
|
2018-06-22 21:22:05 +02:00
|
|
|
DEF("overcommit", HAS_ARG, QEMU_OPTION_overcommit,
|
2018-07-16 21:12:08 +02:00
|
|
|
"-overcommit [mem-lock=on|off][cpu-pm=on|off]\n"
|
2018-06-22 21:22:05 +02:00
|
|
|
" run qemu with overcommit hints\n"
|
|
|
|
" mem-lock=on|off controls memory lock support (default: off)\n"
|
|
|
|
" cpu-pm=on|off controls cpu power management (default: off)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -overcommit mem-lock=on|off
|
|
|
|
@item -overcommit cpu-pm=on|off
|
|
|
|
@findex -overcommit
|
|
|
|
Run qemu with hints about host resource overcommit. The default is
|
|
|
|
to assume that host overcommits all resources.
|
|
|
|
|
|
|
|
Locking qemu and guest memory can be enabled via @option{mem-lock=on} (disabled
|
|
|
|
by default). This works when host memory is not overcommitted and reduces the
|
|
|
|
worst-case latency for guest. This is equivalent to @option{realtime}.
|
|
|
|
|
|
|
|
Guest ability to manage power state of host cpus (increasing latency for other
|
|
|
|
processes on the same host cpu, but decreasing latency for guest) can be
|
|
|
|
enabled via @option{cpu-pm=on} (disabled by default). This works best when
|
|
|
|
host CPU is not overcommitted. When used, host estimates of CPU cycle and power
|
|
|
|
utilization will be incorrect, not taking into account guest idle time.
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-05 20:43:41 +02:00
|
|
|
DEF("gdb", HAS_ARG, QEMU_OPTION_gdb, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-gdb dev wait for gdb connection on 'dev'\n", QEMU_ARCH_ALL)
|
2009-04-05 20:43:41 +02:00
|
|
|
STEXI
|
|
|
|
@item -gdb @var{dev}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -gdb
|
2009-04-05 20:43:41 +02:00
|
|
|
Wait for gdb connection on device @var{dev} (@pxref{gdb_usage}). Typical
|
|
|
|
connections will likely be TCP-based, but also UDP, pseudo TTY, or even
|
2012-05-11 22:25:50 +02:00
|
|
|
stdio are reasonable use case. The latter is allowing to start QEMU from
|
2009-04-05 20:43:41 +02:00
|
|
|
within gdb and establish the connection via a pipe:
|
|
|
|
@example
|
2012-05-11 22:21:50 +02:00
|
|
|
(gdb) target remote | exec qemu-system-i386 -gdb stdio ...
|
2009-04-05 20:43:41 +02:00
|
|
|
@end example
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2009-04-05 20:43:41 +02:00
|
|
|
DEF("s", 0, QEMU_OPTION_s, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-s shorthand for -gdb tcp::" DEFAULT_GDBSTUB_PORT "\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2009-04-05 20:43:41 +02:00
|
|
|
@item -s
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -s
|
2009-04-05 20:43:41 +02:00
|
|
|
Shorthand for -gdb tcp::1234, i.e. open a gdbserver on TCP port 1234
|
|
|
|
(@pxref{gdb_usage}).
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("d", HAS_ARG, QEMU_OPTION_d, \
|
2013-02-26 18:52:40 +01:00
|
|
|
"-d item1,... enable logging of specified items (use '-d help' for a list of log items)\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2013-02-26 18:52:40 +01:00
|
|
|
@item -d @var{item1}[,...]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -d
|
2013-02-26 18:52:40 +01:00
|
|
|
Enable logging of specified items. Use '-d help' for a list of log items.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2011-06-07 18:32:40 +02:00
|
|
|
DEF("D", HAS_ARG, QEMU_OPTION_D, \
|
2013-02-26 18:52:40 +01:00
|
|
|
"-D logfile output log to logfile (default stderr)\n",
|
2011-06-07 18:32:40 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2012-05-11 22:40:50 +02:00
|
|
|
@item -D @var{logfile}
|
2011-06-07 18:32:40 +02:00
|
|
|
@findex -D
|
2013-02-26 18:52:40 +01:00
|
|
|
Output log in @var{logfile} instead of to stderr
|
2011-06-07 18:32:40 +02:00
|
|
|
ETEXI
|
|
|
|
|
2016-03-15 15:30:20 +01:00
|
|
|
DEF("dfilter", HAS_ARG, QEMU_OPTION_DFILTER, \
|
|
|
|
"-dfilter range,.. filter debug output to range of addresses (useful for -d cpu,exec,etc..)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -dfilter @var{range1}[,...]
|
|
|
|
@findex -dfilter
|
|
|
|
Filter debug output to that relevant to a range of target addresses. The filter
|
|
|
|
spec can be either @var{start}+@var{size}, @var{start}-@var{size} or
|
|
|
|
@var{start}..@var{end} where @var{start} @var{end} and @var{size} are the
|
|
|
|
addresses and sizes required. For example:
|
|
|
|
@example
|
|
|
|
-dfilter 0x8000..0x8fff,0xffffffc000080000+0x200,0xffffffc000060000-0x1000
|
|
|
|
@end example
|
|
|
|
Will dump output for any code in the 0x1000 sized block starting at 0x8000 and
|
|
|
|
the 0x200 sized block starting at 0xffffffc000080000 and another 0x1000 sized
|
|
|
|
block starting at 0xffffffc00005f000.
|
|
|
|
ETEXI
|
|
|
|
|
2019-03-14 21:06:29 +01:00
|
|
|
DEF("seed", HAS_ARG, QEMU_OPTION_seed, \
|
|
|
|
"-seed number seed the pseudo-random number generator\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -seed @var{number}
|
|
|
|
@findex -seed
|
|
|
|
Force the guest to use a deterministic pseudo-random number generator, seeded
|
|
|
|
with @var{number}. This does not affect crypto routines within the host.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("L", HAS_ARG, QEMU_OPTION_L, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-L path set the directory for the BIOS, VGA BIOS and keymaps\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -L @var{path}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -L
|
2009-03-28 07:44:27 +01:00
|
|
|
Set the directory for the BIOS, VGA BIOS and keymaps.
|
2016-05-16 18:34:35 +02:00
|
|
|
|
|
|
|
To list all the data directories, use @code{-L help}.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("bios", HAS_ARG, QEMU_OPTION_bios, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-bios file set the filename for the BIOS\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -bios @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -bios
|
2009-03-28 07:44:27 +01:00
|
|
|
Set the filename for the BIOS.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("enable-kvm", 0, QEMU_OPTION_enable_kvm, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-enable-kvm enable KVM full virtualization support\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -enable-kvm
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -enable-kvm
|
2009-03-28 07:44:27 +01:00
|
|
|
Enable KVM full virtualization support. This option is only available
|
|
|
|
if KVM support is enabled when compiling.
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-22 17:19:10 +02:00
|
|
|
DEF("xen-domid", HAS_ARG, QEMU_OPTION_xen_domid,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-xen-domid id specify xen guest domain id\n", QEMU_ARCH_ALL)
|
2009-04-22 17:19:10 +02:00
|
|
|
DEF("xen-attach", 0, QEMU_OPTION_xen_attach,
|
|
|
|
"-xen-attach attach to existing xen domain\n"
|
2018-09-14 13:18:30 +02:00
|
|
|
" libxl will use this when starting QEMU\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2017-03-22 10:39:15 +01:00
|
|
|
DEF("xen-domid-restrict", 0, QEMU_OPTION_xen_domid_restrict,
|
|
|
|
"-xen-domid-restrict restrict set of available xen operations\n"
|
|
|
|
" to specified domain id. (Does not affect\n"
|
|
|
|
" xenpv machine type).\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-01-20 22:25:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -xen-domid @var{id}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -xen-domid
|
2010-01-20 22:25:27 +01:00
|
|
|
Specify xen guest domain @var{id} (XEN only).
|
|
|
|
@item -xen-attach
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -xen-attach
|
2010-01-20 22:25:27 +01:00
|
|
|
Attach to existing xen domain.
|
2018-09-14 13:18:30 +02:00
|
|
|
libxl will use this when starting QEMU (XEN only).
|
2017-03-22 10:39:15 +01:00
|
|
|
@findex -xen-domid-restrict
|
|
|
|
Restrict set of available xen operations to specified domain id (XEN only).
|
2010-01-20 22:25:27 +01:00
|
|
|
ETEXI
|
2009-04-22 17:19:10 +02:00
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("no-reboot", 0, QEMU_OPTION_no_reboot, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-no-reboot exit instead of rebooting\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -no-reboot
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -no-reboot
|
2009-03-28 07:44:27 +01:00
|
|
|
Exit instead of rebooting.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-shutdown", 0, QEMU_OPTION_no_shutdown, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-no-shutdown stop before shutdown\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -no-shutdown
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -no-shutdown
|
2009-03-28 07:44:27 +01:00
|
|
|
Don't exit QEMU on guest shutdown, but instead only stop the emulation.
|
|
|
|
This allows for instance switching to monitor to commit changes to the
|
|
|
|
disk image.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("loadvm", HAS_ARG, QEMU_OPTION_loadvm, \
|
|
|
|
"-loadvm [tag|id]\n" \
|
2010-03-29 21:23:52 +02:00
|
|
|
" start right away with a saved state (loadvm in monitor)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -loadvm @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -loadvm
|
2009-03-28 07:44:27 +01:00
|
|
|
Start right away with a saved state (@code{loadvm} in monitor)
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
#ifndef _WIN32
|
|
|
|
DEF("daemonize", 0, QEMU_OPTION_daemonize, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-daemonize daemonize QEMU after initializing\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
#endif
|
|
|
|
STEXI
|
|
|
|
@item -daemonize
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -daemonize
|
2009-03-28 07:44:27 +01:00
|
|
|
Daemonize the QEMU process after initialization. QEMU will not detach from
|
|
|
|
standard IO until it is ready to receive connections on any of its devices.
|
|
|
|
This option is a useful way for external programs to launch QEMU without having
|
|
|
|
to cope with initialization race conditions.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("option-rom", HAS_ARG, QEMU_OPTION_option_rom, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-option-rom rom load a file, rom, into the option ROM space\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -option-rom @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -option-rom
|
2009-03-28 07:44:27 +01:00
|
|
|
Load the contents of @var{file} as an option ROM.
|
|
|
|
This option is useful to load things like EtherBoot.
|
|
|
|
ETEXI
|
|
|
|
|
2009-09-15 13:36:04 +02:00
|
|
|
DEF("rtc", HAS_ARG, QEMU_OPTION_rtc, \
|
2018-10-18 09:12:52 +02:00
|
|
|
"-rtc [base=utc|localtime|<datetime>][,clock=host|rt|vm][,driftfix=none|slew]\n" \
|
2010-03-29 21:23:52 +02:00
|
|
|
" set the RTC base and clock, enable drift fix for clock ticks (x86 only)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
|
|
|
|
STEXI
|
|
|
|
|
2018-10-18 09:12:52 +02:00
|
|
|
@item -rtc [base=utc|localtime|@var{datetime}][,clock=host|rt|vm][,driftfix=none|slew]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -rtc
|
2009-09-15 13:36:04 +02:00
|
|
|
Specify @option{base} as @code{utc} or @code{localtime} to let the RTC start at the current
|
|
|
|
UTC or local time, respectively. @code{localtime} is required for correct date in
|
2018-10-18 09:12:52 +02:00
|
|
|
MS-DOS or Windows. To start at a specific point in time, provide @var{datetime} in the
|
2009-09-15 13:36:04 +02:00
|
|
|
format @code{2006-06-17T16:01:21} or @code{2006-06-17}. The default base is UTC.
|
|
|
|
|
2014-04-07 11:34:58 +02:00
|
|
|
By default the RTC is driven by the host system time. This allows using of the
|
2009-09-15 13:36:04 +02:00
|
|
|
RTC as accurate reference clock inside the guest, specifically if the host
|
|
|
|
time is smoothly following an accurate external reference clock, e.g. via NTP.
|
2012-03-30 12:31:21 +02:00
|
|
|
If you want to isolate the guest time from the host, you can set @option{clock}
|
2018-10-18 09:12:52 +02:00
|
|
|
to @code{rt} instead, which provides a host monotonic clock if host support it.
|
|
|
|
To even prevent the RTC from progressing during suspension, you can set @option{clock}
|
|
|
|
to @code{vm} (virtual clock). @samp{clock=vm} is recommended especially in
|
|
|
|
icount mode in order to preserve determinism; however, note that in icount mode
|
|
|
|
the speed of the virtual clock is variable and can in general differ from the
|
|
|
|
host clock.
|
2009-09-15 13:36:04 +02:00
|
|
|
|
2009-09-15 13:36:04 +02:00
|
|
|
Enable @option{driftfix} (i386 targets only) if you experience time drift problems,
|
|
|
|
specifically with Windows' ACPI HAL. This option will try to figure out how
|
|
|
|
many timer interrupts were not processed by the Windows guest and will
|
|
|
|
re-inject them.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("icount", HAS_ARG, QEMU_OPTION_icount, \
|
2017-01-24 08:17:47 +01:00
|
|
|
"-icount [shift=N|auto][,align=on|off][,sleep=on|off,rr=record|replay,rrfile=<filename>,rrsnapshot=<snapshot>]\n" \
|
2009-04-05 20:43:37 +02:00
|
|
|
" enable virtual instruction counter with 2^N clock ticks per\n" \
|
2015-05-29 17:14:05 +02:00
|
|
|
" instruction, enable aligning the host and virtual clocks\n" \
|
|
|
|
" or disable real time cpu sleeping\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2017-01-24 08:17:47 +01:00
|
|
|
@item -icount [shift=@var{N}|auto][,rr=record|replay,rrfile=@var{filename},rrsnapshot=@var{snapshot}]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -icount
|
2009-03-28 07:44:27 +01:00
|
|
|
Enable virtual instruction counter. The virtual cpu will execute one
|
2009-10-09 10:58:36 +02:00
|
|
|
instruction every 2^@var{N} ns of virtual time. If @code{auto} is specified
|
2009-03-28 07:44:27 +01:00
|
|
|
then the virtual cpu speed will be automatically adjusted to keep virtual
|
|
|
|
time within a few seconds of real time.
|
|
|
|
|
2015-05-29 17:14:05 +02:00
|
|
|
When the virtual cpu is sleeping, the virtual time will advance at default
|
2016-02-26 16:16:51 +01:00
|
|
|
speed unless @option{sleep=on|off} is specified.
|
|
|
|
With @option{sleep=on|off}, the virtual time will jump to the next timer deadline
|
2015-05-29 17:14:05 +02:00
|
|
|
instantly whenever the virtual cpu goes to sleep mode and will not advance
|
|
|
|
if no timer is enabled. This behavior give deterministic execution times from
|
|
|
|
the guest point of view.
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
Note that while this option can give deterministic behavior, it does not
|
|
|
|
provide cycle accurate emulation. Modern CPUs contain superscalar out of
|
|
|
|
order cores with complex cache hierarchies. The number of instructions
|
|
|
|
executed often has little or no correlation with actual performance.
|
2014-07-25 11:56:29 +02:00
|
|
|
|
2015-08-26 13:17:13 +02:00
|
|
|
@option{align=on} will activate the delay algorithm which will try
|
2014-07-25 11:56:29 +02:00
|
|
|
to synchronise the host clock and the virtual clock. The goal is to
|
|
|
|
have a guest running at the real frequency imposed by the shift option.
|
|
|
|
Whenever the guest clock is behind the host clock and if
|
2015-04-27 10:12:49 +02:00
|
|
|
@option{align=on} is specified then we print a message to the user
|
2014-07-25 11:56:29 +02:00
|
|
|
to inform about the delay.
|
|
|
|
Currently this option does not work when @option{shift} is @code{auto}.
|
|
|
|
Note: The sync algorithm will work for those shift values for which
|
|
|
|
the guest clock runs ahead of the host clock. Typically this happens
|
|
|
|
when the shift value is high (how high depends on the host machine).
|
2015-09-17 18:25:18 +02:00
|
|
|
|
|
|
|
When @option{rr} option is specified deterministic record/replay is enabled.
|
|
|
|
Replay log is written into @var{filename} file in record mode and
|
|
|
|
read from this file in replay mode.
|
2017-01-24 08:17:47 +01:00
|
|
|
|
|
|
|
Option rrsnapshot is used to create new vm snapshot named @var{snapshot}
|
|
|
|
at the start of execution recording. In replay mode this option is used
|
|
|
|
to load the initial VM state.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2009-04-25 14:56:19 +02:00
|
|
|
DEF("watchdog", HAS_ARG, QEMU_OPTION_watchdog, \
|
2015-06-11 17:32:05 +02:00
|
|
|
"-watchdog model\n" \
|
2010-03-29 21:23:52 +02:00
|
|
|
" enable virtual hardware watchdog [default=none]\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-04-25 14:56:19 +02:00
|
|
|
STEXI
|
|
|
|
@item -watchdog @var{model}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -watchdog
|
2009-04-25 14:56:19 +02:00
|
|
|
Create a virtual hardware watchdog device. Once enabled (by a guest
|
|
|
|
action), the watchdog must be periodically polled by an agent inside
|
2015-06-11 17:32:05 +02:00
|
|
|
the guest or else the guest will be restarted. Choose a model for
|
|
|
|
which your guest has drivers.
|
2009-04-25 14:56:19 +02:00
|
|
|
|
2015-06-11 17:32:05 +02:00
|
|
|
The @var{model} is the model of hardware watchdog to emulate. Use
|
|
|
|
@code{-watchdog help} to list available hardware models. Only one
|
2009-04-25 14:56:19 +02:00
|
|
|
watchdog can be enabled for a guest.
|
2015-06-11 17:32:05 +02:00
|
|
|
|
|
|
|
The following models may be available:
|
|
|
|
@table @option
|
|
|
|
@item ib700
|
|
|
|
iBASE 700 is a very simple ISA watchdog with a single timer.
|
|
|
|
@item i6300esb
|
|
|
|
Intel 6300ESB I/O controller hub is a much more featureful PCI-based
|
|
|
|
dual-timer watchdog.
|
2015-02-05 11:28:32 +01:00
|
|
|
@item diag288
|
|
|
|
A virtual watchdog for s390x backed by the diagnose 288 hypercall
|
|
|
|
(currently KVM only).
|
2015-06-11 17:32:05 +02:00
|
|
|
@end table
|
2009-04-25 14:56:19 +02:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("watchdog-action", HAS_ARG, QEMU_OPTION_watchdog_action, \
|
2017-10-02 16:03:07 +02:00
|
|
|
"-watchdog-action reset|shutdown|poweroff|inject-nmi|pause|debug|none\n" \
|
2010-03-29 21:23:52 +02:00
|
|
|
" action when watchdog fires [default=reset]\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-04-25 14:56:19 +02:00
|
|
|
STEXI
|
|
|
|
@item -watchdog-action @var{action}
|
2013-02-13 19:49:38 +01:00
|
|
|
@findex -watchdog-action
|
2009-04-25 14:56:19 +02:00
|
|
|
|
|
|
|
The @var{action} controls what QEMU will do when the watchdog timer
|
|
|
|
expires.
|
|
|
|
The default is
|
|
|
|
@code{reset} (forcefully reset the guest).
|
|
|
|
Other possible actions are:
|
|
|
|
@code{shutdown} (attempt to gracefully shutdown the guest),
|
|
|
|
@code{poweroff} (forcefully poweroff the guest),
|
2017-10-02 16:03:07 +02:00
|
|
|
@code{inject-nmi} (inject a NMI into the guest),
|
2009-04-25 14:56:19 +02:00
|
|
|
@code{pause} (pause the guest),
|
|
|
|
@code{debug} (print a debug message and continue), or
|
|
|
|
@code{none} (do nothing).
|
|
|
|
|
|
|
|
Note that the @code{shutdown} action requires that the guest responds
|
|
|
|
to ACPI signals, which it may not be able to do in the sort of
|
|
|
|
situations where the watchdog would have expired, and thus
|
|
|
|
@code{-watchdog-action shutdown} is not recommended for production use.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item -watchdog i6300esb -watchdog-action pause
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx -watchdog ib700
|
2009-04-25 14:56:19 +02:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("echr", HAS_ARG, QEMU_OPTION_echr, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-echr chr set terminal escape character instead of ctrl-a\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
|
|
|
|
2009-10-09 10:58:36 +02:00
|
|
|
@item -echr @var{numeric_ascii_value}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -echr
|
2009-03-28 07:44:27 +01:00
|
|
|
Change the escape character used for switching to the monitor when using
|
|
|
|
monitor and serial sharing. The default is @code{0x01} when using the
|
|
|
|
@code{-nographic} option. @code{0x01} is equal to pressing
|
|
|
|
@code{Control-a}. You can select a different character from the ascii
|
|
|
|
control keys where 1 through 26 map to Control-a through Control-z. For
|
|
|
|
instance you could use the either of the following to change the escape
|
|
|
|
character to Control-t.
|
|
|
|
@table @code
|
|
|
|
@item -echr 0x14
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx -echr 20
|
2009-03-28 07:44:27 +01:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("show-cursor", 0, QEMU_OPTION_show_cursor, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-show-cursor show cursor\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2010-01-20 22:25:27 +01:00
|
|
|
@item -show-cursor
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -show-cursor
|
2010-01-20 22:25:27 +01:00
|
|
|
Show cursor.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("tb-size", HAS_ARG, QEMU_OPTION_tb_size, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-tb-size n set TB size\n", QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2010-01-20 22:25:27 +01:00
|
|
|
@item -tb-size @var{n}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -tb-size
|
2010-01-20 22:25:27 +01:00
|
|
|
Set TB size.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("incoming", HAS_ARG, QEMU_OPTION_incoming, \
|
2015-02-10 20:40:47 +01:00
|
|
|
"-incoming tcp:[host]:port[,to=maxport][,ipv4][,ipv6]\n" \
|
|
|
|
"-incoming rdma:host:port[,ipv4][,ipv6]\n" \
|
|
|
|
"-incoming unix:socketpath\n" \
|
|
|
|
" prepare for incoming migration, listen on\n" \
|
|
|
|
" specified protocol and socket address\n" \
|
|
|
|
"-incoming fd:fd\n" \
|
|
|
|
"-incoming exec:cmdline\n" \
|
|
|
|
" accept incoming migration on given file descriptor\n" \
|
2015-05-29 20:52:52 +02:00
|
|
|
" or from given external command\n" \
|
|
|
|
"-incoming defer\n" \
|
|
|
|
" wait for the URI to be specified via migrate_incoming\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
STEXI
|
2015-02-10 20:40:47 +01:00
|
|
|
@item -incoming tcp:[@var{host}]:@var{port}[,to=@var{maxport}][,ipv4][,ipv6]
|
2015-06-15 14:35:59 +02:00
|
|
|
@itemx -incoming rdma:@var{host}:@var{port}[,ipv4][,ipv6]
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -incoming
|
2015-02-10 20:40:47 +01:00
|
|
|
Prepare for incoming migration, listen on a given tcp port.
|
|
|
|
|
|
|
|
@item -incoming unix:@var{socketpath}
|
|
|
|
Prepare for incoming migration, listen on a given unix socket.
|
|
|
|
|
|
|
|
@item -incoming fd:@var{fd}
|
|
|
|
Accept incoming migration from a given filedescriptor.
|
|
|
|
|
|
|
|
@item -incoming exec:@var{cmdline}
|
|
|
|
Accept incoming migration as an output from specified external command.
|
2015-05-29 20:52:52 +02:00
|
|
|
|
|
|
|
@item -incoming defer
|
|
|
|
Wait for the URI to be specified via migrate_incoming. The monitor can
|
|
|
|
be used to change settings (such as migration parameters) prior to issuing
|
|
|
|
the migrate_incoming to allow the migration to begin.
|
2009-03-28 07:44:27 +01:00
|
|
|
ETEXI
|
|
|
|
|
2017-01-16 12:31:51 +01:00
|
|
|
DEF("only-migratable", 0, QEMU_OPTION_only_migratable, \
|
|
|
|
"-only-migratable allow only migratable devices\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -only-migratable
|
|
|
|
@findex -only-migratable
|
|
|
|
Only allow migratable devices. Devices will not be allowed to enter an
|
|
|
|
unmigratable state.
|
|
|
|
ETEXI
|
|
|
|
|
2009-12-08 13:11:46 +01:00
|
|
|
DEF("nodefaults", 0, QEMU_OPTION_nodefaults, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-nodefaults don't create default devices\n", QEMU_ARCH_ALL)
|
2009-12-08 13:11:46 +01:00
|
|
|
STEXI
|
2010-01-16 18:19:44 +01:00
|
|
|
@item -nodefaults
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -nodefaults
|
2012-07-16 14:35:10 +02:00
|
|
|
Don't create default devices. Normally, QEMU sets the default devices like serial
|
|
|
|
port, parallel port, virtual console, monitor device, VGA adapter, floppy and
|
|
|
|
CD-ROM drive and others. The @code{-nodefaults} option will disable all those
|
|
|
|
default devices.
|
2009-12-08 13:11:46 +01:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 07:44:27 +01:00
|
|
|
#ifndef _WIN32
|
|
|
|
DEF("chroot", HAS_ARG, QEMU_OPTION_chroot, \
|
2010-03-29 21:23:52 +02:00
|
|
|
"-chroot dir chroot to dir just before starting the VM\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
#endif
|
|
|
|
STEXI
|
2009-10-09 10:58:36 +02:00
|
|
|
@item -chroot @var{dir}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -chroot
|
2009-03-28 07:44:27 +01:00
|
|
|
Immediately before starting guest execution, chroot to the specified
|
|
|
|
directory. Especially useful in combination with -runas.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
#ifndef _WIN32
|
|
|
|
DEF("runas", HAS_ARG, QEMU_OPTION_runas, \
|
2017-09-15 19:10:44 +02:00
|
|
|
"-runas user change to user id user just before starting the VM\n" \
|
|
|
|
" user can be numeric uid:gid instead\n",
|
2010-03-29 21:23:52 +02:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 07:44:27 +01:00
|
|
|
#endif
|
|
|
|
STEXI
|
2009-10-09 10:58:36 +02:00
|
|
|
@item -runas @var{user}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -runas
|
2009-03-28 07:44:27 +01:00
|
|
|
Immediately before starting guest execution, drop root privileges, switching
|
|
|
|
to the specified user.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("prom-env", HAS_ARG, QEMU_OPTION_prom_env,
|
|
|
|
"-prom-env variable=value\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" set OpenBIOS nvram variables\n",
|
|
|
|
QEMU_ARCH_PPC | QEMU_ARCH_SPARC)
|
2010-01-20 22:25:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -prom-env @var{variable}=@var{value}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -prom-env
|
2010-01-20 22:25:27 +01:00
|
|
|
Set OpenBIOS nvram @var{variable} to given @var{value} (PPC, SPARC only).
|
|
|
|
ETEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("semihosting", 0, QEMU_OPTION_semihosting,
|
2014-04-22 20:18:42 +02:00
|
|
|
"-semihosting semihosting mode\n",
|
2015-06-19 12:08:43 +02:00
|
|
|
QEMU_ARCH_ARM | QEMU_ARCH_M68K | QEMU_ARCH_XTENSA | QEMU_ARCH_LM32 |
|
2019-04-03 21:53:05 +02:00
|
|
|
QEMU_ARCH_MIPS | QEMU_ARCH_NIOS2)
|
2010-01-20 22:25:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -semihosting
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -semihosting
|
2019-04-03 21:53:05 +02:00
|
|
|
Enable semihosting mode (ARM, M68K, Xtensa, MIPS, Nios II only).
|
2014-12-11 13:07:48 +01:00
|
|
|
ETEXI
|
|
|
|
DEF("semihosting-config", HAS_ARG, QEMU_OPTION_semihosting_config,
|
2019-05-14 16:30:14 +02:00
|
|
|
"-semihosting-config [enable=on|off][,target=native|gdb|auto][,chardev=id][,arg=str[,...]]\n" \
|
2015-06-19 15:17:45 +02:00
|
|
|
" semihosting configuration\n",
|
2015-06-19 12:08:43 +02:00
|
|
|
QEMU_ARCH_ARM | QEMU_ARCH_M68K | QEMU_ARCH_XTENSA | QEMU_ARCH_LM32 |
|
2019-04-03 21:53:05 +02:00
|
|
|
QEMU_ARCH_MIPS | QEMU_ARCH_NIOS2)
|
2014-12-11 13:07:48 +01:00
|
|
|
STEXI
|
2019-05-14 16:30:14 +02:00
|
|
|
@item -semihosting-config [enable=on|off][,target=native|gdb|auto][,chardev=id][,arg=str[,...]]
|
2014-12-11 13:07:48 +01:00
|
|
|
@findex -semihosting-config
|
2019-04-03 21:53:05 +02:00
|
|
|
Enable and configure semihosting (ARM, M68K, Xtensa, MIPS, Nios II only).
|
2015-06-19 15:17:45 +02:00
|
|
|
@table @option
|
|
|
|
@item target=@code{native|gdb|auto}
|
|
|
|
Defines where the semihosting calls will be addressed, to QEMU (@code{native})
|
|
|
|
or to GDB (@code{gdb}). The default is @code{auto}, which means @code{gdb}
|
|
|
|
during debug sessions and @code{native} otherwise.
|
2019-05-14 16:30:14 +02:00
|
|
|
@item chardev=@var{str1}
|
|
|
|
Send the output to a chardev backend output for native or auto output when not in gdb
|
2015-06-19 15:17:45 +02:00
|
|
|
@item arg=@var{str1},arg=@var{str2},...
|
|
|
|
Allows the user to pass input arguments, and can be used multiple times to build
|
|
|
|
up a list. The old-style @code{-kernel}/@code{-append} method of passing a
|
|
|
|
command line is still supported for backward compatibility. If both the
|
|
|
|
@code{--semihosting-config arg} and the @code{-kernel}/@code{-append} are
|
|
|
|
specified, the former is passed to semihosting as it always takes precedence.
|
|
|
|
@end table
|
2010-01-20 22:25:27 +01:00
|
|
|
ETEXI
|
2009-03-28 07:44:27 +01:00
|
|
|
DEF("old-param", 0, QEMU_OPTION_old_param,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-old-param old param mode\n", QEMU_ARCH_ARM)
|
2010-01-20 22:25:27 +01:00
|
|
|
STEXI
|
|
|
|
@item -old-param
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -old-param (ARM)
|
2010-01-20 22:25:27 +01:00
|
|
|
Old param mode (ARM only).
|
|
|
|
ETEXI
|
|
|
|
|
2012-08-14 23:44:08 +02:00
|
|
|
DEF("sandbox", HAS_ARG, QEMU_OPTION_sandbox, \
|
2017-03-13 22:13:27 +01:00
|
|
|
"-sandbox on[,obsolete=allow|deny][,elevateprivileges=allow|deny|children]\n" \
|
2017-03-13 22:18:51 +01:00
|
|
|
" [,spawn=allow|deny][,resourcecontrol=allow|deny]\n" \
|
2017-03-01 23:17:29 +01:00
|
|
|
" Enable seccomp mode 2 system call filter (default 'off').\n" \
|
|
|
|
" use 'obsolete' to allow obsolete system calls that are provided\n" \
|
|
|
|
" by the kernel, but typically no longer used by modern\n" \
|
2017-03-13 22:13:27 +01:00
|
|
|
" C library implementations.\n" \
|
|
|
|
" use 'elevateprivileges' to allow or deny QEMU process to elevate\n" \
|
|
|
|
" its privileges by blacklisting all set*uid|gid system calls.\n" \
|
|
|
|
" The value 'children' will deny set*uid|gid system calls for\n" \
|
2017-03-13 22:16:01 +01:00
|
|
|
" main QEMU process but will allow forks and execves to run unprivileged\n" \
|
|
|
|
" use 'spawn' to avoid QEMU to spawn new threads or processes by\n" \
|
2017-03-13 22:18:51 +01:00
|
|
|
" blacklisting *fork and execve\n" \
|
|
|
|
" use 'resourcecontrol' to disable process affinity and schedular priority\n",
|
2012-08-14 23:44:08 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2017-03-13 22:18:51 +01:00
|
|
|
@item -sandbox @var{arg}[,obsolete=@var{string}][,elevateprivileges=@var{string}][,spawn=@var{string}][,resourcecontrol=@var{string}]
|
2012-08-14 23:44:08 +02:00
|
|
|
@findex -sandbox
|
|
|
|
Enable Seccomp mode 2 system call filter. 'on' will enable syscall filtering and 'off' will
|
|
|
|
disable it. The default is 'off'.
|
2017-03-01 23:17:29 +01:00
|
|
|
@table @option
|
|
|
|
@item obsolete=@var{string}
|
|
|
|
Enable Obsolete system calls
|
2017-03-13 22:13:27 +01:00
|
|
|
@item elevateprivileges=@var{string}
|
|
|
|
Disable set*uid|gid system calls
|
2017-03-13 22:16:01 +01:00
|
|
|
@item spawn=@var{string}
|
|
|
|
Disable *fork and execve
|
2017-03-13 22:18:51 +01:00
|
|
|
@item resourcecontrol=@var{string}
|
|
|
|
Disable process affinity and schedular priority
|
2017-03-01 23:17:29 +01:00
|
|
|
@end table
|
2012-08-14 23:44:08 +02:00
|
|
|
ETEXI
|
|
|
|
|
2009-10-14 10:39:28 +02:00
|
|
|
DEF("readconfig", HAS_ARG, QEMU_OPTION_readconfig,
|
2010-03-29 21:23:52 +02:00
|
|
|
"-readconfig <file>\n", QEMU_ARCH_ALL)
|
2010-01-16 18:19:44 +01:00
|
|
|
STEXI
|
|
|
|
@item -readconfig @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -readconfig
|
2012-07-16 14:28:32 +02:00
|
|
|
Read device configuration from @var{file}. This approach is useful when you want to spawn
|
|
|
|
QEMU process with many command line options but you don't want to exceed the command line
|
|
|
|
character limit.
|
2010-01-16 18:19:44 +01:00
|
|
|
ETEXI
|
2009-10-14 10:39:28 +02:00
|
|
|
DEF("writeconfig", HAS_ARG, QEMU_OPTION_writeconfig,
|
|
|
|
"-writeconfig <file>\n"
|
2010-03-29 21:23:52 +02:00
|
|
|
" read/write config file\n", QEMU_ARCH_ALL)
|
2010-01-16 18:19:44 +01:00
|
|
|
STEXI
|
|
|
|
@item -writeconfig @var{file}
|
2010-02-05 23:52:05 +01:00
|
|
|
@findex -writeconfig
|
2012-07-16 14:28:32 +02:00
|
|
|
Write device configuration to @var{file}. The @var{file} can be either filename to save
|
|
|
|
command line and device configuration into file or dash @code{-}) character to print the
|
|
|
|
output to stdout. This can be later used as input file for @code{-readconfig} option.
|
2010-01-16 18:19:44 +01:00
|
|
|
ETEXI
|
2018-08-21 12:59:56 +02:00
|
|
|
|
2012-05-02 18:07:29 +02:00
|
|
|
DEF("no-user-config", 0, QEMU_OPTION_nouserconfig,
|
|
|
|
"-no-user-config\n"
|
2017-10-04 05:00:25 +02:00
|
|
|
" do not load default user-provided config files at startup\n",
|
2012-05-02 18:07:29 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -no-user-config
|
|
|
|
@findex -no-user-config
|
|
|
|
The @code{-no-user-config} option makes QEMU not load any of the user-provided
|
2017-10-04 05:00:25 +02:00
|
|
|
config files on @var{sysconfdir}.
|
2010-01-21 17:57:58 +01:00
|
|
|
ETEXI
|
2018-08-21 12:59:56 +02:00
|
|
|
|
2010-08-09 12:48:32 +02:00
|
|
|
DEF("trace", HAS_ARG, QEMU_OPTION_trace,
|
2016-01-07 14:55:26 +01:00
|
|
|
"-trace [[enable=]<pattern>][,events=<file>][,file=<file>]\n"
|
2011-08-31 20:31:31 +02:00
|
|
|
" specify tracing options\n",
|
2010-08-09 12:48:32 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2011-08-31 20:31:31 +02:00
|
|
|
HXCOMM This line is not accurate, as some sub-options are backend-specific but
|
|
|
|
HXCOMM HX does not support conditional compilation of text.
|
2016-06-17 16:44:08 +02:00
|
|
|
@item -trace [[enable=]@var{pattern}][,events=@var{file}][,file=@var{file}]
|
2010-08-09 12:48:32 +02:00
|
|
|
@findex -trace
|
2016-06-17 16:44:09 +02:00
|
|
|
@include qemu-option-trace.texi
|
2010-08-09 12:48:32 +02:00
|
|
|
ETEXI
|
2010-01-16 18:19:44 +01:00
|
|
|
|
2013-02-13 19:49:37 +01:00
|
|
|
HXCOMM Internal use
|
|
|
|
DEF("qtest", HAS_ARG, QEMU_OPTION_qtest, "", QEMU_ARCH_ALL)
|
|
|
|
DEF("qtest-log", HAS_ARG, QEMU_OPTION_qtest_log, "", QEMU_ARCH_ALL)
|
2012-03-28 15:42:02 +02:00
|
|
|
|
2012-08-03 20:39:21 +02:00
|
|
|
#ifdef __linux__
|
|
|
|
DEF("enable-fips", 0, QEMU_OPTION_enablefips,
|
|
|
|
"-enable-fips enable FIPS 140-2 compliance\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
#endif
|
|
|
|
STEXI
|
|
|
|
@item -enable-fips
|
|
|
|
@findex -enable-fips
|
|
|
|
Enable FIPS 140-2 compliance mode.
|
|
|
|
ETEXI
|
|
|
|
|
2012-10-05 19:51:45 +02:00
|
|
|
HXCOMM Deprecated by -machine accel=tcg property
|
2012-11-20 15:11:21 +01:00
|
|
|
DEF("no-kvm", 0, QEMU_OPTION_no_kvm, "", QEMU_ARCH_I386)
|
2012-10-05 19:51:45 +02:00
|
|
|
|
2013-07-04 05:02:46 +02:00
|
|
|
DEF("msg", HAS_ARG, QEMU_OPTION_msg,
|
|
|
|
"-msg timestamp[=on|off]\n"
|
|
|
|
" change the format of messages\n"
|
|
|
|
" on|off controls leading timestamps (default:on)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -msg timestamp[=on|off]
|
|
|
|
@findex -msg
|
|
|
|
prepend a timestamp to each log message.(default:on)
|
|
|
|
ETEXI
|
|
|
|
|
2014-06-20 15:26:08 +02:00
|
|
|
DEF("dump-vmstate", HAS_ARG, QEMU_OPTION_dump_vmstate,
|
|
|
|
"-dump-vmstate <file>\n"
|
|
|
|
" Output vmstate information in JSON format to file.\n"
|
|
|
|
" Use the scripts/vmstate-static-checker.py file to\n"
|
|
|
|
" check for possible regressions in migration code\n"
|
2015-09-04 21:30:04 +02:00
|
|
|
" by comparing two such vmstate dumps.\n",
|
2014-06-20 15:26:08 +02:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -dump-vmstate @var{file}
|
|
|
|
@findex -dump-vmstate
|
|
|
|
Dump json-encoded vmstate information for current machine type to file
|
|
|
|
in @var{file}
|
|
|
|
ETEXI
|
|
|
|
|
2018-08-15 17:42:49 +02:00
|
|
|
DEF("enable-sync-profile", 0, QEMU_OPTION_enable_sync_profile,
|
|
|
|
"-enable-sync-profile\n"
|
|
|
|
" enable synchronization profiling\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -enable-sync-profile
|
|
|
|
@findex -enable-sync-profile
|
|
|
|
Enable synchronization profiling.
|
|
|
|
ETEXI
|
|
|
|
|
2017-01-04 13:50:37 +01:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
2017-10-02 16:03:00 +02:00
|
|
|
|
|
|
|
DEFHEADING(Generic object creation:)
|
2017-01-04 13:50:37 +01:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
2015-05-13 18:14:03 +02:00
|
|
|
|
|
|
|
DEF("object", HAS_ARG, QEMU_OPTION_object,
|
|
|
|
"-object TYPENAME[,PROP1=VALUE1,...]\n"
|
|
|
|
" create a new object of type TYPENAME setting properties\n"
|
|
|
|
" in the order they are specified. Note that the 'id'\n"
|
|
|
|
" property must be set. These objects are placed in the\n"
|
|
|
|
" '/objects' path.\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -object @var{typename}[,@var{prop1}=@var{value1},...]
|
|
|
|
@findex -object
|
|
|
|
Create a new object of type @var{typename} setting properties
|
|
|
|
in the order they are specified. Note that the 'id'
|
|
|
|
property must be set. These objects are placed in the
|
|
|
|
'/objects' path.
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
hostmem-file: add "align" option
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
fails with a kernel message like
[617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
Because there is no common approach to get such alignment requirement,
we add the 'align' option to 'memory-backend-file', so that users or
management utils, which have enough knowledge about the backend, can
specify a proper alignment via this option.
Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Message-Id: <20171211072806.2812-2-haozhong.zhang@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[ehabkost: fixed typo, fixed error_setg() format string]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-12-11 08:28:04 +01:00
|
|
|
@item -object memory-backend-file,id=@var{id},size=@var{size},mem-path=@var{dir},share=@var{on|off},discard-data=@var{on|off},merge=@var{on|off},dump=@var{on|off},prealloc=@var{on|off},host-nodes=@var{host-nodes},policy=@var{default|preferred|bind|interleave},align=@var{align}
|
2015-05-13 18:14:03 +02:00
|
|
|
|
|
|
|
Creates a memory file backend object, which can be used to back
|
2017-11-28 17:15:28 +01:00
|
|
|
the guest RAM with huge pages.
|
|
|
|
|
|
|
|
The @option{id} parameter is a unique ID that will be used to reference this
|
|
|
|
memory region when configuring the @option{-numa} argument.
|
|
|
|
|
|
|
|
The @option{size} option provides the size of the memory region, and accepts
|
|
|
|
common suffixes, eg @option{500M}.
|
|
|
|
|
|
|
|
The @option{mem-path} provides the path to either a shared memory or huge page
|
|
|
|
filesystem mount.
|
|
|
|
|
2015-05-13 18:14:03 +02:00
|
|
|
The @option{share} boolean option determines whether the memory
|
|
|
|
region is marked as private to QEMU, or shared. The latter allows
|
|
|
|
a co-operating external process to access the QEMU memory region.
|
2017-11-28 17:15:28 +01:00
|
|
|
|
2017-12-13 15:37:37 +01:00
|
|
|
The @option{share} is also required for pvrdma devices due to
|
|
|
|
limitations in the RDMA API provided by Linux.
|
|
|
|
|
|
|
|
Setting share=on might affect the ability to configure NUMA
|
|
|
|
bindings for the memory backend under some circumstances, see
|
|
|
|
Documentation/vm/numa_memory_policy.txt on the Linux kernel
|
|
|
|
source tree for additional details.
|
|
|
|
|
2017-08-24 21:23:15 +02:00
|
|
|
Setting the @option{discard-data} boolean option to @var{on}
|
|
|
|
indicates that file contents can be destroyed when QEMU exits,
|
|
|
|
to avoid unnecessarily flushing data to the backing file. Note
|
|
|
|
that @option{discard-data} is only an optimization, and QEMU
|
|
|
|
might not discard file contents if it aborts unexpectedly or is
|
|
|
|
terminated using SIGKILL.
|
2015-05-13 18:14:03 +02:00
|
|
|
|
2017-11-28 17:15:28 +01:00
|
|
|
The @option{merge} boolean option enables memory merge, also known as
|
|
|
|
MADV_MERGEABLE, so that Kernel Samepage Merging will consider the pages for
|
|
|
|
memory deduplication.
|
|
|
|
|
|
|
|
Setting the @option{dump} boolean option to @var{off} excludes the memory from
|
|
|
|
core dumps. This feature is also known as MADV_DONTDUMP.
|
|
|
|
|
|
|
|
The @option{prealloc} boolean option enables memory preallocation.
|
|
|
|
|
|
|
|
The @option{host-nodes} option binds the memory range to a list of NUMA host
|
|
|
|
nodes.
|
|
|
|
|
|
|
|
The @option{policy} option sets the NUMA policy to one of the following values:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item @var{default}
|
|
|
|
default host policy
|
|
|
|
|
|
|
|
@item @var{preferred}
|
|
|
|
prefer the given host node list for allocation
|
|
|
|
|
|
|
|
@item @var{bind}
|
|
|
|
restrict memory allocation to the given host node list
|
|
|
|
|
|
|
|
@item @var{interleave}
|
|
|
|
interleave memory allocations across the given host node list
|
|
|
|
@end table
|
|
|
|
|
hostmem-file: add "align" option
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
fails with a kernel message like
[617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
Because there is no common approach to get such alignment requirement,
we add the 'align' option to 'memory-backend-file', so that users or
management utils, which have enough knowledge about the backend, can
specify a proper alignment via this option.
Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Message-Id: <20171211072806.2812-2-haozhong.zhang@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[ehabkost: fixed typo, fixed error_setg() format string]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-12-11 08:28:04 +01:00
|
|
|
The @option{align} option specifies the base address alignment when
|
|
|
|
QEMU mmap(2) @option{mem-path}, and accepts common suffixes, eg
|
|
|
|
@option{2M}. Some backend store specified by @option{mem-path}
|
|
|
|
requires an alignment different than the default one used by QEMU, eg
|
|
|
|
the device DAX /dev/dax0.0 requires 2M alignment rather than 4K. In
|
|
|
|
such cases, users can specify the required alignment via this option.
|
|
|
|
|
2018-07-18 09:48:00 +02:00
|
|
|
The @option{pmem} option specifies whether the backing file specified
|
|
|
|
by @option{mem-path} is in host persistent memory that can be accessed
|
|
|
|
using the SNIA NVM programming model (e.g. Intel NVDIMM).
|
|
|
|
If @option{pmem} is set to 'on', QEMU will take necessary operations to
|
|
|
|
guarantee the persistence of its own writes to @option{mem-path}
|
|
|
|
(e.g. in vNVDIMM label emulation and live migration).
|
2019-04-22 02:48:48 +02:00
|
|
|
Also, we will map the backend-file with MAP_SYNC flag, which ensures the
|
|
|
|
file metadata is in sync for @option{mem-path} in case of host crash
|
|
|
|
or a power failure. MAP_SYNC requires support from both the host kernel
|
|
|
|
(since Linux kernel 4.15) and the filesystem of @option{mem-path} mounted
|
|
|
|
with DAX option.
|
2018-07-18 09:48:00 +02:00
|
|
|
|
2017-12-13 15:37:37 +01:00
|
|
|
@item -object memory-backend-ram,id=@var{id},merge=@var{on|off},dump=@var{on|off},share=@var{on|off},prealloc=@var{on|off},size=@var{size},host-nodes=@var{host-nodes},policy=@var{default|preferred|bind|interleave}
|
2017-11-28 17:15:29 +01:00
|
|
|
|
|
|
|
Creates a memory backend object, which can be used to back the guest RAM.
|
|
|
|
Memory backend objects offer more control than the @option{-m} option that is
|
|
|
|
traditionally used to define guest RAM. Please refer to
|
|
|
|
@option{memory-backend-file} for a description of the options.
|
|
|
|
|
2018-08-28 17:38:40 +02:00
|
|
|
@item -object memory-backend-memfd,id=@var{id},merge=@var{on|off},dump=@var{on|off},share=@var{on|off},prealloc=@var{on|off},size=@var{size},host-nodes=@var{host-nodes},policy=@var{default|preferred|bind|interleave},seal=@var{on|off},hugetlb=@var{on|off},hugetlbsize=@var{size}
|
2018-02-01 14:27:54 +01:00
|
|
|
|
|
|
|
Creates an anonymous memory file backend object, which allows QEMU to
|
|
|
|
share the memory with an external process (e.g. when using
|
|
|
|
vhost-user). The memory is allocated with memfd and optional
|
|
|
|
sealing. (Linux only)
|
|
|
|
|
|
|
|
The @option{seal} option creates a sealed-file, that will block
|
|
|
|
further resizing the memory ('on' by default).
|
|
|
|
|
|
|
|
The @option{hugetlb} option specify the file to be created resides in
|
|
|
|
the hugetlbfs filesystem (since Linux 4.14). Used in conjunction with
|
|
|
|
the @option{hugetlb} option, the @option{hugetlbsize} option specify
|
|
|
|
the hugetlb page size on systems that support multiple hugetlb page
|
|
|
|
sizes (it must be a power of 2 value supported by the system).
|
|
|
|
|
|
|
|
In some versions of Linux, the @option{hugetlb} option is incompatible
|
|
|
|
with the @option{seal} option (requires at least Linux 4.16).
|
|
|
|
|
|
|
|
Please refer to @option{memory-backend-file} for a description of the
|
|
|
|
other options.
|
|
|
|
|
2018-08-28 17:38:40 +02:00
|
|
|
The @option{share} boolean option is @var{on} by default with memfd.
|
|
|
|
|
2015-05-13 18:14:03 +02:00
|
|
|
@item -object rng-random,id=@var{id},filename=@var{/dev/random}
|
|
|
|
|
|
|
|
Creates a random number generator backend which obtains entropy from
|
|
|
|
a device on the host. The @option{id} parameter is a unique ID that
|
|
|
|
will be used to reference this entropy backend from the @option{virtio-rng}
|
|
|
|
device. The @option{filename} parameter specifies which file to obtain
|
VirtIO-RNG: Update default entropy source to `/dev/urandom`
When QEMU exposes a VirtIO-RNG device to the guest, that device needs a
source of entropy, and that source needs to be "non-blocking", like
`/dev/urandom`. However, currently QEMU defaults to the problematic
`/dev/random`, which on Linux is "blocking" (as in, it waits until
sufficient entropy is available).
Why prefer `/dev/urandom` over `/dev/random`?
---------------------------------------------
The man pages of urandom(4) and random(4) state:
"The /dev/random device is a legacy interface which dates back to a
time where the cryptographic primitives used in the implementation
of /dev/urandom were not widely trusted. It will return random
bytes only within the estimated number of bits of fresh noise in the
entropy pool, blocking if necessary. /dev/random is suitable for
applications that need high quality randomness, and can afford
indeterminate delays."
Further, the "Usage" section of the said man pages state:
"The /dev/random interface is considered a legacy interface, and
/dev/urandom is preferred and sufficient in all use cases, with the
exception of applications which require randomness during early boot
time; for these applications, getrandom(2) must be used instead,
because it will block until the entropy pool is initialized.
"If a seed file is saved across reboots as recommended below (all
major Linux distributions have done this since 2000 at least), the
output is cryptographically secure against attackers without local
root access as soon as it is reloaded in the boot sequence, and
perfectly adequate for network encryption session keys. Since reads
from /dev/random may block, users will usually want to open it in
nonblocking mode (or perform a read with timeout), and provide some
sort of user notification if the desired entropy is not immediately
available."
And refer to random(7) for a comparison of `/dev/random` and
`/dev/urandom`.
What about other OSes?
----------------------
`/dev/urandom` exists and works on OS-X, FreeBSD, DragonFlyBSD, NetBSD
and OpenBSD, which cover all the non-Linux platforms we explicitly
support, aside from Windows.
On Windows `/dev/random` doesn't work either so we don't regress.
This is actually another argument in favour of using the newly
proposed 'rng-builtin' backend by default, as that will work on
Windows.
- - -
Given the above, change the entropy source for VirtIO-RNG device to
`/dev/urandom`.
Related discussion in these[1][2] past threads.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg08335.html
-- "RNG: Any reason QEMU doesn't default to `/dev/urandom`?"
[2] https://lists.nongnu.org/archive/html/qemu-devel/2018-09/msg02724.html
-- "[RFC] Virtio RNG: Consider changing the default entropy source to
/dev/urandom"
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Message-Id: <20190529143106.11789-2-lvivier@redhat.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
2019-05-29 16:31:03 +02:00
|
|
|
entropy from and if omitted defaults to @option{/dev/urandom}.
|
2015-05-13 18:14:03 +02:00
|
|
|
|
|
|
|
@item -object rng-egd,id=@var{id},chardev=@var{chardevid}
|
|
|
|
|
|
|
|
Creates a random number generator backend which obtains entropy from
|
|
|
|
an external daemon running on the host. The @option{id} parameter is
|
|
|
|
a unique ID that will be used to reference this entropy backend from
|
|
|
|
the @option{virtio-rng} device. The @option{chardev} parameter is
|
|
|
|
the unique ID of a character device backend that provides the connection
|
|
|
|
to the RNG daemon.
|
|
|
|
|
crypto: introduce new module for TLS anonymous credentials
Introduce a QCryptoTLSCredsAnon class which is used to
manage anonymous TLS credentials. Use of this class is
generally discouraged since it does not offer strong
security, but it is required for backwards compatibility
with the current VNC server implementation.
Simple example CLI configuration:
$QEMU -object tls-creds-anon,id=tls0,endpoint=server
Example using pre-created diffie-hellman parameters
$QEMU -object tls-creds-anon,id=tls0,endpoint=server,\
dir=/path/to/creds/dir
The 'id' value in the -object args will be used to associate the
credentials with the network services. For example, when the VNC
server is later converted it would use
$QEMU -object tls-creds-anon,id=tls0,.... \
-vnc 127.0.0.1:1,tls-creds=tls0
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2015-03-13 18:39:26 +01:00
|
|
|
@item -object tls-creds-anon,id=@var{id},endpoint=@var{endpoint},dir=@var{/path/to/cred/dir},verify-peer=@var{on|off}
|
|
|
|
|
|
|
|
Creates a TLS anonymous credentials object, which can be used to provide
|
|
|
|
TLS support on network backends. The @option{id} parameter is a unique
|
|
|
|
ID which network backends will use to access the credentials. The
|
|
|
|
@option{endpoint} is either @option{server} or @option{client} depending
|
|
|
|
on whether the QEMU network backend that uses the credentials will be
|
|
|
|
acting as a client or as a server. If @option{verify-peer} is enabled
|
|
|
|
(the default) then once the handshake is completed, the peer credentials
|
|
|
|
will be verified, though this is a no-op for anonymous credentials.
|
|
|
|
|
|
|
|
The @var{dir} parameter tells QEMU where to find the credential
|
|
|
|
files. For server endpoints, this directory may contain a file
|
|
|
|
@var{dh-params.pem} providing diffie-hellman parameters to use
|
|
|
|
for the TLS server. If the file is missing, QEMU will generate
|
|
|
|
a set of DH parameters at startup. This is a computationally
|
|
|
|
expensive operation that consumes random pool entropy, so it is
|
|
|
|
recommended that a persistent set of parameters be generated
|
|
|
|
upfront and saved.
|
|
|
|
|
crypto: Implement TLS Pre-Shared Keys (PSK).
Pre-Shared Keys (PSK) is a simpler mechanism for enabling TLS
connections than using certificates. It requires only a simple secret
key:
$ mkdir -m 0700 /tmp/keys
$ psktool -u rjones -p /tmp/keys/keys.psk
$ cat /tmp/keys/keys.psk
rjones:d543770c15ad93d76443fb56f501a31969235f47e999720ae8d2336f6a13fcbc
The key can be secretly shared between clients and servers. Clients
must specify the directory containing the "keys.psk" file and a
username (defaults to "qemu"). Servers must specify only the
directory.
Example NBD client:
$ qemu-img info \
--object tls-creds-psk,id=tls0,dir=/tmp/keys,username=rjones,endpoint=client \
--image-opts \
file.driver=nbd,file.host=localhost,file.port=10809,file.tls-creds=tls0,file.export=/
Example NBD server using qemu-nbd:
$ qemu-nbd -t -x / \
--object tls-creds-psk,id=tls0,endpoint=server,dir=/tmp/keys \
--tls-creds tls0 \
image.qcow2
Example NBD server using nbdkit:
$ nbdkit -n -e / -fv \
--tls=on --tls-psk=/tmp/keys/keys.psk \
file file=disk.img
Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2018-07-03 10:03:03 +02:00
|
|
|
@item -object tls-creds-psk,id=@var{id},endpoint=@var{endpoint},dir=@var{/path/to/keys/dir}[,username=@var{username}]
|
|
|
|
|
|
|
|
Creates a TLS Pre-Shared Keys (PSK) credentials object, which can be used to provide
|
|
|
|
TLS support on network backends. The @option{id} parameter is a unique
|
|
|
|
ID which network backends will use to access the credentials. The
|
|
|
|
@option{endpoint} is either @option{server} or @option{client} depending
|
|
|
|
on whether the QEMU network backend that uses the credentials will be
|
|
|
|
acting as a client or as a server. For clients only, @option{username}
|
|
|
|
is the username which will be sent to the server. If omitted
|
|
|
|
it defaults to ``qemu''.
|
|
|
|
|
|
|
|
The @var{dir} parameter tells QEMU where to find the keys file.
|
|
|
|
It is called ``@var{dir}/keys.psk'' and contains ``username:key''
|
|
|
|
pairs. This file can most easily be created using the GnuTLS
|
|
|
|
@code{psktool} program.
|
|
|
|
|
|
|
|
For server endpoints, @var{dir} may also contain a file
|
|
|
|
@var{dh-params.pem} providing diffie-hellman parameters to use
|
|
|
|
for the TLS server. If the file is missing, QEMU will generate
|
|
|
|
a set of DH parameters at startup. This is a computationally
|
|
|
|
expensive operation that consumes random pool entropy, so it is
|
|
|
|
recommended that a persistent set of parameters be generated
|
|
|
|
up front and saved.
|
|
|
|
|
2017-12-08 15:14:30 +01:00
|
|
|
@item -object tls-creds-x509,id=@var{id},endpoint=@var{endpoint},dir=@var{/path/to/cred/dir},priority=@var{priority},verify-peer=@var{on|off},passwordid=@var{id}
|
2015-03-13 18:39:26 +01:00
|
|
|
|
|
|
|
Creates a TLS anonymous credentials object, which can be used to provide
|
|
|
|
TLS support on network backends. The @option{id} parameter is a unique
|
|
|
|
ID which network backends will use to access the credentials. The
|
|
|
|
@option{endpoint} is either @option{server} or @option{client} depending
|
|
|
|
on whether the QEMU network backend that uses the credentials will be
|
|
|
|
acting as a client or as a server. If @option{verify-peer} is enabled
|
|
|
|
(the default) then once the handshake is completed, the peer credentials
|
|
|
|
will be verified. With x509 certificates, this implies that the clients
|
|
|
|
must be provided with valid client certificates too.
|
|
|
|
|
|
|
|
The @var{dir} parameter tells QEMU where to find the credential
|
|
|
|
files. For server endpoints, this directory may contain a file
|
|
|
|
@var{dh-params.pem} providing diffie-hellman parameters to use
|
|
|
|
for the TLS server. If the file is missing, QEMU will generate
|
|
|
|
a set of DH parameters at startup. This is a computationally
|
|
|
|
expensive operation that consumes random pool entropy, so it is
|
|
|
|
recommended that a persistent set of parameters be generated
|
|
|
|
upfront and saved.
|
|
|
|
|
|
|
|
For x509 certificate credentials the directory will contain further files
|
|
|
|
providing the x509 certificates. The certificates must be stored
|
|
|
|
in PEM format, in filenames @var{ca-cert.pem}, @var{ca-crl.pem} (optional),
|
|
|
|
@var{server-cert.pem} (only servers), @var{server-key.pem} (only servers),
|
|
|
|
@var{client-cert.pem} (only clients), and @var{client-key.pem} (only clients).
|
|
|
|
|
2015-10-15 17:14:42 +02:00
|
|
|
For the @var{server-key.pem} and @var{client-key.pem} files which
|
|
|
|
contain sensitive private keys, it is possible to use an encrypted
|
|
|
|
version by providing the @var{passwordid} parameter. This provides
|
|
|
|
the ID of a previously created @code{secret} object containing the
|
|
|
|
password for decryption.
|
|
|
|
|
2017-12-08 15:14:30 +01:00
|
|
|
The @var{priority} parameter allows to override the global default
|
|
|
|
priority used by gnutls. This can be useful if the system administrator
|
|
|
|
needs to use a weaker set of crypto priorities for QEMU without
|
|
|
|
potentially forcing the weakness onto all applications. Or conversely
|
|
|
|
if one wants wants a stronger default for QEMU than for all other
|
|
|
|
applications, they can do this through this parameter. Its format is
|
|
|
|
a gnutls priority string as described at
|
|
|
|
@url{https://gnutls.org/manual/html_node/Priority-Strings.html}.
|
|
|
|
|
2016-03-01 06:37:02 +01:00
|
|
|
@item -object filter-buffer,id=@var{id},netdev=@var{netdevid},interval=@var{t}[,queue=@var{all|rx|tx}][,status=@var{on|off}]
|
2015-10-07 05:52:21 +02:00
|
|
|
|
|
|
|
Interval @var{t} can't be 0, this filter batches the packet delivery: all
|
|
|
|
packets arriving in a given interval on netdev @var{netdevid} are delayed
|
|
|
|
until the end of the interval. Interval is in microseconds.
|
2016-03-01 06:37:02 +01:00
|
|
|
@option{status} is optional that indicate whether the netfilter is
|
|
|
|
on (enabled) or off (disabled), the default status for netfilter will be 'on'.
|
2015-10-07 05:52:21 +02:00
|
|
|
|
|
|
|
queue @var{all|rx|tx} is an option that can be applied to any netfilter.
|
|
|
|
|
|
|
|
@option{all}: the filter is attached both to the receive and the transmit
|
|
|
|
queue of the netdev (default).
|
|
|
|
|
|
|
|
@option{rx}: the filter is attached to the receive queue of the netdev,
|
|
|
|
where it will receive packets sent to the netdev.
|
|
|
|
|
|
|
|
@option{tx}: the filter is attached to the transmit queue of the netdev,
|
|
|
|
where it will receive packets sent by the netdev.
|
|
|
|
|
2017-07-04 08:53:48 +02:00
|
|
|
@item -object filter-mirror,id=@var{id},netdev=@var{netdevid},outdev=@var{chardevid},queue=@var{all|rx|tx}[,vnet_hdr_support]
|
net/filter-mirror:Add filter-mirror
Filter-mirror is a netfilter plugin.
It gives qemu the ability to mirror
packets to a chardev.
usage:
-netdev tap,id=hn0
-chardev socket,id=mirror0,host=ip_primary,port=X,server,nowait
-filter-mirror,id=m0,netdev=hn0,queue=tx/rx/all,outdev=mirror0
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Reviewed-by: Yang Hongyang <hongyang.yang@easystack.cn>
Reviewed-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-03-15 08:41:33 +01:00
|
|
|
|
2017-07-04 08:53:48 +02:00
|
|
|
filter-mirror on netdev @var{netdevid},mirror net packet to chardev@var{chardevid}, if it has the vnet_hdr_support flag, filter-mirror will mirror packet with vnet_hdr_len.
|
net/filter-mirror:Add filter-mirror
Filter-mirror is a netfilter plugin.
It gives qemu the ability to mirror
packets to a chardev.
usage:
-netdev tap,id=hn0
-chardev socket,id=mirror0,host=ip_primary,port=X,server,nowait
-filter-mirror,id=m0,netdev=hn0,queue=tx/rx/all,outdev=mirror0
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Reviewed-by: Yang Hongyang <hongyang.yang@easystack.cn>
Reviewed-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-03-15 08:41:33 +01:00
|
|
|
|
2017-07-04 08:53:49 +02:00
|
|
|
@item -object filter-redirector,id=@var{id},netdev=@var{netdevid},indev=@var{chardevid},outdev=@var{chardevid},queue=@var{all|rx|tx}[,vnet_hdr_support]
|
net/filter-mirror: implement filter-redirector
Filter-redirector is a netfilter plugin.
It gives qemu the ability to redirect net packet.
redirector can redirect filter's net packet to outdev.
and redirect indev's packet to filter.
filter
+
redirector |
+--------------+
| | |
indev +-----------+ +----------> outdev
| | |
+--------------+
|
v
filter
usage:
-netdev user,id=hn0
-chardev socket,id=s0,host=ip_primary,port=X,server,nowait
-chardev socket,id=s1,host=ip_primary,port=Y,server,nowait
-filter-redirector,id=r0,netdev=hn0,queue=tx/rx/all,indev=s0,outdev=s1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-03-17 09:16:26 +01:00
|
|
|
|
|
|
|
filter-redirector on netdev @var{netdevid},redirect filter's net packet to chardev
|
2017-07-04 08:53:49 +02:00
|
|
|
@var{chardevid},and redirect indev's packet to filter.if it has the vnet_hdr_support flag,
|
|
|
|
filter-redirector will redirect packet with vnet_hdr_len.
|
net/filter-mirror: implement filter-redirector
Filter-redirector is a netfilter plugin.
It gives qemu the ability to redirect net packet.
redirector can redirect filter's net packet to outdev.
and redirect indev's packet to filter.
filter
+
redirector |
+--------------+
| | |
indev +-----------+ +----------> outdev
| | |
+--------------+
|
v
filter
usage:
-netdev user,id=hn0
-chardev socket,id=s0,host=ip_primary,port=X,server,nowait
-chardev socket,id=s1,host=ip_primary,port=Y,server,nowait
-filter-redirector,id=r0,netdev=hn0,queue=tx/rx/all,indev=s0,outdev=s1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-03-17 09:16:26 +01:00
|
|
|
Create a filter-redirector we need to differ outdev id from indev id, id can not
|
|
|
|
be the same. we can just use indev or outdev, but at least one of indev or outdev
|
|
|
|
need to be specified.
|
|
|
|
|
2017-07-04 08:53:55 +02:00
|
|
|
@item -object filter-rewriter,id=@var{id},netdev=@var{netdevid},queue=@var{all|rx|tx},[vnet_hdr_support]
|
filter-rewriter: introduce filter-rewriter initialization
Filter-rewriter is a part of COLO project.
It will rewrite some of secondary packet to make
secondary guest's tcp connection established successfully.
In this module we will rewrite tcp packet's ack to the secondary
from primary,and rewrite tcp packet's seq to the primary from
secondary.
usage:
colo secondary:
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
-object filter-rewriter,id=rew0,netdev=hn0,queue=all
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:32 +02:00
|
|
|
|
|
|
|
Filter-rewriter is a part of COLO project.It will rewrite tcp packet to
|
|
|
|
secondary from primary to keep secondary tcp connection,and rewrite
|
|
|
|
tcp packet to primary from secondary make tcp packet can be handled by
|
2017-07-04 08:53:55 +02:00
|
|
|
client.if it has the vnet_hdr_support flag, we can parse packet with vnet header.
|
filter-rewriter: introduce filter-rewriter initialization
Filter-rewriter is a part of COLO project.
It will rewrite some of secondary packet to make
secondary guest's tcp connection established successfully.
In this module we will rewrite tcp packet's ack to the secondary
from primary,and rewrite tcp packet's seq to the primary from
secondary.
usage:
colo secondary:
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
-object filter-rewriter,id=rew0,netdev=hn0,queue=all
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:32 +02:00
|
|
|
|
|
|
|
usage:
|
|
|
|
colo secondary:
|
|
|
|
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
|
|
|
|
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
|
|
|
|
-object filter-rewriter,id=rew0,netdev=hn0,queue=all
|
|
|
|
|
2016-10-11 07:28:32 +02:00
|
|
|
@item -object filter-dump,id=@var{id},netdev=@var{dev}[,file=@var{filename}][,maxlen=@var{len}]
|
2015-10-13 12:40:02 +02:00
|
|
|
|
|
|
|
Dump the network traffic on netdev @var{dev} to the file specified by
|
|
|
|
@var{filename}. At most @var{len} bytes (64k by default) per packet are stored.
|
|
|
|
The file format is libpcap, so it can be analyzed with tools such as tcpdump
|
|
|
|
or Wireshark.
|
|
|
|
|
2019-06-09 18:44:29 +02:00
|
|
|
@item -object colo-compare,id=@var{id},primary_in=@var{chardevid},secondary_in=@var{chardevid},outdev=@var{chardevid},iothread=@var{id}[,vnet_hdr_support][,notify_dev=@var{id}]
|
colo-compare: introduce colo compare initialization
This a COLO net ascii figure:
Primary qemu Secondary qemu
+--------------------------------------------------------------+ +----------------------------------------------------------------+
| +----------------------------------------------------------+ | | +-----------------------------------------------------------+ |
| | | | | | | |
| | guest | | | | guest | |
| | | | | | | |
| +-------^--------------------------+-----------------------+ | | +---------------------+--------+----------------------------+ |
| | | | | ^ | |
| | | | | | | |
| | +------------------------------------------------------+ | | | |
|netfilter| | | | | | netfilter | | |
| +----------+ +----------------------------+ | | | +-----------------------------------------------------------+ |
| | | | | | out | | | | | | filter excute order | |
| | | | +-----------------------------+ | | | | | | +-------------------> | |
| | | | | | | | | | | | | | TCP | |
| | +-----+--+-+ +-----v----+ +-----v----+ |pri +----+----+sec| | | | +------------+ +---+----+---v+rewriter++ +------------+ | |
| | | | | | | | |in | |in | | | | | | | | | | | | |
| | | filter | | filter | | filter +------> colo <------+ +--------> filter +--> adjust | adjust +--> filter | | |
| | | mirror | |redirector| |redirector| | | compare | | | | | | redirector | | ack | seq | | redirector | | |
| | | | | | | | | | | | | | | | | | | | | | | |
| | +----^-----+ +----+-----+ +----------+ | +---------+ | | | | +------------+ +--------+--------------+ +---+--------+ | |
| | | tx | rx rx | | | | | tx all | rx | |
| | | | | | | | +-----------------------------------------------------------+ |
| | | +--------------+ | | | | | |
| | | filter excute order | | | | | | |
| | | +----------------> | | | +--------------------------------------------------------+ |
| +-----------------------------------------+ | | |
| | | | | |
+--------------------------------------------------------------+ +----------------------------------------------------------------+
|guest receive | guest send
| |
+--------+----------------------------v------------------------+
| | NOTE: filter direction is rx/tx/all
| tap | rx:receive packets sent to the netdev
| | tx:receive packets sent by the netdev
+--------------------------------------------------------------+
In COLO-compare, we do packet comparing job.
Packets coming from the primary char indev will be sent to outdev.
Packets coming from the secondary char dev will be dropped after comparing.
colo-comapre need two input chardev and one output chardev:
primary_in=chardev1-id (source: primary send packet)
secondary_in=chardev2-id (source: secondary send packet)
outdev=chardev3-id
usage:
primary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
secondary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=red0,host=3.3.3.3,port=9003
-chardev socket,id=red1,host=3.3.3.3,port=9004
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:26 +02:00
|
|
|
|
|
|
|
Colo-compare gets packet from primary_in@var{chardevid} and secondary_in@var{chardevid}, than compare primary packet with
|
|
|
|
secondary packet. If the packets are same, we will output primary
|
|
|
|
packet to outdev@var{chardevid}, else we will notify colo-frame
|
|
|
|
do checkpoint and send primary packet to outdev@var{chardevid}.
|
2019-04-26 11:07:30 +02:00
|
|
|
In order to improve efficiency, we need to put the task of comparison
|
|
|
|
in another thread. If it has the vnet_hdr_support flag, colo compare
|
|
|
|
will send/recv packet with vnet_hdr_len.
|
2019-06-09 18:44:29 +02:00
|
|
|
If you want to use Xen COLO, will need the notify_dev to notify Xen
|
|
|
|
colo-frame to do checkpoint.
|
colo-compare: introduce colo compare initialization
This a COLO net ascii figure:
Primary qemu Secondary qemu
+--------------------------------------------------------------+ +----------------------------------------------------------------+
| +----------------------------------------------------------+ | | +-----------------------------------------------------------+ |
| | | | | | | |
| | guest | | | | guest | |
| | | | | | | |
| +-------^--------------------------+-----------------------+ | | +---------------------+--------+----------------------------+ |
| | | | | ^ | |
| | | | | | | |
| | +------------------------------------------------------+ | | | |
|netfilter| | | | | | netfilter | | |
| +----------+ +----------------------------+ | | | +-----------------------------------------------------------+ |
| | | | | | out | | | | | | filter excute order | |
| | | | +-----------------------------+ | | | | | | +-------------------> | |
| | | | | | | | | | | | | | TCP | |
| | +-----+--+-+ +-----v----+ +-----v----+ |pri +----+----+sec| | | | +------------+ +---+----+---v+rewriter++ +------------+ | |
| | | | | | | | |in | |in | | | | | | | | | | | | |
| | | filter | | filter | | filter +------> colo <------+ +--------> filter +--> adjust | adjust +--> filter | | |
| | | mirror | |redirector| |redirector| | | compare | | | | | | redirector | | ack | seq | | redirector | | |
| | | | | | | | | | | | | | | | | | | | | | | |
| | +----^-----+ +----+-----+ +----------+ | +---------+ | | | | +------------+ +--------+--------------+ +---+--------+ | |
| | | tx | rx rx | | | | | tx all | rx | |
| | | | | | | | +-----------------------------------------------------------+ |
| | | +--------------+ | | | | | |
| | | filter excute order | | | | | | |
| | | +----------------> | | | +--------------------------------------------------------+ |
| +-----------------------------------------+ | | |
| | | | | |
+--------------------------------------------------------------+ +----------------------------------------------------------------+
|guest receive | guest send
| |
+--------+----------------------------v------------------------+
| | NOTE: filter direction is rx/tx/all
| tap | rx:receive packets sent to the netdev
| | tx:receive packets sent by the netdev
+--------------------------------------------------------------+
In COLO-compare, we do packet comparing job.
Packets coming from the primary char indev will be sent to outdev.
Packets coming from the secondary char dev will be dropped after comparing.
colo-comapre need two input chardev and one output chardev:
primary_in=chardev1-id (source: primary send packet)
secondary_in=chardev2-id (source: secondary send packet)
outdev=chardev3-id
usage:
primary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
secondary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=red0,host=3.3.3.3,port=9003
-chardev socket,id=red1,host=3.3.3.3,port=9004
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:26 +02:00
|
|
|
|
|
|
|
we must use it with the help of filter-mirror and filter-redirector.
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
2019-06-09 18:44:29 +02:00
|
|
|
KVM COLO
|
|
|
|
|
colo-compare: introduce colo compare initialization
This a COLO net ascii figure:
Primary qemu Secondary qemu
+--------------------------------------------------------------+ +----------------------------------------------------------------+
| +----------------------------------------------------------+ | | +-----------------------------------------------------------+ |
| | | | | | | |
| | guest | | | | guest | |
| | | | | | | |
| +-------^--------------------------+-----------------------+ | | +---------------------+--------+----------------------------+ |
| | | | | ^ | |
| | | | | | | |
| | +------------------------------------------------------+ | | | |
|netfilter| | | | | | netfilter | | |
| +----------+ +----------------------------+ | | | +-----------------------------------------------------------+ |
| | | | | | out | | | | | | filter excute order | |
| | | | +-----------------------------+ | | | | | | +-------------------> | |
| | | | | | | | | | | | | | TCP | |
| | +-----+--+-+ +-----v----+ +-----v----+ |pri +----+----+sec| | | | +------------+ +---+----+---v+rewriter++ +------------+ | |
| | | | | | | | |in | |in | | | | | | | | | | | | |
| | | filter | | filter | | filter +------> colo <------+ +--------> filter +--> adjust | adjust +--> filter | | |
| | | mirror | |redirector| |redirector| | | compare | | | | | | redirector | | ack | seq | | redirector | | |
| | | | | | | | | | | | | | | | | | | | | | | |
| | +----^-----+ +----+-----+ +----------+ | +---------+ | | | | +------------+ +--------+--------------+ +---+--------+ | |
| | | tx | rx rx | | | | | tx all | rx | |
| | | | | | | | +-----------------------------------------------------------+ |
| | | +--------------+ | | | | | |
| | | filter excute order | | | | | | |
| | | +----------------> | | | +--------------------------------------------------------+ |
| +-----------------------------------------+ | | |
| | | | | |
+--------------------------------------------------------------+ +----------------------------------------------------------------+
|guest receive | guest send
| |
+--------+----------------------------v------------------------+
| | NOTE: filter direction is rx/tx/all
| tap | rx:receive packets sent to the netdev
| | tx:receive packets sent by the netdev
+--------------------------------------------------------------+
In COLO-compare, we do packet comparing job.
Packets coming from the primary char indev will be sent to outdev.
Packets coming from the secondary char dev will be dropped after comparing.
colo-comapre need two input chardev and one output chardev:
primary_in=chardev1-id (source: primary send packet)
secondary_in=chardev2-id (source: secondary send packet)
outdev=chardev3-id
usage:
primary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
secondary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=red0,host=3.3.3.3,port=9003
-chardev socket,id=red1,host=3.3.3.3,port=9004
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:26 +02:00
|
|
|
primary:
|
|
|
|
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
|
|
|
|
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
|
|
|
|
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
|
|
|
|
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
|
|
|
|
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
|
|
|
|
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
|
|
|
|
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
|
|
|
|
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
|
2019-04-26 11:07:30 +02:00
|
|
|
-object iothread,id=iothread1
|
colo-compare: introduce colo compare initialization
This a COLO net ascii figure:
Primary qemu Secondary qemu
+--------------------------------------------------------------+ +----------------------------------------------------------------+
| +----------------------------------------------------------+ | | +-----------------------------------------------------------+ |
| | | | | | | |
| | guest | | | | guest | |
| | | | | | | |
| +-------^--------------------------+-----------------------+ | | +---------------------+--------+----------------------------+ |
| | | | | ^ | |
| | | | | | | |
| | +------------------------------------------------------+ | | | |
|netfilter| | | | | | netfilter | | |
| +----------+ +----------------------------+ | | | +-----------------------------------------------------------+ |
| | | | | | out | | | | | | filter excute order | |
| | | | +-----------------------------+ | | | | | | +-------------------> | |
| | | | | | | | | | | | | | TCP | |
| | +-----+--+-+ +-----v----+ +-----v----+ |pri +----+----+sec| | | | +------------+ +---+----+---v+rewriter++ +------------+ | |
| | | | | | | | |in | |in | | | | | | | | | | | | |
| | | filter | | filter | | filter +------> colo <------+ +--------> filter +--> adjust | adjust +--> filter | | |
| | | mirror | |redirector| |redirector| | | compare | | | | | | redirector | | ack | seq | | redirector | | |
| | | | | | | | | | | | | | | | | | | | | | | |
| | +----^-----+ +----+-----+ +----------+ | +---------+ | | | | +------------+ +--------+--------------+ +---+--------+ | |
| | | tx | rx rx | | | | | tx all | rx | |
| | | | | | | | +-----------------------------------------------------------+ |
| | | +--------------+ | | | | | |
| | | filter excute order | | | | | | |
| | | +----------------> | | | +--------------------------------------------------------+ |
| +-----------------------------------------+ | | |
| | | | | |
+--------------------------------------------------------------+ +----------------------------------------------------------------+
|guest receive | guest send
| |
+--------+----------------------------v------------------------+
| | NOTE: filter direction is rx/tx/all
| tap | rx:receive packets sent to the netdev
| | tx:receive packets sent by the netdev
+--------------------------------------------------------------+
In COLO-compare, we do packet comparing job.
Packets coming from the primary char indev will be sent to outdev.
Packets coming from the secondary char dev will be dropped after comparing.
colo-comapre need two input chardev and one output chardev:
primary_in=chardev1-id (source: primary send packet)
secondary_in=chardev2-id (source: secondary send packet)
outdev=chardev3-id
usage:
primary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
secondary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=red0,host=3.3.3.3,port=9003
-chardev socket,id=red1,host=3.3.3.3,port=9004
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:26 +02:00
|
|
|
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
|
|
|
|
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
|
|
|
|
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
|
2019-04-26 11:07:30 +02:00
|
|
|
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0,iothread=iothread1
|
colo-compare: introduce colo compare initialization
This a COLO net ascii figure:
Primary qemu Secondary qemu
+--------------------------------------------------------------+ +----------------------------------------------------------------+
| +----------------------------------------------------------+ | | +-----------------------------------------------------------+ |
| | | | | | | |
| | guest | | | | guest | |
| | | | | | | |
| +-------^--------------------------+-----------------------+ | | +---------------------+--------+----------------------------+ |
| | | | | ^ | |
| | | | | | | |
| | +------------------------------------------------------+ | | | |
|netfilter| | | | | | netfilter | | |
| +----------+ +----------------------------+ | | | +-----------------------------------------------------------+ |
| | | | | | out | | | | | | filter excute order | |
| | | | +-----------------------------+ | | | | | | +-------------------> | |
| | | | | | | | | | | | | | TCP | |
| | +-----+--+-+ +-----v----+ +-----v----+ |pri +----+----+sec| | | | +------------+ +---+----+---v+rewriter++ +------------+ | |
| | | | | | | | |in | |in | | | | | | | | | | | | |
| | | filter | | filter | | filter +------> colo <------+ +--------> filter +--> adjust | adjust +--> filter | | |
| | | mirror | |redirector| |redirector| | | compare | | | | | | redirector | | ack | seq | | redirector | | |
| | | | | | | | | | | | | | | | | | | | | | | |
| | +----^-----+ +----+-----+ +----------+ | +---------+ | | | | +------------+ +--------+--------------+ +---+--------+ | |
| | | tx | rx rx | | | | | tx all | rx | |
| | | | | | | | +-----------------------------------------------------------+ |
| | | +--------------+ | | | | | |
| | | filter excute order | | | | | | |
| | | +----------------> | | | +--------------------------------------------------------+ |
| +-----------------------------------------+ | | |
| | | | | |
+--------------------------------------------------------------+ +----------------------------------------------------------------+
|guest receive | guest send
| |
+--------+----------------------------v------------------------+
| | NOTE: filter direction is rx/tx/all
| tap | rx:receive packets sent to the netdev
| | tx:receive packets sent by the netdev
+--------------------------------------------------------------+
In COLO-compare, we do packet comparing job.
Packets coming from the primary char indev will be sent to outdev.
Packets coming from the secondary char dev will be dropped after comparing.
colo-comapre need two input chardev and one output chardev:
primary_in=chardev1-id (source: primary send packet)
secondary_in=chardev2-id (source: secondary send packet)
outdev=chardev3-id
usage:
primary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
secondary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=red0,host=3.3.3.3,port=9003
-chardev socket,id=red1,host=3.3.3.3,port=9004
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:26 +02:00
|
|
|
|
|
|
|
secondary:
|
|
|
|
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
|
|
|
|
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
|
|
|
|
-chardev socket,id=red0,host=3.3.3.3,port=9003
|
|
|
|
-chardev socket,id=red1,host=3.3.3.3,port=9004
|
|
|
|
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
|
|
|
|
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
|
|
|
|
|
2019-06-09 18:44:29 +02:00
|
|
|
|
|
|
|
Xen COLO
|
|
|
|
|
|
|
|
primary:
|
|
|
|
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
|
|
|
|
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
|
|
|
|
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
|
|
|
|
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
|
|
|
|
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
|
|
|
|
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
|
|
|
|
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
|
|
|
|
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
|
|
|
|
-chardev socket,id=notify_way,host=3.3.3.3,port=9009,server,nowait
|
|
|
|
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
|
|
|
|
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
|
|
|
|
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
|
|
|
|
-object iothread,id=iothread1
|
|
|
|
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0,notify_dev=nofity_way,iothread=iothread1
|
|
|
|
|
|
|
|
secondary:
|
|
|
|
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
|
|
|
|
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
|
|
|
|
-chardev socket,id=red0,host=3.3.3.3,port=9003
|
|
|
|
-chardev socket,id=red1,host=3.3.3.3,port=9004
|
|
|
|
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
|
|
|
|
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
|
|
|
|
|
colo-compare: introduce colo compare initialization
This a COLO net ascii figure:
Primary qemu Secondary qemu
+--------------------------------------------------------------+ +----------------------------------------------------------------+
| +----------------------------------------------------------+ | | +-----------------------------------------------------------+ |
| | | | | | | |
| | guest | | | | guest | |
| | | | | | | |
| +-------^--------------------------+-----------------------+ | | +---------------------+--------+----------------------------+ |
| | | | | ^ | |
| | | | | | | |
| | +------------------------------------------------------+ | | | |
|netfilter| | | | | | netfilter | | |
| +----------+ +----------------------------+ | | | +-----------------------------------------------------------+ |
| | | | | | out | | | | | | filter excute order | |
| | | | +-----------------------------+ | | | | | | +-------------------> | |
| | | | | | | | | | | | | | TCP | |
| | +-----+--+-+ +-----v----+ +-----v----+ |pri +----+----+sec| | | | +------------+ +---+----+---v+rewriter++ +------------+ | |
| | | | | | | | |in | |in | | | | | | | | | | | | |
| | | filter | | filter | | filter +------> colo <------+ +--------> filter +--> adjust | adjust +--> filter | | |
| | | mirror | |redirector| |redirector| | | compare | | | | | | redirector | | ack | seq | | redirector | | |
| | | | | | | | | | | | | | | | | | | | | | | |
| | +----^-----+ +----+-----+ +----------+ | +---------+ | | | | +------------+ +--------+--------------+ +---+--------+ | |
| | | tx | rx rx | | | | | tx all | rx | |
| | | | | | | | +-----------------------------------------------------------+ |
| | | +--------------+ | | | | | |
| | | filter excute order | | | | | | |
| | | +----------------> | | | +--------------------------------------------------------+ |
| +-----------------------------------------+ | | |
| | | | | |
+--------------------------------------------------------------+ +----------------------------------------------------------------+
|guest receive | guest send
| |
+--------+----------------------------v------------------------+
| | NOTE: filter direction is rx/tx/all
| tap | rx:receive packets sent to the netdev
| | tx:receive packets sent by the netdev
+--------------------------------------------------------------+
In COLO-compare, we do packet comparing job.
Packets coming from the primary char indev will be sent to outdev.
Packets coming from the secondary char dev will be dropped after comparing.
colo-comapre need two input chardev and one output chardev:
primary_in=chardev1-id (source: primary send packet)
secondary_in=chardev2-id (source: secondary send packet)
outdev=chardev3-id
usage:
primary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
-device e1000,id=e0,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=mirror0,host=3.3.3.3,port=9003,server,nowait
-chardev socket,id=compare1,host=3.3.3.3,port=9004,server,nowait
-chardev socket,id=compare0,host=3.3.3.3,port=9001,server,nowait
-chardev socket,id=compare0-0,host=3.3.3.3,port=9001
-chardev socket,id=compare_out,host=3.3.3.3,port=9005,server,nowait
-chardev socket,id=compare_out0,host=3.3.3.3,port=9005
-object filter-mirror,id=m0,netdev=hn0,queue=tx,outdev=mirror0
-object filter-redirector,netdev=hn0,id=redire0,queue=rx,indev=compare_out
-object filter-redirector,netdev=hn0,id=redire1,queue=rx,outdev=compare0
-object colo-compare,id=comp0,primary_in=compare0-0,secondary_in=compare1,outdev=compare_out0
secondary:
-netdev tap,id=hn0,vhost=off,script=/etc/qemu-ifup,down script=/etc/qemu-ifdown
-device e1000,netdev=hn0,mac=52:a4:00:12:78:66
-chardev socket,id=red0,host=3.3.3.3,port=9003
-chardev socket,id=red1,host=3.3.3.3,port=9004
-object filter-redirector,id=f1,netdev=hn0,queue=tx,indev=red0
-object filter-redirector,id=f2,netdev=hn0,queue=rx,outdev=red1
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
2016-09-27 04:22:26 +02:00
|
|
|
@end example
|
|
|
|
|
|
|
|
If you want to know the detail of above command line, you can read
|
|
|
|
the colo-compare git log.
|
|
|
|
|
2016-10-28 10:33:23 +02:00
|
|
|
@item -object cryptodev-backend-builtin,id=@var{id}[,queues=@var{queues}]
|
|
|
|
|
|
|
|
Creates a cryptodev backend which executes crypto opreation from
|
|
|
|
the QEMU cipher APIS. The @var{id} parameter is
|
|
|
|
a unique ID that will be used to reference this cryptodev backend from
|
|
|
|
the @option{virtio-crypto} device. The @var{queues} parameter is optional,
|
|
|
|
which specify the queue number of cryptodev backend, the default of
|
|
|
|
@var{queues} is 1.
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
|
|
|
# qemu-system-x86_64 \
|
|
|
|
[...] \
|
|
|
|
-object cryptodev-backend-builtin,id=cryptodev0 \
|
|
|
|
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 \
|
|
|
|
[...]
|
|
|
|
@end example
|
|
|
|
|
2018-03-01 14:46:28 +01:00
|
|
|
@item -object cryptodev-vhost-user,id=@var{id},chardev=@var{chardevid}[,queues=@var{queues}]
|
|
|
|
|
|
|
|
Creates a vhost-user cryptodev backend, backed by a chardev @var{chardevid}.
|
|
|
|
The @var{id} parameter is a unique ID that will be used to reference this
|
|
|
|
cryptodev backend from the @option{virtio-crypto} device.
|
|
|
|
The chardev should be a unix domain socket backed one. The vhost-user uses
|
|
|
|
a specifically defined protocol to pass vhost ioctl replacement messages
|
|
|
|
to an application on the other end of the socket.
|
|
|
|
The @var{queues} parameter is optional, which specify the queue number
|
|
|
|
of cryptodev backend for multiqueue vhost-user, the default of @var{queues} is 1.
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
|
|
|
# qemu-system-x86_64 \
|
|
|
|
[...] \
|
|
|
|
-chardev socket,id=chardev0,path=/path/to/socket \
|
|
|
|
-object cryptodev-vhost-user,id=cryptodev0,chardev=chardev0 \
|
|
|
|
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0 \
|
|
|
|
[...]
|
|
|
|
@end example
|
|
|
|
|
crypto: add QCryptoSecret object class for password/key handling
Introduce a new QCryptoSecret object class which will be used
for providing passwords and keys to other objects which need
sensitive credentials.
The new object can provide secret values directly as properties,
or indirectly via a file. The latter includes support for file
descriptor passing syntax on UNIX platforms. Ordinarily passing
secret values directly as properties is insecure, since they
are visible in process listings, or in log files showing the
CLI args / QMP commands. It is possible to use AES-256-CBC to
encrypt the secret values though, in which case all that is
visible is the ciphertext. For ad hoc developer testing though,
it is fine to provide the secrets directly without encryption
so this is not explicitly forbidden.
The anticipated scenario is that libvirtd will create a random
master key per QEMU instance (eg /var/run/libvirt/qemu/$VMNAME.key)
and will use that key to encrypt all passwords it provides to
QEMU via '-object secret,....'. This avoids the need for libvirt
(or other mgmt apps) to worry about file descriptor passing.
It also makes life easier for people who are scripting the
management of QEMU, for whom FD passing is significantly more
complex.
Providing data inline (insecure, only for ad hoc dev testing)
$QEMU -object secret,id=sec0,data=letmein
Providing data indirectly in raw format
printf "letmein" > mypasswd.txt
$QEMU -object secret,id=sec0,file=mypasswd.txt
Providing data indirectly in base64 format
$QEMU -object secret,id=sec0,file=mykey.b64,format=base64
Providing data with encryption
$QEMU -object secret,id=master0,file=mykey.b64,format=base64 \
-object secret,id=sec0,data=[base64 ciphertext],\
keyid=master0,iv=[base64 IV],format=base64
Note that 'format' here refers to the format of the ciphertext
data. The decrypted data must always be in raw byte format.
More examples are shown in the updated docs.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-10-14 10:58:38 +02:00
|
|
|
@item -object secret,id=@var{id},data=@var{string},format=@var{raw|base64}[,keyid=@var{secretid},iv=@var{string}]
|
|
|
|
@item -object secret,id=@var{id},file=@var{filename},format=@var{raw|base64}[,keyid=@var{secretid},iv=@var{string}]
|
|
|
|
|
|
|
|
Defines a secret to store a password, encryption key, or some other sensitive
|
|
|
|
data. The sensitive data can either be passed directly via the @var{data}
|
|
|
|
parameter, or indirectly via the @var{file} parameter. Using the @var{data}
|
|
|
|
parameter is insecure unless the sensitive data is encrypted.
|
|
|
|
|
|
|
|
The sensitive data can be provided in raw format (the default), or base64.
|
|
|
|
When encoded as JSON, the raw format only supports valid UTF-8 characters,
|
|
|
|
so base64 is recommended for sending binary data. QEMU will convert from
|
|
|
|
which ever format is provided to the format it needs internally. eg, an
|
|
|
|
RBD password can be provided in raw format, even though it will be base64
|
|
|
|
encoded when passed onto the RBD sever.
|
|
|
|
|
|
|
|
For added protection, it is possible to encrypt the data associated with
|
|
|
|
a secret using the AES-256-CBC cipher. Use of encryption is indicated
|
|
|
|
by providing the @var{keyid} and @var{iv} parameters. The @var{keyid}
|
|
|
|
parameter provides the ID of a previously defined secret that contains
|
|
|
|
the AES-256 decryption key. This key should be 32-bytes long and be
|
|
|
|
base64 encoded. The @var{iv} parameter provides the random initialization
|
|
|
|
vector used for encryption of this particular secret and should be a
|
2016-04-04 11:33:55 +02:00
|
|
|
base64 encrypted string of the 16-byte IV.
|
crypto: add QCryptoSecret object class for password/key handling
Introduce a new QCryptoSecret object class which will be used
for providing passwords and keys to other objects which need
sensitive credentials.
The new object can provide secret values directly as properties,
or indirectly via a file. The latter includes support for file
descriptor passing syntax on UNIX platforms. Ordinarily passing
secret values directly as properties is insecure, since they
are visible in process listings, or in log files showing the
CLI args / QMP commands. It is possible to use AES-256-CBC to
encrypt the secret values though, in which case all that is
visible is the ciphertext. For ad hoc developer testing though,
it is fine to provide the secrets directly without encryption
so this is not explicitly forbidden.
The anticipated scenario is that libvirtd will create a random
master key per QEMU instance (eg /var/run/libvirt/qemu/$VMNAME.key)
and will use that key to encrypt all passwords it provides to
QEMU via '-object secret,....'. This avoids the need for libvirt
(or other mgmt apps) to worry about file descriptor passing.
It also makes life easier for people who are scripting the
management of QEMU, for whom FD passing is significantly more
complex.
Providing data inline (insecure, only for ad hoc dev testing)
$QEMU -object secret,id=sec0,data=letmein
Providing data indirectly in raw format
printf "letmein" > mypasswd.txt
$QEMU -object secret,id=sec0,file=mypasswd.txt
Providing data indirectly in base64 format
$QEMU -object secret,id=sec0,file=mykey.b64,format=base64
Providing data with encryption
$QEMU -object secret,id=master0,file=mykey.b64,format=base64 \
-object secret,id=sec0,data=[base64 ciphertext],\
keyid=master0,iv=[base64 IV],format=base64
Note that 'format' here refers to the format of the ciphertext
data. The decrypted data must always be in raw byte format.
More examples are shown in the updated docs.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-10-14 10:58:38 +02:00
|
|
|
|
|
|
|
The simplest (insecure) usage is to provide the secret inline
|
|
|
|
|
|
|
|
@example
|
|
|
|
|
|
|
|
# $QEMU -object secret,id=sec0,data=letmein,format=raw
|
|
|
|
|
|
|
|
@end example
|
|
|
|
|
|
|
|
The simplest secure usage is to provide the secret via a file
|
|
|
|
|
tests: Avoid non-portable 'echo -ARG'
POSIX says that backslashes in the arguments to 'echo', as well as
any use of 'echo -n' and 'echo -e', are non-portable; it recommends
people should favor 'printf' instead. This is definitely true where
we do not control which shell is running (such as in makefile snippets
or in documentation examples). But even for scripts where we
require bash (and therefore, where echo does what we want by default),
it is still possible to use 'shopt -s xpg_echo' to change bash's
behavior of echo. And setting a good example never hurts when we are
not sure if a snippet will be copied from a bash-only script to a
general shell script (although I don't change the use of non-portable
\e for ESC when we know the running shell is bash).
Replace 'echo -n "..."' with 'printf %s "..."', and 'echo -e "..."'
with 'printf %b "...\n"', with the optimization that the %s/%b
argument can be omitted if the string being printed is a strict
literal with no '%', '$', or '`' (we could technically also make
this optimization when there are $ or `` substitutions but where
we can prove their results will not be problematic, but proving
that such substitutions are safe makes the patch less trivial
compared to just being consistent).
In the qemu-iotests check script, fix unusual shell quoting
that would result in word-splitting if 'date' outputs a space.
In test 051, take an opportunity to shorten the line.
In test 068, get rid of a pointless second invocation of bash.
CC: qemu-trivial@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-id: 20170703180950.9895-1-eblake@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
2017-07-03 20:09:50 +02:00
|
|
|
# printf "letmein" > mypasswd.txt
|
crypto: add QCryptoSecret object class for password/key handling
Introduce a new QCryptoSecret object class which will be used
for providing passwords and keys to other objects which need
sensitive credentials.
The new object can provide secret values directly as properties,
or indirectly via a file. The latter includes support for file
descriptor passing syntax on UNIX platforms. Ordinarily passing
secret values directly as properties is insecure, since they
are visible in process listings, or in log files showing the
CLI args / QMP commands. It is possible to use AES-256-CBC to
encrypt the secret values though, in which case all that is
visible is the ciphertext. For ad hoc developer testing though,
it is fine to provide the secrets directly without encryption
so this is not explicitly forbidden.
The anticipated scenario is that libvirtd will create a random
master key per QEMU instance (eg /var/run/libvirt/qemu/$VMNAME.key)
and will use that key to encrypt all passwords it provides to
QEMU via '-object secret,....'. This avoids the need for libvirt
(or other mgmt apps) to worry about file descriptor passing.
It also makes life easier for people who are scripting the
management of QEMU, for whom FD passing is significantly more
complex.
Providing data inline (insecure, only for ad hoc dev testing)
$QEMU -object secret,id=sec0,data=letmein
Providing data indirectly in raw format
printf "letmein" > mypasswd.txt
$QEMU -object secret,id=sec0,file=mypasswd.txt
Providing data indirectly in base64 format
$QEMU -object secret,id=sec0,file=mykey.b64,format=base64
Providing data with encryption
$QEMU -object secret,id=master0,file=mykey.b64,format=base64 \
-object secret,id=sec0,data=[base64 ciphertext],\
keyid=master0,iv=[base64 IV],format=base64
Note that 'format' here refers to the format of the ciphertext
data. The decrypted data must always be in raw byte format.
More examples are shown in the updated docs.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-10-14 10:58:38 +02:00
|
|
|
# $QEMU -object secret,id=sec0,file=mypasswd.txt,format=raw
|
|
|
|
|
|
|
|
For greater security, AES-256-CBC should be used. To illustrate usage,
|
|
|
|
consider the openssl command line tool which can encrypt the data. Note
|
|
|
|
that when encrypting, the plaintext must be padded to the cipher block
|
|
|
|
size (32 bytes) using the standard PKCS#5/6 compatible padding algorithm.
|
|
|
|
|
|
|
|
First a master key needs to be created in base64 encoding:
|
|
|
|
|
|
|
|
@example
|
|
|
|
# openssl rand -base64 32 > key.b64
|
|
|
|
# KEY=$(base64 -d key.b64 | hexdump -v -e '/1 "%02X"')
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Each secret to be encrypted needs to have a random initialization vector
|
|
|
|
generated. These do not need to be kept secret
|
|
|
|
|
|
|
|
@example
|
|
|
|
# openssl rand -base64 16 > iv.b64
|
|
|
|
# IV=$(base64 -d iv.b64 | hexdump -v -e '/1 "%02X"')
|
|
|
|
@end example
|
|
|
|
|
|
|
|
The secret to be defined can now be encrypted, in this case we're
|
|
|
|
telling openssl to base64 encode the result, but it could be left
|
|
|
|
as raw bytes if desired.
|
|
|
|
|
|
|
|
@example
|
tests: Avoid non-portable 'echo -ARG'
POSIX says that backslashes in the arguments to 'echo', as well as
any use of 'echo -n' and 'echo -e', are non-portable; it recommends
people should favor 'printf' instead. This is definitely true where
we do not control which shell is running (such as in makefile snippets
or in documentation examples). But even for scripts where we
require bash (and therefore, where echo does what we want by default),
it is still possible to use 'shopt -s xpg_echo' to change bash's
behavior of echo. And setting a good example never hurts when we are
not sure if a snippet will be copied from a bash-only script to a
general shell script (although I don't change the use of non-portable
\e for ESC when we know the running shell is bash).
Replace 'echo -n "..."' with 'printf %s "..."', and 'echo -e "..."'
with 'printf %b "...\n"', with the optimization that the %s/%b
argument can be omitted if the string being printed is a strict
literal with no '%', '$', or '`' (we could technically also make
this optimization when there are $ or `` substitutions but where
we can prove their results will not be problematic, but proving
that such substitutions are safe makes the patch less trivial
compared to just being consistent).
In the qemu-iotests check script, fix unusual shell quoting
that would result in word-splitting if 'date' outputs a space.
In test 051, take an opportunity to shorten the line.
In test 068, get rid of a pointless second invocation of bash.
CC: qemu-trivial@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-id: 20170703180950.9895-1-eblake@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
2017-07-03 20:09:50 +02:00
|
|
|
# SECRET=$(printf "letmein" |
|
crypto: add QCryptoSecret object class for password/key handling
Introduce a new QCryptoSecret object class which will be used
for providing passwords and keys to other objects which need
sensitive credentials.
The new object can provide secret values directly as properties,
or indirectly via a file. The latter includes support for file
descriptor passing syntax on UNIX platforms. Ordinarily passing
secret values directly as properties is insecure, since they
are visible in process listings, or in log files showing the
CLI args / QMP commands. It is possible to use AES-256-CBC to
encrypt the secret values though, in which case all that is
visible is the ciphertext. For ad hoc developer testing though,
it is fine to provide the secrets directly without encryption
so this is not explicitly forbidden.
The anticipated scenario is that libvirtd will create a random
master key per QEMU instance (eg /var/run/libvirt/qemu/$VMNAME.key)
and will use that key to encrypt all passwords it provides to
QEMU via '-object secret,....'. This avoids the need for libvirt
(or other mgmt apps) to worry about file descriptor passing.
It also makes life easier for people who are scripting the
management of QEMU, for whom FD passing is significantly more
complex.
Providing data inline (insecure, only for ad hoc dev testing)
$QEMU -object secret,id=sec0,data=letmein
Providing data indirectly in raw format
printf "letmein" > mypasswd.txt
$QEMU -object secret,id=sec0,file=mypasswd.txt
Providing data indirectly in base64 format
$QEMU -object secret,id=sec0,file=mykey.b64,format=base64
Providing data with encryption
$QEMU -object secret,id=master0,file=mykey.b64,format=base64 \
-object secret,id=sec0,data=[base64 ciphertext],\
keyid=master0,iv=[base64 IV],format=base64
Note that 'format' here refers to the format of the ciphertext
data. The decrypted data must always be in raw byte format.
More examples are shown in the updated docs.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-10-14 10:58:38 +02:00
|
|
|
openssl enc -aes-256-cbc -a -K $KEY -iv $IV)
|
|
|
|
@end example
|
|
|
|
|
|
|
|
When launching QEMU, create a master secret pointing to @code{key.b64}
|
|
|
|
and specify that to be used to decrypt the user password. Pass the
|
|
|
|
contents of @code{iv.b64} to the second secret
|
|
|
|
|
|
|
|
@example
|
|
|
|
# $QEMU \
|
|
|
|
-object secret,id=secmaster0,format=base64,file=key.b64 \
|
|
|
|
-object secret,id=sec0,keyid=secmaster0,format=base64,\
|
|
|
|
data=$SECRET,iv=$(<iv.b64)
|
|
|
|
@end example
|
|
|
|
|
2018-03-08 13:48:41 +01:00
|
|
|
@item -object sev-guest,id=@var{id},cbitpos=@var{cbitpos},reduced-phys-bits=@var{val},[sev-device=@var{string},policy=@var{policy},handle=@var{handle},dh-cert-file=@var{file},session-file=@var{file}]
|
|
|
|
|
|
|
|
Create a Secure Encrypted Virtualization (SEV) guest object, which can be used
|
|
|
|
to provide the guest memory encryption support on AMD processors.
|
|
|
|
|
|
|
|
When memory encryption is enabled, one of the physical address bit (aka the
|
|
|
|
C-bit) is utilized to mark if a memory page is protected. The @option{cbitpos}
|
|
|
|
is used to provide the C-bit position. The C-bit position is Host family dependent
|
|
|
|
hence user must provide this value. On EPYC, the value should be 47.
|
|
|
|
|
|
|
|
When memory encryption is enabled, we loose certain bits in physical address space.
|
|
|
|
The @option{reduced-phys-bits} is used to provide the number of bits we loose in
|
|
|
|
physical address space. Similar to C-bit, the value is Host family dependent.
|
|
|
|
On EPYC, the value should be 5.
|
|
|
|
|
|
|
|
The @option{sev-device} provides the device file to use for communicating with
|
|
|
|
the SEV firmware running inside AMD Secure Processor. The default device is
|
|
|
|
'/dev/sev'. If hardware supports memory encryption then /dev/sev devices are
|
|
|
|
created by CCP driver.
|
|
|
|
|
|
|
|
The @option{policy} provides the guest policy to be enforced by the SEV firmware
|
|
|
|
and restrict what configuration and operational commands can be performed on this
|
|
|
|
guest by the hypervisor. The policy should be provided by the guest owner and is
|
|
|
|
bound to the guest and cannot be changed throughout the lifetime of the guest.
|
|
|
|
The default is 0.
|
|
|
|
|
|
|
|
If guest @option{policy} allows sharing the key with another SEV guest then
|
|
|
|
@option{handle} can be use to provide handle of the guest from which to share
|
|
|
|
the key.
|
|
|
|
|
|
|
|
The @option{dh-cert-file} and @option{session-file} provides the guest owner's
|
|
|
|
Public Diffie-Hillman key defined in SEV spec. The PDH and session parameters
|
|
|
|
are used for establishing a cryptographic session with the guest owner to
|
|
|
|
negotiate keys used for attestation. The file must be encoded in base64.
|
|
|
|
|
|
|
|
e.g to launch a SEV guest
|
|
|
|
@example
|
|
|
|
# $QEMU \
|
|
|
|
......
|
|
|
|
-object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=5 \
|
|
|
|
-machine ...,memory-encryption=sev0
|
|
|
|
.....
|
|
|
|
|
|
|
|
@end example
|
2018-05-02 16:40:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
@item -object authz-simple,id=@var{id},identity=@var{string}
|
|
|
|
|
|
|
|
Create an authorization object that will control access to network services.
|
|
|
|
|
|
|
|
The @option{identity} parameter is identifies the user and its format
|
|
|
|
depends on the network service that authorization object is associated
|
|
|
|
with. For authorizing based on TLS x509 certificates, the identity must
|
|
|
|
be the x509 distinguished name. Note that care must be taken to escape
|
|
|
|
any commas in the distinguished name.
|
|
|
|
|
|
|
|
An example authorization object to validate a x509 distinguished name
|
|
|
|
would look like:
|
|
|
|
@example
|
|
|
|
# $QEMU \
|
|
|
|
...
|
|
|
|
-object 'authz-simple,id=auth0,identity=CN=laptop.example.com,,O=Example Org,,L=London,,ST=London,,C=GB' \
|
|
|
|
...
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Note the use of quotes due to the x509 distinguished name containing
|
|
|
|
whitespace, and escaping of ','.
|
|
|
|
|
authz: add QAuthZListFile object type for a file access control list
Add a QAuthZListFile object type that implements the QAuthZ interface. This
built-in implementation is a proxy around the QAuthZList object type,
initializing it from an external file, and optionally, automatically
reloading it whenever it changes.
To create an instance of this object via the QMP monitor, the syntax
used would be:
{
"execute": "object-add",
"arguments": {
"qom-type": "authz-list-file",
"id": "authz0",
"props": {
"filename": "/etc/qemu/vnc.acl",
"refresh": true
}
}
}
If "refresh" is "yes", inotify is used to monitor the file,
automatically reloading changes. If an error occurs during reloading,
all authorizations will fail until the file is next successfully
loaded.
The /etc/qemu/vnc.acl file would contain a JSON representation of a
QAuthZList object
{
"rules": [
{ "match": "fred", "policy": "allow", "format": "exact" },
{ "match": "bob", "policy": "allow", "format": "exact" },
{ "match": "danb", "policy": "deny", "format": "glob" },
{ "match": "dan*", "policy": "allow", "format": "exact" },
],
"policy": "deny"
}
This sets up an authorization rule that allows 'fred', 'bob' and anyone
whose name starts with 'dan', except for 'danb'. Everyone unmatched is
denied.
The object can be loaded on the comand line using
-object authz-list-file,id=authz0,filename=/etc/qemu/vnc.acl,refresh=yes
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2018-05-11 13:19:59 +02:00
|
|
|
@item -object authz-listfile,id=@var{id},filename=@var{path},refresh=@var{yes|no}
|
|
|
|
|
|
|
|
Create an authorization object that will control access to network services.
|
|
|
|
|
|
|
|
The @option{filename} parameter is the fully qualified path to a file
|
|
|
|
containing the access control list rules in JSON format.
|
|
|
|
|
|
|
|
An example set of rules that match against SASL usernames might look
|
|
|
|
like:
|
|
|
|
|
|
|
|
@example
|
|
|
|
@{
|
|
|
|
"rules": [
|
|
|
|
@{ "match": "fred", "policy": "allow", "format": "exact" @},
|
|
|
|
@{ "match": "bob", "policy": "allow", "format": "exact" @},
|
|
|
|
@{ "match": "danb", "policy": "deny", "format": "glob" @},
|
|
|
|
@{ "match": "dan*", "policy": "allow", "format": "exact" @},
|
|
|
|
],
|
|
|
|
"policy": "deny"
|
|
|
|
@}
|
|
|
|
@end example
|
|
|
|
|
|
|
|
When checking access the object will iterate over all the rules and
|
|
|
|
the first rule to match will have its @option{policy} value returned
|
|
|
|
as the result. If no rules match, then the default @option{policy}
|
|
|
|
value is returned.
|
|
|
|
|
|
|
|
The rules can either be an exact string match, or they can use the
|
|
|
|
simple UNIX glob pattern matching to allow wildcards to be used.
|
|
|
|
|
|
|
|
If @option{refresh} is set to true the file will be monitored
|
|
|
|
and automatically reloaded whenever its content changes.
|
|
|
|
|
|
|
|
As with the @code{authz-simple} object, the format of the identity
|
|
|
|
strings being matched depends on the network service, but is usually
|
|
|
|
a TLS x509 distinguished name, or a SASL username.
|
|
|
|
|
|
|
|
An example authorization object to validate a SASL username
|
|
|
|
would look like:
|
|
|
|
@example
|
|
|
|
# $QEMU \
|
|
|
|
...
|
|
|
|
-object authz-simple,id=auth0,filename=/etc/qemu/vnc-sasl.acl,refresh=yes
|
|
|
|
...
|
|
|
|
@end example
|
|
|
|
|
authz: add QAuthZPAM object type for authorizing using PAM
Add an authorization backend that talks to PAM to check whether the user
identity is allowed. This only uses the PAM account validation facility,
which is essentially just a check to see if the provided username is permitted
access. It doesn't use the authentication or session parts of PAM, since
that's dealt with by the relevant part of QEMU (eg VNC server).
Consider starting QEMU with a VNC server and telling it to use TLS with
x509 client certificates and configuring it to use an PAM to validate
the x509 distinguished name. In this example we're telling it to use PAM
for the QAuthZ impl with a service name of "qemu-vnc"
$ qemu-system-x86_64 \
-object tls-creds-x509,id=tls0,dir=/home/berrange/security/qemutls,\
endpoint=server,verify-peer=yes \
-object authz-pam,id=authz0,service=qemu-vnc \
-vnc :1,tls-creds=tls0,tls-authz=authz0
This requires an /etc/pam/qemu-vnc file to be created with the auth
rules. A very simple file based whitelist can be setup using
$ cat > /etc/pam/qemu-vnc <<EOF
account requisite pam_listfile.so item=user sense=allow file=/etc/qemu/vnc.allow
EOF
The /etc/qemu/vnc.allow file simply contains one username per line. Any
username not in the file is denied. The usernames in this example are
the x509 distinguished name from the client's x509 cert.
$ cat > /etc/qemu/vnc.allow <<EOF
CN=laptop.berrange.com,O=Berrange Home,L=London,ST=London,C=GB
EOF
More interesting would be to configure PAM to use an LDAP backend, so
that the QEMU authorization check data can be centralized instead of
requiring each compute host to have file maintained.
The main limitation with this PAM module is that the rules apply to all
QEMU instances on the host. Setting up different rules per VM, would
require creating a separate PAM service name & config file for every
guest. An alternative approach for the future might be to not pass in
the plain username to PAM, but instead combine the VM name or UUID with
the username. This requires further consideration though.
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-07-27 15:13:56 +02:00
|
|
|
@item -object authz-pam,id=@var{id},service=@var{string}
|
|
|
|
|
|
|
|
Create an authorization object that will control access to network services.
|
|
|
|
|
|
|
|
The @option{service} parameter provides the name of a PAM service to use
|
|
|
|
for authorization. It requires that a file @code{/etc/pam.d/@var{service}}
|
|
|
|
exist to provide the configuration for the @code{account} subsystem.
|
|
|
|
|
|
|
|
An example authorization object to validate a TLS x509 distinguished
|
|
|
|
name would look like:
|
|
|
|
|
|
|
|
@example
|
|
|
|
# $QEMU \
|
|
|
|
...
|
|
|
|
-object authz-pam,id=auth0,service=qemu-vnc
|
|
|
|
...
|
|
|
|
@end example
|
|
|
|
|
|
|
|
There would then be a corresponding config file for PAM at
|
|
|
|
@code{/etc/pam.d/qemu-vnc} that contains:
|
|
|
|
|
|
|
|
@example
|
|
|
|
account requisite pam_listfile.so item=user sense=allow \
|
|
|
|
file=/etc/qemu/vnc.allow
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Finally the @code{/etc/qemu/vnc.allow} file would contain
|
|
|
|
the list of x509 distingished names that are permitted
|
|
|
|
access
|
|
|
|
|
|
|
|
@example
|
|
|
|
CN=laptop.example.com,O=Example Home,L=London,ST=London,C=GB
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
2015-05-13 18:14:03 +02:00
|
|
|
@end table
|
|
|
|
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
|
2010-01-16 18:19:44 +01:00
|
|
|
HXCOMM This is the last statement. Insert new options before this line!
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|