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