2009-03-28 09:44:27 +03: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 23:23:52 +04: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 09:44:27 +03:00
|
|
|
HXCOMM HXCOMM can be used for comments, discarded from both texi and C
|
|
|
|
|
|
|
|
DEFHEADING(Standard options:)
|
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("help", 0, QEMU_OPTION_h,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-h or -help display this help and exit\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -h
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -h
|
2009-03-28 09:44:27 +03:00
|
|
|
Display help and exit
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-08 02:58:45 +04:00
|
|
|
DEF("version", 0, QEMU_OPTION_version,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-version display version information and exit\n", QEMU_ARCH_ALL)
|
2009-04-08 02:58:45 +04:00
|
|
|
STEXI
|
|
|
|
@item -version
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -version
|
2009-04-08 02:58:45 +04:00
|
|
|
Display version information and exit
|
|
|
|
ETEXI
|
|
|
|
|
2011-07-23 14:39:46 +04:00
|
|
|
DEF("machine", HAS_ARG, QEMU_OPTION_machine, \
|
|
|
|
"-machine [type=]name[,prop[=value][,...]]\n"
|
2012-10-04 19:22:01 +04:00
|
|
|
" selects emulated machine ('-machine help' for list)\n"
|
2011-07-23 14:39:46 +04:00
|
|
|
" property accel=accel1[:accel2[:...]] selects accelerator\n"
|
2011-10-15 15:43:48 +04:00
|
|
|
" supported accelerators are kvm, xen, tcg (default: tcg)\n"
|
2012-01-25 21:14:15 +04:00
|
|
|
" kernel_irqchip=on|off controls accelerated irqchip support\n"
|
2012-08-02 23:44:16 +04:00
|
|
|
" kvm_shadow_mem=size of KVM shadow MMU\n"
|
2012-09-05 23:50:16 +04:00
|
|
|
" dump-guest-core=on|off include guest memory in a core dump (default=on)\n"
|
|
|
|
" mem-merge=on|off controls memory merge support (default: on)\n",
|
2011-07-23 14:39:46 +04:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2011-07-23 14:39:46 +04:00
|
|
|
@item -machine [type=]@var{name}[,prop=@var{value}[,...]]
|
|
|
|
@findex -machine
|
2012-10-04 19:22:01 +04:00
|
|
|
Select the emulated machine by @var{name}. Use @code{-machine help} to list
|
2011-07-23 14:39:46 +04:00
|
|
|
available machines. Supported machine properties are:
|
|
|
|
@table @option
|
|
|
|
@item accel=@var{accels1}[:@var{accels2}[:...]]
|
|
|
|
This is used to enable an accelerator. Depending on the target architecture,
|
|
|
|
kvm, xen, or tcg can be available. By default, tcg is used. If there is more
|
|
|
|
than one accelerator specified, the next one is used if the previous one fails
|
|
|
|
to initialize.
|
2011-10-15 15:43:48 +04:00
|
|
|
@item kernel_irqchip=on|off
|
|
|
|
Enables in-kernel irqchip support for the chosen accelerator when available.
|
2012-01-25 21:14:15 +04:00
|
|
|
@item kvm_shadow_mem=size
|
|
|
|
Defines the size of the KVM shadow MMU.
|
2012-08-02 23:44:16 +04:00
|
|
|
@item dump-guest-core=on|off
|
|
|
|
Include guest memory in a core dump. The default is on.
|
2012-09-05 23:50:16 +04: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).
|
2011-07-23 14:39:46 +04:00
|
|
|
@end table
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2011-07-23 14:39:46 +04:00
|
|
|
HXCOMM Deprecated by -machine
|
|
|
|
DEF("M", HAS_ARG, QEMU_OPTION_M, "", QEMU_ARCH_ALL)
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("cpu", HAS_ARG, QEMU_OPTION_cpu,
|
2012-10-04 19:22:01 +04:00
|
|
|
"-cpu cpu select CPU ('-cpu help' for list)\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -cpu @var{model}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -cpu
|
2012-10-04 19:22:01 +04:00
|
|
|
Select CPU model (@code{-cpu help} for list and additional feature selection)
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("smp", HAS_ARG, QEMU_OPTION_smp,
|
vl: convert -smp to qemu_opts_parse()
This also introduces a new suboption, "cpus=",
which is the default. So after this patch,
-smp n,sockets=y
is the same as
-smp cpus=n,sockets=y
(with "cpu" being some generic thing, referring to
either cores, or threads, or sockets, as before).
We still don't validate relations between different
numbers, for example it is still possible to say
-smp 1,sockets=10
and it will be accepted to mean sockets=1.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Message-id: 1372072012-30305-1-git-send-email-mjt@msgid.tls.msk.ru
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 15:06:52 +04:00
|
|
|
"-smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]\n"
|
2009-07-23 19:03:42 +04:00
|
|
|
" set the number of CPUs to 'n' [default=1]\n"
|
|
|
|
" maxcpus= maximum number of total cpus, including\n"
|
2010-01-06 22:33:57 +03:00
|
|
|
" offline CPUs for hotplug, etc\n"
|
2009-08-28 12:49:57 +04:00
|
|
|
" cores= number of CPU cores on one socket\n"
|
|
|
|
" threads= number of threads on one CPU core\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" sockets= number of discrete sockets in the system\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
vl: convert -smp to qemu_opts_parse()
This also introduces a new suboption, "cpus=",
which is the default. So after this patch,
-smp n,sockets=y
is the same as
-smp cpus=n,sockets=y
(with "cpu" being some generic thing, referring to
either cores, or threads, or sockets, as before).
We still don't validate relations between different
numbers, for example it is still possible to say
-smp 1,sockets=10
and it will be accepted to mean sockets=1.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Message-id: 1372072012-30305-1-git-send-email-mjt@msgid.tls.msk.ru
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-06-24 15:06:52 +04:00
|
|
|
@item -smp [cpus=]@var{n}[,cores=@var{cores}][,threads=@var{threads}][,sockets=@var{sockets}][,maxcpus=@var{maxcpus}]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -smp
|
2009-03-28 09:44:27 +03: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.
|
2009-08-28 12:49:57 +04:00
|
|
|
For the PC target, the number of @var{cores} per socket, the number
|
|
|
|
of @var{threads} per cores 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 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-04-22 02:30:27 +04:00
|
|
|
DEF("numa", HAS_ARG, QEMU_OPTION_numa,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]\n", QEMU_ARCH_ALL)
|
2009-04-22 02:30:27 +04:00
|
|
|
STEXI
|
|
|
|
@item -numa @var{opts}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -numa
|
2009-04-22 02:30:27 +04:00
|
|
|
Simulate a multi node NUMA system. If mem and cpus are omitted, resources
|
|
|
|
are split equally.
|
|
|
|
ETEXI
|
|
|
|
|
2012-10-18 23:19:34 +04: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-06 01:52:05 +03: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 23:23:52 +04:00
|
|
|
" i.e. -set drive.$id.file=/path/to/image\n", QEMU_ARCH_ALL)
|
2010-02-06 01:52:05 +03:00
|
|
|
STEXI
|
2013-02-13 22:49:39 +04:00
|
|
|
@item -set @var{group}.@var{id}.@var{arg}=@var{value}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -set
|
2013-02-13 22:49:39 +04:00
|
|
|
Set parameter @var{arg} for item @var{id} of type @var{group}\n"
|
2010-02-06 01:52:05 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("global", HAS_ARG, QEMU_OPTION_global,
|
2012-03-21 16:46:54 +04:00
|
|
|
"-global driver.prop=value\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" set a global default for a driver property\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-02-06 01:52:05 +03:00
|
|
|
STEXI
|
2012-03-21 16:46:54 +04:00
|
|
|
@item -global @var{driver}.@var{prop}=@var{value}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -global
|
2012-03-21 16:46:54 +04:00
|
|
|
Set default value of @var{driver}'s property @var{prop} to @var{value}, e.g.:
|
|
|
|
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -global ide-drive.physical_block_size=4096 -drive file=file,if=ide,index=0,media=disk
|
2012-03-21 16:46:54 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
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
|
|
|
|
created automatically and set properties on it, use -@option{device}.
|
2010-02-06 01:52:05 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("boot", HAS_ARG, QEMU_OPTION_boot,
|
2009-07-02 02:19:02 +04:00
|
|
|
"-boot [order=drives][,once=drives][,menu=on|off]\n"
|
2013-03-19 10:23:27 +04:00
|
|
|
" [,splash=sp_name][,splash-time=sp_time][,reboot-timeout=rb_time][,strict=on|off]\n"
|
2011-07-27 14:04:55 +04: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 07:11:03 +04: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 23:23:52 +04:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2013-03-19 10:23:27 +04: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-06 01:52:05 +03:00
|
|
|
@findex -boot
|
2009-07-02 02:19:02 +04:00
|
|
|
Specify boot order @var{drives} as a string of drive letters. Valid
|
|
|
|
drive letters depend on the target achitecture. The x86 PC uses: a, b
|
|
|
|
(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
|
|
|
|
@option{once}.
|
|
|
|
|
|
|
|
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 14:04:55 +04: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 07:11:03 +04: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 10:23:27 +04: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 02:19:02 +04:00
|
|
|
@example
|
|
|
|
# try to boot from network first, then from hard disk
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -boot order=nc
|
2009-07-02 02:19:02 +04:00
|
|
|
# boot from CD-ROM first, switch back to default order after reboot
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -boot once=d
|
2011-07-27 14:04:55 +04:00
|
|
|
# boot with a splash picture for 5 seconds.
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -boot menu=on,splash=/root/boot.bmp,splash-time=5000
|
2009-07-02 02:19:02 +04: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 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("m", HAS_ARG, QEMU_OPTION_m,
|
2013-11-27 04:27:35 +04:00
|
|
|
"-m [size=]megs\n"
|
|
|
|
" configure guest RAM\n"
|
|
|
|
" size: initial amount of guest memory (default: "
|
|
|
|
stringify(DEFAULT_RAM_SIZE) "MiB)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2013-11-27 04:27:35 +04:00
|
|
|
@item -m [size=]@var{megs}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -m
|
2009-03-28 09:44:27 +03:00
|
|
|
Set virtual 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.
|
|
|
|
ETEXI
|
|
|
|
|
2010-03-02 02:25:08 +03:00
|
|
|
DEF("mem-path", HAS_ARG, QEMU_OPTION_mempath,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-mem-path FILE provide backing storage for guest RAM\n", QEMU_ARCH_ALL)
|
2010-03-02 02:25:08 +03:00
|
|
|
STEXI
|
|
|
|
@item -mem-path @var{path}
|
2013-02-13 22:49:38 +04:00
|
|
|
@findex -mem-path
|
2010-03-02 02:25:08 +03:00
|
|
|
Allocate guest RAM from a temporarily created file in @var{path}.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("mem-prealloc", 0, QEMU_OPTION_mem_prealloc,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-mem-prealloc preallocate guest memory (use with -mem-path)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-03-02 02:25:08 +03:00
|
|
|
STEXI
|
|
|
|
@item -mem-prealloc
|
2013-02-13 22:49:38 +04:00
|
|
|
@findex -mem-prealloc
|
2010-03-02 02:25:08 +03:00
|
|
|
Preallocate memory when using -mem-path.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("k", HAS_ARG, QEMU_OPTION_k,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-k language use keyboard layout (for example 'fr' for French)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -k @var{language}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -k
|
2009-03-28 09:44:27 +03: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
|
|
|
|
keycodes (e.g. on Macs, with some X11 servers or with a VNC
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
DEF("audio-help", 0, QEMU_OPTION_audio_help,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-audio-help print list of audio drivers and their options\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -audio-help
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -audio-help
|
2009-03-28 09:44:27 +03:00
|
|
|
Will show the audio subsystem help: list of drivers, tunable
|
|
|
|
parameters.
|
|
|
|
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 19:22:01 +04: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 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -soundhw @var{card1}[,@var{card2},...] or -soundhw all
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -soundhw
|
2012-10-04 19:22:01 +04:00
|
|
|
Enable audio and selected sound hardware. Use 'help' to print all
|
2009-03-28 09:44:27 +03:00
|
|
|
available sound hardware.
|
|
|
|
|
|
|
|
@example
|
2013-02-13 22:49:43 +04: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("balloon", HAS_ARG, QEMU_OPTION_balloon,
|
|
|
|
"-balloon none disable balloon device\n"
|
|
|
|
"-balloon virtio[,addr=str]\n"
|
|
|
|
" enable virtio balloon device (default)\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -balloon none
|
|
|
|
@findex -balloon
|
|
|
|
Disable balloon device.
|
|
|
|
@item -balloon virtio[,addr=@var{addr}]
|
|
|
|
Enable virtio balloon device (default), optionally with PCI address
|
|
|
|
@var{addr}.
|
|
|
|
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}.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("name", HAS_ARG, QEMU_OPTION_name,
|
2014-01-30 14:20:31 +04:00
|
|
|
"-name string1[,process=string2][,debug-threads=on|off]\n"
|
2013-02-13 22:49:43 +04:00
|
|
|
" set the name of the guest\n"
|
2014-01-30 14:20:31 +04:00
|
|
|
" string1 sets the window title and string2 the process name (on Linux)\n"
|
|
|
|
" When debug-threads is enabled, individual threads are given a separate name (on Linux)\n"
|
|
|
|
" NOTE: The thread names are for debugging and not a stable API.\n",
|
2013-02-13 22:49:43 +04: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 14:20:31 +04:00
|
|
|
Naming of individual threads can also be enabled on Linux to aid debugging.
|
2013-02-13 22:49:43 +04: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()
|
|
|
|
|
|
|
|
DEFHEADING(Block device options:)
|
|
|
|
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}
|
|
|
|
@item -fdb @var{file}
|
|
|
|
@findex -fda
|
|
|
|
@findex -fdb
|
|
|
|
Use @var{file} as floppy disk 0/1 image (@pxref{disk_images}). You can
|
|
|
|
use the host floppy by using @file{/dev/fd0} as filename (@pxref{host_drives}).
|
|
|
|
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}
|
|
|
|
@item -hdb @var{file}
|
|
|
|
@item -hdc @var{file}
|
|
|
|
@item -hdd @var{file}
|
|
|
|
@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
|
|
|
|
|
|
|
|
DEF("drive", HAS_ARG, QEMU_OPTION_drive,
|
|
|
|
"-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]\n"
|
|
|
|
" [,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]\n"
|
|
|
|
" [,cache=writethrough|writeback|none|directsync|unsafe][,format=f]\n"
|
2014-04-23 15:55:37 +04:00
|
|
|
" [,serial=s][,addr=A][,rerror=ignore|stop|report]\n"
|
|
|
|
" [,werror=ignore|stop|report|enospc][,id=name][,aio=threads|native]\n"
|
2013-02-13 22:49:43 +04:00
|
|
|
" [,readonly=on|off][,copy-on-read=on|off]\n"
|
2014-05-18 02:58:19 +04:00
|
|
|
" [,detect-zeroes=on|off|unmap]\n"
|
2013-09-02 16:14:40 +04: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 16:14:41 +04:00
|
|
|
" [[,iops_size=is]]\n"
|
2013-02-13 22:49:43 +04:00
|
|
|
" use 'file' as a drive image\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -drive @var{option}[,@var{option}[,@var{option}[,...]]]
|
|
|
|
@findex -drive
|
|
|
|
|
|
|
|
Define a new drive. Valid options are:
|
|
|
|
|
|
|
|
@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.
|
|
|
|
Available types are: ide, scsi, sd, mtd, floppy, pflash, virtio.
|
|
|
|
@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 cyls=@var{c},heads=@var{h},secs=@var{s}[,trans=@var{t}]
|
|
|
|
These options have the same definition as they have in @option{-hdachs}.
|
|
|
|
@item snapshot=@var{snapshot}
|
2014-04-07 13:34:58 +04:00
|
|
|
@var{snapshot} is "on" or "off" and controls snapshot mode for the given drive
|
|
|
|
(see @option{-snapshot}).
|
2013-02-13 22:49:43 +04:00
|
|
|
@item cache=@var{cache}
|
|
|
|
@var{cache} is "none", "writeback", "unsafe", "directsync" or "writethrough" and controls how the host cache is used to access block data.
|
|
|
|
@item aio=@var{aio}
|
|
|
|
@var{aio} is "threads", or "native" and selects between pthread based disk I/O and native Linux AIO.
|
2013-02-08 17:06:12 +04:00
|
|
|
@item discard=@var{discard}
|
|
|
|
@var{discard} is one of "ignore" (or "off") or "unmap" (or "on") and controls whether @dfn{discard} (also known as @dfn{trim} or @dfn{unmap}) requests are ignored or passed to the filesystem. Some machine types may not support discard requests.
|
2013-02-13 22:49:43 +04:00
|
|
|
@item format=@var{format}
|
|
|
|
Specify which disk @var{format} will be used rather than detecting
|
|
|
|
the format. Can be used to specifiy format=raw to avoid interpreting
|
|
|
|
an untrusted format header.
|
|
|
|
@item serial=@var{serial}
|
|
|
|
This option specifies the serial number to assign to the device.
|
|
|
|
@item addr=@var{addr}
|
|
|
|
Specify the controller's PCI address (if=virtio only).
|
|
|
|
@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 readonly
|
|
|
|
Open drive @option{file} as read-only. Guest write attempts will fail.
|
|
|
|
@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.
|
2014-05-18 02:58:19 +04:00
|
|
|
@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 UNMAP operation.
|
2013-02-13 22:49:43 +04:00
|
|
|
@end table
|
|
|
|
|
|
|
|
By default, the @option{cache=writeback} mode is used. It will report data
|
|
|
|
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.
|
|
|
|
|
|
|
|
For such guests, you should consider using @option{cache=writethrough}. This
|
|
|
|
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.
|
|
|
|
|
|
|
|
The host page cache can be avoided entirely with @option{cache=none}. This will
|
|
|
|
attempt to do disk IO directly to the guest's memory. QEMU may still perform
|
|
|
|
an internal copy of the data. Note that this is considered a writeback mode and
|
|
|
|
the guest OS must handle the disk write cache correctly in order to avoid data
|
|
|
|
corruption on host crashes.
|
|
|
|
|
|
|
|
The host page cache can be avoided while only sending write notifications to
|
|
|
|
the guest when the data has been flushed to the disk using
|
|
|
|
@option{cache=directsync}.
|
|
|
|
|
|
|
|
In case you don't care about data integrity over host failures, use
|
|
|
|
@option{cache=unsafe}. 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. When using
|
|
|
|
the @option{-snapshot} option, unsafe caching is always used.
|
|
|
|
|
|
|
|
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 09:44:27 +03:00
|
|
|
@end example
|
|
|
|
|
2013-02-13 22:49:43 +04: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 09:44:27 +03:00
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
You can connect a SCSI disk with unit ID 6 on the bus #0:
|
2009-03-28 09:44:27 +03:00
|
|
|
@example
|
2013-02-13 22:49:43 +04:00
|
|
|
qemu-system-i386 -drive file=file,if=scsi,bus=0,unit=6
|
2009-03-28 09:44:27 +03:00
|
|
|
@end example
|
|
|
|
|
2013-02-13 22:49:43 +04: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 10:19:32 +04:00
|
|
|
|
2013-02-13 22:49:43 +04: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 22:49:42 +04:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
DEF("mtdblock", HAS_ARG, QEMU_OPTION_mtdblock,
|
|
|
|
"-mtdblock file use 'file' as on-board Flash memory image\n",
|
2013-02-13 22:49:42 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2013-02-13 22:49:43 +04:00
|
|
|
@item -mtdblock @var{file}
|
|
|
|
@findex -mtdblock
|
|
|
|
Use @var{file} as on-board Flash memory image.
|
2013-02-13 22:49:42 +04:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
DEF("sd", HAS_ARG, QEMU_OPTION_sd,
|
|
|
|
"-sd file use 'file' as SecureDigital card image\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2013-02-13 22:49:43 +04:00
|
|
|
@item -sd @var{file}
|
|
|
|
@findex -sd
|
|
|
|
Use @var{file} as SecureDigital card image.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
DEF("pflash", HAS_ARG, QEMU_OPTION_pflash,
|
|
|
|
"-pflash file use 'file' as a parallel flash image\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2013-02-13 22:49:43 +04:00
|
|
|
@item -pflash @var{file}
|
|
|
|
@findex -pflash
|
|
|
|
Use @var{file} as a parallel flash image.
|
2013-02-13 22:49:40 +04:00
|
|
|
ETEXI
|
2009-03-28 09:44:27 +03:00
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
DEF("snapshot", 0, QEMU_OPTION_snapshot,
|
|
|
|
"-snapshot write to temporary files instead of disk image files\n",
|
2013-02-13 22:49:40 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2013-02-13 22:49:43 +04: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 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
DEF("hdachs", HAS_ARG, QEMU_OPTION_hdachs, \
|
|
|
|
"-hdachs c,h,s[,t]\n" \
|
|
|
|
" force hard disk 0 physical geometry and the optional BIOS\n" \
|
|
|
|
" translation (t=none or lba) (usually QEMU can guess them)\n",
|
2010-03-29 23:23:52 +04:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2013-02-13 22:49:43 +04:00
|
|
|
@item -hdachs @var{c},@var{h},@var{s},[,@var{t}]
|
|
|
|
@findex -hdachs
|
|
|
|
Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <=
|
|
|
|
@var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS
|
|
|
|
translation mode (@var{t}=none, lba or auto). Usually QEMU can guess
|
|
|
|
all those parameters. This option is useful for old MS-DOS disk
|
|
|
|
images.
|
2013-02-13 22:49:40 +04:00
|
|
|
ETEXI
|
2010-04-29 16:14:43 +04:00
|
|
|
|
|
|
|
DEF("fsdev", HAS_ARG, QEMU_OPTION_fsdev,
|
2012-01-19 10:51:11 +04:00
|
|
|
"-fsdev fsdriver,id=id[,path=path,][security_model={mapped-xattr|mapped-file|passthrough|none}]\n"
|
2011-12-14 12:28:47 +04:00
|
|
|
" [,writeout=immediate][,readonly][,socket=socket|sock_fd=sock_fd]\n",
|
2010-04-29 16:14:43 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
|
2011-12-14 12:28:47 +04:00
|
|
|
@item -fsdev @var{fsdriver},id=@var{id},path=@var{path},[security_model=@var{security_model}][,writeout=@var{writeout}][,readonly][,socket=@var{socket}|sock_fd=@var{sock_fd}]
|
2010-04-29 16:14:43 +04:00
|
|
|
@findex -fsdev
|
2011-10-12 17:41:24 +04:00
|
|
|
Define a new file system device. Valid options are:
|
|
|
|
@table @option
|
|
|
|
@item @var{fsdriver}
|
|
|
|
This option specifies the fs driver backend to use.
|
2011-12-14 12:28:46 +04:00
|
|
|
Currently "local", "handle" and "proxy" file system drivers are supported.
|
2011-10-12 17:41:24 +04:00
|
|
|
@item id=@var{id}
|
|
|
|
Specifies identifier for this device
|
|
|
|
@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 10:51:11 +04:00
|
|
|
Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
|
2011-10-12 17:41:24 +04:00
|
|
|
In "passthrough" security model, files are stored using the same
|
2012-05-12 00:25:50 +04:00
|
|
|
credentials as they are created on the guest. This requires QEMU
|
2012-01-19 10:51:11 +04:00
|
|
|
to run as root. In "mapped-xattr" security model, some of the file
|
2011-10-12 17:41:24 +04:00
|
|
|
attributes like uid, gid, mode bits and link target are stored as
|
2012-01-19 10:51:11 +04: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 17:41:24 +04: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 11:29:37 +04:00
|
|
|
set file attributes like ownership. Security model is mandatory
|
2011-12-14 12:28:46 +04:00
|
|
|
only for local fsdriver. Other fsdrivers (like handle, proxy) don't take
|
2011-10-14 11:29:37 +04:00
|
|
|
security model as a parameter.
|
2011-10-12 17:41:24 +04: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 10:40:39 +04:00
|
|
|
@item readonly
|
|
|
|
Enables exporting 9p share as a readonly mount for guests. By default
|
|
|
|
read-write access is given.
|
2011-12-14 12:28:47 +04:00
|
|
|
@item socket=@var{socket}
|
|
|
|
Enables proxy filesystem driver to use passed socket file for communicating
|
|
|
|
with virtfs-proxy-helper
|
2011-12-14 12:28:46 +04:00
|
|
|
@item sock_fd=@var{sock_fd}
|
|
|
|
Enables proxy filesystem driver to use passed socket descriptor for
|
|
|
|
communicating with virtfs-proxy-helper. Usually a helper like libvirt
|
|
|
|
will create socketpair and pass one of the fds as sock_fd
|
2011-10-12 17:41:24 +04:00
|
|
|
@end table
|
2010-06-15 00:34:40 +04:00
|
|
|
|
2011-10-12 17:41:24 +04:00
|
|
|
-fsdev option is used along with -device driver "virtio-9p-pci".
|
|
|
|
@item -device virtio-9p-pci,fsdev=@var{id},mount_tag=@var{mount_tag}
|
|
|
|
Options for virtio-9p-pci driver are:
|
|
|
|
@table @option
|
|
|
|
@item fsdev=@var{id}
|
|
|
|
Specifies the id value specified along with -fsdev option
|
|
|
|
@item mount_tag=@var{mount_tag}
|
|
|
|
Specifies the tag name to be used by the guest to mount this export point
|
2010-04-29 16:14:43 +04:00
|
|
|
@end table
|
2011-10-12 17:41:24 +04:00
|
|
|
|
2010-04-29 16:14:43 +04: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 16:15:03 +04:00
|
|
|
DEF("virtfs", HAS_ARG, QEMU_OPTION_virtfs,
|
2012-01-19 10:51:11 +04:00
|
|
|
"-virtfs local,path=path,mount_tag=tag,security_model=[mapped-xattr|mapped-file|passthrough|none]\n"
|
2011-12-14 12:28:47 +04:00
|
|
|
" [,writeout=immediate][,readonly][,socket=socket|sock_fd=sock_fd]\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 16:15:03 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
|
2011-12-14 12:28:47 +04:00
|
|
|
@item -virtfs @var{fsdriver}[,path=@var{path}],mount_tag=@var{mount_tag}[,security_model=@var{security_model}][,writeout=@var{writeout}][,readonly][,socket=@var{socket}|sock_fd=@var{sock_fd}]
|
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 16:15:03 +04:00
|
|
|
@findex -virtfs
|
|
|
|
|
2011-10-12 17:41:24 +04:00
|
|
|
The general form of a Virtual File system pass-through options are:
|
|
|
|
@table @option
|
|
|
|
@item @var{fsdriver}
|
|
|
|
This option specifies the fs driver backend to use.
|
2011-12-14 12:28:46 +04:00
|
|
|
Currently "local", "handle" and "proxy" file system drivers are supported.
|
2011-10-12 17:41:24 +04:00
|
|
|
@item id=@var{id}
|
|
|
|
Specifies identifier for this device
|
|
|
|
@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 10:51:11 +04:00
|
|
|
Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
|
2011-10-12 17:41:24 +04:00
|
|
|
In "passthrough" security model, files are stored using the same
|
2012-05-12 00:25:50 +04:00
|
|
|
credentials as they are created on the guest. This requires QEMU
|
2012-01-19 10:51:11 +04:00
|
|
|
to run as root. In "mapped-xattr" security model, some of the file
|
2011-10-12 17:41:24 +04:00
|
|
|
attributes like uid, gid, mode bits and link target are stored as
|
2012-01-19 10:51:11 +04: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 17:41:24 +04: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 11:29:37 +04:00
|
|
|
set file attributes like ownership. Security model is mandatory only
|
2011-12-14 12:28:46 +04:00
|
|
|
for local fsdriver. Other fsdrivers (like handle, proxy) don't take security
|
2011-10-14 11:29:37 +04:00
|
|
|
model as a parameter.
|
2011-10-12 17:41:24 +04: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 10:40:39 +04:00
|
|
|
@item readonly
|
|
|
|
Enables exporting 9p share as a readonly mount for guests. By default
|
|
|
|
read-write access is given.
|
2011-12-14 12:28:47 +04:00
|
|
|
@item socket=@var{socket}
|
|
|
|
Enables proxy filesystem driver to use passed socket file for
|
|
|
|
communicating with virtfs-proxy-helper. Usually a helper like libvirt
|
|
|
|
will create socketpair and pass one of the fds as sock_fd
|
2011-12-14 12:28:46 +04:00
|
|
|
@item sock_fd
|
|
|
|
Enables proxy filesystem driver to use passed 'sock_fd' as the socket
|
|
|
|
descriptor for interfacing with virtfs-proxy-helper
|
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 16:15:03 +04:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2011-10-25 10:40:40 +04: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
|
|
|
|
Create synthetic file system image
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2013-02-13 22:49:43 +04:00
|
|
|
DEFHEADING(USB options:)
|
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("usb", 0, QEMU_OPTION_usb,
|
|
|
|
"-usb enable the USB driver (will be the default soon)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
@item -usb
|
|
|
|
@findex -usb
|
|
|
|
Enable the USB driver (will be the default soon)
|
|
|
|
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
|
|
|
|
Add the USB device @var{devname}. @xref{usb_devices}.
|
|
|
|
|
|
|
|
@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 disk:[format=@var{format}]:@var{file}
|
|
|
|
Mass storage device based on file. The optional @var{format} argument
|
|
|
|
will be used rather than detecting the format. Can be used to specifiy
|
|
|
|
@code{format=raw} to avoid interpreting an untrusted format header.
|
|
|
|
|
|
|
|
@item host:@var{bus}.@var{addr}
|
|
|
|
Pass through the host device identified by @var{bus}.@var{addr} (Linux only).
|
|
|
|
|
|
|
|
@item host:@var{vendor_id}:@var{product_id}
|
|
|
|
Pass through the host device identified by @var{vendor_id}:@var{product_id}
|
|
|
|
(Linux only).
|
|
|
|
|
|
|
|
@item serial:[vendorid=@var{vendor_id}][,productid=@var{product_id}]:@var{dev}
|
|
|
|
Serial converter to host character device @var{dev}, see @code{-serial} for the
|
|
|
|
available devices.
|
|
|
|
|
|
|
|
@item braille
|
|
|
|
Braille device. This will use BrlAPI to display the braille output on a real
|
|
|
|
or fake device.
|
|
|
|
|
|
|
|
@item net:@var{options}
|
|
|
|
Network adapter that supports CDC ethernet and RNDIS protocols.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEFHEADING(Display options:)
|
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
2011-03-16 15:33:31 +03:00
|
|
|
DEF("display", HAS_ARG, QEMU_OPTION_display,
|
|
|
|
"-display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]\n"
|
2011-03-16 15:33:33 +03:00
|
|
|
" [,window_close=on|off]|curses|none|\n"
|
2014-03-12 11:33:50 +04:00
|
|
|
" gtk[,grab_on_hover=on|off]|\n"
|
2011-03-16 15:33:33 +03:00
|
|
|
" vnc=<display>[,<optargs>]\n"
|
2011-03-16 15:33:31 +03:00
|
|
|
" select display type\n", QEMU_ARCH_ALL)
|
|
|
|
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.
|
2011-03-16 15:33:32 +03: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 11:33:50 +04: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 15:33:33 +03:00
|
|
|
@item vnc
|
|
|
|
Start a VNC server on display <arg>
|
2011-03-16 15:33:31 +03:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("nographic", 0, QEMU_OPTION_nographic,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-nographic disable graphical output and redirect serial I/Os to console\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -nographic
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -nographic
|
2009-03-28 09:44:27 +03:00
|
|
|
Normally, QEMU uses SDL to display the VGA output. 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
|
2013-07-03 20:29:45 +04:00
|
|
|
the console and muxed with the monitor (unless redirected elsewhere
|
|
|
|
explicitly). Therefore, you can still use QEMU to debug a Linux kernel
|
2013-07-20 15:23:09 +04:00
|
|
|
with a serial console. Use @key{C-a h} for help on switching between
|
|
|
|
the console and monitor.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("curses", 0, QEMU_OPTION_curses,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-curses use a curses/ncurses interface instead of SDL\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -curses
|
2013-02-13 22:49:38 +04:00
|
|
|
@findex -curses
|
2009-03-28 09:44:27 +03:00
|
|
|
Normally, QEMU uses SDL to display the VGA output. With this option,
|
|
|
|
QEMU can display the VGA output when in text mode using a
|
|
|
|
curses/ncurses interface. Nothing is displayed in graphical mode.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-frame", 0, QEMU_OPTION_no_frame,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-no-frame open SDL window without a frame and window decorations\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-frame
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-frame
|
2009-03-28 09:44:27 +03:00
|
|
|
Do not use decorations for SDL windows and start them using the whole
|
|
|
|
available screen space. This makes the using QEMU in a dedicated desktop
|
|
|
|
workspace more convenient.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("alt-grab", 0, QEMU_OPTION_alt_grab,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -alt-grab
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -alt-grab
|
2011-04-29 15:46:12 +04: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 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-09-18 00:48:04 +04:00
|
|
|
DEF("ctrl-grab", 0, QEMU_OPTION_ctrl_grab,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-09-18 00:48:04 +04:00
|
|
|
STEXI
|
|
|
|
@item -ctrl-grab
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -ctrl-grab
|
2011-04-29 15:46:12 +04: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-18 00:48:04 +04:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("no-quit", 0, QEMU_OPTION_no_quit,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-no-quit disable SDL window close capability\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-quit
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-quit
|
2009-03-28 09:44:27 +03:00
|
|
|
Disable SDL window close capability.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("sdl", 0, QEMU_OPTION_sdl,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-sdl enable SDL\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -sdl
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -sdl
|
2009-03-28 09:44:27 +03:00
|
|
|
Enable SDL.
|
|
|
|
ETEXI
|
|
|
|
|
2010-03-11 17:13:27 +03:00
|
|
|
DEF("spice", HAS_ARG, QEMU_OPTION_spice,
|
2012-08-21 14:54:20 +04: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"
|
|
|
|
" [,x509-dh-key-file=<file>][,addr=addr][,ipv4|ipv6]\n"
|
|
|
|
" [,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 17:37:27 +04:00
|
|
|
" [,disable-agent-file-xfer][,agent-mouse=[on|off]]\n"
|
|
|
|
" [,playback-compression=[on|off]][,seamless-migration=[on|off]]\n"
|
2012-08-21 14:54:20 +04:00
|
|
|
" enable spice\n"
|
|
|
|
" at least one of {port, tls-port} is mandatory\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-03-11 17:13:27 +03: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 17:13:32 +03:00
|
|
|
Set the TCP port spice is listening on for plaintext channels.
|
2010-03-11 17:13:27 +03:00
|
|
|
|
2010-08-27 16:29:16 +04:00
|
|
|
@item addr=<addr>
|
|
|
|
Set the IP address spice is listening on. Default is any address.
|
|
|
|
|
|
|
|
@item ipv4
|
|
|
|
@item ipv6
|
|
|
|
Force using the specified IP version.
|
|
|
|
|
2010-03-11 17:13:27 +03:00
|
|
|
@item password=<secret>
|
|
|
|
Set the password you need to authenticate.
|
|
|
|
|
2011-05-17 12:40:33 +04: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 17:13:27 +03:00
|
|
|
@item disable-ticketing
|
|
|
|
Allow client connects without authentication.
|
|
|
|
|
2011-03-27 18:43:54 +04:00
|
|
|
@item disable-copy-paste
|
|
|
|
Disable copy paste between the client and the guest.
|
|
|
|
|
2013-06-08 17:37:27 +04:00
|
|
|
@item disable-agent-file-xfer
|
|
|
|
Disable spice-vdagent based file-xfer between the client and the guest.
|
|
|
|
|
2010-03-11 17:13:32 +03: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>
|
|
|
|
@item x509-key-password=<file>
|
|
|
|
@item x509-cert-file=<file>
|
|
|
|
@item x509-cacert-file=<file>
|
|
|
|
@item x509-dh-key-file=<file>
|
|
|
|
The x509 file names can also be configured individually.
|
|
|
|
|
|
|
|
@item tls-ciphers=<list>
|
|
|
|
Specify which ciphers to use.
|
|
|
|
|
2011-12-20 15:05:18 +04:00
|
|
|
@item tls-channel=[main|display|cursor|inputs|record|playback]
|
|
|
|
@item plaintext-channel=[main|display|cursor|inputs|record|playback]
|
2010-08-27 16:09:56 +04: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 14:26:34 +04: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]
|
|
|
|
@item zlib-glz-wan-compression=[auto|never|always]
|
|
|
|
Configure wan image compression (lossy for slow links).
|
|
|
|
Default is auto.
|
|
|
|
|
2010-08-30 18:36:53 +04:00
|
|
|
@item streaming-video=[off|all|filter]
|
|
|
|
Configure video stream detection. Default is filter.
|
|
|
|
|
|
|
|
@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 12:51:59 +04:00
|
|
|
@item seamless-migration=[on|off]
|
|
|
|
Enable/disable spice seamless migration. Default is off.
|
|
|
|
|
2010-03-11 17:13:27 +03:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("portrait", 0, QEMU_OPTION_portrait,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-portrait rotate graphical output 90 deg left (only PXA LCD)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -portrait
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -portrait
|
2009-03-28 09:44:27 +03:00
|
|
|
Rotate graphical output 90 deg left (only PXA LCD).
|
|
|
|
ETEXI
|
|
|
|
|
2011-06-17 14:04:36 +04: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 22:49:39 +04:00
|
|
|
@item -rotate @var{deg}
|
2011-06-17 14:04:36 +04:00
|
|
|
@findex -rotate
|
|
|
|
Rotate graphical output some deg left (only PXA LCD).
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("vga", HAS_ARG, QEMU_OPTION_vga,
|
2014-03-18 01:46:25 +04:00
|
|
|
"-vga [std|cirrus|vmware|qxl|xenfb|tcx|cg3|none]\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" select video card type\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2012-08-27 18:33:21 +04:00
|
|
|
@item -vga @var{type}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -vga
|
2009-03-28 09:44:27 +03:00
|
|
|
Select type of VGA card to emulate. Valid values for @var{type} are
|
2009-10-09 12:58:35 +04:00
|
|
|
@table @option
|
2009-03-28 09:44:27 +03: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.
|
|
|
|
(This one is the default)
|
|
|
|
@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
|
|
|
|
this option.
|
|
|
|
@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 13:50:11 +04: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-18 01:46:25 +04: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.
|
2009-03-28 09:44:27 +03:00
|
|
|
@item none
|
|
|
|
Disable VGA card.
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("full-screen", 0, QEMU_OPTION_full_screen,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-full-screen start in full screen\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -full-screen
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -full-screen
|
2009-03-28 09:44:27 +03:00
|
|
|
Start in full screen.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("g", 1, QEMU_OPTION_g ,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-g WxH[xDEPTH] Set the initial graphical resolution and depth\n",
|
|
|
|
QEMU_ARCH_PPC | QEMU_ARCH_SPARC)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2010-01-21 00:25:27 +03:00
|
|
|
@item -g @var{width}x@var{height}[x@var{depth}]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -g
|
2010-01-21 00:25:27 +03:00
|
|
|
Set the initial graphical resolution and depth (PPC, SPARC only).
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("vnc", HAS_ARG, QEMU_OPTION_vnc ,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-vnc display start a VNC server on display\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -vnc @var{display}[,@var{option}[,@var{option}[,...]]]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -vnc
|
2009-03-28 09:44:27 +03:00
|
|
|
Normally, QEMU uses SDL to display the VGA output. 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 (option @option{-usbdevice
|
|
|
|
tablet}). When using the VNC display, you 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-10-09 12:58:35 +04:00
|
|
|
@table @option
|
2009-03-28 09:44:27 +03: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 12:58:36 +04:00
|
|
|
@item unix:@var{path}
|
2009-03-28 09:44:27 +03: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 12:58:35 +04:00
|
|
|
@table @option
|
2009-03-28 09:44:27 +03: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 14:04:44 +04:00
|
|
|
@item websocket
|
|
|
|
|
|
|
|
Opens an additional TCP listening port dedicated to VNC Websocket connections.
|
2013-03-18 21:20:07 +04:00
|
|
|
By definition the Websocket port is 5700+@var{display}. If @var{host} is
|
2013-01-21 14:04:44 +04:00
|
|
|
specified connections will only be allowed from this host.
|
|
|
|
As an alternative the Websocket port could be specified by using
|
|
|
|
@code{websocket}=@var{port}.
|
2013-04-23 18:33:01 +04:00
|
|
|
TLS encryption for the Websocket connection is supported if the required
|
|
|
|
certificates are specified with the VNC option @option{x509}.
|
2013-01-21 14:04:44 +04:00
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
@item password
|
|
|
|
|
|
|
|
Require that password based authentication is used for client connections.
|
2012-07-16 17:54:38 +04: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 09:44:27 +03:00
|
|
|
|
|
|
|
@item tls
|
|
|
|
|
|
|
|
Require that client use TLS when communicating with the VNC server. This
|
|
|
|
uses anonymous TLS credentials so is susceptible to a man-in-the-middle
|
|
|
|
attack. It is recommended that this option be combined with either the
|
2009-10-09 12:58:36 +04:00
|
|
|
@option{x509} or @option{x509verify} options.
|
2009-03-28 09:44:27 +03:00
|
|
|
|
|
|
|
@item x509=@var{/path/to/certificate/dir}
|
|
|
|
|
|
|
|
Valid if @option{tls} is specified. Require that x509 credentials are used
|
|
|
|
for negotiating the TLS session. The server will send its x509 certificate
|
|
|
|
to the client. It is recommended that a password be set on the VNC server
|
|
|
|
to provide authentication of the client when this is used. The path following
|
|
|
|
this option specifies where the x509 certificates are to be loaded from.
|
|
|
|
See the @ref{vnc_security} section for details on generating certificates.
|
|
|
|
|
|
|
|
@item x509verify=@var{/path/to/certificate/dir}
|
|
|
|
|
|
|
|
Valid if @option{tls} is specified. Require that x509 credentials are used
|
|
|
|
for negotiating the TLS session. The server will send its x509 certificate
|
|
|
|
to the client, and request that the client send its own x509 certificate.
|
|
|
|
The server will validate the client's certificate against the CA certificate,
|
|
|
|
and reject clients when validation fails. If the certificate authority is
|
|
|
|
trusted, this is a sufficient authentication mechanism. You may still wish
|
|
|
|
to set a password on the VNC server as a second authentication layer. The
|
|
|
|
path following this option specifies where the x509 certificates are to
|
|
|
|
be loaded from. See the @ref{vnc_security} section for details on generating
|
|
|
|
certificates.
|
|
|
|
|
|
|
|
@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.
|
|
|
|
|
|
|
|
@item acl
|
|
|
|
|
|
|
|
Turn on access control lists for checking of the x509 client certificate
|
|
|
|
and SASL party. For x509 certs, the ACL check is made against the
|
|
|
|
certificate's distinguished name. This is something that looks like
|
|
|
|
@code{C=GB,O=ACME,L=Boston,CN=bob}. For SASL party, the ACL check is
|
|
|
|
made against the username, which depending on the SASL plugin, may
|
|
|
|
include a realm component, eg @code{bob} or @code{bob@@EXAMPLE.COM}.
|
|
|
|
When the @option{acl} flag is set, the initial access list will be
|
|
|
|
empty, with a @code{deny} policy. Thus no one will be allowed to
|
|
|
|
use the VNC server until the ACLs have been loaded. This can be
|
|
|
|
achieved using the @code{acl} monitor command.
|
|
|
|
|
2010-07-07 22:57:51 +04: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 11:06:08 +03: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-14 00:45:22 +04:00
|
|
|
This can be really helpful to save bandwidth when playing videos. Disabling
|
2014-04-07 13:34:58 +04:00
|
|
|
adaptive encodings restores the original static behavior of encodings
|
2011-02-04 11:06:08 +03:00
|
|
|
like Tight.
|
|
|
|
|
2011-11-24 21:10:49 +04: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-12 00:25:50 +04:00
|
|
|
spec but is traditional QEMU behavior.
|
2011-11-24 21:10:49 +04:00
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
2011-12-19 10:19:31 +04:00
|
|
|
ARCHHEADING(, QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
|
2011-12-19 10:19:31 +04:00
|
|
|
ARCHHEADING(i386 target only:, QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("win2k-hack", 0, QEMU_OPTION_win2k_hack,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-win2k-hack use it when installing Windows 2000 to avoid a disk full bug\n",
|
|
|
|
QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -win2k-hack
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -win2k-hack
|
2009-03-28 09:44:27 +03: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
|
|
|
|
|
2009-09-15 15:36:04 +04:00
|
|
|
HXCOMM Deprecated by -rtc
|
2010-03-29 23:23:52 +04:00
|
|
|
DEF("rtc-td-hack", 0, QEMU_OPTION_rtc_td_hack, "", QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
|
|
|
|
DEF("no-fd-bootchk", 0, QEMU_OPTION_no_fd_bootchk,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-no-fd-bootchk disable boot signature checking for floppy disks\n",
|
|
|
|
QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-fd-bootchk
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-fd-bootchk
|
2013-06-14 15:15:06 +04:00
|
|
|
Disable boot signature checking for floppy disks in BIOS. May
|
2009-03-28 09:44:27 +03:00
|
|
|
be needed to boot from old floppy disks.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-acpi", 0, QEMU_OPTION_no_acpi,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-no-acpi disable ACPI\n", QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-acpi
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-acpi
|
2009-03-28 09:44:27 +03: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 23:23:52 +04:00
|
|
|
"-no-hpet disable HPET\n", QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-hpet
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-hpet
|
2009-03-28 09:44:27 +03:00
|
|
|
Disable HPET support.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("acpitable", HAS_ARG, QEMU_OPTION_acpitable,
|
2011-05-12 18:44:17 +04: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 23:23:52 +04:00
|
|
|
" ACPI table description\n", QEMU_ARCH_I386)
|
2009-03-28 09:44:27 +03: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-06 01:52:05 +03:00
|
|
|
@findex -acpitable
|
2009-03-28 09:44:27 +03:00
|
|
|
Add ACPI table with specified header fields and context from specified files.
|
2011-05-12 18:44:17 +04: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.
|
2009-03-28 09:44:27 +03: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 22:59:56 +04:00
|
|
|
DEF("smbios", HAS_ARG, QEMU_OPTION_smbios,
|
|
|
|
"-smbios file=binary\n"
|
2010-01-06 22:33:57 +03:00
|
|
|
" load SMBIOS entry from binary file\n"
|
2014-05-19 18:09:54 +04:00
|
|
|
"-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d][,uefi=on|off]\n"
|
2010-01-06 22:33:57 +03: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 22:59:56 +04:00
|
|
|
"-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]\n"
|
|
|
|
" [,uuid=uuid][,sku=str][,family=str]\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" specify SMBIOS type 1 fields\n", QEMU_ARCH_I386)
|
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 22:59:56 +04:00
|
|
|
STEXI
|
|
|
|
@item -smbios file=@var{binary}
|
2010-02-06 01:52:05 +03: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 22:59:56 +04:00
|
|
|
Load SMBIOS entry from binary file.
|
|
|
|
|
2014-05-19 18:09:54 +04: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 22:59:56 +04:00
|
|
|
Specify SMBIOS type 0 fields
|
|
|
|
|
2010-03-18 21:41:49 +03: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 22:59:56 +04:00
|
|
|
Specify SMBIOS type 1 fields
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
2013-02-13 22:49:40 +04:00
|
|
|
DEFHEADING()
|
2009-03-28 09:44:27 +03:00
|
|
|
|
|
|
|
DEFHEADING(Network options:)
|
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
2009-06-24 16:42:28 +04:00
|
|
|
HXCOMM Legacy slirp options (now moved to -net user):
|
|
|
|
#ifdef CONFIG_SLIRP
|
2010-03-29 23:23:52 +04:00
|
|
|
DEF("tftp", HAS_ARG, QEMU_OPTION_tftp, "", QEMU_ARCH_ALL)
|
|
|
|
DEF("bootp", HAS_ARG, QEMU_OPTION_bootp, "", QEMU_ARCH_ALL)
|
|
|
|
DEF("redir", HAS_ARG, QEMU_OPTION_redir, "", QEMU_ARCH_ALL)
|
2009-06-24 16:42:28 +04:00
|
|
|
#ifndef _WIN32
|
2010-03-29 23:23:52 +04:00
|
|
|
DEF("smb", HAS_ARG, QEMU_OPTION_smb, "", QEMU_ARCH_ALL)
|
2009-06-24 16:42:28 +04:00
|
|
|
#endif
|
|
|
|
#endif
|
|
|
|
|
2009-06-09 22:50:02 +04:00
|
|
|
DEF("net", HAS_ARG, QEMU_OPTION_net,
|
2009-06-21 20:51:18 +04:00
|
|
|
"-net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]\n"
|
2009-03-28 09:44:27 +03:00
|
|
|
" create a new Network Interface Card and connect it to VLAN 'n'\n"
|
|
|
|
#ifdef CONFIG_SLIRP
|
2011-07-20 14:20:14 +04:00
|
|
|
"-net user[,vlan=n][,name=str][,net=addr[/mask]][,host=addr][,restrict=on|off]\n"
|
2012-10-27 21:53:39 +04:00
|
|
|
" [,hostname=host][,dhcpstart=addr][,dns=addr][,dnssearch=domain][,tftp=dir]\n"
|
|
|
|
" [,bootfile=f][,hostfwd=rule][,guestfwd=rule]"
|
2009-06-24 16:42:28 +04:00
|
|
|
#ifndef _WIN32
|
2009-06-24 16:42:28 +04:00
|
|
|
"[,smb=dir[,smbserver=addr]]\n"
|
2009-06-24 16:42:28 +04:00
|
|
|
#endif
|
|
|
|
" connect the user mode network stack to VLAN 'n', configure its\n"
|
|
|
|
" DHCP server and enabled optional services\n"
|
2009-03-28 09:44:27 +03:00
|
|
|
#endif
|
|
|
|
#ifdef _WIN32
|
|
|
|
"-net tap[,vlan=n][,name=str],ifname=name\n"
|
|
|
|
" connect the host TAP network interface to VLAN 'n'\n"
|
|
|
|
#else
|
2013-02-22 18:57:52 +04:00
|
|
|
"-net tap[,vlan=n][,name=str][,fd=h][,fds=x:y:...:z][,ifname=name][,script=file][,downscript=dfile][,helper=helper][,sndbuf=nbytes][,vnet_hdr=on|off][,vhost=on|off][,vhostfd=h][,vhostfds=x:y:...:z][,vhostforce=on|off][,queues=n]\n"
|
2012-11-23 12:52:39 +04:00
|
|
|
" connect the host TAP network interface to VLAN 'n'\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 18:42:27 +04: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 22:33:57 +03: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 18:42:27 +04:00
|
|
|
" use network helper 'helper' (default=" DEFAULT_BRIDGE_HELPER ") to\n"
|
|
|
|
" configure it\n"
|
2009-03-28 09:44:27 +03:00
|
|
|
" use 'fd=h' to connect to an already opened TAP interface\n"
|
2013-02-20 14:04:01 +04:00
|
|
|
" use 'fds=x:y:...:z' to connect to already opened multiqueue capable TAP interfaces\n"
|
2010-01-06 22:33:57 +03:00
|
|
|
" use 'sndbuf=nbytes' to limit the size of the send buffer (the\n"
|
2011-02-01 15:25:40 +03:00
|
|
|
" default is disabled 'sndbuf=0' to enable flow control set 'sndbuf=1048576')\n"
|
2010-01-06 22:33:57 +03: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 14:08:24 +03:00
|
|
|
" use vhost=on to enable experimental in kernel accelerator\n"
|
2011-02-01 23:13:42 +03: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 14:08:24 +03:00
|
|
|
" use 'vhostfd=h' to connect to an already opened vhost net device\n"
|
2013-02-20 14:04:01 +04:00
|
|
|
" use 'vhostfds=x:y:...:z to connect to multiple already opened vhost net devices\n"
|
2013-02-22 18:57:52 +04:00
|
|
|
" use 'queues=n' to specify the number of queues to be created for multiqueue TAP\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 18:42:27 +04:00
|
|
|
"-net bridge[,vlan=n][,name=str][,br=bridge][,helper=helper]\n"
|
|
|
|
" connects a host TAP network interface to a host bridge device 'br'\n"
|
|
|
|
" (default=" DEFAULT_BRIDGE_INTERFACE ") using the program 'helper'\n"
|
|
|
|
" (default=" DEFAULT_BRIDGE_HELPER ")\n"
|
2009-03-28 09:44:27 +03:00
|
|
|
#endif
|
|
|
|
"-net socket[,vlan=n][,name=str][,fd=h][,listen=[host]:port][,connect=host:port]\n"
|
|
|
|
" connect the vlan 'n' to another VLAN using a socket connection\n"
|
2010-12-01 22:16:47 +03:00
|
|
|
"-net socket[,vlan=n][,name=str][,fd=h][,mcast=maddr:port[,localaddr=addr]]\n"
|
2009-03-28 09:44:27 +03:00
|
|
|
" connect the vlan 'n' to multicast maddr and port\n"
|
2010-12-01 22:16:47 +03:00
|
|
|
" use 'localaddr=addr' to specify the host address to send packets from\n"
|
2012-01-11 04:20:54 +04:00
|
|
|
"-net socket[,vlan=n][,name=str][,fd=h][,udp=host:port][,localaddr=host:port]\n"
|
|
|
|
" connect the vlan 'n' to another VLAN using an UDP tunnel\n"
|
2009-03-28 09:44:27 +03:00
|
|
|
#ifdef CONFIG_VDE
|
|
|
|
"-net vde[,vlan=n][,name=str][,sock=socketpath][,port=n][,group=groupname][,mode=octalmode]\n"
|
|
|
|
" connect the vlan 'n' to port 'n' of a vde switch running\n"
|
|
|
|
" on host and listening for incoming connections on 'socketpath'.\n"
|
|
|
|
" Use group 'groupname' and mode 'octalmode' to change default\n"
|
|
|
|
" ownership and permissions for communication port.\n"
|
2013-11-06 14:44:06 +04:00
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_NETMAP
|
|
|
|
"-net netmap,ifname=name[,devname=nmname]\n"
|
|
|
|
" 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 09:44:27 +03:00
|
|
|
#endif
|
2009-04-21 23:56:28 +04:00
|
|
|
"-net dump[,vlan=n][,file=f][,len=n]\n"
|
|
|
|
" dump traffic on vlan 'n' to file 'f' (max n bytes per packet)\n"
|
2010-01-06 22:33:57 +03:00
|
|
|
"-net none use it alone to have zero network devices. If no -net option\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" is provided, the default is '-net nic -net user'\n", QEMU_ARCH_ALL)
|
2009-10-08 22:58:26 +04:00
|
|
|
DEF("netdev", HAS_ARG, QEMU_OPTION_netdev,
|
|
|
|
"-netdev ["
|
|
|
|
#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 18:42:27 +04:00
|
|
|
"bridge|"
|
2009-10-08 22:58:26 +04:00
|
|
|
#ifdef CONFIG_VDE
|
|
|
|
"vde|"
|
2013-11-06 14:44:06 +04:00
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_NETMAP
|
|
|
|
"netmap|"
|
2009-10-08 22:58:26 +04:00
|
|
|
#endif
|
2013-02-26 14:07:16 +04:00
|
|
|
"socket|"
|
|
|
|
"hubport],id=str[,option][,option][,...]\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2010-03-18 21:41:49 +03:00
|
|
|
@item -net nic[,vlan=@var{n}][,macaddr=@var{mac}][,model=@var{type}] [,name=@var{name}][,addr=@var{addr}][,vectors=@var{v}]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -net
|
2009-03-28 09:44:27 +03:00
|
|
|
Create a new Network Interface Card and connect it to VLAN @var{n} (@var{n}
|
2009-08-14 20:20:47 +04:00
|
|
|
= 0 is the default). The NIC is an e1000 by default on the PC
|
2009-06-18 17:14:08 +04:00
|
|
|
target. Optionally, the MAC address can be changed to @var{mac}, the
|
|
|
|
device address set to @var{addr} (PCI cards only),
|
2009-06-21 20:51:18 +04:00
|
|
|
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
|
2012-04-07 11:23:36 +04:00
|
|
|
NIC is created. QEMU can emulate several different models of network card.
|
2009-03-28 09:44:27 +03:00
|
|
|
Valid values for @var{type} are
|
2009-06-21 20:51:18 +04:00
|
|
|
@code{virtio}, @code{i82551}, @code{i82557b}, @code{i82559er},
|
2009-03-28 09:44:27 +03:00
|
|
|
@code{ne2k_pci}, @code{ne2k_isa}, @code{pcnet}, @code{rtl8139},
|
|
|
|
@code{e1000}, @code{smc91c111}, @code{lance} and @code{mcf_fec}.
|
2012-10-04 19:22:01 +04:00
|
|
|
Not all devices are supported on all targets. Use @code{-net nic,model=help}
|
2009-03-28 09:44:27 +03:00
|
|
|
for a list of available devices for your target.
|
|
|
|
|
2012-08-14 17:14:27 +04:00
|
|
|
@item -netdev user,id=@var{id}[,@var{option}][,@var{option}][,...]
|
2013-02-13 22:49:38 +04:00
|
|
|
@findex -netdev
|
2009-06-24 16:42:28 +04:00
|
|
|
@item -net user[,@var{option}][,@var{option}][,...]
|
2009-03-28 09:44:27 +03:00
|
|
|
Use the user mode network stack which requires no administrator
|
2009-06-24 16:42:28 +04:00
|
|
|
privilege to run. Valid options are:
|
|
|
|
|
2009-10-09 12:58:35 +04:00
|
|
|
@table @option
|
2009-06-24 16:42:28 +04:00
|
|
|
@item vlan=@var{n}
|
|
|
|
Connect user mode stack to VLAN @var{n} (@var{n} = 0 is the default).
|
|
|
|
|
2012-08-14 17:14:27 +04:00
|
|
|
@item id=@var{id}
|
2009-06-24 16:42:28 +04:00
|
|
|
@item name=@var{name}
|
|
|
|
Assign symbolic name for use in monitor commands.
|
|
|
|
|
2009-06-24 16:42:28 +04: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 11:19:56 +04:00
|
|
|
10.0.2.0/24.
|
2009-06-24 16:42:28 +04: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 16:42:28 +04:00
|
|
|
|
2011-07-20 14:20:14 +04:00
|
|
|
@item restrict=on|off
|
2011-06-09 01:50:43 +04:00
|
|
|
If this option is enabled, the guest will be isolated, i.e. it will not be
|
2009-06-24 16:42:28 +04:00
|
|
|
able to contact the host and no guest IP packets will be routed over the host
|
2011-06-09 01:50:43 +04:00
|
|
|
to the outside. This option does not affect any explicitly set forwarding rules.
|
2009-06-24 16:42:28 +04:00
|
|
|
|
|
|
|
@item hostname=@var{name}
|
2012-10-27 21:53:39 +04:00
|
|
|
Specifies the client hostname reported by the built-in DHCP server.
|
2009-06-24 16:42:28 +04:00
|
|
|
|
2009-06-24 16:42:28 +04:00
|
|
|
@item dhcpstart=@var{addr}
|
|
|
|
Specify the first of the 16 IPs the built-in DHCP server can assign. Default
|
2011-04-24 11:19:56 +04: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 16:42:28 +04: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.
|
|
|
|
|
2012-10-27 21:53:39 +04: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
|
|
|
|
qemu -net user,dnssearch=mgmt.example.org,dnssearch=example.org [...]
|
|
|
|
@end example
|
|
|
|
|
2009-06-24 16:42:28 +04: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 16:42:28 +04:00
|
|
|
@code{bin} of the Unix TFTP client).
|
2009-06-24 16:42:28 +04: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
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -hda linux.img -boot n -net user,tftp=/path/to/tftp/files,bootfile=/pxelinux.0
|
2009-06-24 16:42:28 +04:00
|
|
|
@end example
|
|
|
|
|
2009-06-24 16:42:28 +04:00
|
|
|
@item smb=@var{dir}[,smbserver=@var{addr}]
|
2009-06-24 16:42:28 +04: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 16:42:28 +04: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 16:42:28 +04: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-03 00:53:28 +04:00
|
|
|
Note that a SAMBA server must be installed on the host OS.
|
|
|
|
QEMU was tested successfully with smbd versions from Red Hat 9,
|
|
|
|
Fedora Core 3 and OpenSUSE 11.x.
|
2009-06-24 16:42:28 +04:00
|
|
|
|
2009-06-24 16:42:28 +04:00
|
|
|
@item hostfwd=[tcp|udp]:[@var{hostaddr}]:@var{hostport}-[@var{guestaddr}]:@var{guestport}
|
2009-06-24 16:42:28 +04: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 16:42:28 +04: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 16:42:28 +04:00
|
|
|
used. This option can be given multiple times.
|
2009-06-24 16:42:28 +04:00
|
|
|
|
|
|
|
For example, to redirect host X11 connection from screen 1 to guest
|
|
|
|
screen 0, use the following:
|
|
|
|
|
|
|
|
@example
|
|
|
|
# on the host
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -net user,hostfwd=tcp:127.0.0.1:6001-:6000 [...]
|
2009-06-24 16:42:28 +04: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
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -net user,hostfwd=tcp::5555-:23 [...]
|
2009-06-24 16:42:28 +04: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 09:44:27 +03:00
|
|
|
|
2009-06-24 16:42:28 +04:00
|
|
|
@item guestfwd=[tcp]:@var{server}:@var{port}-@var{dev}
|
2012-06-03 11:45:01 +04:00
|
|
|
@item guestfwd=[tcp]:@var{server}:@var{port}-@var{cmd:command}
|
2009-06-24 16:42:28 +04:00
|
|
|
Forward guest TCP connections to the IP address @var{server} on port @var{port}
|
2012-06-03 11:45:01 +04: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-21 01:26:02 +04:00
|
|
|
You can either use a chardev directly and have that one used throughout QEMU's
|
2012-06-03 11:45:01 +04: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
|
|
|
|
qemu -net user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321 [...]
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Or you can execute a command on every TCP connection established by the guest,
|
2012-07-21 01:26:02 +04:00
|
|
|
so that QEMU behaves similar to an inetd process for that virtual server:
|
2012-06-03 11:45:01 +04: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
|
|
|
|
qemu -net 'user,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321'
|
|
|
|
@end example
|
2009-06-24 16:42:28 +04:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
Note: Legacy stand-alone options -tftp, -bootp, -smb and -redir are still
|
|
|
|
processed and applied to -net user. Mixing them with the new configuration
|
|
|
|
syntax gives undefined results. Their use for new applications is discouraged
|
|
|
|
as they will be removed from future versions.
|
2009-03-28 09:44:27 +03:00
|
|
|
|
2012-08-14 17:14:27 +04:00
|
|
|
@item -netdev tap,id=@var{id}[,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,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 18:42:27 +04:00
|
|
|
@item -net tap[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}]
|
|
|
|
Connect the host TAP network interface @var{name} to VLAN @var{n}.
|
|
|
|
|
|
|
|
Use the network script @var{file} to configure it and the network script
|
2009-03-28 09:44:27 +03: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 18:42:27 +04: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
|
|
|
|
@var{helper} to configure the TAP interface. The default network
|
2013-10-23 00:49:28 +04:00
|
|
|
helper executable is @file{/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 18:42:27 +04:00
|
|
|
|
|
|
|
@option{fd}=@var{h} can be used to specify the handle of an already
|
|
|
|
opened host TAP interface.
|
|
|
|
|
|
|
|
Examples:
|
2009-03-28 09:44:27 +03: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 18:42:27 +04:00
|
|
|
#launch a QEMU instance with the default network script
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img -net nic -net tap
|
2009-03-28 09:44:27 +03: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 18:42:27 +04:00
|
|
|
#launch a QEMU instance with two NICs, each one connected
|
|
|
|
#to a TAP device
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,vlan=0 -net tap,vlan=0,ifname=tap0 \
|
|
|
|
-net nic,vlan=1 -net tap,vlan=1,ifname=tap1
|
2009-03-28 09:44:27 +03: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 18:42:27 +04:00
|
|
|
@example
|
|
|
|
#launch a QEMU instance with the default network helper to
|
|
|
|
#connect a TAP device to bridge br0
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
2013-10-23 00:49:28 +04:00
|
|
|
-net nic -net tap,"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 18:42:27 +04:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 17:14:27 +04: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 18:42:27 +04:00
|
|
|
@item -net bridge[,vlan=@var{n}][,name=@var{name}][,br=@var{bridge}][,helper=@var{helper}]
|
|
|
|
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-23 00:49:28 +04: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 18:42:27 +04:00
|
|
|
device is @file{br0}.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
@example
|
|
|
|
#launch a QEMU instance with the default network helper to
|
|
|
|
#connect a TAP device to bridge br0
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img -net bridge -net nic,model=virtio
|
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 18:42:27 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
@example
|
|
|
|
#launch a QEMU instance with the default network helper to
|
|
|
|
#connect a TAP device to bridge qemubr0
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img -net bridge,br=qemubr0 -net nic,model=virtio
|
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 18:42:27 +04:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 17:14:27 +04:00
|
|
|
@item -netdev socket,id=@var{id}[,fd=@var{h}][,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}]
|
2010-03-18 21:41:49 +03:00
|
|
|
@item -net socket[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}] [,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}]
|
2009-03-28 09:44:27 +03:00
|
|
|
|
|
|
|
Connect the VLAN @var{n} to a remote VLAN in another QEMU virtual
|
|
|
|
machine using a TCP socket connection. If @option{listen} is
|
|
|
|
specified, QEMU waits for incoming connections on @var{port}
|
|
|
|
(@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-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:56 \
|
|
|
|
-net socket,listen=:1234
|
2009-03-28 09:44:27 +03:00
|
|
|
# connect the VLAN 0 of this instance to the VLAN 0
|
|
|
|
# of the first instance
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:57 \
|
|
|
|
-net socket,connect=127.0.0.1:1234
|
2009-03-28 09:44:27 +03:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 17:14:27 +04:00
|
|
|
@item -netdev socket,id=@var{id}[,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]]
|
2010-12-01 22:16:47 +03:00
|
|
|
@item -net socket[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]]
|
2009-03-28 09:44:27 +03:00
|
|
|
|
|
|
|
Create a VLAN @var{n} shared 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}.
|
|
|
|
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-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:56 \
|
|
|
|
-net socket,mcast=230.0.0.1:1234
|
2009-03-28 09:44:27 +03:00
|
|
|
# launch another QEMU instance on same "bus"
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:57 \
|
|
|
|
-net socket,mcast=230.0.0.1:1234
|
2009-03-28 09:44:27 +03:00
|
|
|
# launch yet another QEMU instance on same "bus"
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:58 \
|
|
|
|
-net socket,mcast=230.0.0.1:1234
|
2009-03-28 09:44:27 +03:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Example (User Mode Linux compat.):
|
|
|
|
@example
|
|
|
|
# launch QEMU instance (note mcast address selected
|
|
|
|
# is UML's default)
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:56 \
|
|
|
|
-net socket,mcast=239.192.168.1:1102
|
2009-03-28 09:44:27 +03:00
|
|
|
# launch UML
|
|
|
|
/path/to/linux ubd0=/path/to/root_fs eth0=mcast
|
|
|
|
@end example
|
|
|
|
|
2010-12-01 22:16:47 +03:00
|
|
|
Example (send packets from host's 1.2.3.4):
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img \
|
|
|
|
-net nic,macaddr=52:54:00:12:34:56 \
|
|
|
|
-net socket,mcast=239.192.168.1:1102,localaddr=1.2.3.4
|
2010-12-01 22:16:47 +03:00
|
|
|
@end example
|
|
|
|
|
2012-08-14 17:14:27 +04:00
|
|
|
@item -netdev vde,id=@var{id}[,sock=@var{socketpath}][,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}]
|
2010-03-18 21:41:49 +03:00
|
|
|
@item -net vde[,vlan=@var{n}][,name=@var{name}][,sock=@var{socketpath}] [,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}]
|
2009-03-28 09:44:27 +03:00
|
|
|
Connect VLAN @var{n} to PORT @var{n} of a vde switch running on host and
|
|
|
|
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 20:13:03 +04:00
|
|
|
communication port. This option is only available if QEMU has been compiled
|
2009-03-28 09:44:27 +03:00
|
|
|
with vde support enabled.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
# launch vde switch
|
|
|
|
vde_switch -F -sock /tmp/myswitch
|
|
|
|
# launch QEMU instance
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 linux.img -net nic -net vde,sock=/tmp/myswitch
|
2009-03-28 09:44:27 +03:00
|
|
|
@end example
|
|
|
|
|
2013-02-26 14:07:16 +04:00
|
|
|
@item -netdev hubport,id=@var{id},hubid=@var{hubid}
|
|
|
|
|
|
|
|
Create a hub port on QEMU "vlan" @var{hubid}.
|
|
|
|
|
|
|
|
The hubport netdev lets you connect a NIC to a QEMU "vlan" instead of a single
|
|
|
|
netdev. @code{-net} and @code{-device} with parameter @option{vlan} create the
|
|
|
|
required hub automatically.
|
|
|
|
|
2009-04-21 23:56:28 +04:00
|
|
|
@item -net dump[,vlan=@var{n}][,file=@var{file}][,len=@var{len}]
|
|
|
|
Dump network traffic on VLAN @var{n} to file @var{file} (@file{qemu-vlan0.pcap} by default).
|
|
|
|
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.
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
@item -net none
|
|
|
|
Indicate that no network devices should be configured. It is used to
|
|
|
|
override the default configuration (@option{-net nic -net user}) which
|
|
|
|
is activated if no @option{-net} options are provided.
|
2013-02-13 22:49:40 +04:00
|
|
|
ETEXI
|
2009-03-28 09:44:27 +03:00
|
|
|
|
2013-02-13 22:49:40 +04:00
|
|
|
STEXI
|
2009-03-28 09:44:27 +03:00
|
|
|
@end table
|
|
|
|
ETEXI
|
2009-10-30 16:41:12 +03:00
|
|
|
DEFHEADING()
|
|
|
|
|
|
|
|
DEFHEADING(Character device options:)
|
2013-02-13 22:49:40 +04:00
|
|
|
STEXI
|
|
|
|
|
|
|
|
The general form of a character device option is:
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
2009-10-30 16:41:12 +03:00
|
|
|
|
|
|
|
DEF("chardev", HAS_ARG, QEMU_OPTION_chardev,
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev null,id=id[,mux=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
"-chardev socket,id=id[,host=host],port=host[,to=to][,ipv4][,ipv6][,nodelay]\n"
|
2010-04-06 18:55:54 +04:00
|
|
|
" [,server][,nowait][,telnet][,mux=on|off] (tcp)\n"
|
|
|
|
"-chardev socket,id=id,path=path[,server][,nowait][,telnet],[mux=on|off] (unix)\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
"-chardev udp,id=id[,host=host],port=port[,localaddr=localaddr]\n"
|
2010-04-06 18:55:54 +04:00
|
|
|
" [,localport=localport][,ipv4][,ipv6][,mux=on|off]\n"
|
|
|
|
"-chardev msmouse,id=id[,mux=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
"-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]\n"
|
2010-04-06 18:55:54 +04:00
|
|
|
" [,mux=on|off]\n"
|
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 18:44:32 +04:00
|
|
|
"-chardev ringbuf,id=id[,size=size]\n"
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev file,id=id,path=path[,mux=on|off]\n"
|
|
|
|
"-chardev pipe,id=id,path=path[,mux=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
#ifdef _WIN32
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev console,id=id[,mux=on|off]\n"
|
|
|
|
"-chardev serial,id=id,path=path[,mux=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
#else
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev pty,id=id[,mux=on|off]\n"
|
2010-07-13 23:13:12 +04:00
|
|
|
"-chardev stdio,id=id[,mux=on|off][,signal=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_BRLAPI
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev braille,id=id[,mux=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
#endif
|
|
|
|
#if defined(__linux__) || defined(__sun__) || defined(__FreeBSD__) \
|
|
|
|
|| defined(__NetBSD__) || defined(__OpenBSD__) || defined(__DragonFly__)
|
2012-12-19 16:50:29 +04:00
|
|
|
"-chardev serial,id=id,path=path[,mux=on|off]\n"
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev tty,id=id,path=path[,mux=on|off]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
#endif
|
|
|
|
#if defined(__linux__) || defined(__FreeBSD__) || defined(__DragonFly__)
|
2013-01-10 17:20:58 +04:00
|
|
|
"-chardev parallel,id=id,path=path[,mux=on|off]\n"
|
2010-04-06 18:55:54 +04:00
|
|
|
"-chardev parport,id=id,path=path[,mux=on|off]\n"
|
2011-01-19 11:49:50 +03:00
|
|
|
#endif
|
|
|
|
#if defined(CONFIG_SPICE)
|
|
|
|
"-chardev spicevmc,id=id,name=name[,debug=debug]\n"
|
2012-12-05 19:15:34 +04:00
|
|
|
"-chardev spiceport,id=id,name=name[,debug=debug]\n"
|
2009-10-30 16:41:12 +03:00
|
|
|
#endif
|
2010-03-29 23:23:52 +04:00
|
|
|
, QEMU_ARCH_ALL
|
2009-10-30 16:41:12 +03:00
|
|
|
)
|
|
|
|
|
|
|
|
STEXI
|
2010-04-06 18:55:54 +04:00
|
|
|
@item -chardev @var{backend} ,id=@var{id} [,mux=on|off] [,@var{options}]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -chardev
|
2009-10-30 16:41:12 +03: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 18:44:32 +04:00
|
|
|
@option{ringbuf},
|
2009-10-30 16:41:12 +03:00
|
|
|
@option{file},
|
|
|
|
@option{pipe},
|
|
|
|
@option{console},
|
|
|
|
@option{serial},
|
|
|
|
@option{pty},
|
|
|
|
@option{stdio},
|
|
|
|
@option{braille},
|
|
|
|
@option{tty},
|
2013-01-10 17:20:58 +04:00
|
|
|
@option{parallel},
|
2011-01-19 11:49:50 +03:00
|
|
|
@option{parport},
|
|
|
|
@option{spicevmc}.
|
2012-12-05 19:15:34 +04:00
|
|
|
@option{spiceport}.
|
2009-10-30 16:41:12 +03:00
|
|
|
The specific backend will determine the applicable options.
|
|
|
|
|
|
|
|
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 18:55:54 +04:00
|
|
|
A character device may be used in multiplexing mode by multiple front-ends.
|
|
|
|
The key sequence of @key{Control-a} and @key{c} will rotate the input focus
|
|
|
|
between attached front-ends. Specify @option{mux=on} to enable this mode.
|
|
|
|
|
2009-10-30 16:41:12 +03:00
|
|
|
Options to each backend are described below.
|
|
|
|
|
|
|
|
@item -chardev null ,id=@var{id}
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item -chardev socket ,id=@var{id} [@var{TCP options} or @var{unix options}] [,server] [,nowait] [,telnet]
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
TCP and unix socket options are given below:
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
|
2010-03-27 13:52:05 +03:00
|
|
|
@item TCP options: port=@var{port} [,host=@var{host}] [,to=@var{to}] [,ipv4] [,ipv6] [,nodelay]
|
2009-10-30 16:41:12 +03: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
|
|
|
|
|
|
|
|
@item -chardev udp ,id=@var{id} [,host=@var{host}] ,port=@var{port} [,localaddr=@var{localaddr}] [,localport=@var{localport}] [,ipv4] [,ipv6]
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item -chardev msmouse ,id=@var{id}
|
|
|
|
|
|
|
|
Forward QEMU's emulated msmouse events to the guest. @option{msmouse} does not
|
|
|
|
take any options.
|
|
|
|
|
|
|
|
@item -chardev vc ,id=@var{id} [[,width=@var{width}] [,height=@var{height}]] [[,cols=@var{cols}] [,rows=@var{rows}]]
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
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 18:44:32 +04:00
|
|
|
@item -chardev ringbuf ,id=@var{id} [,size=@var{size}]
|
2013-01-24 20:03:19 +04: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-07 00:27:24 +04:00
|
|
|
Create a ring buffer with fixed size @option{size}.
|
|
|
|
@var{size} must be a power of two, and defaults to @code{64K}).
|
2013-01-24 20:03:19 +04:00
|
|
|
|
2009-10-30 16:41:12 +03:00
|
|
|
@item -chardev file ,id=@var{id} ,path=@var{path}
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item -chardev pipe ,id=@var{id} ,path=@var{path}
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item -chardev console ,id=@var{id}
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item -chardev serial ,id=@var{id} ,path=@option{path}
|
|
|
|
|
|
|
|
Send traffic from the guest to a serial device on the host.
|
|
|
|
|
2012-12-19 16:50:29 +04:00
|
|
|
On Unix hosts serial will actually accept any tty device,
|
|
|
|
not only serial lines.
|
2009-10-30 16:41:12 +03:00
|
|
|
|
|
|
|
@option{path} specifies the name of the serial device to open.
|
|
|
|
|
|
|
|
@item -chardev pty ,id=@var{id}
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
2010-07-13 23:13:12 +04:00
|
|
|
@item -chardev stdio ,id=@var{id} [,signal=on|off]
|
2012-05-12 00:25:50 +04:00
|
|
|
Connect to standard input and standard output of the QEMU process.
|
2010-07-13 23:13:12 +04: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.
|
|
|
|
|
|
|
|
@option{stdio} is not available on Windows hosts.
|
2009-10-30 16:41:12 +03:00
|
|
|
|
|
|
|
@item -chardev braille ,id=@var{id}
|
|
|
|
|
|
|
|
Connect to a local BrlAPI server. @option{braille} does not take any options.
|
|
|
|
|
|
|
|
@item -chardev tty ,id=@var{id} ,path=@var{path}
|
|
|
|
|
|
|
|
@option{tty} is only available on Linux, Sun, FreeBSD, NetBSD, OpenBSD and
|
2013-02-13 18:54:15 +04:00
|
|
|
DragonFlyBSD hosts. It is an alias for @option{serial}.
|
2009-10-30 16:41:12 +03:00
|
|
|
|
|
|
|
@option{path} specifies the path to the tty. @option{path} is required.
|
|
|
|
|
2013-01-10 17:20:58 +04:00
|
|
|
@item -chardev parallel ,id=@var{id} ,path=@var{path}
|
2009-10-30 16:41:12 +03:00
|
|
|
@item -chardev parport ,id=@var{id} ,path=@var{path}
|
|
|
|
|
2013-01-10 17:20:58 +04:00
|
|
|
@option{parallel} is only available on Linux, FreeBSD and DragonFlyBSD hosts.
|
2009-10-30 16:41:12 +03:00
|
|
|
|
|
|
|
Connect to a local parallel port.
|
|
|
|
|
|
|
|
@option{path} specifies the path to the parallel port device. @option{path} is
|
|
|
|
required.
|
|
|
|
|
2011-01-19 11:49:50 +03:00
|
|
|
@item -chardev spicevmc ,id=@var{id} ,debug=@var{debug}, name=@var{name}
|
|
|
|
|
2011-10-06 14:24:12 +04:00
|
|
|
@option{spicevmc} is only available when spice support is built in.
|
|
|
|
|
2011-01-19 11:49:50 +03: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.
|
|
|
|
|
2012-12-05 19:15:34 +04:00
|
|
|
@item -chardev spiceport ,id=@var{id} ,debug=@var{debug}, name=@var{name}
|
|
|
|
|
|
|
|
@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 22:49:40 +04:00
|
|
|
ETEXI
|
2012-12-05 19:15:34 +04:00
|
|
|
|
2013-02-13 22:49:40 +04:00
|
|
|
STEXI
|
2009-10-30 16:41:12 +03:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
2011-10-26 16:51:37 +04:00
|
|
|
DEFHEADING(Device URL Syntax:)
|
2013-02-13 22:49:40 +04:00
|
|
|
STEXI
|
2011-10-26 16:51:37 +04:00
|
|
|
|
|
|
|
In addition to using normal file images for the emulated storage devices,
|
|
|
|
QEMU can also use networked resources such as iSCSI devices. These are
|
|
|
|
specified using a special URL syntax.
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item iSCSI
|
|
|
|
iSCSI support allows QEMU to access iSCSI resources directly and use as
|
|
|
|
images for the guest storage. Both disk and cdrom images are supported.
|
|
|
|
|
|
|
|
Syntax for specifying iSCSI LUNs is
|
|
|
|
``iscsi://<target-ip>[:<port>]/<target-iqn>/<lun>''
|
|
|
|
|
2012-08-06 12:24:55 +04:00
|
|
|
By default qemu will use the iSCSI initiator-name
|
|
|
|
'iqn.2008-11.org.linux-kvm[:<name>]' but this can also be set from the command
|
|
|
|
line or a configuration file.
|
|
|
|
|
|
|
|
|
2011-10-26 16:51:37 +04:00
|
|
|
Example (without authentication):
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -iscsi initiator-name=iqn.2001-04.com.example:my-initiator \
|
|
|
|
-cdrom iscsi://192.0.2.1/iqn.2001-04.com.example/2 \
|
|
|
|
-drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
|
2011-10-26 16:51:37 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Example (CHAP username/password via URL):
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -drive file=iscsi://user%password@@192.0.2.1/iqn.2001-04.com.example/1
|
2011-10-26 16:51:37 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Example (CHAP username/password via environment variables):
|
|
|
|
@example
|
|
|
|
LIBISCSI_CHAP_USERNAME="user" \
|
|
|
|
LIBISCSI_CHAP_PASSWORD="password" \
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
|
2011-10-26 16:51:37 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
iSCSI support is an optional feature of QEMU and only available when
|
|
|
|
compiled and linked against libiscsi.
|
2012-01-26 02:39:02 +04:00
|
|
|
ETEXI
|
|
|
|
DEF("iscsi", HAS_ARG, QEMU_OPTION_iscsi,
|
|
|
|
"-iscsi [user=user][,password=password]\n"
|
|
|
|
" [,header-digest=CRC32C|CR32C-NONE|NONE-CRC32C|NONE\n"
|
2013-12-06 19:08:05 +04:00
|
|
|
" [,initiator-name=initiator-iqn][,id=target-iqn]\n"
|
2012-01-26 02:39:02 +04:00
|
|
|
" iSCSI session parameters\n", QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2011-10-26 16:51:37 +04:00
|
|
|
|
2012-08-06 12:24:55 +04:00
|
|
|
iSCSI parameters such as username and password can also be specified via
|
|
|
|
a configuration file. See qemu-doc for more information and examples.
|
|
|
|
|
2011-10-27 13:33:21 +04:00
|
|
|
@item NBD
|
|
|
|
QEMU supports NBD (Network Block Devices) both using TCP protocol as well
|
|
|
|
as Unix Domain Sockets.
|
|
|
|
|
|
|
|
Syntax for specifying a NBD device using TCP
|
|
|
|
``nbd:<server-ip>:<port>[:exportname=<export>]''
|
|
|
|
|
|
|
|
Syntax for specifying a NBD device using Unix Domain Sockets
|
|
|
|
``nbd:unix:<domain-socket>[:exportname=<export>]''
|
|
|
|
|
|
|
|
|
|
|
|
Example for TCP
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 --drive file=nbd:192.0.2.1:30000
|
2011-10-27 13:33:21 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
Example for Unix Domain Sockets
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
qemu-system-i386 --drive file=nbd:unix:/tmp/nbd-socket
|
2011-10-27 13:33:21 +04:00
|
|
|
@end example
|
|
|
|
|
2013-04-09 18:30:53 +04:00
|
|
|
@item SSH
|
|
|
|
QEMU supports SSH (Secure Shell) access to remote disks.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
@example
|
|
|
|
qemu-system-i386 -drive file=ssh://user@@host/path/to/disk.img
|
|
|
|
qemu-system-i386 -drive file.driver=ssh,file.user=user,file.host=host,file.port=22,file.path=/path/to/disk.img
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Currently authentication must be done using ssh-agent. Other
|
|
|
|
authentication methods may be supported in future.
|
|
|
|
|
2011-10-28 13:13:39 +04:00
|
|
|
@item Sheepdog
|
|
|
|
Sheepdog is a distributed storage system for QEMU.
|
|
|
|
QEMU supports using either local sheepdog devices or remote networked
|
|
|
|
devices.
|
|
|
|
|
|
|
|
Syntax for specifying a sheepdog device
|
2013-02-22 07:39:51 +04:00
|
|
|
@example
|
2013-02-22 07:39:53 +04:00
|
|
|
sheepdog[+tcp|+unix]://[host:port]/vdiname[?socket=path][#snapid|#tag]
|
2013-02-22 07:39:51 +04:00
|
|
|
@end example
|
2011-10-28 13:13:39 +04:00
|
|
|
|
|
|
|
Example
|
|
|
|
@example
|
2013-02-22 07:39:51 +04:00
|
|
|
qemu-system-i386 --drive file=sheepdog://192.0.2.1:30000/MyVirtualMachine
|
2011-10-28 13:13:39 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
See also @url{http://http://www.osrg.net/sheepdog/}.
|
|
|
|
|
2012-10-24 15:47:53 +04:00
|
|
|
@item GlusterFS
|
|
|
|
GlusterFS is an user space distributed file system.
|
|
|
|
QEMU supports the use of GlusterFS volumes for hosting VM disk images using
|
|
|
|
TCP, Unix Domain Sockets and RDMA transport protocols.
|
|
|
|
|
|
|
|
Syntax for specifying a VM disk image on GlusterFS volume is
|
|
|
|
@example
|
|
|
|
gluster[+transport]://[server[:port]]/volname/image[?socket=...]
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
|
|
Example
|
|
|
|
@example
|
2013-03-07 11:50:26 +04:00
|
|
|
qemu-system-x86_64 --drive file=gluster://192.0.2.1/testvol/a.img
|
2012-10-24 15:47:53 +04:00
|
|
|
@end example
|
|
|
|
|
|
|
|
See also @url{http://www.gluster.org}.
|
2014-05-15 03:28:43 +04:00
|
|
|
|
|
|
|
@item HTTP/HTTPS/FTP/FTPS/TFTP
|
|
|
|
QEMU supports read-only access to files accessed over http(s), ftp(s) and tftp.
|
|
|
|
|
|
|
|
Syntax using a single filename:
|
|
|
|
@example
|
|
|
|
<protocol>://[<username>[:<password>]@@]<host>/<path>
|
|
|
|
@end example
|
|
|
|
|
|
|
|
where:
|
|
|
|
@table @option
|
|
|
|
@item protocol
|
|
|
|
'http', 'https', 'ftp', 'ftps', or 'tftp'.
|
|
|
|
|
|
|
|
@item username
|
|
|
|
Optional username for authentication to the remote server.
|
|
|
|
|
|
|
|
@item password
|
|
|
|
Optional password for authentication to the remote server.
|
|
|
|
|
|
|
|
@item host
|
|
|
|
Address of the remote server.
|
|
|
|
|
|
|
|
@item path
|
|
|
|
Path on the remote server, including any query string.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
The following options are also supported:
|
|
|
|
@table @option
|
|
|
|
@item url
|
|
|
|
The full URL when passing options to the driver explicitly.
|
|
|
|
|
|
|
|
@item readahead
|
|
|
|
The amount of data to read ahead with each range request to the remote server.
|
|
|
|
This value may optionally have the suffix 'T', 'G', 'M', 'K', 'k' or 'b'. If it
|
|
|
|
does not have a suffix, it will be assumed to be in bytes. The value must be a
|
|
|
|
multiple of 512 bytes. It defaults to 256k.
|
|
|
|
|
|
|
|
@item sslverify
|
|
|
|
Whether to verify the remote server's certificate when connecting over SSL. It
|
|
|
|
can have the value 'on' or 'off'. It defaults to 'on'.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
Note that when passing options to qemu explicitly, @option{driver} is the value
|
|
|
|
of <protocol>.
|
|
|
|
|
|
|
|
Example: boot from a remote Fedora 20 live ISO image
|
|
|
|
@example
|
|
|
|
qemu-system-x86_64 --drive media=cdrom,file=http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso,readonly
|
|
|
|
|
|
|
|
qemu-system-x86_64 --drive media=cdrom,file.driver=http,file.url=http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso,readonly
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Example: boot from a remote Fedora 20 cloud image using a local overlay for
|
|
|
|
writes, copy-on-read, and a readahead of 64k
|
|
|
|
@example
|
|
|
|
qemu-img create -f qcow2 -o backing_file='json:@{"file.driver":"http",, "file.url":"https://dl.fedoraproject.org/pub/fedora/linux/releases/20/Images/x86_64/Fedora-x86_64-20-20131211.1-sda.qcow2",, "file.readahead":"64k"@}' /tmp/Fedora-x86_64-20-20131211.1-sda.qcow2
|
|
|
|
|
|
|
|
qemu-system-x86_64 -drive file=/tmp/Fedora-x86_64-20-20131211.1-sda.qcow2,copy-on-read=on
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Example: boot from an image stored on a VMware vSphere server with a self-signed
|
|
|
|
certificate using a local overlay for writes and a readahead of 64k
|
|
|
|
@example
|
|
|
|
qemu-img create -f qcow2 -o backing_file='json:@{"file.driver":"https",, "file.url":"https://user:password@@vsphere.example.com/folder/test/test-flat.vmdk?dcPath=Datacenter&dsName=datastore1",, "file.sslverify":"off",, "file.readahead":"64k"@}' /tmp/test.qcow2
|
|
|
|
|
|
|
|
qemu-system-x86_64 -drive file=/tmp/test.qcow2
|
|
|
|
@end example
|
2013-02-13 22:49:40 +04:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
STEXI
|
2011-10-26 16:51:37 +04:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-10-30 16:41:12 +03:00
|
|
|
DEFHEADING(Bluetooth(R) options:)
|
2013-02-13 22:49:40 +04:00
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
2009-10-30 16:41:12 +03:00
|
|
|
|
2009-03-28 09:44:27 +03: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 23:23:52 +04:00
|
|
|
" emulate a bluetooth device 'dev' in scatternet 'n'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -bt hci[...]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -bt
|
2009-03-28 09:44:27 +03: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.
|
|
|
|
|
|
|
|
@anchor{bt-hcis}
|
|
|
|
The following three types are recognized:
|
|
|
|
|
2009-10-09 12:58:35 +04:00
|
|
|
@table @option
|
2009-03-28 09:44:27 +03: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-12 00:21:50 +04:00
|
|
|
qemu-system-i386 [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5
|
2009-03-28 09:44:27 +03: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 12:58:35 +04:00
|
|
|
@table @option
|
2009-03-28 09:44:27 +03:00
|
|
|
@item keyboard
|
|
|
|
Virtual wireless keyboard implementing the HIDP bluetooth profile.
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2013-02-13 22:49:40 +04:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
2009-03-28 09:44:27 +03: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 21:47:49 +04:00
|
|
|
#ifdef CONFIG_TPM
|
|
|
|
DEFHEADING(TPM device options:)
|
|
|
|
|
|
|
|
DEF("tpmdev", HAS_ARG, QEMU_OPTION_tpmdev, \
|
2013-02-27 21:47:54 +04: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"
|
|
|
|
" not provided it will be searched for in /sys/class/misc/tpm?/device\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 21:47:49 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
|
|
|
|
|
|
|
The general form of a TPM device option is:
|
|
|
|
@table @option
|
|
|
|
|
|
|
|
@item -tpmdev @var{backend} ,id=@var{id} [,@var{options}]
|
|
|
|
@findex -tpmdev
|
|
|
|
Backend type must be:
|
2013-02-27 21:47:53 +04:00
|
|
|
@option{passthrough}.
|
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 21:47:49 +04:00
|
|
|
|
|
|
|
The specific backend type will determine the applicable options.
|
2013-03-20 20:34:49 +04: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 21:47:49 +04:00
|
|
|
|
|
|
|
Options to each backend are described below.
|
|
|
|
|
|
|
|
Use 'help' to print all available TPM backend types.
|
|
|
|
@example
|
|
|
|
qemu -tpmdev help
|
|
|
|
@end example
|
|
|
|
|
2013-02-27 21:47:54 +04:00
|
|
|
@item -tpmdev passthrough, id=@var{id}, path=@var{path}, cancel-path=@var{cancel-path}
|
2013-02-27 21:47:53 +04: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 21:47:54 +04: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 21:47:53 +04: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.
|
|
|
|
|
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 21:47:49 +04:00
|
|
|
@end table
|
|
|
|
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEFHEADING()
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
2009-06-28 18:55:55 +04:00
|
|
|
DEFHEADING(Linux/Multiboot boot specific:)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2009-06-28 18:55:55 +04: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 09:44:27 +03:00
|
|
|
for easier testing of various kernels.
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("kernel", HAS_ARG, QEMU_OPTION_kernel, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-kernel bzImage use 'bzImage' as kernel image\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -kernel @var{bzImage}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -kernel
|
2009-06-28 18:55:55 +04:00
|
|
|
Use @var{bzImage} as kernel image. The kernel can be either a Linux kernel
|
|
|
|
or in multiboot format.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("append", HAS_ARG, QEMU_OPTION_append, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-append cmdline use 'cmdline' as kernel command line\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -append @var{cmdline}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -append
|
2009-03-28 09:44:27 +03:00
|
|
|
Use @var{cmdline} as kernel command line
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("initrd", HAS_ARG, QEMU_OPTION_initrd, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-initrd file use 'file' as initial ram disk\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -initrd @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -initrd
|
2009-03-28 09:44:27 +03:00
|
|
|
Use @var{file} as initial ram disk.
|
2009-06-28 18:55:55 +04: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 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2012-03-02 15:56:38 +04:00
|
|
|
DEF("dtb", HAS_ARG, QEMU_OPTION_dtb, \
|
2012-03-04 15:03:54 +04:00
|
|
|
"-dtb file use 'file' as device tree image\n", QEMU_ARCH_ALL)
|
2012-03-02 15:56:38 +04: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 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
DEFHEADING()
|
|
|
|
|
|
|
|
DEFHEADING(Debug/Expert options:)
|
|
|
|
STEXI
|
|
|
|
@table @option
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("serial", HAS_ARG, QEMU_OPTION_serial, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-serial dev redirect the serial port to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -serial @var{dev}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -serial
|
2009-03-28 09:44:27 +03: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 12:58:35 +04:00
|
|
|
@table @option
|
2009-10-09 12:58:36 +04:00
|
|
|
@item vc[:@var{W}x@var{H}]
|
2009-03-28 09:44:27 +03: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 17:44:53 +04:00
|
|
|
@item chardev:@var{id}
|
|
|
|
Use a named character device defined with the @code{-chardev} option.
|
2009-03-28 09:44:27 +03: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-12 00:25:50 +04: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 09:44:27 +03:00
|
|
|
will appear in the netconsole session.
|
|
|
|
|
|
|
|
If you plan to send characters back via netconsole or you want to stop
|
2012-05-12 00:25:50 +04:00
|
|
|
and start QEMU a lot of times, you should have QEMU use the same
|
2009-03-28 09:44:27 +03:00
|
|
|
source port each time by using something like @code{-serial
|
2012-05-12 00:25:50 +04:00
|
|
|
udp::4555@@:4556} to QEMU. Another approach is to use a patched
|
2009-03-28 09:44:27 +03: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
|
|
|
|
use the following options to step up a netcat redirector to allow
|
2012-05-12 00:25:50 +04:00
|
|
|
telnet on port 5555 to access the QEMU port.
|
2009-03-28 09:44:27 +03:00
|
|
|
@table @code
|
2012-04-07 11:23:36 +04:00
|
|
|
@item QEMU Options:
|
2009-03-28 09:44:27 +03: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
|
|
|
|
|
|
|
|
@item tcp:[@var{host}]:@var{port}[,@var{server}][,nowait][,nodelay]
|
|
|
|
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
|
|
|
|
algorithm. If @var{host} is omitted, 0.0.0.0 is assumed. Only
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item unix:@var{path}[,server][,nowait]
|
|
|
|
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 20:29:45 +04:00
|
|
|
@key{Control-a} and then pressing @key{c}.
|
2009-03-28 09:44:27 +03: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 12:55:50 +04: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 09:44:27 +03:00
|
|
|
|
|
|
|
@item braille
|
|
|
|
Braille device. This will use BrlAPI to display the braille output on a real
|
|
|
|
or fake device.
|
|
|
|
|
2009-10-09 12:58:37 +04:00
|
|
|
@item msmouse
|
|
|
|
Three button serial mouse. Configure the guest to use Microsoft protocol.
|
2009-03-28 09:44:27 +03:00
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("parallel", HAS_ARG, QEMU_OPTION_parallel, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-parallel dev redirect the parallel port to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -parallel @var{dev}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -parallel
|
2009-03-28 09:44:27 +03: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 23:23:52 +04:00
|
|
|
"-monitor dev redirect the monitor to char device 'dev'\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2009-12-08 15:11:37 +03:00
|
|
|
@item -monitor @var{dev}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -monitor
|
2009-03-28 09:44:27 +03: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 20:02:55 +04:00
|
|
|
Use @code{-monitor none} to disable the default monitor.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
2009-12-08 15:11:52 +03:00
|
|
|
DEF("qmp", HAS_ARG, QEMU_OPTION_qmp, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-qmp dev like -monitor but opens in 'control' mode\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-01-21 00:25:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -qmp @var{dev}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -qmp
|
2010-01-21 00:25:27 +03:00
|
|
|
Like -monitor but opens in 'control' mode.
|
|
|
|
ETEXI
|
2009-03-28 09:44:27 +03:00
|
|
|
|
2009-12-08 15:11:51 +03:00
|
|
|
DEF("mon", HAS_ARG, QEMU_OPTION_mon, \
|
2013-06-15 13:47:32 +04:00
|
|
|
"-mon [chardev=]name[,mode=readline|control][,default]\n", QEMU_ARCH_ALL)
|
2009-12-08 15:11:51 +03:00
|
|
|
STEXI
|
2013-06-15 13:47:32 +04:00
|
|
|
@item -mon [chardev=]name[,mode=readline|control][,default]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -mon
|
2009-12-08 15:11:51 +03:00
|
|
|
Setup monitor on chardev @var{name}.
|
|
|
|
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-30 00:51:36 +03:00
|
|
|
DEF("debugcon", HAS_ARG, QEMU_OPTION_debugcon, \
|
2010-03-29 23:23:52 +04: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-30 00:51:36 +03:00
|
|
|
STEXI
|
|
|
|
@item -debugcon @var{dev}
|
2010-02-06 01:52:05 +03: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-30 00:51:36 +03: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 09:44:27 +03:00
|
|
|
DEF("pidfile", HAS_ARG, QEMU_OPTION_pidfile, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-pidfile file write PID to 'file'\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -pidfile @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -pidfile
|
2009-03-28 09:44:27 +03:00
|
|
|
Store the QEMU process PID in @var{file}. It is useful if you launch QEMU
|
|
|
|
from a script.
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-06 00:08:59 +04:00
|
|
|
DEF("singlestep", 0, QEMU_OPTION_singlestep, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-singlestep always run in singlestep mode\n", QEMU_ARCH_ALL)
|
2009-04-06 00:08:59 +04:00
|
|
|
STEXI
|
|
|
|
@item -singlestep
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -singlestep
|
2009-04-06 00:08:59 +04:00
|
|
|
Run the emulation in single step mode.
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("S", 0, QEMU_OPTION_S, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-S freeze CPU at startup (use 'c' to start execution)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -S
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -S
|
2009-03-28 09:44:27 +03:00
|
|
|
Do not start CPU at startup (you must type 'c' in the monitor).
|
|
|
|
ETEXI
|
|
|
|
|
2013-04-19 18:42:06 +04: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
|
|
|
|
|
2009-04-05 22:43:41 +04:00
|
|
|
DEF("gdb", HAS_ARG, QEMU_OPTION_gdb, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-gdb dev wait for gdb connection on 'dev'\n", QEMU_ARCH_ALL)
|
2009-04-05 22:43:41 +04:00
|
|
|
STEXI
|
|
|
|
@item -gdb @var{dev}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -gdb
|
2009-04-05 22:43:41 +04: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-12 00:25:50 +04:00
|
|
|
stdio are reasonable use case. The latter is allowing to start QEMU from
|
2009-04-05 22:43:41 +04:00
|
|
|
within gdb and establish the connection via a pipe:
|
|
|
|
@example
|
2012-05-12 00:21:50 +04:00
|
|
|
(gdb) target remote | exec qemu-system-i386 -gdb stdio ...
|
2009-04-05 22:43:41 +04:00
|
|
|
@end example
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-04-05 22:43:41 +04:00
|
|
|
DEF("s", 0, QEMU_OPTION_s, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-s shorthand for -gdb tcp::" DEFAULT_GDBSTUB_PORT "\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2009-04-05 22:43:41 +04:00
|
|
|
@item -s
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -s
|
2009-04-05 22:43:41 +04:00
|
|
|
Shorthand for -gdb tcp::1234, i.e. open a gdbserver on TCP port 1234
|
|
|
|
(@pxref{gdb_usage}).
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("d", HAS_ARG, QEMU_OPTION_d, \
|
2013-02-26 21:52:40 +04:00
|
|
|
"-d item1,... enable logging of specified items (use '-d help' for a list of log items)\n",
|
2010-03-29 23:23:52 +04:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2013-02-26 21:52:40 +04:00
|
|
|
@item -d @var{item1}[,...]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -d
|
2013-02-26 21:52:40 +04:00
|
|
|
Enable logging of specified items. Use '-d help' for a list of log items.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2011-06-07 20:32:40 +04:00
|
|
|
DEF("D", HAS_ARG, QEMU_OPTION_D, \
|
2013-02-26 21:52:40 +04:00
|
|
|
"-D logfile output log to logfile (default stderr)\n",
|
2011-06-07 20:32:40 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2012-05-12 00:40:50 +04:00
|
|
|
@item -D @var{logfile}
|
2011-06-07 20:32:40 +04:00
|
|
|
@findex -D
|
2013-02-26 21:52:40 +04:00
|
|
|
Output log in @var{logfile} instead of to stderr
|
2011-06-07 20:32:40 +04:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("L", HAS_ARG, QEMU_OPTION_L, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-L path set the directory for the BIOS, VGA BIOS and keymaps\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -L @var{path}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -L
|
2009-03-28 09:44:27 +03:00
|
|
|
Set the directory for the BIOS, VGA BIOS and keymaps.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("bios", HAS_ARG, QEMU_OPTION_bios, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-bios file set the filename for the BIOS\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -bios @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -bios
|
2009-03-28 09:44:27 +03:00
|
|
|
Set the filename for the BIOS.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("enable-kvm", 0, QEMU_OPTION_enable_kvm, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-enable-kvm enable KVM full virtualization support\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -enable-kvm
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -enable-kvm
|
2009-03-28 09:44:27 +03:00
|
|
|
Enable KVM full virtualization support. This option is only available
|
|
|
|
if KVM support is enabled when compiling.
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-22 19:19:10 +04:00
|
|
|
DEF("xen-domid", HAS_ARG, QEMU_OPTION_xen_domid,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-xen-domid id specify xen guest domain id\n", QEMU_ARCH_ALL)
|
2009-04-22 19:19:10 +04:00
|
|
|
DEF("xen-create", 0, QEMU_OPTION_xen_create,
|
|
|
|
"-xen-create create domain using xen hypercalls, bypassing xend\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" warning: should not be used when xend is in use\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-04-22 19:19:10 +04:00
|
|
|
DEF("xen-attach", 0, QEMU_OPTION_xen_attach,
|
|
|
|
"-xen-attach attach to existing xen domain\n"
|
2012-05-12 00:25:50 +04:00
|
|
|
" xend will use this when starting QEMU\n",
|
2010-03-29 23:23:52 +04:00
|
|
|
QEMU_ARCH_ALL)
|
2010-01-21 00:25:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -xen-domid @var{id}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -xen-domid
|
2010-01-21 00:25:27 +03:00
|
|
|
Specify xen guest domain @var{id} (XEN only).
|
|
|
|
@item -xen-create
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -xen-create
|
2010-01-21 00:25:27 +03:00
|
|
|
Create domain using xen hypercalls, bypassing xend.
|
|
|
|
Warning: should not be used when xend is in use (XEN only).
|
|
|
|
@item -xen-attach
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -xen-attach
|
2010-01-21 00:25:27 +03:00
|
|
|
Attach to existing xen domain.
|
2012-05-12 00:25:50 +04:00
|
|
|
xend will use this when starting QEMU (XEN only).
|
2010-01-21 00:25:27 +03:00
|
|
|
ETEXI
|
2009-04-22 19:19:10 +04:00
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("no-reboot", 0, QEMU_OPTION_no_reboot, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-no-reboot exit instead of rebooting\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-reboot
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-reboot
|
2009-03-28 09:44:27 +03:00
|
|
|
Exit instead of rebooting.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("no-shutdown", 0, QEMU_OPTION_no_shutdown, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-no-shutdown stop before shutdown\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -no-shutdown
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -no-shutdown
|
2009-03-28 09:44:27 +03: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 23:23:52 +04:00
|
|
|
" start right away with a saved state (loadvm in monitor)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -loadvm @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -loadvm
|
2009-03-28 09:44:27 +03:00
|
|
|
Start right away with a saved state (@code{loadvm} in monitor)
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
#ifndef _WIN32
|
|
|
|
DEF("daemonize", 0, QEMU_OPTION_daemonize, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-daemonize daemonize QEMU after initializing\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
#endif
|
|
|
|
STEXI
|
|
|
|
@item -daemonize
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -daemonize
|
2009-03-28 09:44:27 +03: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 23:23:52 +04:00
|
|
|
"-option-rom rom load a file, rom, into the option ROM space\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -option-rom @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -option-rom
|
2009-03-28 09:44:27 +03:00
|
|
|
Load the contents of @var{file} as an option ROM.
|
|
|
|
This option is useful to load things like EtherBoot.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("clock", HAS_ARG, QEMU_OPTION_clock, \
|
|
|
|
"-clock force the use of the given methods for timer alarm.\n" \
|
2012-10-04 19:22:01 +04:00
|
|
|
" To see what timers are available use '-clock help'\n",
|
2010-03-29 23:23:52 +04:00
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -clock @var{method}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -clock
|
2009-03-28 09:44:27 +03:00
|
|
|
Force the use of the given methods for timer alarm. To see what timers
|
2012-10-04 19:22:01 +04:00
|
|
|
are available use @code{-clock help}.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-09-15 15:36:04 +04:00
|
|
|
HXCOMM Options deprecated by -rtc
|
2010-03-29 23:23:52 +04:00
|
|
|
DEF("localtime", 0, QEMU_OPTION_localtime, "", QEMU_ARCH_ALL)
|
|
|
|
DEF("startdate", HAS_ARG, QEMU_OPTION_startdate, "", QEMU_ARCH_ALL)
|
2009-09-15 15:36:04 +04:00
|
|
|
|
|
|
|
DEF("rtc", HAS_ARG, QEMU_OPTION_rtc, \
|
2012-03-30 14:31:21 +04:00
|
|
|
"-rtc [base=utc|localtime|date][,clock=host|rt|vm][,driftfix=none|slew]\n" \
|
2010-03-29 23:23:52 +04:00
|
|
|
" set the RTC base and clock, enable drift fix for clock ticks (x86 only)\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
|
|
|
|
STEXI
|
|
|
|
|
2009-09-15 15:36:04 +04:00
|
|
|
@item -rtc [base=utc|localtime|@var{date}][,clock=host|vm][,driftfix=none|slew]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -rtc
|
2009-09-15 15:36:04 +04: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
|
|
|
|
MS-DOS or Windows. To start at a specific point in time, provide @var{date} in the
|
|
|
|
format @code{2006-06-17T16:01:21} or @code{2006-06-17}. The default base is UTC.
|
|
|
|
|
2014-04-07 13:34:58 +04:00
|
|
|
By default the RTC is driven by the host system time. This allows using of the
|
2009-09-15 15:36:04 +04: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 14:31:21 +04:00
|
|
|
If you want to isolate the guest time from the host, you can set @option{clock}
|
|
|
|
to @code{rt} instead. To even prevent it from progressing during suspension,
|
|
|
|
you can set it to @code{vm}.
|
2009-09-15 15:36:04 +04:00
|
|
|
|
2009-09-15 15:36:04 +04: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 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("icount", HAS_ARG, QEMU_OPTION_icount, \
|
|
|
|
"-icount [N|auto]\n" \
|
2009-04-05 22:43:37 +04:00
|
|
|
" enable virtual instruction counter with 2^N clock ticks per\n" \
|
2010-03-29 23:23:52 +04:00
|
|
|
" instruction\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2009-10-09 12:58:36 +04:00
|
|
|
@item -icount [@var{N}|auto]
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -icount
|
2009-03-28 09:44:27 +03:00
|
|
|
Enable virtual instruction counter. The virtual cpu will execute one
|
2009-10-09 12:58:36 +04:00
|
|
|
instruction every 2^@var{N} ns of virtual time. If @code{auto} is specified
|
2009-03-28 09:44:27 +03:00
|
|
|
then the virtual cpu speed will be automatically adjusted to keep virtual
|
|
|
|
time within a few seconds of real time.
|
|
|
|
|
|
|
|
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.
|
|
|
|
ETEXI
|
|
|
|
|
2009-04-25 16:56:19 +04:00
|
|
|
DEF("watchdog", HAS_ARG, QEMU_OPTION_watchdog, \
|
|
|
|
"-watchdog i6300esb|ib700\n" \
|
2010-03-29 23:23:52 +04:00
|
|
|
" enable virtual hardware watchdog [default=none]\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-04-25 16:56:19 +04:00
|
|
|
STEXI
|
|
|
|
@item -watchdog @var{model}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -watchdog
|
2009-04-25 16:56:19 +04:00
|
|
|
Create a virtual hardware watchdog device. Once enabled (by a guest
|
|
|
|
action), the watchdog must be periodically polled by an agent inside
|
|
|
|
the guest or else the guest will be restarted.
|
|
|
|
|
|
|
|
The @var{model} is the model of hardware watchdog to emulate. Choices
|
|
|
|
for model are: @code{ib700} (iBASE 700) which is a very simple ISA
|
|
|
|
watchdog with a single timer, or @code{i6300esb} (Intel 6300ESB I/O
|
|
|
|
controller hub) which is a much more featureful PCI-based dual-timer
|
|
|
|
watchdog. Choose a model for which your guest has drivers.
|
|
|
|
|
2012-10-04 19:22:01 +04:00
|
|
|
Use @code{-watchdog help} to list available hardware models. Only one
|
2009-04-25 16:56:19 +04:00
|
|
|
watchdog can be enabled for a guest.
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("watchdog-action", HAS_ARG, QEMU_OPTION_watchdog_action, \
|
|
|
|
"-watchdog-action reset|shutdown|poweroff|pause|debug|none\n" \
|
2010-03-29 23:23:52 +04:00
|
|
|
" action when watchdog fires [default=reset]\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-04-25 16:56:19 +04:00
|
|
|
STEXI
|
|
|
|
@item -watchdog-action @var{action}
|
2013-02-13 22:49:38 +04:00
|
|
|
@findex -watchdog-action
|
2009-04-25 16:56:19 +04: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),
|
|
|
|
@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
|
|
|
|
@item -watchdog ib700
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("echr", HAS_ARG, QEMU_OPTION_echr, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-echr chr set terminal escape character instead of ctrl-a\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
|
2009-10-09 12:58:36 +04:00
|
|
|
@item -echr @var{numeric_ascii_value}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -echr
|
2009-03-28 09:44:27 +03: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
|
|
|
|
@item -echr 20
|
|
|
|
@end table
|
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("virtioconsole", HAS_ARG, QEMU_OPTION_virtiocon, \
|
|
|
|
"-virtioconsole c\n" \
|
2010-03-29 23:23:52 +04:00
|
|
|
" set virtio console\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -virtioconsole @var{c}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -virtioconsole
|
2009-03-28 09:44:27 +03:00
|
|
|
Set virtio console.
|
virtio-console: qdev conversion, new virtio-serial-bus
This commit converts the virtio-console device to create a new
virtio-serial bus that can host console and generic serial ports. The
file hosting this code is now called virtio-serial-bus.c.
The virtio console is now a very simple qdev device that sits on the
virtio-serial-bus and communicates between the bus and qemu's chardevs.
This commit also includes a few changes to the virtio backing code for
pci and s390 to spawn the virtio-serial bus.
As a result of the qdev conversion, we get rid of a lot of legacy code.
The old-style way of instantiating a virtio console using
-virtioconsole ...
is maintained, but the new, preferred way is to use
-device virtio-serial -device virtconsole,chardev=...
With this commit, multiple devices as well as multiple ports with a
single device can be supported.
For multiple ports support, each port gets an IO vq pair. Since the
guest needs to know in advance how many vqs a particular device will
need, we have to set this number as a property of the virtio-serial
device and also as a config option.
In addition, we also spawn a pair of control IO vqs. This is an internal
channel meant for guest-host communication for things like port
open/close, sending port properties over to the guest, etc.
This commit is a part of a series of other commits to get the full
implementation of multiport support. Future commits will add other
support as well as ride on the savevm version that we bump up here.
Signed-off-by: Amit Shah <amit.shah@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2010-01-19 22:06:52 +03:00
|
|
|
|
|
|
|
This option is maintained for backward compatibility.
|
|
|
|
|
|
|
|
Please use @code{-device virtconsole} for the new way of invocation.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("show-cursor", 0, QEMU_OPTION_show_cursor, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-show-cursor show cursor\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2010-01-21 00:25:27 +03:00
|
|
|
@item -show-cursor
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -show-cursor
|
2010-01-21 00:25:27 +03:00
|
|
|
Show cursor.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("tb-size", HAS_ARG, QEMU_OPTION_tb_size, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-tb-size n set TB size\n", QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2010-01-21 00:25:27 +03:00
|
|
|
@item -tb-size @var{n}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -tb-size
|
2010-01-21 00:25:27 +03:00
|
|
|
Set TB size.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
|
|
|
DEF("incoming", HAS_ARG, QEMU_OPTION_incoming, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-incoming p prepare for incoming migration, listen on port p\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
STEXI
|
2010-01-21 00:25:27 +03:00
|
|
|
@item -incoming @var{port}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -incoming
|
2010-01-21 00:25:27 +03:00
|
|
|
Prepare for incoming migration, listen on @var{port}.
|
2009-03-28 09:44:27 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-12-08 15:11:46 +03:00
|
|
|
DEF("nodefaults", 0, QEMU_OPTION_nodefaults, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-nodefaults don't create default devices\n", QEMU_ARCH_ALL)
|
2009-12-08 15:11:46 +03:00
|
|
|
STEXI
|
2010-01-16 20:19:44 +03:00
|
|
|
@item -nodefaults
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -nodefaults
|
2012-07-16 16:35:10 +04: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 15:11:46 +03:00
|
|
|
ETEXI
|
|
|
|
|
2009-03-28 09:44:27 +03:00
|
|
|
#ifndef _WIN32
|
|
|
|
DEF("chroot", HAS_ARG, QEMU_OPTION_chroot, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-chroot dir chroot to dir just before starting the VM\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
#endif
|
|
|
|
STEXI
|
2009-10-09 12:58:36 +04:00
|
|
|
@item -chroot @var{dir}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -chroot
|
2009-03-28 09:44:27 +03: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, \
|
2010-03-29 23:23:52 +04:00
|
|
|
"-runas user change to user id user just before starting the VM\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2009-03-28 09:44:27 +03:00
|
|
|
#endif
|
|
|
|
STEXI
|
2009-10-09 12:58:36 +04:00
|
|
|
@item -runas @var{user}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -runas
|
2009-03-28 09:44:27 +03: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 23:23:52 +04:00
|
|
|
" set OpenBIOS nvram variables\n",
|
|
|
|
QEMU_ARCH_PPC | QEMU_ARCH_SPARC)
|
2010-01-21 00:25:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -prom-env @var{variable}=@var{value}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -prom-env
|
2010-01-21 00:25:27 +03:00
|
|
|
Set OpenBIOS nvram @var{variable} to given @var{value} (PPC, SPARC only).
|
|
|
|
ETEXI
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("semihosting", 0, QEMU_OPTION_semihosting,
|
2014-04-22 22:18:42 +04:00
|
|
|
"-semihosting semihosting mode\n",
|
|
|
|
QEMU_ARCH_ARM | QEMU_ARCH_M68K | QEMU_ARCH_XTENSA | QEMU_ARCH_LM32)
|
2010-01-21 00:25:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -semihosting
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -semihosting
|
2011-09-06 03:55:47 +04:00
|
|
|
Semihosting mode (ARM, M68K, Xtensa only).
|
2010-01-21 00:25:27 +03:00
|
|
|
ETEXI
|
2009-03-28 09:44:27 +03:00
|
|
|
DEF("old-param", 0, QEMU_OPTION_old_param,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-old-param old param mode\n", QEMU_ARCH_ARM)
|
2010-01-21 00:25:27 +03:00
|
|
|
STEXI
|
|
|
|
@item -old-param
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -old-param (ARM)
|
2010-01-21 00:25:27 +03:00
|
|
|
Old param mode (ARM only).
|
|
|
|
ETEXI
|
|
|
|
|
2012-08-15 01:44:08 +04:00
|
|
|
DEF("sandbox", HAS_ARG, QEMU_OPTION_sandbox, \
|
|
|
|
"-sandbox <arg> Enable seccomp mode 2 system call filter (default 'off').\n",
|
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2013-02-13 22:49:39 +04:00
|
|
|
@item -sandbox @var{arg}
|
2012-08-15 01:44:08 +04:00
|
|
|
@findex -sandbox
|
|
|
|
Enable Seccomp mode 2 system call filter. 'on' will enable syscall filtering and 'off' will
|
|
|
|
disable it. The default is 'off'.
|
|
|
|
ETEXI
|
|
|
|
|
2009-10-14 12:39:28 +04:00
|
|
|
DEF("readconfig", HAS_ARG, QEMU_OPTION_readconfig,
|
2010-03-29 23:23:52 +04:00
|
|
|
"-readconfig <file>\n", QEMU_ARCH_ALL)
|
2010-01-16 20:19:44 +03:00
|
|
|
STEXI
|
|
|
|
@item -readconfig @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -readconfig
|
2012-07-16 16:28:32 +04: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 20:19:44 +03:00
|
|
|
ETEXI
|
2009-10-14 12:39:28 +04:00
|
|
|
DEF("writeconfig", HAS_ARG, QEMU_OPTION_writeconfig,
|
|
|
|
"-writeconfig <file>\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" read/write config file\n", QEMU_ARCH_ALL)
|
2010-01-16 20:19:44 +03:00
|
|
|
STEXI
|
|
|
|
@item -writeconfig @var{file}
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -writeconfig
|
2012-07-16 16:28:32 +04: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 20:19:44 +03:00
|
|
|
ETEXI
|
2010-01-21 19:57:58 +03:00
|
|
|
DEF("nodefconfig", 0, QEMU_OPTION_nodefconfig,
|
|
|
|
"-nodefconfig\n"
|
2010-03-29 23:23:52 +04:00
|
|
|
" do not load default config files at startup\n",
|
|
|
|
QEMU_ARCH_ALL)
|
2010-01-21 19:57:58 +03:00
|
|
|
STEXI
|
|
|
|
@item -nodefconfig
|
2010-02-06 01:52:05 +03:00
|
|
|
@findex -nodefconfig
|
2012-05-02 20:07:29 +04:00
|
|
|
Normally QEMU loads configuration files from @var{sysconfdir} and @var{datadir} at startup.
|
|
|
|
The @code{-nodefconfig} option will prevent QEMU from loading any of those config files.
|
|
|
|
ETEXI
|
|
|
|
DEF("no-user-config", 0, QEMU_OPTION_nouserconfig,
|
|
|
|
"-no-user-config\n"
|
|
|
|
" do not load user-provided config files at startup\n",
|
|
|
|
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
|
|
|
|
config files on @var{sysconfdir}, but won't make it skip the QEMU-provided config
|
|
|
|
files from @var{datadir}.
|
2010-01-21 19:57:58 +03:00
|
|
|
ETEXI
|
2010-08-09 14:48:32 +04:00
|
|
|
DEF("trace", HAS_ARG, QEMU_OPTION_trace,
|
2011-08-31 22:31:31 +04:00
|
|
|
"-trace [events=<file>][,file=<file>]\n"
|
|
|
|
" specify tracing options\n",
|
2010-08-09 14:48:32 +04:00
|
|
|
QEMU_ARCH_ALL)
|
|
|
|
STEXI
|
2011-08-31 22:31:31 +04:00
|
|
|
HXCOMM This line is not accurate, as some sub-options are backend-specific but
|
|
|
|
HXCOMM HX does not support conditional compilation of text.
|
|
|
|
@item -trace [events=@var{file}][,file=@var{file}]
|
2010-08-09 14:48:32 +04:00
|
|
|
@findex -trace
|
2011-08-31 22:31:03 +04:00
|
|
|
|
2011-08-31 22:31:31 +04:00
|
|
|
Specify tracing options.
|
|
|
|
|
|
|
|
@table @option
|
|
|
|
@item events=@var{file}
|
|
|
|
Immediately enable events listed in @var{file}.
|
|
|
|
The file must contain one event name (as listed in the @var{trace-events} file)
|
|
|
|
per line.
|
2011-09-05 20:13:03 +04:00
|
|
|
This option is only available if QEMU has been compiled with
|
|
|
|
either @var{simple} or @var{stderr} tracing backend.
|
2011-08-31 22:31:31 +04:00
|
|
|
@item file=@var{file}
|
|
|
|
Log output traces to @var{file}.
|
|
|
|
|
2011-09-05 20:13:03 +04:00
|
|
|
This option is only available if QEMU has been compiled with
|
|
|
|
the @var{simple} tracing backend.
|
2011-08-31 22:31:31 +04:00
|
|
|
@end table
|
2010-08-09 14:48:32 +04:00
|
|
|
ETEXI
|
2010-01-16 20:19:44 +03:00
|
|
|
|
2013-02-13 22:49:37 +04: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 17:42:02 +04:00
|
|
|
|
2012-08-03 22:39:21 +04: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 21:51:45 +04:00
|
|
|
HXCOMM Deprecated by -machine accel=tcg property
|
2012-11-20 18:11:21 +04:00
|
|
|
DEF("no-kvm", 0, QEMU_OPTION_no_kvm, "", QEMU_ARCH_I386)
|
2012-10-05 21:51:45 +04:00
|
|
|
|
2012-10-05 21:51:42 +04:00
|
|
|
HXCOMM Deprecated by kvm-pit driver properties
|
2012-11-20 18:11:21 +04:00
|
|
|
DEF("no-kvm-pit-reinjection", 0, QEMU_OPTION_no_kvm_pit_reinjection,
|
2012-10-05 21:51:42 +04:00
|
|
|
"", QEMU_ARCH_I386)
|
|
|
|
|
2012-10-05 21:51:41 +04:00
|
|
|
HXCOMM Deprecated (ignored)
|
2012-11-20 18:11:21 +04:00
|
|
|
DEF("no-kvm-pit", 0, QEMU_OPTION_no_kvm_pit, "", QEMU_ARCH_I386)
|
2012-10-05 21:51:41 +04:00
|
|
|
|
2012-10-05 21:51:40 +04:00
|
|
|
HXCOMM Deprecated by -machine kernel_irqchip=on|off property
|
2012-11-20 18:11:21 +04:00
|
|
|
DEF("no-kvm-irqchip", 0, QEMU_OPTION_no_kvm_irqchip, "", QEMU_ARCH_I386)
|
2012-10-05 21:51:40 +04:00
|
|
|
|
2012-10-05 21:51:44 +04:00
|
|
|
HXCOMM Deprecated (ignored)
|
|
|
|
DEF("tdf", 0, QEMU_OPTION_tdf,"", QEMU_ARCH_ALL)
|
|
|
|
|
2012-06-25 23:36:33 +04:00
|
|
|
DEF("object", HAS_ARG, QEMU_OPTION_object,
|
|
|
|
"-object TYPENAME[,PROP1=VALUE1,...]\n"
|
|
|
|
" create an 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)
|
2013-02-13 22:49:39 +04:00
|
|
|
STEXI
|
|
|
|
@item -object @var{typename}[,@var{prop1}=@var{value1},...]
|
|
|
|
@findex -object
|
|
|
|
Create an 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.
|
|
|
|
ETEXI
|
2012-06-25 23:36:33 +04:00
|
|
|
|
2013-07-04 07:02:46 +04: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
|
|
|
|
|
2010-01-16 20:19:44 +03:00
|
|
|
HXCOMM This is the last statement. Insert new options before this line!
|
|
|
|
STEXI
|
|
|
|
@end table
|
|
|
|
ETEXI
|