xref: /openbmc/qemu/qemu-options.hx (revision 1559e0d4)
1HXCOMM Use DEFHEADING() to define headings in both help text and texi
2HXCOMM Text between STEXI and ETEXI are copied to texi version and
3HXCOMM discarded from C version
4HXCOMM DEF(option, HAS_ARG/0, opt_enum, opt_help, arch_mask) is used to
5HXCOMM construct option structures, enums and help message for specified
6HXCOMM architectures.
7HXCOMM HXCOMM can be used for comments, discarded from both texi and C
8
9DEFHEADING(Standard options:)
10STEXI
11@table @option
12ETEXI
13
14DEF("help", 0, QEMU_OPTION_h,
15    "-h or -help     display this help and exit\n", QEMU_ARCH_ALL)
16STEXI
17@item -h
18@findex -h
19Display help and exit
20ETEXI
21
22DEF("version", 0, QEMU_OPTION_version,
23    "-version        display version information and exit\n", QEMU_ARCH_ALL)
24STEXI
25@item -version
26@findex -version
27Display version information and exit
28ETEXI
29
30DEF("machine", HAS_ARG, QEMU_OPTION_machine, \
31    "-machine [type=]name[,prop[=value][,...]]\n"
32    "                selects emulated machine ('-machine help' for list)\n"
33    "                property accel=accel1[:accel2[:...]] selects accelerator\n"
34    "                supported accelerators are kvm, xen, tcg (default: tcg)\n"
35    "                kernel_irqchip=on|off controls accelerated irqchip support\n"
36    "                kvm_shadow_mem=size of KVM shadow MMU\n"
37    "                dump-guest-core=on|off include guest memory in a core dump (default=on)\n"
38    "                mem-merge=on|off controls memory merge support (default: on)\n",
39    QEMU_ARCH_ALL)
40STEXI
41@item -machine [type=]@var{name}[,prop=@var{value}[,...]]
42@findex -machine
43Select the emulated machine by @var{name}. Use @code{-machine help} to list
44available machines. Supported machine properties are:
45@table @option
46@item accel=@var{accels1}[:@var{accels2}[:...]]
47This is used to enable an accelerator. Depending on the target architecture,
48kvm, xen, or tcg can be available. By default, tcg is used. If there is more
49than one accelerator specified, the next one is used if the previous one fails
50to initialize.
51@item kernel_irqchip=on|off
52Enables in-kernel irqchip support for the chosen accelerator when available.
53@item kvm_shadow_mem=size
54Defines the size of the KVM shadow MMU.
55@item dump-guest-core=on|off
56Include guest memory in a core dump. The default is on.
57@item mem-merge=on|off
58Enables or disables memory merge support. This feature, when supported by
59the host, de-duplicates identical memory pages among VMs instances
60(enabled by default).
61@end table
62ETEXI
63
64HXCOMM Deprecated by -machine
65DEF("M", HAS_ARG, QEMU_OPTION_M, "", QEMU_ARCH_ALL)
66
67DEF("cpu", HAS_ARG, QEMU_OPTION_cpu,
68    "-cpu cpu        select CPU ('-cpu help' for list)\n", QEMU_ARCH_ALL)
69STEXI
70@item -cpu @var{model}
71@findex -cpu
72Select CPU model (@code{-cpu help} for list and additional feature selection)
73ETEXI
74
75DEF("smp", HAS_ARG, QEMU_OPTION_smp,
76    "-smp n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]\n"
77    "                set the number of CPUs to 'n' [default=1]\n"
78    "                maxcpus= maximum number of total cpus, including\n"
79    "                offline CPUs for hotplug, etc\n"
80    "                cores= number of CPU cores on one socket\n"
81    "                threads= number of threads on one CPU core\n"
82    "                sockets= number of discrete sockets in the system\n",
83        QEMU_ARCH_ALL)
84STEXI
85@item -smp @var{n}[,cores=@var{cores}][,threads=@var{threads}][,sockets=@var{sockets}][,maxcpus=@var{maxcpus}]
86@findex -smp
87Simulate an SMP system with @var{n} CPUs. On the PC target, up to 255
88CPUs are supported. On Sparc32 target, Linux limits the number of usable CPUs
89to 4.
90For the PC target, the number of @var{cores} per socket, the number
91of @var{threads} per cores and the total number of @var{sockets} can be
92specified. Missing values will be computed. If any on the three values is
93given, the total number of CPUs @var{n} can be omitted. @var{maxcpus}
94specifies the maximum number of hotpluggable CPUs.
95ETEXI
96
97DEF("numa", HAS_ARG, QEMU_OPTION_numa,
98    "-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]\n", QEMU_ARCH_ALL)
99STEXI
100@item -numa @var{opts}
101@findex -numa
102Simulate a multi node NUMA system. If mem and cpus are omitted, resources
103are split equally.
104ETEXI
105
106DEF("add-fd", HAS_ARG, QEMU_OPTION_add_fd,
107    "-add-fd fd=fd,set=set[,opaque=opaque]\n"
108    "                Add 'fd' to fd 'set'\n", QEMU_ARCH_ALL)
109STEXI
110@item -add-fd fd=@var{fd},set=@var{set}[,opaque=@var{opaque}]
111@findex -add-fd
112
113Add a file descriptor to an fd set.  Valid options are:
114
115@table @option
116@item fd=@var{fd}
117This option defines the file descriptor of which a duplicate is added to fd set.
118The file descriptor cannot be stdin, stdout, or stderr.
119@item set=@var{set}
120This option defines the ID of the fd set to add the file descriptor to.
121@item opaque=@var{opaque}
122This option defines a free-form string that can be used to describe @var{fd}.
123@end table
124
125You can open an image using pre-opened file descriptors from an fd set:
126@example
127qemu-system-i386
128-add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
129-add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
130-drive file=/dev/fdset/2,index=0,media=disk
131@end example
132ETEXI
133
134DEF("set", HAS_ARG, QEMU_OPTION_set,
135    "-set group.id.arg=value\n"
136    "                set <arg> parameter for item <id> of type <group>\n"
137    "                i.e. -set drive.$id.file=/path/to/image\n", QEMU_ARCH_ALL)
138STEXI
139@item -set @var{group}.@var{id}.@var{arg}=@var{value}
140@findex -set
141Set parameter @var{arg} for item @var{id} of type @var{group}\n"
142ETEXI
143
144DEF("global", HAS_ARG, QEMU_OPTION_global,
145    "-global driver.prop=value\n"
146    "                set a global default for a driver property\n",
147    QEMU_ARCH_ALL)
148STEXI
149@item -global @var{driver}.@var{prop}=@var{value}
150@findex -global
151Set default value of @var{driver}'s property @var{prop} to @var{value}, e.g.:
152
153@example
154qemu-system-i386 -global ide-drive.physical_block_size=4096 -drive file=file,if=ide,index=0,media=disk
155@end example
156
157In particular, you can use this to set driver properties for devices which are
158created automatically by the machine model. To create a device which is not
159created automatically and set properties on it, use -@option{device}.
160ETEXI
161
162DEF("boot", HAS_ARG, QEMU_OPTION_boot,
163    "-boot [order=drives][,once=drives][,menu=on|off]\n"
164    "      [,splash=sp_name][,splash-time=sp_time][,reboot-timeout=rb_time]\n"
165    "                'drives': floppy (a), hard disk (c), CD-ROM (d), network (n)\n"
166    "                'sp_name': the file's name that would be passed to bios as logo picture, if menu=on\n"
167    "                'sp_time': the period that splash picture last if menu=on, unit is ms\n"
168    "                'rb_timeout': the timeout before guest reboot when boot failed, unit is ms\n",
169    QEMU_ARCH_ALL)
170STEXI
171@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}]
172@findex -boot
173Specify boot order @var{drives} as a string of drive letters. Valid
174drive letters depend on the target achitecture. The x86 PC uses: a, b
175(floppy 1 and 2), c (first hard disk), d (first CD-ROM), n-p (Etherboot
176from network adapter 1-4), hard disk boot is the default. To apply a
177particular boot order only on the first startup, specify it via
178@option{once}.
179
180Interactive boot menus/prompts can be enabled via @option{menu=on} as far
181as firmware/BIOS supports them. The default is non-interactive boot.
182
183A splash picture could be passed to bios, enabling user to show it as logo,
184when option splash=@var{sp_name} is given and menu=on, If firmware/BIOS
185supports them. Currently Seabios for X86 system support it.
186limitation: The splash file could be a jpeg file or a BMP file in 24 BPP
187format(true color). The resolution should be supported by the SVGA mode, so
188the recommended is 320x240, 640x480, 800x640.
189
190A timeout could be passed to bios, guest will pause for @var{rb_timeout} ms
191when boot failed, then reboot. If @var{rb_timeout} is '-1', guest will not
192reboot, qemu passes '-1' to bios by default. Currently Seabios for X86
193system support it.
194
195@example
196# try to boot from network first, then from hard disk
197qemu-system-i386 -boot order=nc
198# boot from CD-ROM first, switch back to default order after reboot
199qemu-system-i386 -boot once=d
200# boot with a splash picture for 5 seconds.
201qemu-system-i386 -boot menu=on,splash=/root/boot.bmp,splash-time=5000
202@end example
203
204Note: The legacy format '-boot @var{drives}' is still supported but its
205use is discouraged as it may be removed from future versions.
206ETEXI
207
208DEF("m", HAS_ARG, QEMU_OPTION_m,
209    "-m megs         set virtual RAM size to megs MB [default="
210    stringify(DEFAULT_RAM_SIZE) "]\n", QEMU_ARCH_ALL)
211STEXI
212@item -m @var{megs}
213@findex -m
214Set virtual RAM size to @var{megs} megabytes. Default is 128 MiB.  Optionally,
215a suffix of ``M'' or ``G'' can be used to signify a value in megabytes or
216gigabytes respectively.
217ETEXI
218
219DEF("mem-path", HAS_ARG, QEMU_OPTION_mempath,
220    "-mem-path FILE  provide backing storage for guest RAM\n", QEMU_ARCH_ALL)
221STEXI
222@item -mem-path @var{path}
223@findex -mem-path
224Allocate guest RAM from a temporarily created file in @var{path}.
225ETEXI
226
227#ifdef MAP_POPULATE
228DEF("mem-prealloc", 0, QEMU_OPTION_mem_prealloc,
229    "-mem-prealloc   preallocate guest memory (use with -mem-path)\n",
230    QEMU_ARCH_ALL)
231STEXI
232@item -mem-prealloc
233@findex -mem-prealloc
234Preallocate memory when using -mem-path.
235ETEXI
236#endif
237
238DEF("k", HAS_ARG, QEMU_OPTION_k,
239    "-k language     use keyboard layout (for example 'fr' for French)\n",
240    QEMU_ARCH_ALL)
241STEXI
242@item -k @var{language}
243@findex -k
244Use keyboard layout @var{language} (for example @code{fr} for
245French). This option is only needed where it is not easy to get raw PC
246keycodes (e.g. on Macs, with some X11 servers or with a VNC
247display). You don't normally need to use it on PC/Linux or PC/Windows
248hosts.
249
250The available layouts are:
251@example
252ar  de-ch  es  fo     fr-ca  hu  ja  mk     no  pt-br  sv
253da  en-gb  et  fr     fr-ch  is  lt  nl     pl  ru     th
254de  en-us  fi  fr-be  hr     it  lv  nl-be  pt  sl     tr
255@end example
256
257The default is @code{en-us}.
258ETEXI
259
260
261DEF("audio-help", 0, QEMU_OPTION_audio_help,
262    "-audio-help     print list of audio drivers and their options\n",
263    QEMU_ARCH_ALL)
264STEXI
265@item -audio-help
266@findex -audio-help
267Will show the audio subsystem help: list of drivers, tunable
268parameters.
269ETEXI
270
271DEF("soundhw", HAS_ARG, QEMU_OPTION_soundhw,
272    "-soundhw c1,... enable audio support\n"
273    "                and only specified sound cards (comma separated list)\n"
274    "                use '-soundhw help' to get the list of supported cards\n"
275    "                use '-soundhw all' to enable all of them\n", QEMU_ARCH_ALL)
276STEXI
277@item -soundhw @var{card1}[,@var{card2},...] or -soundhw all
278@findex -soundhw
279Enable audio and selected sound hardware. Use 'help' to print all
280available sound hardware.
281
282@example
283qemu-system-i386 -soundhw sb16,adlib disk.img
284qemu-system-i386 -soundhw es1370 disk.img
285qemu-system-i386 -soundhw ac97 disk.img
286qemu-system-i386 -soundhw hda disk.img
287qemu-system-i386 -soundhw all disk.img
288qemu-system-i386 -soundhw help
289@end example
290
291Note that Linux's i810_audio OSS kernel (for AC97) module might
292require manually specifying clocking.
293
294@example
295modprobe i810_audio clocking=48000
296@end example
297ETEXI
298
299DEF("balloon", HAS_ARG, QEMU_OPTION_balloon,
300    "-balloon none   disable balloon device\n"
301    "-balloon virtio[,addr=str]\n"
302    "                enable virtio balloon device (default)\n", QEMU_ARCH_ALL)
303STEXI
304@item -balloon none
305@findex -balloon
306Disable balloon device.
307@item -balloon virtio[,addr=@var{addr}]
308Enable virtio balloon device (default), optionally with PCI address
309@var{addr}.
310ETEXI
311
312DEF("device", HAS_ARG, QEMU_OPTION_device,
313    "-device driver[,prop[=value][,...]]\n"
314    "                add device (based on driver)\n"
315    "                prop=value,... sets driver properties\n"
316    "                use '-device help' to print all possible drivers\n"
317    "                use '-device driver,help' to print all possible properties\n",
318    QEMU_ARCH_ALL)
319STEXI
320@item -device @var{driver}[,@var{prop}[=@var{value}][,...]]
321@findex -device
322Add device @var{driver}.  @var{prop}=@var{value} sets driver
323properties.  Valid properties depend on the driver.  To get help on
324possible drivers and properties, use @code{-device help} and
325@code{-device @var{driver},help}.
326ETEXI
327
328DEF("name", HAS_ARG, QEMU_OPTION_name,
329    "-name string1[,process=string2]\n"
330    "                set the name of the guest\n"
331    "                string1 sets the window title and string2 the process name (on Linux)\n",
332    QEMU_ARCH_ALL)
333STEXI
334@item -name @var{name}
335@findex -name
336Sets the @var{name} of the guest.
337This name will be displayed in the SDL window caption.
338The @var{name} will also be used for the VNC server.
339Also optionally set the top visible process name in Linux.
340ETEXI
341
342DEF("uuid", HAS_ARG, QEMU_OPTION_uuid,
343    "-uuid %08x-%04x-%04x-%04x-%012x\n"
344    "                specify machine UUID\n", QEMU_ARCH_ALL)
345STEXI
346@item -uuid @var{uuid}
347@findex -uuid
348Set system UUID.
349ETEXI
350
351STEXI
352@end table
353ETEXI
354DEFHEADING()
355
356DEFHEADING(Block device options:)
357STEXI
358@table @option
359ETEXI
360
361DEF("fda", HAS_ARG, QEMU_OPTION_fda,
362    "-fda/-fdb file  use 'file' as floppy disk 0/1 image\n", QEMU_ARCH_ALL)
363DEF("fdb", HAS_ARG, QEMU_OPTION_fdb, "", QEMU_ARCH_ALL)
364STEXI
365@item -fda @var{file}
366@item -fdb @var{file}
367@findex -fda
368@findex -fdb
369Use @var{file} as floppy disk 0/1 image (@pxref{disk_images}). You can
370use the host floppy by using @file{/dev/fd0} as filename (@pxref{host_drives}).
371ETEXI
372
373DEF("hda", HAS_ARG, QEMU_OPTION_hda,
374    "-hda/-hdb file  use 'file' as IDE hard disk 0/1 image\n", QEMU_ARCH_ALL)
375DEF("hdb", HAS_ARG, QEMU_OPTION_hdb, "", QEMU_ARCH_ALL)
376DEF("hdc", HAS_ARG, QEMU_OPTION_hdc,
377    "-hdc/-hdd file  use 'file' as IDE hard disk 2/3 image\n", QEMU_ARCH_ALL)
378DEF("hdd", HAS_ARG, QEMU_OPTION_hdd, "", QEMU_ARCH_ALL)
379STEXI
380@item -hda @var{file}
381@item -hdb @var{file}
382@item -hdc @var{file}
383@item -hdd @var{file}
384@findex -hda
385@findex -hdb
386@findex -hdc
387@findex -hdd
388Use @var{file} as hard disk 0, 1, 2 or 3 image (@pxref{disk_images}).
389ETEXI
390
391DEF("cdrom", HAS_ARG, QEMU_OPTION_cdrom,
392    "-cdrom file     use 'file' as IDE cdrom image (cdrom is ide1 master)\n",
393    QEMU_ARCH_ALL)
394STEXI
395@item -cdrom @var{file}
396@findex -cdrom
397Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and
398@option{-cdrom} at the same time). You can use the host CD-ROM by
399using @file{/dev/cdrom} as filename (@pxref{host_drives}).
400ETEXI
401
402DEF("drive", HAS_ARG, QEMU_OPTION_drive,
403    "-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]\n"
404    "       [,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]\n"
405    "       [,cache=writethrough|writeback|none|directsync|unsafe][,format=f]\n"
406    "       [,serial=s][,addr=A][,id=name][,aio=threads|native]\n"
407    "       [,readonly=on|off][,copy-on-read=on|off]\n"
408    "       [[,bps=b]|[[,bps_rd=r][,bps_wr=w]]][[,iops=i]|[[,iops_rd=r][,iops_wr=w]]\n"
409    "                use 'file' as a drive image\n", QEMU_ARCH_ALL)
410STEXI
411@item -drive @var{option}[,@var{option}[,@var{option}[,...]]]
412@findex -drive
413
414Define a new drive. Valid options are:
415
416@table @option
417@item file=@var{file}
418This option defines which disk image (@pxref{disk_images}) to use with
419this drive. If the filename contains comma, you must double it
420(for instance, "file=my,,file" to use file "my,file").
421
422Special files such as iSCSI devices can be specified using protocol
423specific URLs. See the section for "Device URL Syntax" for more information.
424@item if=@var{interface}
425This option defines on which type on interface the drive is connected.
426Available types are: ide, scsi, sd, mtd, floppy, pflash, virtio.
427@item bus=@var{bus},unit=@var{unit}
428These options define where is connected the drive by defining the bus number and
429the unit id.
430@item index=@var{index}
431This option defines where is connected the drive by using an index in the list
432of available connectors of a given interface type.
433@item media=@var{media}
434This option defines the type of the media: disk or cdrom.
435@item cyls=@var{c},heads=@var{h},secs=@var{s}[,trans=@var{t}]
436These options have the same definition as they have in @option{-hdachs}.
437@item snapshot=@var{snapshot}
438@var{snapshot} is "on" or "off" and allows to enable snapshot for given drive (see @option{-snapshot}).
439@item cache=@var{cache}
440@var{cache} is "none", "writeback", "unsafe", "directsync" or "writethrough" and controls how the host cache is used to access block data.
441@item aio=@var{aio}
442@var{aio} is "threads", or "native" and selects between pthread based disk I/O and native Linux AIO.
443@item discard=@var{discard}
444@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.
445@item format=@var{format}
446Specify which disk @var{format} will be used rather than detecting
447the format.  Can be used to specifiy format=raw to avoid interpreting
448an untrusted format header.
449@item serial=@var{serial}
450This option specifies the serial number to assign to the device.
451@item addr=@var{addr}
452Specify the controller's PCI address (if=virtio only).
453@item werror=@var{action},rerror=@var{action}
454Specify which @var{action} to take on write and read errors. Valid actions are:
455"ignore" (ignore the error and try to continue), "stop" (pause QEMU),
456"report" (report the error to the guest), "enospc" (pause QEMU only if the
457host disk is full; report the error to the guest otherwise).
458The default setting is @option{werror=enospc} and @option{rerror=report}.
459@item readonly
460Open drive @option{file} as read-only. Guest write attempts will fail.
461@item copy-on-read=@var{copy-on-read}
462@var{copy-on-read} is "on" or "off" and enables whether to copy read backing
463file sectors into the image file.
464@end table
465
466By default, the @option{cache=writeback} mode is used. It will report data
467writes as completed as soon as the data is present in the host page cache.
468This is safe as long as your guest OS makes sure to correctly flush disk caches
469where needed. If your guest OS does not handle volatile disk write caches
470correctly and your host crashes or loses power, then the guest may experience
471data corruption.
472
473For such guests, you should consider using @option{cache=writethrough}. This
474means that the host page cache will be used to read and write data, but write
475notification will be sent to the guest only after QEMU has made sure to flush
476each write to the disk. Be aware that this has a major impact on performance.
477
478The host page cache can be avoided entirely with @option{cache=none}.  This will
479attempt to do disk IO directly to the guest's memory.  QEMU may still perform
480an internal copy of the data. Note that this is considered a writeback mode and
481the guest OS must handle the disk write cache correctly in order to avoid data
482corruption on host crashes.
483
484The host page cache can be avoided while only sending write notifications to
485the guest when the data has been flushed to the disk using
486@option{cache=directsync}.
487
488In case you don't care about data integrity over host failures, use
489@option{cache=unsafe}. This option tells QEMU that it never needs to write any
490data to the disk but can instead keep things in cache. If anything goes wrong,
491like your host losing power, the disk storage getting disconnected accidentally,
492etc. your image will most probably be rendered unusable.   When using
493the @option{-snapshot} option, unsafe caching is always used.
494
495Copy-on-read avoids accessing the same backing file sectors repeatedly and is
496useful when the backing file is over a slow network.  By default copy-on-read
497is off.
498
499Instead of @option{-cdrom} you can use:
500@example
501qemu-system-i386 -drive file=file,index=2,media=cdrom
502@end example
503
504Instead of @option{-hda}, @option{-hdb}, @option{-hdc}, @option{-hdd}, you can
505use:
506@example
507qemu-system-i386 -drive file=file,index=0,media=disk
508qemu-system-i386 -drive file=file,index=1,media=disk
509qemu-system-i386 -drive file=file,index=2,media=disk
510qemu-system-i386 -drive file=file,index=3,media=disk
511@end example
512
513You can open an image using pre-opened file descriptors from an fd set:
514@example
515qemu-system-i386
516-add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
517-add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
518-drive file=/dev/fdset/2,index=0,media=disk
519@end example
520
521You can connect a CDROM to the slave of ide0:
522@example
523qemu-system-i386 -drive file=file,if=ide,index=1,media=cdrom
524@end example
525
526If you don't specify the "file=" argument, you define an empty drive:
527@example
528qemu-system-i386 -drive if=ide,index=1,media=cdrom
529@end example
530
531You can connect a SCSI disk with unit ID 6 on the bus #0:
532@example
533qemu-system-i386 -drive file=file,if=scsi,bus=0,unit=6
534@end example
535
536Instead of @option{-fda}, @option{-fdb}, you can use:
537@example
538qemu-system-i386 -drive file=file,index=0,if=floppy
539qemu-system-i386 -drive file=file,index=1,if=floppy
540@end example
541
542By default, @var{interface} is "ide" and @var{index} is automatically
543incremented:
544@example
545qemu-system-i386 -drive file=a -drive file=b"
546@end example
547is interpreted like:
548@example
549qemu-system-i386 -hda a -hdb b
550@end example
551ETEXI
552
553DEF("mtdblock", HAS_ARG, QEMU_OPTION_mtdblock,
554    "-mtdblock file  use 'file' as on-board Flash memory image\n",
555    QEMU_ARCH_ALL)
556STEXI
557@item -mtdblock @var{file}
558@findex -mtdblock
559Use @var{file} as on-board Flash memory image.
560ETEXI
561
562DEF("sd", HAS_ARG, QEMU_OPTION_sd,
563    "-sd file        use 'file' as SecureDigital card image\n", QEMU_ARCH_ALL)
564STEXI
565@item -sd @var{file}
566@findex -sd
567Use @var{file} as SecureDigital card image.
568ETEXI
569
570DEF("pflash", HAS_ARG, QEMU_OPTION_pflash,
571    "-pflash file    use 'file' as a parallel flash image\n", QEMU_ARCH_ALL)
572STEXI
573@item -pflash @var{file}
574@findex -pflash
575Use @var{file} as a parallel flash image.
576ETEXI
577
578DEF("snapshot", 0, QEMU_OPTION_snapshot,
579    "-snapshot       write to temporary files instead of disk image files\n",
580    QEMU_ARCH_ALL)
581STEXI
582@item -snapshot
583@findex -snapshot
584Write to temporary files instead of disk image files. In this case,
585the raw disk image you use is not written back. You can however force
586the write back by pressing @key{C-a s} (@pxref{disk_images}).
587ETEXI
588
589DEF("hdachs", HAS_ARG, QEMU_OPTION_hdachs, \
590    "-hdachs c,h,s[,t]\n" \
591    "                force hard disk 0 physical geometry and the optional BIOS\n" \
592    "                translation (t=none or lba) (usually QEMU can guess them)\n",
593    QEMU_ARCH_ALL)
594STEXI
595@item -hdachs @var{c},@var{h},@var{s},[,@var{t}]
596@findex -hdachs
597Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <=
598@var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS
599translation mode (@var{t}=none, lba or auto). Usually QEMU can guess
600all those parameters. This option is useful for old MS-DOS disk
601images.
602ETEXI
603
604DEF("fsdev", HAS_ARG, QEMU_OPTION_fsdev,
605    "-fsdev fsdriver,id=id[,path=path,][security_model={mapped-xattr|mapped-file|passthrough|none}]\n"
606    " [,writeout=immediate][,readonly][,socket=socket|sock_fd=sock_fd]\n",
607    QEMU_ARCH_ALL)
608
609STEXI
610
611@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}]
612@findex -fsdev
613Define a new file system device. Valid options are:
614@table @option
615@item @var{fsdriver}
616This option specifies the fs driver backend to use.
617Currently "local", "handle" and "proxy" file system drivers are supported.
618@item id=@var{id}
619Specifies identifier for this device
620@item path=@var{path}
621Specifies the export path for the file system device. Files under
622this path will be available to the 9p client on the guest.
623@item security_model=@var{security_model}
624Specifies the security model to be used for this export path.
625Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
626In "passthrough" security model, files are stored using the same
627credentials as they are created on the guest. This requires QEMU
628to run as root. In "mapped-xattr" security model, some of the file
629attributes like uid, gid, mode bits and link target are stored as
630file attributes. For "mapped-file" these attributes are stored in the
631hidden .virtfs_metadata directory. Directories exported by this security model cannot
632interact with other unix tools. "none" security model is same as
633passthrough except the sever won't report failures if it fails to
634set file attributes like ownership. Security model is mandatory
635only for local fsdriver. Other fsdrivers (like handle, proxy) don't take
636security model as a parameter.
637@item writeout=@var{writeout}
638This is an optional argument. The only supported value is "immediate".
639This means that host page cache will be used to read and write data but
640write notification will be sent to the guest only when the data has been
641reported as written by the storage subsystem.
642@item readonly
643Enables exporting 9p share as a readonly mount for guests. By default
644read-write access is given.
645@item socket=@var{socket}
646Enables proxy filesystem driver to use passed socket file for communicating
647with virtfs-proxy-helper
648@item sock_fd=@var{sock_fd}
649Enables proxy filesystem driver to use passed socket descriptor for
650communicating with virtfs-proxy-helper. Usually a helper like libvirt
651will create socketpair and pass one of the fds as sock_fd
652@end table
653
654-fsdev option is used along with -device driver "virtio-9p-pci".
655@item -device virtio-9p-pci,fsdev=@var{id},mount_tag=@var{mount_tag}
656Options for virtio-9p-pci driver are:
657@table @option
658@item fsdev=@var{id}
659Specifies the id value specified along with -fsdev option
660@item mount_tag=@var{mount_tag}
661Specifies the tag name to be used by the guest to mount this export point
662@end table
663
664ETEXI
665
666DEF("virtfs", HAS_ARG, QEMU_OPTION_virtfs,
667    "-virtfs local,path=path,mount_tag=tag,security_model=[mapped-xattr|mapped-file|passthrough|none]\n"
668    "        [,writeout=immediate][,readonly][,socket=socket|sock_fd=sock_fd]\n",
669    QEMU_ARCH_ALL)
670
671STEXI
672
673@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}]
674@findex -virtfs
675
676The general form of a Virtual File system pass-through options are:
677@table @option
678@item @var{fsdriver}
679This option specifies the fs driver backend to use.
680Currently "local", "handle" and "proxy" file system drivers are supported.
681@item id=@var{id}
682Specifies identifier for this device
683@item path=@var{path}
684Specifies the export path for the file system device. Files under
685this path will be available to the 9p client on the guest.
686@item security_model=@var{security_model}
687Specifies the security model to be used for this export path.
688Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none".
689In "passthrough" security model, files are stored using the same
690credentials as they are created on the guest. This requires QEMU
691to run as root. In "mapped-xattr" security model, some of the file
692attributes like uid, gid, mode bits and link target are stored as
693file attributes. For "mapped-file" these attributes are stored in the
694hidden .virtfs_metadata directory. Directories exported by this security model cannot
695interact with other unix tools. "none" security model is same as
696passthrough except the sever won't report failures if it fails to
697set file attributes like ownership. Security model is mandatory only
698for local fsdriver. Other fsdrivers (like handle, proxy) don't take security
699model as a parameter.
700@item writeout=@var{writeout}
701This is an optional argument. The only supported value is "immediate".
702This means that host page cache will be used to read and write data but
703write notification will be sent to the guest only when the data has been
704reported as written by the storage subsystem.
705@item readonly
706Enables exporting 9p share as a readonly mount for guests. By default
707read-write access is given.
708@item socket=@var{socket}
709Enables proxy filesystem driver to use passed socket file for
710communicating with virtfs-proxy-helper. Usually a helper like libvirt
711will create socketpair and pass one of the fds as sock_fd
712@item sock_fd
713Enables proxy filesystem driver to use passed 'sock_fd' as the socket
714descriptor for interfacing with virtfs-proxy-helper
715@end table
716ETEXI
717
718DEF("virtfs_synth", 0, QEMU_OPTION_virtfs_synth,
719    "-virtfs_synth Create synthetic file system image\n",
720    QEMU_ARCH_ALL)
721STEXI
722@item -virtfs_synth
723@findex -virtfs_synth
724Create synthetic file system image
725ETEXI
726
727STEXI
728@end table
729ETEXI
730DEFHEADING()
731
732DEFHEADING(USB options:)
733STEXI
734@table @option
735ETEXI
736
737DEF("usb", 0, QEMU_OPTION_usb,
738    "-usb            enable the USB driver (will be the default soon)\n",
739    QEMU_ARCH_ALL)
740STEXI
741@item -usb
742@findex -usb
743Enable the USB driver (will be the default soon)
744ETEXI
745
746DEF("usbdevice", HAS_ARG, QEMU_OPTION_usbdevice,
747    "-usbdevice name add the host or guest USB device 'name'\n",
748    QEMU_ARCH_ALL)
749STEXI
750
751@item -usbdevice @var{devname}
752@findex -usbdevice
753Add the USB device @var{devname}. @xref{usb_devices}.
754
755@table @option
756
757@item mouse
758Virtual Mouse. This will override the PS/2 mouse emulation when activated.
759
760@item tablet
761Pointer device that uses absolute coordinates (like a touchscreen). This
762means QEMU is able to report the mouse position without having to grab the
763mouse. Also overrides the PS/2 mouse emulation when activated.
764
765@item disk:[format=@var{format}]:@var{file}
766Mass storage device based on file. The optional @var{format} argument
767will be used rather than detecting the format. Can be used to specifiy
768@code{format=raw} to avoid interpreting an untrusted format header.
769
770@item host:@var{bus}.@var{addr}
771Pass through the host device identified by @var{bus}.@var{addr} (Linux only).
772
773@item host:@var{vendor_id}:@var{product_id}
774Pass through the host device identified by @var{vendor_id}:@var{product_id}
775(Linux only).
776
777@item serial:[vendorid=@var{vendor_id}][,productid=@var{product_id}]:@var{dev}
778Serial converter to host character device @var{dev}, see @code{-serial} for the
779available devices.
780
781@item braille
782Braille device.  This will use BrlAPI to display the braille output on a real
783or fake device.
784
785@item net:@var{options}
786Network adapter that supports CDC ethernet and RNDIS protocols.
787
788@end table
789ETEXI
790
791STEXI
792@end table
793ETEXI
794DEFHEADING()
795
796DEFHEADING(Display options:)
797STEXI
798@table @option
799ETEXI
800
801DEF("display", HAS_ARG, QEMU_OPTION_display,
802    "-display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]\n"
803    "            [,window_close=on|off]|curses|none|\n"
804    "            vnc=<display>[,<optargs>]\n"
805    "                select display type\n", QEMU_ARCH_ALL)
806STEXI
807@item -display @var{type}
808@findex -display
809Select type of display to use. This option is a replacement for the
810old style -sdl/-curses/... options. Valid values for @var{type} are
811@table @option
812@item sdl
813Display video output via SDL (usually in a separate graphics
814window; see the SDL documentation for other possibilities).
815@item curses
816Display video output via curses. For graphics device models which
817support a text mode, QEMU can display this output using a
818curses/ncurses interface. Nothing is displayed when the graphics
819device is in graphical mode or if the graphics device does not support
820a text mode. Generally only the VGA device models support text mode.
821@item none
822Do not display video output. The guest will still see an emulated
823graphics card, but its output will not be displayed to the QEMU
824user. This option differs from the -nographic option in that it
825only affects what is done with video output; -nographic also changes
826the destination of the serial and parallel port data.
827@item vnc
828Start a VNC server on display <arg>
829@end table
830ETEXI
831
832DEF("nographic", 0, QEMU_OPTION_nographic,
833    "-nographic      disable graphical output and redirect serial I/Os to console\n",
834    QEMU_ARCH_ALL)
835STEXI
836@item -nographic
837@findex -nographic
838Normally, QEMU uses SDL to display the VGA output. With this option,
839you can totally disable graphical output so that QEMU is a simple
840command line application. The emulated serial port is redirected on
841the console. Therefore, you can still use QEMU to debug a Linux kernel
842with a serial console.
843ETEXI
844
845DEF("curses", 0, QEMU_OPTION_curses,
846    "-curses         use a curses/ncurses interface instead of SDL\n",
847    QEMU_ARCH_ALL)
848STEXI
849@item -curses
850@findex -curses
851Normally, QEMU uses SDL to display the VGA output.  With this option,
852QEMU can display the VGA output when in text mode using a
853curses/ncurses interface.  Nothing is displayed in graphical mode.
854ETEXI
855
856DEF("no-frame", 0, QEMU_OPTION_no_frame,
857    "-no-frame       open SDL window without a frame and window decorations\n",
858    QEMU_ARCH_ALL)
859STEXI
860@item -no-frame
861@findex -no-frame
862Do not use decorations for SDL windows and start them using the whole
863available screen space. This makes the using QEMU in a dedicated desktop
864workspace more convenient.
865ETEXI
866
867DEF("alt-grab", 0, QEMU_OPTION_alt_grab,
868    "-alt-grab       use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)\n",
869    QEMU_ARCH_ALL)
870STEXI
871@item -alt-grab
872@findex -alt-grab
873Use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt). Note that this also
874affects the special keys (for fullscreen, monitor-mode switching, etc).
875ETEXI
876
877DEF("ctrl-grab", 0, QEMU_OPTION_ctrl_grab,
878    "-ctrl-grab      use Right-Ctrl to grab mouse (instead of Ctrl-Alt)\n",
879    QEMU_ARCH_ALL)
880STEXI
881@item -ctrl-grab
882@findex -ctrl-grab
883Use Right-Ctrl to grab mouse (instead of Ctrl-Alt). Note that this also
884affects the special keys (for fullscreen, monitor-mode switching, etc).
885ETEXI
886
887DEF("no-quit", 0, QEMU_OPTION_no_quit,
888    "-no-quit        disable SDL window close capability\n", QEMU_ARCH_ALL)
889STEXI
890@item -no-quit
891@findex -no-quit
892Disable SDL window close capability.
893ETEXI
894
895DEF("sdl", 0, QEMU_OPTION_sdl,
896    "-sdl            enable SDL\n", QEMU_ARCH_ALL)
897STEXI
898@item -sdl
899@findex -sdl
900Enable SDL.
901ETEXI
902
903DEF("spice", HAS_ARG, QEMU_OPTION_spice,
904    "-spice [port=port][,tls-port=secured-port][,x509-dir=<dir>]\n"
905    "       [,x509-key-file=<file>][,x509-key-password=<file>]\n"
906    "       [,x509-cert-file=<file>][,x509-cacert-file=<file>]\n"
907    "       [,x509-dh-key-file=<file>][,addr=addr][,ipv4|ipv6]\n"
908    "       [,tls-ciphers=<list>]\n"
909    "       [,tls-channel=[main|display|cursor|inputs|record|playback]]\n"
910    "       [,plaintext-channel=[main|display|cursor|inputs|record|playback]]\n"
911    "       [,sasl][,password=<secret>][,disable-ticketing]\n"
912    "       [,image-compression=[auto_glz|auto_lz|quic|glz|lz|off]]\n"
913    "       [,jpeg-wan-compression=[auto|never|always]]\n"
914    "       [,zlib-glz-wan-compression=[auto|never|always]]\n"
915    "       [,streaming-video=[off|all|filter]][,disable-copy-paste]\n"
916    "       [,agent-mouse=[on|off]][,playback-compression=[on|off]]\n"
917    "       [,seamless-migration=[on|off]]\n"
918    "   enable spice\n"
919    "   at least one of {port, tls-port} is mandatory\n",
920    QEMU_ARCH_ALL)
921STEXI
922@item -spice @var{option}[,@var{option}[,...]]
923@findex -spice
924Enable the spice remote desktop protocol. Valid options are
925
926@table @option
927
928@item port=<nr>
929Set the TCP port spice is listening on for plaintext channels.
930
931@item addr=<addr>
932Set the IP address spice is listening on.  Default is any address.
933
934@item ipv4
935@item ipv6
936Force using the specified IP version.
937
938@item password=<secret>
939Set the password you need to authenticate.
940
941@item sasl
942Require that the client use SASL to authenticate with the spice.
943The exact choice of authentication method used is controlled from the
944system / user's SASL configuration file for the 'qemu' service. This
945is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
946unprivileged user, an environment variable SASL_CONF_PATH can be used
947to make it search alternate locations for the service config.
948While some SASL auth methods can also provide data encryption (eg GSSAPI),
949it is recommended that SASL always be combined with the 'tls' and
950'x509' settings to enable use of SSL and server certificates. This
951ensures a data encryption preventing compromise of authentication
952credentials.
953
954@item disable-ticketing
955Allow client connects without authentication.
956
957@item disable-copy-paste
958Disable copy paste between the client and the guest.
959
960@item tls-port=<nr>
961Set the TCP port spice is listening on for encrypted channels.
962
963@item x509-dir=<dir>
964Set the x509 file directory. Expects same filenames as -vnc $display,x509=$dir
965
966@item x509-key-file=<file>
967@item x509-key-password=<file>
968@item x509-cert-file=<file>
969@item x509-cacert-file=<file>
970@item x509-dh-key-file=<file>
971The x509 file names can also be configured individually.
972
973@item tls-ciphers=<list>
974Specify which ciphers to use.
975
976@item tls-channel=[main|display|cursor|inputs|record|playback]
977@item plaintext-channel=[main|display|cursor|inputs|record|playback]
978Force specific channel to be used with or without TLS encryption.  The
979options can be specified multiple times to configure multiple
980channels.  The special name "default" can be used to set the default
981mode.  For channels which are not explicitly forced into one mode the
982spice client is allowed to pick tls/plaintext as he pleases.
983
984@item image-compression=[auto_glz|auto_lz|quic|glz|lz|off]
985Configure image compression (lossless).
986Default is auto_glz.
987
988@item jpeg-wan-compression=[auto|never|always]
989@item zlib-glz-wan-compression=[auto|never|always]
990Configure wan image compression (lossy for slow links).
991Default is auto.
992
993@item streaming-video=[off|all|filter]
994Configure video stream detection.  Default is filter.
995
996@item agent-mouse=[on|off]
997Enable/disable passing mouse events via vdagent.  Default is on.
998
999@item playback-compression=[on|off]
1000Enable/disable audio stream compression (using celt 0.5.1).  Default is on.
1001
1002@item seamless-migration=[on|off]
1003Enable/disable spice seamless migration. Default is off.
1004
1005@end table
1006ETEXI
1007
1008DEF("portrait", 0, QEMU_OPTION_portrait,
1009    "-portrait       rotate graphical output 90 deg left (only PXA LCD)\n",
1010    QEMU_ARCH_ALL)
1011STEXI
1012@item -portrait
1013@findex -portrait
1014Rotate graphical output 90 deg left (only PXA LCD).
1015ETEXI
1016
1017DEF("rotate", HAS_ARG, QEMU_OPTION_rotate,
1018    "-rotate <deg>   rotate graphical output some deg left (only PXA LCD)\n",
1019    QEMU_ARCH_ALL)
1020STEXI
1021@item -rotate @var{deg}
1022@findex -rotate
1023Rotate graphical output some deg left (only PXA LCD).
1024ETEXI
1025
1026DEF("vga", HAS_ARG, QEMU_OPTION_vga,
1027    "-vga [std|cirrus|vmware|qxl|xenfb|none]\n"
1028    "                select video card type\n", QEMU_ARCH_ALL)
1029STEXI
1030@item -vga @var{type}
1031@findex -vga
1032Select type of VGA card to emulate. Valid values for @var{type} are
1033@table @option
1034@item cirrus
1035Cirrus Logic GD5446 Video card. All Windows versions starting from
1036Windows 95 should recognize and use this graphic card. For optimal
1037performances, use 16 bit color depth in the guest and the host OS.
1038(This one is the default)
1039@item std
1040Standard VGA card with Bochs VBE extensions.  If your guest OS
1041supports the VESA 2.0 VBE extensions (e.g. Windows XP) and if you want
1042to use high resolution modes (>= 1280x1024x16) then you should use
1043this option.
1044@item vmware
1045VMWare SVGA-II compatible adapter. Use it if you have sufficiently
1046recent XFree86/XOrg server or Windows guest with a driver for this
1047card.
1048@item qxl
1049QXL paravirtual graphic card.  It is VGA compatible (including VESA
10502.0 VBE support).  Works best with qxl guest drivers installed though.
1051Recommended choice when using the spice protocol.
1052@item none
1053Disable VGA card.
1054@end table
1055ETEXI
1056
1057DEF("full-screen", 0, QEMU_OPTION_full_screen,
1058    "-full-screen    start in full screen\n", QEMU_ARCH_ALL)
1059STEXI
1060@item -full-screen
1061@findex -full-screen
1062Start in full screen.
1063ETEXI
1064
1065DEF("g", 1, QEMU_OPTION_g ,
1066    "-g WxH[xDEPTH]  Set the initial graphical resolution and depth\n",
1067    QEMU_ARCH_PPC | QEMU_ARCH_SPARC)
1068STEXI
1069@item -g @var{width}x@var{height}[x@var{depth}]
1070@findex -g
1071Set the initial graphical resolution and depth (PPC, SPARC only).
1072ETEXI
1073
1074DEF("vnc", HAS_ARG, QEMU_OPTION_vnc ,
1075    "-vnc display    start a VNC server on display\n", QEMU_ARCH_ALL)
1076STEXI
1077@item -vnc @var{display}[,@var{option}[,@var{option}[,...]]]
1078@findex -vnc
1079Normally, QEMU uses SDL to display the VGA output.  With this option,
1080you can have QEMU listen on VNC display @var{display} and redirect the VGA
1081display over the VNC session.  It is very useful to enable the usb
1082tablet device when using this option (option @option{-usbdevice
1083tablet}). When using the VNC display, you must use the @option{-k}
1084parameter to set the keyboard layout if you are not using en-us. Valid
1085syntax for the @var{display} is
1086
1087@table @option
1088
1089@item @var{host}:@var{d}
1090
1091TCP connections will only be allowed from @var{host} on display @var{d}.
1092By convention the TCP port is 5900+@var{d}. Optionally, @var{host} can
1093be omitted in which case the server will accept connections from any host.
1094
1095@item unix:@var{path}
1096
1097Connections will be allowed over UNIX domain sockets where @var{path} is the
1098location of a unix socket to listen for connections on.
1099
1100@item none
1101
1102VNC is initialized but not started. The monitor @code{change} command
1103can be used to later start the VNC server.
1104
1105@end table
1106
1107Following the @var{display} value there may be one or more @var{option} flags
1108separated by commas. Valid options are
1109
1110@table @option
1111
1112@item reverse
1113
1114Connect to a listening VNC client via a ``reverse'' connection. The
1115client is specified by the @var{display}. For reverse network
1116connections (@var{host}:@var{d},@code{reverse}), the @var{d} argument
1117is a TCP port number, not a display number.
1118
1119@item websocket
1120
1121Opens an additional TCP listening port dedicated to VNC Websocket connections.
1122By defintion the Websocket port is 5700+@var{display}. If @var{host} is
1123specified connections will only be allowed from this host.
1124As an alternative the Websocket port could be specified by using
1125@code{websocket}=@var{port}.
1126
1127@item password
1128
1129Require that password based authentication is used for client connections.
1130
1131The password must be set separately using the @code{set_password} command in
1132the @ref{pcsys_monitor}. The syntax to change your password is:
1133@code{set_password <protocol> <password>} where <protocol> could be either
1134"vnc" or "spice".
1135
1136If you would like to change <protocol> password expiration, you should use
1137@code{expire_password <protocol> <expiration-time>} where expiration time could
1138be one of the following options: now, never, +seconds or UNIX time of
1139expiration, e.g. +60 to make password expire in 60 seconds, or 1335196800
1140to make password expire on "Mon Apr 23 12:00:00 EDT 2012" (UNIX time for this
1141date and time).
1142
1143You can also use keywords "now" or "never" for the expiration time to
1144allow <protocol> password to expire immediately or never expire.
1145
1146@item tls
1147
1148Require that client use TLS when communicating with the VNC server. This
1149uses anonymous TLS credentials so is susceptible to a man-in-the-middle
1150attack. It is recommended that this option be combined with either the
1151@option{x509} or @option{x509verify} options.
1152
1153@item x509=@var{/path/to/certificate/dir}
1154
1155Valid if @option{tls} is specified. Require that x509 credentials are used
1156for negotiating the TLS session. The server will send its x509 certificate
1157to the client. It is recommended that a password be set on the VNC server
1158to provide authentication of the client when this is used. The path following
1159this option specifies where the x509 certificates are to be loaded from.
1160See the @ref{vnc_security} section for details on generating certificates.
1161
1162@item x509verify=@var{/path/to/certificate/dir}
1163
1164Valid if @option{tls} is specified. Require that x509 credentials are used
1165for negotiating the TLS session. The server will send its x509 certificate
1166to the client, and request that the client send its own x509 certificate.
1167The server will validate the client's certificate against the CA certificate,
1168and reject clients when validation fails. If the certificate authority is
1169trusted, this is a sufficient authentication mechanism. You may still wish
1170to set a password on the VNC server as a second authentication layer. The
1171path following this option specifies where the x509 certificates are to
1172be loaded from. See the @ref{vnc_security} section for details on generating
1173certificates.
1174
1175@item sasl
1176
1177Require that the client use SASL to authenticate with the VNC server.
1178The exact choice of authentication method used is controlled from the
1179system / user's SASL configuration file for the 'qemu' service. This
1180is typically found in /etc/sasl2/qemu.conf. If running QEMU as an
1181unprivileged user, an environment variable SASL_CONF_PATH can be used
1182to make it search alternate locations for the service config.
1183While some SASL auth methods can also provide data encryption (eg GSSAPI),
1184it is recommended that SASL always be combined with the 'tls' and
1185'x509' settings to enable use of SSL and server certificates. This
1186ensures a data encryption preventing compromise of authentication
1187credentials. See the @ref{vnc_security} section for details on using
1188SASL authentication.
1189
1190@item acl
1191
1192Turn on access control lists for checking of the x509 client certificate
1193and SASL party. For x509 certs, the ACL check is made against the
1194certificate's distinguished name. This is something that looks like
1195@code{C=GB,O=ACME,L=Boston,CN=bob}. For SASL party, the ACL check is
1196made against the username, which depending on the SASL plugin, may
1197include a realm component, eg @code{bob} or @code{bob@@EXAMPLE.COM}.
1198When the @option{acl} flag is set, the initial access list will be
1199empty, with a @code{deny} policy. Thus no one will be allowed to
1200use the VNC server until the ACLs have been loaded. This can be
1201achieved using the @code{acl} monitor command.
1202
1203@item lossy
1204
1205Enable lossy compression methods (gradient, JPEG, ...). If this
1206option is set, VNC client may receive lossy framebuffer updates
1207depending on its encoding settings. Enabling this option can save
1208a lot of bandwidth at the expense of quality.
1209
1210@item non-adaptive
1211
1212Disable adaptive encodings. Adaptive encodings are enabled by default.
1213An adaptive encoding will try to detect frequently updated screen regions,
1214and send updates in these regions using a lossy encoding (like JPEG).
1215This can be really helpful to save bandwidth when playing videos. Disabling
1216adaptive encodings allows to restore the original static behavior of encodings
1217like Tight.
1218
1219@item share=[allow-exclusive|force-shared|ignore]
1220
1221Set display sharing policy.  'allow-exclusive' allows clients to ask
1222for exclusive access.  As suggested by the rfb spec this is
1223implemented by dropping other connections.  Connecting multiple
1224clients in parallel requires all clients asking for a shared session
1225(vncviewer: -shared switch).  This is the default.  'force-shared'
1226disables exclusive client access.  Useful for shared desktop sessions,
1227where you don't want someone forgetting specify -shared disconnect
1228everybody else.  'ignore' completely ignores the shared flag and
1229allows everybody connect unconditionally.  Doesn't conform to the rfb
1230spec but is traditional QEMU behavior.
1231
1232@end table
1233ETEXI
1234
1235STEXI
1236@end table
1237ETEXI
1238ARCHHEADING(, QEMU_ARCH_I386)
1239
1240ARCHHEADING(i386 target only:, QEMU_ARCH_I386)
1241STEXI
1242@table @option
1243ETEXI
1244
1245DEF("win2k-hack", 0, QEMU_OPTION_win2k_hack,
1246    "-win2k-hack     use it when installing Windows 2000 to avoid a disk full bug\n",
1247    QEMU_ARCH_I386)
1248STEXI
1249@item -win2k-hack
1250@findex -win2k-hack
1251Use it when installing Windows 2000 to avoid a disk full bug. After
1252Windows 2000 is installed, you no longer need this option (this option
1253slows down the IDE transfers).
1254ETEXI
1255
1256HXCOMM Deprecated by -rtc
1257DEF("rtc-td-hack", 0, QEMU_OPTION_rtc_td_hack, "", QEMU_ARCH_I386)
1258
1259DEF("no-fd-bootchk", 0, QEMU_OPTION_no_fd_bootchk,
1260    "-no-fd-bootchk  disable boot signature checking for floppy disks\n",
1261    QEMU_ARCH_I386)
1262STEXI
1263@item -no-fd-bootchk
1264@findex -no-fd-bootchk
1265Disable boot signature checking for floppy disks in Bochs BIOS. It may
1266be needed to boot from old floppy disks.
1267TODO: check reference to Bochs BIOS.
1268ETEXI
1269
1270DEF("no-acpi", 0, QEMU_OPTION_no_acpi,
1271           "-no-acpi        disable ACPI\n", QEMU_ARCH_I386)
1272STEXI
1273@item -no-acpi
1274@findex -no-acpi
1275Disable ACPI (Advanced Configuration and Power Interface) support. Use
1276it if your guest OS complains about ACPI problems (PC target machine
1277only).
1278ETEXI
1279
1280DEF("no-hpet", 0, QEMU_OPTION_no_hpet,
1281    "-no-hpet        disable HPET\n", QEMU_ARCH_I386)
1282STEXI
1283@item -no-hpet
1284@findex -no-hpet
1285Disable HPET support.
1286ETEXI
1287
1288DEF("acpitable", HAS_ARG, QEMU_OPTION_acpitable,
1289    "-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"
1290    "                ACPI table description\n", QEMU_ARCH_I386)
1291STEXI
1292@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}]...]
1293@findex -acpitable
1294Add ACPI table with specified header fields and context from specified files.
1295For file=, take whole ACPI table from the specified files, including all
1296ACPI headers (possible overridden by other options).
1297For data=, only data
1298portion of the table is used, all header information is specified in the
1299command line.
1300ETEXI
1301
1302DEF("smbios", HAS_ARG, QEMU_OPTION_smbios,
1303    "-smbios file=binary\n"
1304    "                load SMBIOS entry from binary file\n"
1305    "-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]\n"
1306    "                specify SMBIOS type 0 fields\n"
1307    "-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]\n"
1308    "              [,uuid=uuid][,sku=str][,family=str]\n"
1309    "                specify SMBIOS type 1 fields\n", QEMU_ARCH_I386)
1310STEXI
1311@item -smbios file=@var{binary}
1312@findex -smbios
1313Load SMBIOS entry from binary file.
1314
1315@item -smbios type=0[,vendor=@var{str}][,version=@var{str}][,date=@var{str}][,release=@var{%d.%d}]
1316Specify SMBIOS type 0 fields
1317
1318@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}]
1319Specify SMBIOS type 1 fields
1320ETEXI
1321
1322STEXI
1323@end table
1324ETEXI
1325DEFHEADING()
1326
1327DEFHEADING(Network options:)
1328STEXI
1329@table @option
1330ETEXI
1331
1332HXCOMM Legacy slirp options (now moved to -net user):
1333#ifdef CONFIG_SLIRP
1334DEF("tftp", HAS_ARG, QEMU_OPTION_tftp, "", QEMU_ARCH_ALL)
1335DEF("bootp", HAS_ARG, QEMU_OPTION_bootp, "", QEMU_ARCH_ALL)
1336DEF("redir", HAS_ARG, QEMU_OPTION_redir, "", QEMU_ARCH_ALL)
1337#ifndef _WIN32
1338DEF("smb", HAS_ARG, QEMU_OPTION_smb, "", QEMU_ARCH_ALL)
1339#endif
1340#endif
1341
1342DEF("net", HAS_ARG, QEMU_OPTION_net,
1343    "-net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]\n"
1344    "                create a new Network Interface Card and connect it to VLAN 'n'\n"
1345#ifdef CONFIG_SLIRP
1346    "-net user[,vlan=n][,name=str][,net=addr[/mask]][,host=addr][,restrict=on|off]\n"
1347    "         [,hostname=host][,dhcpstart=addr][,dns=addr][,dnssearch=domain][,tftp=dir]\n"
1348    "         [,bootfile=f][,hostfwd=rule][,guestfwd=rule]"
1349#ifndef _WIN32
1350                                             "[,smb=dir[,smbserver=addr]]\n"
1351#endif
1352    "                connect the user mode network stack to VLAN 'n', configure its\n"
1353    "                DHCP server and enabled optional services\n"
1354#endif
1355#ifdef _WIN32
1356    "-net tap[,vlan=n][,name=str],ifname=name\n"
1357    "                connect the host TAP network interface to VLAN 'n'\n"
1358#else
1359    "-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]\n"
1360    "                connect the host TAP network interface to VLAN 'n'\n"
1361    "                use network scripts 'file' (default=" DEFAULT_NETWORK_SCRIPT ")\n"
1362    "                to configure it and 'dfile' (default=" DEFAULT_NETWORK_DOWN_SCRIPT ")\n"
1363    "                to deconfigure it\n"
1364    "                use '[down]script=no' to disable script execution\n"
1365    "                use network helper 'helper' (default=" DEFAULT_BRIDGE_HELPER ") to\n"
1366    "                configure it\n"
1367    "                use 'fd=h' to connect to an already opened TAP interface\n"
1368    "                use 'fds=x:y:...:z' to connect to already opened multiqueue capable TAP interfaces\n"
1369    "                use 'sndbuf=nbytes' to limit the size of the send buffer (the\n"
1370    "                default is disabled 'sndbuf=0' to enable flow control set 'sndbuf=1048576')\n"
1371    "                use vnet_hdr=off to avoid enabling the IFF_VNET_HDR tap flag\n"
1372    "                use vnet_hdr=on to make the lack of IFF_VNET_HDR support an error condition\n"
1373    "                use vhost=on to enable experimental in kernel accelerator\n"
1374    "                    (only has effect for virtio guests which use MSIX)\n"
1375    "                use vhostforce=on to force vhost on for non-MSIX virtio guests\n"
1376    "                use 'vhostfd=h' to connect to an already opened vhost net device\n"
1377    "                use 'vhostfds=x:y:...:z to connect to multiple already opened vhost net devices\n"
1378    "-net bridge[,vlan=n][,name=str][,br=bridge][,helper=helper]\n"
1379    "                connects a host TAP network interface to a host bridge device 'br'\n"
1380    "                (default=" DEFAULT_BRIDGE_INTERFACE ") using the program 'helper'\n"
1381    "                (default=" DEFAULT_BRIDGE_HELPER ")\n"
1382#endif
1383    "-net socket[,vlan=n][,name=str][,fd=h][,listen=[host]:port][,connect=host:port]\n"
1384    "                connect the vlan 'n' to another VLAN using a socket connection\n"
1385    "-net socket[,vlan=n][,name=str][,fd=h][,mcast=maddr:port[,localaddr=addr]]\n"
1386    "                connect the vlan 'n' to multicast maddr and port\n"
1387    "                use 'localaddr=addr' to specify the host address to send packets from\n"
1388    "-net socket[,vlan=n][,name=str][,fd=h][,udp=host:port][,localaddr=host:port]\n"
1389    "                connect the vlan 'n' to another VLAN using an UDP tunnel\n"
1390#ifdef CONFIG_VDE
1391    "-net vde[,vlan=n][,name=str][,sock=socketpath][,port=n][,group=groupname][,mode=octalmode]\n"
1392    "                connect the vlan 'n' to port 'n' of a vde switch running\n"
1393    "                on host and listening for incoming connections on 'socketpath'.\n"
1394    "                Use group 'groupname' and mode 'octalmode' to change default\n"
1395    "                ownership and permissions for communication port.\n"
1396#endif
1397    "-net dump[,vlan=n][,file=f][,len=n]\n"
1398    "                dump traffic on vlan 'n' to file 'f' (max n bytes per packet)\n"
1399    "-net none       use it alone to have zero network devices. If no -net option\n"
1400    "                is provided, the default is '-net nic -net user'\n", QEMU_ARCH_ALL)
1401DEF("netdev", HAS_ARG, QEMU_OPTION_netdev,
1402    "-netdev ["
1403#ifdef CONFIG_SLIRP
1404    "user|"
1405#endif
1406    "tap|"
1407    "bridge|"
1408#ifdef CONFIG_VDE
1409    "vde|"
1410#endif
1411    "socket],id=str[,option][,option][,...]\n", QEMU_ARCH_ALL)
1412STEXI
1413@item -net nic[,vlan=@var{n}][,macaddr=@var{mac}][,model=@var{type}] [,name=@var{name}][,addr=@var{addr}][,vectors=@var{v}]
1414@findex -net
1415Create a new Network Interface Card and connect it to VLAN @var{n} (@var{n}
1416= 0 is the default). The NIC is an e1000 by default on the PC
1417target. Optionally, the MAC address can be changed to @var{mac}, the
1418device address set to @var{addr} (PCI cards only),
1419and a @var{name} can be assigned for use in monitor commands.
1420Optionally, for PCI cards, you can specify the number @var{v} of MSI-X vectors
1421that the card should have; this option currently only affects virtio cards; set
1422@var{v} = 0 to disable MSI-X. If no @option{-net} option is specified, a single
1423NIC is created.  QEMU can emulate several different models of network card.
1424Valid values for @var{type} are
1425@code{virtio}, @code{i82551}, @code{i82557b}, @code{i82559er},
1426@code{ne2k_pci}, @code{ne2k_isa}, @code{pcnet}, @code{rtl8139},
1427@code{e1000}, @code{smc91c111}, @code{lance} and @code{mcf_fec}.
1428Not all devices are supported on all targets.  Use @code{-net nic,model=help}
1429for a list of available devices for your target.
1430
1431@item -netdev user,id=@var{id}[,@var{option}][,@var{option}][,...]
1432@findex -netdev
1433@item -net user[,@var{option}][,@var{option}][,...]
1434Use the user mode network stack which requires no administrator
1435privilege to run. Valid options are:
1436
1437@table @option
1438@item vlan=@var{n}
1439Connect user mode stack to VLAN @var{n} (@var{n} = 0 is the default).
1440
1441@item id=@var{id}
1442@item name=@var{name}
1443Assign symbolic name for use in monitor commands.
1444
1445@item net=@var{addr}[/@var{mask}]
1446Set IP network address the guest will see. Optionally specify the netmask,
1447either in the form a.b.c.d or as number of valid top-most bits. Default is
144810.0.2.0/24.
1449
1450@item host=@var{addr}
1451Specify the guest-visible address of the host. Default is the 2nd IP in the
1452guest network, i.e. x.x.x.2.
1453
1454@item restrict=on|off
1455If this option is enabled, the guest will be isolated, i.e. it will not be
1456able to contact the host and no guest IP packets will be routed over the host
1457to the outside. This option does not affect any explicitly set forwarding rules.
1458
1459@item hostname=@var{name}
1460Specifies the client hostname reported by the built-in DHCP server.
1461
1462@item dhcpstart=@var{addr}
1463Specify the first of the 16 IPs the built-in DHCP server can assign. Default
1464is the 15th to 31st IP in the guest network, i.e. x.x.x.15 to x.x.x.31.
1465
1466@item dns=@var{addr}
1467Specify the guest-visible address of the virtual nameserver. The address must
1468be different from the host address. Default is the 3rd IP in the guest network,
1469i.e. x.x.x.3.
1470
1471@item dnssearch=@var{domain}
1472Provides an entry for the domain-search list sent by the built-in
1473DHCP server. More than one domain suffix can be transmitted by specifying
1474this option multiple times. If supported, this will cause the guest to
1475automatically try to append the given domain suffix(es) in case a domain name
1476can not be resolved.
1477
1478Example:
1479@example
1480qemu -net user,dnssearch=mgmt.example.org,dnssearch=example.org [...]
1481@end example
1482
1483@item tftp=@var{dir}
1484When using the user mode network stack, activate a built-in TFTP
1485server. The files in @var{dir} will be exposed as the root of a TFTP server.
1486The TFTP client on the guest must be configured in binary mode (use the command
1487@code{bin} of the Unix TFTP client).
1488
1489@item bootfile=@var{file}
1490When using the user mode network stack, broadcast @var{file} as the BOOTP
1491filename. In conjunction with @option{tftp}, this can be used to network boot
1492a guest from a local directory.
1493
1494Example (using pxelinux):
1495@example
1496qemu-system-i386 -hda linux.img -boot n -net user,tftp=/path/to/tftp/files,bootfile=/pxelinux.0
1497@end example
1498
1499@item smb=@var{dir}[,smbserver=@var{addr}]
1500When using the user mode network stack, activate a built-in SMB
1501server so that Windows OSes can access to the host files in @file{@var{dir}}
1502transparently. The IP address of the SMB server can be set to @var{addr}. By
1503default the 4th IP in the guest network is used, i.e. x.x.x.4.
1504
1505In the guest Windows OS, the line:
1506@example
150710.0.2.4 smbserver
1508@end example
1509must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me)
1510or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000).
1511
1512Then @file{@var{dir}} can be accessed in @file{\\smbserver\qemu}.
1513
1514Note that a SAMBA server must be installed on the host OS.
1515QEMU was tested successfully with smbd versions from Red Hat 9,
1516Fedora Core 3 and OpenSUSE 11.x.
1517
1518@item hostfwd=[tcp|udp]:[@var{hostaddr}]:@var{hostport}-[@var{guestaddr}]:@var{guestport}
1519Redirect incoming TCP or UDP connections to the host port @var{hostport} to
1520the guest IP address @var{guestaddr} on guest port @var{guestport}. If
1521@var{guestaddr} is not specified, its value is x.x.x.15 (default first address
1522given by the built-in DHCP server). By specifying @var{hostaddr}, the rule can
1523be bound to a specific host interface. If no connection type is set, TCP is
1524used. This option can be given multiple times.
1525
1526For example, to redirect host X11 connection from screen 1 to guest
1527screen 0, use the following:
1528
1529@example
1530# on the host
1531qemu-system-i386 -net user,hostfwd=tcp:127.0.0.1:6001-:6000 [...]
1532# this host xterm should open in the guest X11 server
1533xterm -display :1
1534@end example
1535
1536To redirect telnet connections from host port 5555 to telnet port on
1537the guest, use the following:
1538
1539@example
1540# on the host
1541qemu-system-i386 -net user,hostfwd=tcp::5555-:23 [...]
1542telnet localhost 5555
1543@end example
1544
1545Then when you use on the host @code{telnet localhost 5555}, you
1546connect to the guest telnet server.
1547
1548@item guestfwd=[tcp]:@var{server}:@var{port}-@var{dev}
1549@item guestfwd=[tcp]:@var{server}:@var{port}-@var{cmd:command}
1550Forward guest TCP connections to the IP address @var{server} on port @var{port}
1551to the character device @var{dev} or to a program executed by @var{cmd:command}
1552which gets spawned for each connection. This option can be given multiple times.
1553
1554You can either use a chardev directly and have that one used throughout QEMU's
1555lifetime, like in the following example:
1556
1557@example
1558# open 10.10.1.1:4321 on bootup, connect 10.0.2.100:1234 to it whenever
1559# the guest accesses it
1560qemu -net user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321 [...]
1561@end example
1562
1563Or you can execute a command on every TCP connection established by the guest,
1564so that QEMU behaves similar to an inetd process for that virtual server:
1565
1566@example
1567# call "netcat 10.10.1.1 4321" on every TCP connection to 10.0.2.100:1234
1568# and connect the TCP stream to its stdin/stdout
1569qemu -net 'user,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321'
1570@end example
1571
1572@end table
1573
1574Note: Legacy stand-alone options -tftp, -bootp, -smb and -redir are still
1575processed and applied to -net user. Mixing them with the new configuration
1576syntax gives undefined results. Their use for new applications is discouraged
1577as they will be removed from future versions.
1578
1579@item -netdev tap,id=@var{id}[,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}]
1580@item -net tap[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}]
1581Connect the host TAP network interface @var{name} to VLAN @var{n}.
1582
1583Use the network script @var{file} to configure it and the network script
1584@var{dfile} to deconfigure it. If @var{name} is not provided, the OS
1585automatically provides one. The default network configure script is
1586@file{/etc/qemu-ifup} and the default network deconfigure script is
1587@file{/etc/qemu-ifdown}. Use @option{script=no} or @option{downscript=no}
1588to disable script execution.
1589
1590If running QEMU as an unprivileged user, use the network helper
1591@var{helper} to configure the TAP interface. The default network
1592helper executable is @file{/usr/local/libexec/qemu-bridge-helper}.
1593
1594@option{fd}=@var{h} can be used to specify the handle of an already
1595opened host TAP interface.
1596
1597Examples:
1598
1599@example
1600#launch a QEMU instance with the default network script
1601qemu-system-i386 linux.img -net nic -net tap
1602@end example
1603
1604@example
1605#launch a QEMU instance with two NICs, each one connected
1606#to a TAP device
1607qemu-system-i386 linux.img \
1608                 -net nic,vlan=0 -net tap,vlan=0,ifname=tap0 \
1609                 -net nic,vlan=1 -net tap,vlan=1,ifname=tap1
1610@end example
1611
1612@example
1613#launch a QEMU instance with the default network helper to
1614#connect a TAP device to bridge br0
1615qemu-system-i386 linux.img \
1616                 -net nic -net tap,"helper=/usr/local/libexec/qemu-bridge-helper"
1617@end example
1618
1619@item -netdev bridge,id=@var{id}[,br=@var{bridge}][,helper=@var{helper}]
1620@item -net bridge[,vlan=@var{n}][,name=@var{name}][,br=@var{bridge}][,helper=@var{helper}]
1621Connect a host TAP network interface to a host bridge device.
1622
1623Use the network helper @var{helper} to configure the TAP interface and
1624attach it to the bridge. The default network helper executable is
1625@file{/usr/local/libexec/qemu-bridge-helper} and the default bridge
1626device is @file{br0}.
1627
1628Examples:
1629
1630@example
1631#launch a QEMU instance with the default network helper to
1632#connect a TAP device to bridge br0
1633qemu-system-i386 linux.img -net bridge -net nic,model=virtio
1634@end example
1635
1636@example
1637#launch a QEMU instance with the default network helper to
1638#connect a TAP device to bridge qemubr0
1639qemu-system-i386 linux.img -net bridge,br=qemubr0 -net nic,model=virtio
1640@end example
1641
1642@item -netdev socket,id=@var{id}[,fd=@var{h}][,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}]
1643@item -net socket[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}] [,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}]
1644
1645Connect the VLAN @var{n} to a remote VLAN in another QEMU virtual
1646machine using a TCP socket connection. If @option{listen} is
1647specified, QEMU waits for incoming connections on @var{port}
1648(@var{host} is optional). @option{connect} is used to connect to
1649another QEMU instance using the @option{listen} option. @option{fd}=@var{h}
1650specifies an already opened TCP socket.
1651
1652Example:
1653@example
1654# launch a first QEMU instance
1655qemu-system-i386 linux.img \
1656                 -net nic,macaddr=52:54:00:12:34:56 \
1657                 -net socket,listen=:1234
1658# connect the VLAN 0 of this instance to the VLAN 0
1659# of the first instance
1660qemu-system-i386 linux.img \
1661                 -net nic,macaddr=52:54:00:12:34:57 \
1662                 -net socket,connect=127.0.0.1:1234
1663@end example
1664
1665@item -netdev socket,id=@var{id}[,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]]
1666@item -net socket[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]]
1667
1668Create a VLAN @var{n} shared with another QEMU virtual
1669machines using a UDP multicast socket, effectively making a bus for
1670every QEMU with same multicast address @var{maddr} and @var{port}.
1671NOTES:
1672@enumerate
1673@item
1674Several QEMU can be running on different hosts and share same bus (assuming
1675correct multicast setup for these hosts).
1676@item
1677mcast support is compatible with User Mode Linux (argument @option{eth@var{N}=mcast}), see
1678@url{http://user-mode-linux.sf.net}.
1679@item
1680Use @option{fd=h} to specify an already opened UDP multicast socket.
1681@end enumerate
1682
1683Example:
1684@example
1685# launch one QEMU instance
1686qemu-system-i386 linux.img \
1687                 -net nic,macaddr=52:54:00:12:34:56 \
1688                 -net socket,mcast=230.0.0.1:1234
1689# launch another QEMU instance on same "bus"
1690qemu-system-i386 linux.img \
1691                 -net nic,macaddr=52:54:00:12:34:57 \
1692                 -net socket,mcast=230.0.0.1:1234
1693# launch yet another QEMU instance on same "bus"
1694qemu-system-i386 linux.img \
1695                 -net nic,macaddr=52:54:00:12:34:58 \
1696                 -net socket,mcast=230.0.0.1:1234
1697@end example
1698
1699Example (User Mode Linux compat.):
1700@example
1701# launch QEMU instance (note mcast address selected
1702# is UML's default)
1703qemu-system-i386 linux.img \
1704                 -net nic,macaddr=52:54:00:12:34:56 \
1705                 -net socket,mcast=239.192.168.1:1102
1706# launch UML
1707/path/to/linux ubd0=/path/to/root_fs eth0=mcast
1708@end example
1709
1710Example (send packets from host's 1.2.3.4):
1711@example
1712qemu-system-i386 linux.img \
1713                 -net nic,macaddr=52:54:00:12:34:56 \
1714                 -net socket,mcast=239.192.168.1:1102,localaddr=1.2.3.4
1715@end example
1716
1717@item -netdev vde,id=@var{id}[,sock=@var{socketpath}][,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}]
1718@item -net vde[,vlan=@var{n}][,name=@var{name}][,sock=@var{socketpath}] [,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}]
1719Connect VLAN @var{n} to PORT @var{n} of a vde switch running on host and
1720listening for incoming connections on @var{socketpath}. Use GROUP @var{groupname}
1721and MODE @var{octalmode} to change default ownership and permissions for
1722communication port. This option is only available if QEMU has been compiled
1723with vde support enabled.
1724
1725Example:
1726@example
1727# launch vde switch
1728vde_switch -F -sock /tmp/myswitch
1729# launch QEMU instance
1730qemu-system-i386 linux.img -net nic -net vde,sock=/tmp/myswitch
1731@end example
1732
1733@item -net dump[,vlan=@var{n}][,file=@var{file}][,len=@var{len}]
1734Dump network traffic on VLAN @var{n} to file @var{file} (@file{qemu-vlan0.pcap} by default).
1735At most @var{len} bytes (64k by default) per packet are stored. The file format is
1736libpcap, so it can be analyzed with tools such as tcpdump or Wireshark.
1737
1738@item -net none
1739Indicate that no network devices should be configured. It is used to
1740override the default configuration (@option{-net nic -net user}) which
1741is activated if no @option{-net} options are provided.
1742ETEXI
1743
1744STEXI
1745@end table
1746ETEXI
1747DEFHEADING()
1748
1749DEFHEADING(Character device options:)
1750STEXI
1751
1752The general form of a character device option is:
1753@table @option
1754ETEXI
1755
1756DEF("chardev", HAS_ARG, QEMU_OPTION_chardev,
1757    "-chardev null,id=id[,mux=on|off]\n"
1758    "-chardev socket,id=id[,host=host],port=host[,to=to][,ipv4][,ipv6][,nodelay]\n"
1759    "         [,server][,nowait][,telnet][,mux=on|off] (tcp)\n"
1760    "-chardev socket,id=id,path=path[,server][,nowait][,telnet],[mux=on|off] (unix)\n"
1761    "-chardev udp,id=id[,host=host],port=port[,localaddr=localaddr]\n"
1762    "         [,localport=localport][,ipv4][,ipv6][,mux=on|off]\n"
1763    "-chardev msmouse,id=id[,mux=on|off]\n"
1764    "-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]\n"
1765    "         [,mux=on|off]\n"
1766    "-chardev ringbuf,id=id[,size=size]\n"
1767    "-chardev file,id=id,path=path[,mux=on|off]\n"
1768    "-chardev pipe,id=id,path=path[,mux=on|off]\n"
1769#ifdef _WIN32
1770    "-chardev console,id=id[,mux=on|off]\n"
1771    "-chardev serial,id=id,path=path[,mux=on|off]\n"
1772#else
1773    "-chardev pty,id=id[,mux=on|off]\n"
1774    "-chardev stdio,id=id[,mux=on|off][,signal=on|off]\n"
1775#endif
1776#ifdef CONFIG_BRLAPI
1777    "-chardev braille,id=id[,mux=on|off]\n"
1778#endif
1779#if defined(__linux__) || defined(__sun__) || defined(__FreeBSD__) \
1780        || defined(__NetBSD__) || defined(__OpenBSD__) || defined(__DragonFly__)
1781    "-chardev serial,id=id,path=path[,mux=on|off]\n"
1782    "-chardev tty,id=id,path=path[,mux=on|off]\n"
1783#endif
1784#if defined(__linux__) || defined(__FreeBSD__) || defined(__DragonFly__)
1785    "-chardev parallel,id=id,path=path[,mux=on|off]\n"
1786    "-chardev parport,id=id,path=path[,mux=on|off]\n"
1787#endif
1788#if defined(CONFIG_SPICE)
1789    "-chardev spicevmc,id=id,name=name[,debug=debug]\n"
1790    "-chardev spiceport,id=id,name=name[,debug=debug]\n"
1791#endif
1792    , QEMU_ARCH_ALL
1793)
1794
1795STEXI
1796@item -chardev @var{backend} ,id=@var{id} [,mux=on|off] [,@var{options}]
1797@findex -chardev
1798Backend is one of:
1799@option{null},
1800@option{socket},
1801@option{udp},
1802@option{msmouse},
1803@option{vc},
1804@option{ringbuf},
1805@option{file},
1806@option{pipe},
1807@option{console},
1808@option{serial},
1809@option{pty},
1810@option{stdio},
1811@option{braille},
1812@option{tty},
1813@option{parallel},
1814@option{parport},
1815@option{spicevmc}.
1816@option{spiceport}.
1817The specific backend will determine the applicable options.
1818
1819All devices must have an id, which can be any string up to 127 characters long.
1820It is used to uniquely identify this device in other command line directives.
1821
1822A character device may be used in multiplexing mode by multiple front-ends.
1823The key sequence of @key{Control-a} and @key{c} will rotate the input focus
1824between attached front-ends. Specify @option{mux=on} to enable this mode.
1825
1826Options to each backend are described below.
1827
1828@item -chardev null ,id=@var{id}
1829A void device. This device will not emit any data, and will drop any data it
1830receives. The null backend does not take any options.
1831
1832@item -chardev socket ,id=@var{id} [@var{TCP options} or @var{unix options}] [,server] [,nowait] [,telnet]
1833
1834Create a two-way stream socket, which can be either a TCP or a unix socket. A
1835unix socket will be created if @option{path} is specified. Behaviour is
1836undefined if TCP options are specified for a unix socket.
1837
1838@option{server} specifies that the socket shall be a listening socket.
1839
1840@option{nowait} specifies that QEMU should not block waiting for a client to
1841connect to a listening socket.
1842
1843@option{telnet} specifies that traffic on the socket should interpret telnet
1844escape sequences.
1845
1846TCP and unix socket options are given below:
1847
1848@table @option
1849
1850@item TCP options: port=@var{port} [,host=@var{host}] [,to=@var{to}] [,ipv4] [,ipv6] [,nodelay]
1851
1852@option{host} for a listening socket specifies the local address to be bound.
1853For a connecting socket species the remote host to connect to. @option{host} is
1854optional for listening sockets. If not specified it defaults to @code{0.0.0.0}.
1855
1856@option{port} for a listening socket specifies the local port to be bound. For a
1857connecting socket specifies the port on the remote host to connect to.
1858@option{port} can be given as either a port number or a service name.
1859@option{port} is required.
1860
1861@option{to} is only relevant to listening sockets. If it is specified, and
1862@option{port} cannot be bound, QEMU will attempt to bind to subsequent ports up
1863to and including @option{to} until it succeeds. @option{to} must be specified
1864as a port number.
1865
1866@option{ipv4} and @option{ipv6} specify that either IPv4 or IPv6 must be used.
1867If neither is specified the socket may use either protocol.
1868
1869@option{nodelay} disables the Nagle algorithm.
1870
1871@item unix options: path=@var{path}
1872
1873@option{path} specifies the local path of the unix socket. @option{path} is
1874required.
1875
1876@end table
1877
1878@item -chardev udp ,id=@var{id} [,host=@var{host}] ,port=@var{port} [,localaddr=@var{localaddr}] [,localport=@var{localport}] [,ipv4] [,ipv6]
1879
1880Sends all traffic from the guest to a remote host over UDP.
1881
1882@option{host} specifies the remote host to connect to. If not specified it
1883defaults to @code{localhost}.
1884
1885@option{port} specifies the port on the remote host to connect to. @option{port}
1886is required.
1887
1888@option{localaddr} specifies the local address to bind to. If not specified it
1889defaults to @code{0.0.0.0}.
1890
1891@option{localport} specifies the local port to bind to. If not specified any
1892available local port will be used.
1893
1894@option{ipv4} and @option{ipv6} specify that either IPv4 or IPv6 must be used.
1895If neither is specified the device may use either protocol.
1896
1897@item -chardev msmouse ,id=@var{id}
1898
1899Forward QEMU's emulated msmouse events to the guest. @option{msmouse} does not
1900take any options.
1901
1902@item -chardev vc ,id=@var{id} [[,width=@var{width}] [,height=@var{height}]] [[,cols=@var{cols}] [,rows=@var{rows}]]
1903
1904Connect to a QEMU text console. @option{vc} may optionally be given a specific
1905size.
1906
1907@option{width} and @option{height} specify the width and height respectively of
1908the console, in pixels.
1909
1910@option{cols} and @option{rows} specify that the console be sized to fit a text
1911console with the given dimensions.
1912
1913@item -chardev ringbuf ,id=@var{id} [,size=@var{size}]
1914
1915Create a ring buffer with fixed size @option{size}.
1916@var{size} must be a power of two, and defaults to @code{64K}).
1917
1918@item -chardev file ,id=@var{id} ,path=@var{path}
1919
1920Log all traffic received from the guest to a file.
1921
1922@option{path} specifies the path of the file to be opened. This file will be
1923created if it does not already exist, and overwritten if it does. @option{path}
1924is required.
1925
1926@item -chardev pipe ,id=@var{id} ,path=@var{path}
1927
1928Create a two-way connection to the guest. The behaviour differs slightly between
1929Windows hosts and other hosts:
1930
1931On Windows, a single duplex pipe will be created at
1932@file{\\.pipe\@option{path}}.
1933
1934On other hosts, 2 pipes will be created called @file{@option{path}.in} and
1935@file{@option{path}.out}. Data written to @file{@option{path}.in} will be
1936received by the guest. Data written by the guest can be read from
1937@file{@option{path}.out}. QEMU will not create these fifos, and requires them to
1938be present.
1939
1940@option{path} forms part of the pipe path as described above. @option{path} is
1941required.
1942
1943@item -chardev console ,id=@var{id}
1944
1945Send traffic from the guest to QEMU's standard output. @option{console} does not
1946take any options.
1947
1948@option{console} is only available on Windows hosts.
1949
1950@item -chardev serial ,id=@var{id} ,path=@option{path}
1951
1952Send traffic from the guest to a serial device on the host.
1953
1954On Unix hosts serial will actually accept any tty device,
1955not only serial lines.
1956
1957@option{path} specifies the name of the serial device to open.
1958
1959@item -chardev pty ,id=@var{id}
1960
1961Create a new pseudo-terminal on the host and connect to it. @option{pty} does
1962not take any options.
1963
1964@option{pty} is not available on Windows hosts.
1965
1966@item -chardev stdio ,id=@var{id} [,signal=on|off]
1967Connect to standard input and standard output of the QEMU process.
1968
1969@option{signal} controls if signals are enabled on the terminal, that includes
1970exiting QEMU with the key sequence @key{Control-c}. This option is enabled by
1971default, use @option{signal=off} to disable it.
1972
1973@option{stdio} is not available on Windows hosts.
1974
1975@item -chardev braille ,id=@var{id}
1976
1977Connect to a local BrlAPI server. @option{braille} does not take any options.
1978
1979@item -chardev tty ,id=@var{id} ,path=@var{path}
1980
1981@option{tty} is only available on Linux, Sun, FreeBSD, NetBSD, OpenBSD and
1982DragonFlyBSD hosts.  It is an alias for @option{serial}.
1983
1984@option{path} specifies the path to the tty. @option{path} is required.
1985
1986@item -chardev parallel ,id=@var{id} ,path=@var{path}
1987@item -chardev parport ,id=@var{id} ,path=@var{path}
1988
1989@option{parallel} is only available on Linux, FreeBSD and DragonFlyBSD hosts.
1990
1991Connect to a local parallel port.
1992
1993@option{path} specifies the path to the parallel port device. @option{path} is
1994required.
1995
1996@item -chardev spicevmc ,id=@var{id} ,debug=@var{debug}, name=@var{name}
1997
1998@option{spicevmc} is only available when spice support is built in.
1999
2000@option{debug} debug level for spicevmc
2001
2002@option{name} name of spice channel to connect to
2003
2004Connect to a spice virtual machine channel, such as vdiport.
2005
2006@item -chardev spiceport ,id=@var{id} ,debug=@var{debug}, name=@var{name}
2007
2008@option{spiceport} is only available when spice support is built in.
2009
2010@option{debug} debug level for spicevmc
2011
2012@option{name} name of spice port to connect to
2013
2014Connect to a spice port, allowing a Spice client to handle the traffic
2015identified by a name (preferably a fqdn).
2016ETEXI
2017
2018STEXI
2019@end table
2020ETEXI
2021DEFHEADING()
2022
2023DEFHEADING(Device URL Syntax:)
2024STEXI
2025
2026In addition to using normal file images for the emulated storage devices,
2027QEMU can also use networked resources such as iSCSI devices. These are
2028specified using a special URL syntax.
2029
2030@table @option
2031@item iSCSI
2032iSCSI support allows QEMU to access iSCSI resources directly and use as
2033images for the guest storage. Both disk and cdrom images are supported.
2034
2035Syntax for specifying iSCSI LUNs is
2036``iscsi://<target-ip>[:<port>]/<target-iqn>/<lun>''
2037
2038By default qemu will use the iSCSI initiator-name
2039'iqn.2008-11.org.linux-kvm[:<name>]' but this can also be set from the command
2040line or a configuration file.
2041
2042
2043Example (without authentication):
2044@example
2045qemu-system-i386 -iscsi initiator-name=iqn.2001-04.com.example:my-initiator \
2046                 -cdrom iscsi://192.0.2.1/iqn.2001-04.com.example/2 \
2047                 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
2048@end example
2049
2050Example (CHAP username/password via URL):
2051@example
2052qemu-system-i386 -drive file=iscsi://user%password@@192.0.2.1/iqn.2001-04.com.example/1
2053@end example
2054
2055Example (CHAP username/password via environment variables):
2056@example
2057LIBISCSI_CHAP_USERNAME="user" \
2058LIBISCSI_CHAP_PASSWORD="password" \
2059qemu-system-i386 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
2060@end example
2061
2062iSCSI support is an optional feature of QEMU and only available when
2063compiled and linked against libiscsi.
2064ETEXI
2065DEF("iscsi", HAS_ARG, QEMU_OPTION_iscsi,
2066    "-iscsi [user=user][,password=password]\n"
2067    "       [,header-digest=CRC32C|CR32C-NONE|NONE-CRC32C|NONE\n"
2068    "       [,initiator-name=iqn]\n"
2069    "                iSCSI session parameters\n", QEMU_ARCH_ALL)
2070STEXI
2071
2072iSCSI parameters such as username and password can also be specified via
2073a configuration file. See qemu-doc for more information and examples.
2074
2075@item NBD
2076QEMU supports NBD (Network Block Devices) both using TCP protocol as well
2077as Unix Domain Sockets.
2078
2079Syntax for specifying a NBD device using TCP
2080``nbd:<server-ip>:<port>[:exportname=<export>]''
2081
2082Syntax for specifying a NBD device using Unix Domain Sockets
2083``nbd:unix:<domain-socket>[:exportname=<export>]''
2084
2085
2086Example for TCP
2087@example
2088qemu-system-i386 --drive file=nbd:192.0.2.1:30000
2089@end example
2090
2091Example for Unix Domain Sockets
2092@example
2093qemu-system-i386 --drive file=nbd:unix:/tmp/nbd-socket
2094@end example
2095
2096@item Sheepdog
2097Sheepdog is a distributed storage system for QEMU.
2098QEMU supports using either local sheepdog devices or remote networked
2099devices.
2100
2101Syntax for specifying a sheepdog device
2102@table @list
2103``sheepdog:<vdiname>''
2104
2105``sheepdog:<vdiname>:<snapid>''
2106
2107``sheepdog:<vdiname>:<tag>''
2108
2109``sheepdog:<host>:<port>:<vdiname>''
2110
2111``sheepdog:<host>:<port>:<vdiname>:<snapid>''
2112
2113``sheepdog:<host>:<port>:<vdiname>:<tag>''
2114@end table
2115
2116Example
2117@example
2118qemu-system-i386 --drive file=sheepdog:192.0.2.1:30000:MyVirtualMachine
2119@end example
2120
2121See also @url{http://http://www.osrg.net/sheepdog/}.
2122
2123@item GlusterFS
2124GlusterFS is an user space distributed file system.
2125QEMU supports the use of GlusterFS volumes for hosting VM disk images using
2126TCP, Unix Domain Sockets and RDMA transport protocols.
2127
2128Syntax for specifying a VM disk image on GlusterFS volume is
2129@example
2130gluster[+transport]://[server[:port]]/volname/image[?socket=...]
2131@end example
2132
2133
2134Example
2135@example
2136qemu-system-x86_84 --drive file=gluster://192.0.2.1/testvol/a.img
2137@end example
2138
2139See also @url{http://www.gluster.org}.
2140ETEXI
2141
2142STEXI
2143@end table
2144ETEXI
2145
2146DEFHEADING(Bluetooth(R) options:)
2147STEXI
2148@table @option
2149ETEXI
2150
2151DEF("bt", HAS_ARG, QEMU_OPTION_bt, \
2152    "-bt hci,null    dumb bluetooth HCI - doesn't respond to commands\n" \
2153    "-bt hci,host[:id]\n" \
2154    "                use host's HCI with the given name\n" \
2155    "-bt hci[,vlan=n]\n" \
2156    "                emulate a standard HCI in virtual scatternet 'n'\n" \
2157    "-bt vhci[,vlan=n]\n" \
2158    "                add host computer to virtual scatternet 'n' using VHCI\n" \
2159    "-bt device:dev[,vlan=n]\n" \
2160    "                emulate a bluetooth device 'dev' in scatternet 'n'\n",
2161    QEMU_ARCH_ALL)
2162STEXI
2163@item -bt hci[...]
2164@findex -bt
2165Defines the function of the corresponding Bluetooth HCI.  -bt options
2166are matched with the HCIs present in the chosen machine type.  For
2167example when emulating a machine with only one HCI built into it, only
2168the first @code{-bt hci[...]} option is valid and defines the HCI's
2169logic.  The Transport Layer is decided by the machine type.  Currently
2170the machines @code{n800} and @code{n810} have one HCI and all other
2171machines have none.
2172
2173@anchor{bt-hcis}
2174The following three types are recognized:
2175
2176@table @option
2177@item -bt hci,null
2178(default) The corresponding Bluetooth HCI assumes no internal logic
2179and will not respond to any HCI commands or emit events.
2180
2181@item -bt hci,host[:@var{id}]
2182(@code{bluez} only) The corresponding HCI passes commands / events
2183to / from the physical HCI identified by the name @var{id} (default:
2184@code{hci0}) on the computer running QEMU.  Only available on @code{bluez}
2185capable systems like Linux.
2186
2187@item -bt hci[,vlan=@var{n}]
2188Add a virtual, standard HCI that will participate in the Bluetooth
2189scatternet @var{n} (default @code{0}).  Similarly to @option{-net}
2190VLANs, devices inside a bluetooth network @var{n} can only communicate
2191with other devices in the same network (scatternet).
2192@end table
2193
2194@item -bt vhci[,vlan=@var{n}]
2195(Linux-host only) Create a HCI in scatternet @var{n} (default 0) attached
2196to the host bluetooth stack instead of to the emulated target.  This
2197allows the host and target machines to participate in a common scatternet
2198and communicate.  Requires the Linux @code{vhci} driver installed.  Can
2199be used as following:
2200
2201@example
2202qemu-system-i386 [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5
2203@end example
2204
2205@item -bt device:@var{dev}[,vlan=@var{n}]
2206Emulate a bluetooth device @var{dev} and place it in network @var{n}
2207(default @code{0}).  QEMU can only emulate one type of bluetooth devices
2208currently:
2209
2210@table @option
2211@item keyboard
2212Virtual wireless keyboard implementing the HIDP bluetooth profile.
2213@end table
2214ETEXI
2215
2216STEXI
2217@end table
2218ETEXI
2219DEFHEADING()
2220
2221DEFHEADING(Linux/Multiboot boot specific:)
2222STEXI
2223
2224When using these options, you can use a given Linux or Multiboot
2225kernel without installing it in the disk image. It can be useful
2226for easier testing of various kernels.
2227
2228@table @option
2229ETEXI
2230
2231DEF("kernel", HAS_ARG, QEMU_OPTION_kernel, \
2232    "-kernel bzImage use 'bzImage' as kernel image\n", QEMU_ARCH_ALL)
2233STEXI
2234@item -kernel @var{bzImage}
2235@findex -kernel
2236Use @var{bzImage} as kernel image. The kernel can be either a Linux kernel
2237or in multiboot format.
2238ETEXI
2239
2240DEF("append", HAS_ARG, QEMU_OPTION_append, \
2241    "-append cmdline use 'cmdline' as kernel command line\n", QEMU_ARCH_ALL)
2242STEXI
2243@item -append @var{cmdline}
2244@findex -append
2245Use @var{cmdline} as kernel command line
2246ETEXI
2247
2248DEF("initrd", HAS_ARG, QEMU_OPTION_initrd, \
2249           "-initrd file    use 'file' as initial ram disk\n", QEMU_ARCH_ALL)
2250STEXI
2251@item -initrd @var{file}
2252@findex -initrd
2253Use @var{file} as initial ram disk.
2254
2255@item -initrd "@var{file1} arg=foo,@var{file2}"
2256
2257This syntax is only available with multiboot.
2258
2259Use @var{file1} and @var{file2} as modules and pass arg=foo as parameter to the
2260first module.
2261ETEXI
2262
2263DEF("dtb", HAS_ARG, QEMU_OPTION_dtb, \
2264    "-dtb    file    use 'file' as device tree image\n", QEMU_ARCH_ALL)
2265STEXI
2266@item -dtb @var{file}
2267@findex -dtb
2268Use @var{file} as a device tree binary (dtb) image and pass it to the kernel
2269on boot.
2270ETEXI
2271
2272STEXI
2273@end table
2274ETEXI
2275DEFHEADING()
2276
2277DEFHEADING(Debug/Expert options:)
2278STEXI
2279@table @option
2280ETEXI
2281
2282DEF("serial", HAS_ARG, QEMU_OPTION_serial, \
2283    "-serial dev     redirect the serial port to char device 'dev'\n",
2284    QEMU_ARCH_ALL)
2285STEXI
2286@item -serial @var{dev}
2287@findex -serial
2288Redirect the virtual serial port to host character device
2289@var{dev}. The default device is @code{vc} in graphical mode and
2290@code{stdio} in non graphical mode.
2291
2292This option can be used several times to simulate up to 4 serial
2293ports.
2294
2295Use @code{-serial none} to disable all serial ports.
2296
2297Available character devices are:
2298@table @option
2299@item vc[:@var{W}x@var{H}]
2300Virtual console. Optionally, a width and height can be given in pixel with
2301@example
2302vc:800x600
2303@end example
2304It is also possible to specify width or height in characters:
2305@example
2306vc:80Cx24C
2307@end example
2308@item pty
2309[Linux only] Pseudo TTY (a new PTY is automatically allocated)
2310@item none
2311No device is allocated.
2312@item null
2313void device
2314@item /dev/XXX
2315[Linux only] Use host tty, e.g. @file{/dev/ttyS0}. The host serial port
2316parameters are set according to the emulated ones.
2317@item /dev/parport@var{N}
2318[Linux only, parallel port only] Use host parallel port
2319@var{N}. Currently SPP and EPP parallel port features can be used.
2320@item file:@var{filename}
2321Write output to @var{filename}. No character can be read.
2322@item stdio
2323[Unix only] standard input/output
2324@item pipe:@var{filename}
2325name pipe @var{filename}
2326@item COM@var{n}
2327[Windows only] Use host serial port @var{n}
2328@item udp:[@var{remote_host}]:@var{remote_port}[@@[@var{src_ip}]:@var{src_port}]
2329This implements UDP Net Console.
2330When @var{remote_host} or @var{src_ip} are not specified
2331they default to @code{0.0.0.0}.
2332When not using a specified @var{src_port} a random port is automatically chosen.
2333
2334If you just want a simple readonly console you can use @code{netcat} or
2335@code{nc}, by starting QEMU with: @code{-serial udp::4555} and nc as:
2336@code{nc -u -l -p 4555}. Any time QEMU writes something to that port it
2337will appear in the netconsole session.
2338
2339If you plan to send characters back via netconsole or you want to stop
2340and start QEMU a lot of times, you should have QEMU use the same
2341source port each time by using something like @code{-serial
2342udp::4555@@:4556} to QEMU. Another approach is to use a patched
2343version of netcat which can listen to a TCP port and send and receive
2344characters via udp.  If you have a patched version of netcat which
2345activates telnet remote echo and single char transfer, then you can
2346use the following options to step up a netcat redirector to allow
2347telnet on port 5555 to access the QEMU port.
2348@table @code
2349@item QEMU Options:
2350-serial udp::4555@@:4556
2351@item netcat options:
2352-u -P 4555 -L 0.0.0.0:4556 -t -p 5555 -I -T
2353@item telnet options:
2354localhost 5555
2355@end table
2356
2357@item tcp:[@var{host}]:@var{port}[,@var{server}][,nowait][,nodelay]
2358The TCP Net Console has two modes of operation.  It can send the serial
2359I/O to a location or wait for a connection from a location.  By default
2360the TCP Net Console is sent to @var{host} at the @var{port}.  If you use
2361the @var{server} option QEMU will wait for a client socket application
2362to connect to the port before continuing, unless the @code{nowait}
2363option was specified.  The @code{nodelay} option disables the Nagle buffering
2364algorithm.  If @var{host} is omitted, 0.0.0.0 is assumed. Only
2365one TCP connection at a time is accepted. You can use @code{telnet} to
2366connect to the corresponding character device.
2367@table @code
2368@item Example to send tcp console to 192.168.0.2 port 4444
2369-serial tcp:192.168.0.2:4444
2370@item Example to listen and wait on port 4444 for connection
2371-serial tcp::4444,server
2372@item Example to not wait and listen on ip 192.168.0.100 port 4444
2373-serial tcp:192.168.0.100:4444,server,nowait
2374@end table
2375
2376@item telnet:@var{host}:@var{port}[,server][,nowait][,nodelay]
2377The telnet protocol is used instead of raw tcp sockets.  The options
2378work the same as if you had specified @code{-serial tcp}.  The
2379difference is that the port acts like a telnet server or client using
2380telnet option negotiation.  This will also allow you to send the
2381MAGIC_SYSRQ sequence if you use a telnet that supports sending the break
2382sequence.  Typically in unix telnet you do it with Control-] and then
2383type "send break" followed by pressing the enter key.
2384
2385@item unix:@var{path}[,server][,nowait]
2386A unix domain socket is used instead of a tcp socket.  The option works the
2387same as if you had specified @code{-serial tcp} except the unix domain socket
2388@var{path} is used for connections.
2389
2390@item mon:@var{dev_string}
2391This is a special option to allow the monitor to be multiplexed onto
2392another serial port.  The monitor is accessed with key sequence of
2393@key{Control-a} and then pressing @key{c}. See monitor access
2394@ref{pcsys_keys} in the -nographic section for more keys.
2395@var{dev_string} should be any one of the serial devices specified
2396above.  An example to multiplex the monitor onto a telnet server
2397listening on port 4444 would be:
2398@table @code
2399@item -serial mon:telnet::4444,server,nowait
2400@end table
2401
2402@item braille
2403Braille device.  This will use BrlAPI to display the braille output on a real
2404or fake device.
2405
2406@item msmouse
2407Three button serial mouse. Configure the guest to use Microsoft protocol.
2408@end table
2409ETEXI
2410
2411DEF("parallel", HAS_ARG, QEMU_OPTION_parallel, \
2412    "-parallel dev   redirect the parallel port to char device 'dev'\n",
2413    QEMU_ARCH_ALL)
2414STEXI
2415@item -parallel @var{dev}
2416@findex -parallel
2417Redirect the virtual parallel port to host device @var{dev} (same
2418devices as the serial port). On Linux hosts, @file{/dev/parportN} can
2419be used to use hardware devices connected on the corresponding host
2420parallel port.
2421
2422This option can be used several times to simulate up to 3 parallel
2423ports.
2424
2425Use @code{-parallel none} to disable all parallel ports.
2426ETEXI
2427
2428DEF("monitor", HAS_ARG, QEMU_OPTION_monitor, \
2429    "-monitor dev    redirect the monitor to char device 'dev'\n",
2430    QEMU_ARCH_ALL)
2431STEXI
2432@item -monitor @var{dev}
2433@findex -monitor
2434Redirect the monitor to host device @var{dev} (same devices as the
2435serial port).
2436The default device is @code{vc} in graphical mode and @code{stdio} in
2437non graphical mode.
2438ETEXI
2439DEF("qmp", HAS_ARG, QEMU_OPTION_qmp, \
2440    "-qmp dev        like -monitor but opens in 'control' mode\n",
2441    QEMU_ARCH_ALL)
2442STEXI
2443@item -qmp @var{dev}
2444@findex -qmp
2445Like -monitor but opens in 'control' mode.
2446ETEXI
2447
2448DEF("mon", HAS_ARG, QEMU_OPTION_mon, \
2449    "-mon chardev=[name][,mode=readline|control][,default]\n", QEMU_ARCH_ALL)
2450STEXI
2451@item -mon chardev=[name][,mode=readline|control][,default]
2452@findex -mon
2453Setup monitor on chardev @var{name}.
2454ETEXI
2455
2456DEF("debugcon", HAS_ARG, QEMU_OPTION_debugcon, \
2457    "-debugcon dev   redirect the debug console to char device 'dev'\n",
2458    QEMU_ARCH_ALL)
2459STEXI
2460@item -debugcon @var{dev}
2461@findex -debugcon
2462Redirect the debug console to host device @var{dev} (same devices as the
2463serial port).  The debug console is an I/O port which is typically port
24640xe9; writing to that I/O port sends output to this device.
2465The default device is @code{vc} in graphical mode and @code{stdio} in
2466non graphical mode.
2467ETEXI
2468
2469DEF("pidfile", HAS_ARG, QEMU_OPTION_pidfile, \
2470    "-pidfile file   write PID to 'file'\n", QEMU_ARCH_ALL)
2471STEXI
2472@item -pidfile @var{file}
2473@findex -pidfile
2474Store the QEMU process PID in @var{file}. It is useful if you launch QEMU
2475from a script.
2476ETEXI
2477
2478DEF("singlestep", 0, QEMU_OPTION_singlestep, \
2479    "-singlestep     always run in singlestep mode\n", QEMU_ARCH_ALL)
2480STEXI
2481@item -singlestep
2482@findex -singlestep
2483Run the emulation in single step mode.
2484ETEXI
2485
2486DEF("S", 0, QEMU_OPTION_S, \
2487    "-S              freeze CPU at startup (use 'c' to start execution)\n",
2488    QEMU_ARCH_ALL)
2489STEXI
2490@item -S
2491@findex -S
2492Do not start CPU at startup (you must type 'c' in the monitor).
2493ETEXI
2494
2495DEF("gdb", HAS_ARG, QEMU_OPTION_gdb, \
2496    "-gdb dev        wait for gdb connection on 'dev'\n", QEMU_ARCH_ALL)
2497STEXI
2498@item -gdb @var{dev}
2499@findex -gdb
2500Wait for gdb connection on device @var{dev} (@pxref{gdb_usage}). Typical
2501connections will likely be TCP-based, but also UDP, pseudo TTY, or even
2502stdio are reasonable use case. The latter is allowing to start QEMU from
2503within gdb and establish the connection via a pipe:
2504@example
2505(gdb) target remote | exec qemu-system-i386 -gdb stdio ...
2506@end example
2507ETEXI
2508
2509DEF("s", 0, QEMU_OPTION_s, \
2510    "-s              shorthand for -gdb tcp::" DEFAULT_GDBSTUB_PORT "\n",
2511    QEMU_ARCH_ALL)
2512STEXI
2513@item -s
2514@findex -s
2515Shorthand for -gdb tcp::1234, i.e. open a gdbserver on TCP port 1234
2516(@pxref{gdb_usage}).
2517ETEXI
2518
2519DEF("d", HAS_ARG, QEMU_OPTION_d, \
2520    "-d item1,...    enable logging of specified items (use '-d help' for a list of log items)\n",
2521    QEMU_ARCH_ALL)
2522STEXI
2523@item -d @var{item1}[,...]
2524@findex -d
2525Enable logging of specified items. Use '-d help' for a list of log items.
2526ETEXI
2527
2528DEF("D", HAS_ARG, QEMU_OPTION_D, \
2529    "-D logfile      output log to logfile (default stderr)\n",
2530    QEMU_ARCH_ALL)
2531STEXI
2532@item -D @var{logfile}
2533@findex -D
2534Output log in @var{logfile} instead of to stderr
2535ETEXI
2536
2537DEF("L", HAS_ARG, QEMU_OPTION_L, \
2538    "-L path         set the directory for the BIOS, VGA BIOS and keymaps\n",
2539    QEMU_ARCH_ALL)
2540STEXI
2541@item -L  @var{path}
2542@findex -L
2543Set the directory for the BIOS, VGA BIOS and keymaps.
2544ETEXI
2545
2546DEF("bios", HAS_ARG, QEMU_OPTION_bios, \
2547    "-bios file      set the filename for the BIOS\n", QEMU_ARCH_ALL)
2548STEXI
2549@item -bios @var{file}
2550@findex -bios
2551Set the filename for the BIOS.
2552ETEXI
2553
2554DEF("enable-kvm", 0, QEMU_OPTION_enable_kvm, \
2555    "-enable-kvm     enable KVM full virtualization support\n", QEMU_ARCH_ALL)
2556STEXI
2557@item -enable-kvm
2558@findex -enable-kvm
2559Enable KVM full virtualization support. This option is only available
2560if KVM support is enabled when compiling.
2561ETEXI
2562
2563DEF("xen-domid", HAS_ARG, QEMU_OPTION_xen_domid,
2564    "-xen-domid id   specify xen guest domain id\n", QEMU_ARCH_ALL)
2565DEF("xen-create", 0, QEMU_OPTION_xen_create,
2566    "-xen-create     create domain using xen hypercalls, bypassing xend\n"
2567    "                warning: should not be used when xend is in use\n",
2568    QEMU_ARCH_ALL)
2569DEF("xen-attach", 0, QEMU_OPTION_xen_attach,
2570    "-xen-attach     attach to existing xen domain\n"
2571    "                xend will use this when starting QEMU\n",
2572    QEMU_ARCH_ALL)
2573STEXI
2574@item -xen-domid @var{id}
2575@findex -xen-domid
2576Specify xen guest domain @var{id} (XEN only).
2577@item -xen-create
2578@findex -xen-create
2579Create domain using xen hypercalls, bypassing xend.
2580Warning: should not be used when xend is in use (XEN only).
2581@item -xen-attach
2582@findex -xen-attach
2583Attach to existing xen domain.
2584xend will use this when starting QEMU (XEN only).
2585ETEXI
2586
2587DEF("no-reboot", 0, QEMU_OPTION_no_reboot, \
2588    "-no-reboot      exit instead of rebooting\n", QEMU_ARCH_ALL)
2589STEXI
2590@item -no-reboot
2591@findex -no-reboot
2592Exit instead of rebooting.
2593ETEXI
2594
2595DEF("no-shutdown", 0, QEMU_OPTION_no_shutdown, \
2596    "-no-shutdown    stop before shutdown\n", QEMU_ARCH_ALL)
2597STEXI
2598@item -no-shutdown
2599@findex -no-shutdown
2600Don't exit QEMU on guest shutdown, but instead only stop the emulation.
2601This allows for instance switching to monitor to commit changes to the
2602disk image.
2603ETEXI
2604
2605DEF("loadvm", HAS_ARG, QEMU_OPTION_loadvm, \
2606    "-loadvm [tag|id]\n" \
2607    "                start right away with a saved state (loadvm in monitor)\n",
2608    QEMU_ARCH_ALL)
2609STEXI
2610@item -loadvm @var{file}
2611@findex -loadvm
2612Start right away with a saved state (@code{loadvm} in monitor)
2613ETEXI
2614
2615#ifndef _WIN32
2616DEF("daemonize", 0, QEMU_OPTION_daemonize, \
2617    "-daemonize      daemonize QEMU after initializing\n", QEMU_ARCH_ALL)
2618#endif
2619STEXI
2620@item -daemonize
2621@findex -daemonize
2622Daemonize the QEMU process after initialization.  QEMU will not detach from
2623standard IO until it is ready to receive connections on any of its devices.
2624This option is a useful way for external programs to launch QEMU without having
2625to cope with initialization race conditions.
2626ETEXI
2627
2628DEF("option-rom", HAS_ARG, QEMU_OPTION_option_rom, \
2629    "-option-rom rom load a file, rom, into the option ROM space\n",
2630    QEMU_ARCH_ALL)
2631STEXI
2632@item -option-rom @var{file}
2633@findex -option-rom
2634Load the contents of @var{file} as an option ROM.
2635This option is useful to load things like EtherBoot.
2636ETEXI
2637
2638DEF("clock", HAS_ARG, QEMU_OPTION_clock, \
2639    "-clock          force the use of the given methods for timer alarm.\n" \
2640    "                To see what timers are available use '-clock help'\n",
2641    QEMU_ARCH_ALL)
2642STEXI
2643@item -clock @var{method}
2644@findex -clock
2645Force the use of the given methods for timer alarm. To see what timers
2646are available use @code{-clock help}.
2647ETEXI
2648
2649HXCOMM Options deprecated by -rtc
2650DEF("localtime", 0, QEMU_OPTION_localtime, "", QEMU_ARCH_ALL)
2651DEF("startdate", HAS_ARG, QEMU_OPTION_startdate, "", QEMU_ARCH_ALL)
2652
2653DEF("rtc", HAS_ARG, QEMU_OPTION_rtc, \
2654    "-rtc [base=utc|localtime|date][,clock=host|rt|vm][,driftfix=none|slew]\n" \
2655    "                set the RTC base and clock, enable drift fix for clock ticks (x86 only)\n",
2656    QEMU_ARCH_ALL)
2657
2658STEXI
2659
2660@item -rtc [base=utc|localtime|@var{date}][,clock=host|vm][,driftfix=none|slew]
2661@findex -rtc
2662Specify @option{base} as @code{utc} or @code{localtime} to let the RTC start at the current
2663UTC or local time, respectively. @code{localtime} is required for correct date in
2664MS-DOS or Windows. To start at a specific point in time, provide @var{date} in the
2665format @code{2006-06-17T16:01:21} or @code{2006-06-17}. The default base is UTC.
2666
2667By default the RTC is driven by the host system time. This allows to use the
2668RTC as accurate reference clock inside the guest, specifically if the host
2669time is smoothly following an accurate external reference clock, e.g. via NTP.
2670If you want to isolate the guest time from the host, you can set @option{clock}
2671to @code{rt} instead.  To even prevent it from progressing during suspension,
2672you can set it to @code{vm}.
2673
2674Enable @option{driftfix} (i386 targets only) if you experience time drift problems,
2675specifically with Windows' ACPI HAL. This option will try to figure out how
2676many timer interrupts were not processed by the Windows guest and will
2677re-inject them.
2678ETEXI
2679
2680DEF("icount", HAS_ARG, QEMU_OPTION_icount, \
2681    "-icount [N|auto]\n" \
2682    "                enable virtual instruction counter with 2^N clock ticks per\n" \
2683    "                instruction\n", QEMU_ARCH_ALL)
2684STEXI
2685@item -icount [@var{N}|auto]
2686@findex -icount
2687Enable virtual instruction counter.  The virtual cpu will execute one
2688instruction every 2^@var{N} ns of virtual time.  If @code{auto} is specified
2689then the virtual cpu speed will be automatically adjusted to keep virtual
2690time within a few seconds of real time.
2691
2692Note that while this option can give deterministic behavior, it does not
2693provide cycle accurate emulation.  Modern CPUs contain superscalar out of
2694order cores with complex cache hierarchies.  The number of instructions
2695executed often has little or no correlation with actual performance.
2696ETEXI
2697
2698DEF("watchdog", HAS_ARG, QEMU_OPTION_watchdog, \
2699    "-watchdog i6300esb|ib700\n" \
2700    "                enable virtual hardware watchdog [default=none]\n",
2701    QEMU_ARCH_ALL)
2702STEXI
2703@item -watchdog @var{model}
2704@findex -watchdog
2705Create a virtual hardware watchdog device.  Once enabled (by a guest
2706action), the watchdog must be periodically polled by an agent inside
2707the guest or else the guest will be restarted.
2708
2709The @var{model} is the model of hardware watchdog to emulate.  Choices
2710for model are: @code{ib700} (iBASE 700) which is a very simple ISA
2711watchdog with a single timer, or @code{i6300esb} (Intel 6300ESB I/O
2712controller hub) which is a much more featureful PCI-based dual-timer
2713watchdog.  Choose a model for which your guest has drivers.
2714
2715Use @code{-watchdog help} to list available hardware models.  Only one
2716watchdog can be enabled for a guest.
2717ETEXI
2718
2719DEF("watchdog-action", HAS_ARG, QEMU_OPTION_watchdog_action, \
2720    "-watchdog-action reset|shutdown|poweroff|pause|debug|none\n" \
2721    "                action when watchdog fires [default=reset]\n",
2722    QEMU_ARCH_ALL)
2723STEXI
2724@item -watchdog-action @var{action}
2725@findex -watchdog-action
2726
2727The @var{action} controls what QEMU will do when the watchdog timer
2728expires.
2729The default is
2730@code{reset} (forcefully reset the guest).
2731Other possible actions are:
2732@code{shutdown} (attempt to gracefully shutdown the guest),
2733@code{poweroff} (forcefully poweroff the guest),
2734@code{pause} (pause the guest),
2735@code{debug} (print a debug message and continue), or
2736@code{none} (do nothing).
2737
2738Note that the @code{shutdown} action requires that the guest responds
2739to ACPI signals, which it may not be able to do in the sort of
2740situations where the watchdog would have expired, and thus
2741@code{-watchdog-action shutdown} is not recommended for production use.
2742
2743Examples:
2744
2745@table @code
2746@item -watchdog i6300esb -watchdog-action pause
2747@item -watchdog ib700
2748@end table
2749ETEXI
2750
2751DEF("echr", HAS_ARG, QEMU_OPTION_echr, \
2752    "-echr chr       set terminal escape character instead of ctrl-a\n",
2753    QEMU_ARCH_ALL)
2754STEXI
2755
2756@item -echr @var{numeric_ascii_value}
2757@findex -echr
2758Change the escape character used for switching to the monitor when using
2759monitor and serial sharing.  The default is @code{0x01} when using the
2760@code{-nographic} option.  @code{0x01} is equal to pressing
2761@code{Control-a}.  You can select a different character from the ascii
2762control keys where 1 through 26 map to Control-a through Control-z.  For
2763instance you could use the either of the following to change the escape
2764character to Control-t.
2765@table @code
2766@item -echr 0x14
2767@item -echr 20
2768@end table
2769ETEXI
2770
2771DEF("virtioconsole", HAS_ARG, QEMU_OPTION_virtiocon, \
2772    "-virtioconsole c\n" \
2773    "                set virtio console\n", QEMU_ARCH_ALL)
2774STEXI
2775@item -virtioconsole @var{c}
2776@findex -virtioconsole
2777Set virtio console.
2778
2779This option is maintained for backward compatibility.
2780
2781Please use @code{-device virtconsole} for the new way of invocation.
2782ETEXI
2783
2784DEF("show-cursor", 0, QEMU_OPTION_show_cursor, \
2785    "-show-cursor    show cursor\n", QEMU_ARCH_ALL)
2786STEXI
2787@item -show-cursor
2788@findex -show-cursor
2789Show cursor.
2790ETEXI
2791
2792DEF("tb-size", HAS_ARG, QEMU_OPTION_tb_size, \
2793    "-tb-size n      set TB size\n", QEMU_ARCH_ALL)
2794STEXI
2795@item -tb-size @var{n}
2796@findex -tb-size
2797Set TB size.
2798ETEXI
2799
2800DEF("incoming", HAS_ARG, QEMU_OPTION_incoming, \
2801    "-incoming p     prepare for incoming migration, listen on port p\n",
2802    QEMU_ARCH_ALL)
2803STEXI
2804@item -incoming @var{port}
2805@findex -incoming
2806Prepare for incoming migration, listen on @var{port}.
2807ETEXI
2808
2809DEF("nodefaults", 0, QEMU_OPTION_nodefaults, \
2810    "-nodefaults     don't create default devices\n", QEMU_ARCH_ALL)
2811STEXI
2812@item -nodefaults
2813@findex -nodefaults
2814Don't create default devices. Normally, QEMU sets the default devices like serial
2815port, parallel port, virtual console, monitor device, VGA adapter, floppy and
2816CD-ROM drive and others. The @code{-nodefaults} option will disable all those
2817default devices.
2818ETEXI
2819
2820#ifndef _WIN32
2821DEF("chroot", HAS_ARG, QEMU_OPTION_chroot, \
2822    "-chroot dir     chroot to dir just before starting the VM\n",
2823    QEMU_ARCH_ALL)
2824#endif
2825STEXI
2826@item -chroot @var{dir}
2827@findex -chroot
2828Immediately before starting guest execution, chroot to the specified
2829directory.  Especially useful in combination with -runas.
2830ETEXI
2831
2832#ifndef _WIN32
2833DEF("runas", HAS_ARG, QEMU_OPTION_runas, \
2834    "-runas user     change to user id user just before starting the VM\n",
2835    QEMU_ARCH_ALL)
2836#endif
2837STEXI
2838@item -runas @var{user}
2839@findex -runas
2840Immediately before starting guest execution, drop root privileges, switching
2841to the specified user.
2842ETEXI
2843
2844DEF("prom-env", HAS_ARG, QEMU_OPTION_prom_env,
2845    "-prom-env variable=value\n"
2846    "                set OpenBIOS nvram variables\n",
2847    QEMU_ARCH_PPC | QEMU_ARCH_SPARC)
2848STEXI
2849@item -prom-env @var{variable}=@var{value}
2850@findex -prom-env
2851Set OpenBIOS nvram @var{variable} to given @var{value} (PPC, SPARC only).
2852ETEXI
2853DEF("semihosting", 0, QEMU_OPTION_semihosting,
2854    "-semihosting    semihosting mode\n", QEMU_ARCH_ARM | QEMU_ARCH_M68K | QEMU_ARCH_XTENSA)
2855STEXI
2856@item -semihosting
2857@findex -semihosting
2858Semihosting mode (ARM, M68K, Xtensa only).
2859ETEXI
2860DEF("old-param", 0, QEMU_OPTION_old_param,
2861    "-old-param      old param mode\n", QEMU_ARCH_ARM)
2862STEXI
2863@item -old-param
2864@findex -old-param (ARM)
2865Old param mode (ARM only).
2866ETEXI
2867
2868DEF("sandbox", HAS_ARG, QEMU_OPTION_sandbox, \
2869    "-sandbox <arg>  Enable seccomp mode 2 system call filter (default 'off').\n",
2870    QEMU_ARCH_ALL)
2871STEXI
2872@item -sandbox @var{arg}
2873@findex -sandbox
2874Enable Seccomp mode 2 system call filter. 'on' will enable syscall filtering and 'off' will
2875disable it.  The default is 'off'.
2876ETEXI
2877
2878DEF("readconfig", HAS_ARG, QEMU_OPTION_readconfig,
2879    "-readconfig <file>\n", QEMU_ARCH_ALL)
2880STEXI
2881@item -readconfig @var{file}
2882@findex -readconfig
2883Read device configuration from @var{file}. This approach is useful when you want to spawn
2884QEMU process with many command line options but you don't want to exceed the command line
2885character limit.
2886ETEXI
2887DEF("writeconfig", HAS_ARG, QEMU_OPTION_writeconfig,
2888    "-writeconfig <file>\n"
2889    "                read/write config file\n", QEMU_ARCH_ALL)
2890STEXI
2891@item -writeconfig @var{file}
2892@findex -writeconfig
2893Write device configuration to @var{file}. The @var{file} can be either filename to save
2894command line and device configuration into file or dash @code{-}) character to print the
2895output to stdout. This can be later used as input file for @code{-readconfig} option.
2896ETEXI
2897DEF("nodefconfig", 0, QEMU_OPTION_nodefconfig,
2898    "-nodefconfig\n"
2899    "                do not load default config files at startup\n",
2900    QEMU_ARCH_ALL)
2901STEXI
2902@item -nodefconfig
2903@findex -nodefconfig
2904Normally QEMU loads configuration files from @var{sysconfdir} and @var{datadir} at startup.
2905The @code{-nodefconfig} option will prevent QEMU from loading any of those config files.
2906ETEXI
2907DEF("no-user-config", 0, QEMU_OPTION_nouserconfig,
2908    "-no-user-config\n"
2909    "                do not load user-provided config files at startup\n",
2910    QEMU_ARCH_ALL)
2911STEXI
2912@item -no-user-config
2913@findex -no-user-config
2914The @code{-no-user-config} option makes QEMU not load any of the user-provided
2915config files on @var{sysconfdir}, but won't make it skip the QEMU-provided config
2916files from @var{datadir}.
2917ETEXI
2918DEF("trace", HAS_ARG, QEMU_OPTION_trace,
2919    "-trace [events=<file>][,file=<file>]\n"
2920    "                specify tracing options\n",
2921    QEMU_ARCH_ALL)
2922STEXI
2923HXCOMM This line is not accurate, as some sub-options are backend-specific but
2924HXCOMM HX does not support conditional compilation of text.
2925@item -trace [events=@var{file}][,file=@var{file}]
2926@findex -trace
2927
2928Specify tracing options.
2929
2930@table @option
2931@item events=@var{file}
2932Immediately enable events listed in @var{file}.
2933The file must contain one event name (as listed in the @var{trace-events} file)
2934per line.
2935This option is only available if QEMU has been compiled with
2936either @var{simple} or @var{stderr} tracing backend.
2937@item file=@var{file}
2938Log output traces to @var{file}.
2939
2940This option is only available if QEMU has been compiled with
2941the @var{simple} tracing backend.
2942@end table
2943ETEXI
2944
2945HXCOMM Internal use
2946DEF("qtest", HAS_ARG, QEMU_OPTION_qtest, "", QEMU_ARCH_ALL)
2947DEF("qtest-log", HAS_ARG, QEMU_OPTION_qtest_log, "", QEMU_ARCH_ALL)
2948
2949#ifdef __linux__
2950DEF("enable-fips", 0, QEMU_OPTION_enablefips,
2951    "-enable-fips    enable FIPS 140-2 compliance\n",
2952    QEMU_ARCH_ALL)
2953#endif
2954STEXI
2955@item -enable-fips
2956@findex -enable-fips
2957Enable FIPS 140-2 compliance mode.
2958ETEXI
2959
2960HXCOMM Deprecated by -machine accel=tcg property
2961DEF("no-kvm", 0, QEMU_OPTION_no_kvm, "", QEMU_ARCH_I386)
2962
2963HXCOMM Deprecated by kvm-pit driver properties
2964DEF("no-kvm-pit-reinjection", 0, QEMU_OPTION_no_kvm_pit_reinjection,
2965    "", QEMU_ARCH_I386)
2966
2967HXCOMM Deprecated (ignored)
2968DEF("no-kvm-pit", 0, QEMU_OPTION_no_kvm_pit, "", QEMU_ARCH_I386)
2969
2970HXCOMM Deprecated by -machine kernel_irqchip=on|off property
2971DEF("no-kvm-irqchip", 0, QEMU_OPTION_no_kvm_irqchip, "", QEMU_ARCH_I386)
2972
2973HXCOMM Deprecated (ignored)
2974DEF("tdf", 0, QEMU_OPTION_tdf,"", QEMU_ARCH_ALL)
2975
2976DEF("object", HAS_ARG, QEMU_OPTION_object,
2977    "-object TYPENAME[,PROP1=VALUE1,...]\n"
2978    "                create an new object of type TYPENAME setting properties\n"
2979    "                in the order they are specified.  Note that the 'id'\n"
2980    "                property must be set.  These objects are placed in the\n"
2981    "                '/objects' path.\n",
2982    QEMU_ARCH_ALL)
2983STEXI
2984@item -object @var{typename}[,@var{prop1}=@var{value1},...]
2985@findex -object
2986Create an new object of type @var{typename} setting properties
2987in the order they are specified.  Note that the 'id'
2988property must be set.  These objects are placed in the
2989'/objects' path.
2990ETEXI
2991
2992HXCOMM This is the last statement. Insert new options before this line!
2993STEXI
2994@end table
2995ETEXI
2996