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 " kernel_irqchip=on|off|split controls accelerated irqchip support (default=off)\n" 37 " vmport=on|off|auto controls emulation of vmport (default: auto)\n" 38 " kvm_shadow_mem=size of KVM shadow MMU\n" 39 " dump-guest-core=on|off include guest memory in a core dump (default=on)\n" 40 " mem-merge=on|off controls memory merge support (default: on)\n" 41 " iommu=on|off controls emulated Intel IOMMU (VT-d) support (default=off)\n" 42 " igd-passthru=on|off controls IGD GFX passthrough support (default=off)\n" 43 " aes-key-wrap=on|off controls support for AES key wrapping (default=on)\n" 44 " dea-key-wrap=on|off controls support for DEA key wrapping (default=on)\n" 45 " suppress-vmdesc=on|off disables self-describing migration (default=off)\n" 46 " nvdimm=on|off controls NVDIMM support (default=off)\n" 47 " enforce-config-section=on|off enforce configuration section migration (default=off)\n", 48 QEMU_ARCH_ALL) 49STEXI 50@item -machine [type=]@var{name}[,prop=@var{value}[,...]] 51@findex -machine 52Select the emulated machine by @var{name}. Use @code{-machine help} to list 53available machines. Supported machine properties are: 54@table @option 55@item accel=@var{accels1}[:@var{accels2}[:...]] 56This is used to enable an accelerator. Depending on the target architecture, 57kvm, xen, or tcg can be available. By default, tcg is used. If there is more 58than one accelerator specified, the next one is used if the previous one fails 59to initialize. 60@item kernel_irqchip=on|off 61Controls in-kernel irqchip support for the chosen accelerator when available. 62@item gfx_passthru=on|off 63Enables IGD GFX passthrough support for the chosen machine when available. 64@item vmport=on|off|auto 65Enables emulation of VMWare IO port, for vmmouse etc. auto says to select the 66value based on accel. For accel=xen the default is off otherwise the default 67is on. 68@item kvm_shadow_mem=size 69Defines the size of the KVM shadow MMU. 70@item dump-guest-core=on|off 71Include guest memory in a core dump. The default is on. 72@item mem-merge=on|off 73Enables or disables memory merge support. This feature, when supported by 74the host, de-duplicates identical memory pages among VMs instances 75(enabled by default). 76@item iommu=on|off 77Enables or disables emulated Intel IOMMU (VT-d) support. The default is off. 78@item aes-key-wrap=on|off 79Enables or disables AES key wrapping support on s390-ccw hosts. This feature 80controls whether AES wrapping keys will be created to allow 81execution of AES cryptographic functions. The default is on. 82@item dea-key-wrap=on|off 83Enables or disables DEA key wrapping support on s390-ccw hosts. This feature 84controls whether DEA wrapping keys will be created to allow 85execution of DEA cryptographic functions. The default is on. 86@item nvdimm=on|off 87Enables or disables NVDIMM support. The default is off. 88@end table 89ETEXI 90 91HXCOMM Deprecated by -machine 92DEF("M", HAS_ARG, QEMU_OPTION_M, "", QEMU_ARCH_ALL) 93 94DEF("cpu", HAS_ARG, QEMU_OPTION_cpu, 95 "-cpu cpu select CPU ('-cpu help' for list)\n", QEMU_ARCH_ALL) 96STEXI 97@item -cpu @var{model} 98@findex -cpu 99Select CPU model (@code{-cpu help} for list and additional feature selection) 100ETEXI 101 102DEF("smp", HAS_ARG, QEMU_OPTION_smp, 103 "-smp [cpus=]n[,maxcpus=cpus][,cores=cores][,threads=threads][,sockets=sockets]\n" 104 " set the number of CPUs to 'n' [default=1]\n" 105 " maxcpus= maximum number of total cpus, including\n" 106 " offline CPUs for hotplug, etc\n" 107 " cores= number of CPU cores on one socket\n" 108 " threads= number of threads on one CPU core\n" 109 " sockets= number of discrete sockets in the system\n", 110 QEMU_ARCH_ALL) 111STEXI 112@item -smp [cpus=]@var{n}[,cores=@var{cores}][,threads=@var{threads}][,sockets=@var{sockets}][,maxcpus=@var{maxcpus}] 113@findex -smp 114Simulate an SMP system with @var{n} CPUs. On the PC target, up to 255 115CPUs are supported. On Sparc32 target, Linux limits the number of usable CPUs 116to 4. 117For the PC target, the number of @var{cores} per socket, the number 118of @var{threads} per cores and the total number of @var{sockets} can be 119specified. Missing values will be computed. If any on the three values is 120given, the total number of CPUs @var{n} can be omitted. @var{maxcpus} 121specifies the maximum number of hotpluggable CPUs. 122ETEXI 123 124DEF("numa", HAS_ARG, QEMU_OPTION_numa, 125 "-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]\n" 126 "-numa node[,memdev=id][,cpus=cpu[-cpu]][,nodeid=node]\n", QEMU_ARCH_ALL) 127STEXI 128@item -numa node[,mem=@var{size}][,cpus=@var{cpu[-cpu]}][,nodeid=@var{node}] 129@itemx -numa node[,memdev=@var{id}][,cpus=@var{cpu[-cpu]}][,nodeid=@var{node}] 130@findex -numa 131Simulate a multi node NUMA system. If @samp{mem}, @samp{memdev} 132and @samp{cpus} are omitted, resources are split equally. Also, note 133that the -@option{numa} option doesn't allocate any of the specified 134resources. That is, it just assigns existing resources to NUMA nodes. This 135means that one still has to use the @option{-m}, @option{-smp} options 136to allocate RAM and VCPUs respectively, and possibly @option{-object} 137to specify the memory backend for the @samp{memdev} suboption. 138 139@samp{mem} and @samp{memdev} are mutually exclusive. Furthermore, if one 140node uses @samp{memdev}, all of them have to use it. 141ETEXI 142 143DEF("add-fd", HAS_ARG, QEMU_OPTION_add_fd, 144 "-add-fd fd=fd,set=set[,opaque=opaque]\n" 145 " Add 'fd' to fd 'set'\n", QEMU_ARCH_ALL) 146STEXI 147@item -add-fd fd=@var{fd},set=@var{set}[,opaque=@var{opaque}] 148@findex -add-fd 149 150Add a file descriptor to an fd set. Valid options are: 151 152@table @option 153@item fd=@var{fd} 154This option defines the file descriptor of which a duplicate is added to fd set. 155The file descriptor cannot be stdin, stdout, or stderr. 156@item set=@var{set} 157This option defines the ID of the fd set to add the file descriptor to. 158@item opaque=@var{opaque} 159This option defines a free-form string that can be used to describe @var{fd}. 160@end table 161 162You can open an image using pre-opened file descriptors from an fd set: 163@example 164qemu-system-i386 165-add-fd fd=3,set=2,opaque="rdwr:/path/to/file" 166-add-fd fd=4,set=2,opaque="rdonly:/path/to/file" 167-drive file=/dev/fdset/2,index=0,media=disk 168@end example 169ETEXI 170 171DEF("set", HAS_ARG, QEMU_OPTION_set, 172 "-set group.id.arg=value\n" 173 " set <arg> parameter for item <id> of type <group>\n" 174 " i.e. -set drive.$id.file=/path/to/image\n", QEMU_ARCH_ALL) 175STEXI 176@item -set @var{group}.@var{id}.@var{arg}=@var{value} 177@findex -set 178Set parameter @var{arg} for item @var{id} of type @var{group}\n" 179ETEXI 180 181DEF("global", HAS_ARG, QEMU_OPTION_global, 182 "-global driver.property=value\n" 183 "-global driver=driver,property=property,value=value\n" 184 " set a global default for a driver property\n", 185 QEMU_ARCH_ALL) 186STEXI 187@item -global @var{driver}.@var{prop}=@var{value} 188@itemx -global driver=@var{driver},property=@var{property},value=@var{value} 189@findex -global 190Set default value of @var{driver}'s property @var{prop} to @var{value}, e.g.: 191 192@example 193qemu-system-i386 -global ide-drive.physical_block_size=4096 -drive file=file,if=ide,index=0,media=disk 194@end example 195 196In particular, you can use this to set driver properties for devices which are 197created automatically by the machine model. To create a device which is not 198created automatically and set properties on it, use -@option{device}. 199 200-global @var{driver}.@var{prop}=@var{value} is shorthand for -global 201driver=@var{driver},property=@var{prop},value=@var{value}. The 202longhand syntax works even when @var{driver} contains a dot. 203ETEXI 204 205DEF("boot", HAS_ARG, QEMU_OPTION_boot, 206 "-boot [order=drives][,once=drives][,menu=on|off]\n" 207 " [,splash=sp_name][,splash-time=sp_time][,reboot-timeout=rb_time][,strict=on|off]\n" 208 " 'drives': floppy (a), hard disk (c), CD-ROM (d), network (n)\n" 209 " 'sp_name': the file's name that would be passed to bios as logo picture, if menu=on\n" 210 " 'sp_time': the period that splash picture last if menu=on, unit is ms\n" 211 " 'rb_timeout': the timeout before guest reboot when boot failed, unit is ms\n", 212 QEMU_ARCH_ALL) 213STEXI 214@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] 215@findex -boot 216Specify boot order @var{drives} as a string of drive letters. Valid 217drive letters depend on the target architecture. The x86 PC uses: a, b 218(floppy 1 and 2), c (first hard disk), d (first CD-ROM), n-p (Etherboot 219from network adapter 1-4), hard disk boot is the default. To apply a 220particular boot order only on the first startup, specify it via 221@option{once}. 222 223Interactive boot menus/prompts can be enabled via @option{menu=on} as far 224as firmware/BIOS supports them. The default is non-interactive boot. 225 226A splash picture could be passed to bios, enabling user to show it as logo, 227when option splash=@var{sp_name} is given and menu=on, If firmware/BIOS 228supports them. Currently Seabios for X86 system support it. 229limitation: The splash file could be a jpeg file or a BMP file in 24 BPP 230format(true color). The resolution should be supported by the SVGA mode, so 231the recommended is 320x240, 640x480, 800x640. 232 233A timeout could be passed to bios, guest will pause for @var{rb_timeout} ms 234when boot failed, then reboot. If @var{rb_timeout} is '-1', guest will not 235reboot, qemu passes '-1' to bios by default. Currently Seabios for X86 236system support it. 237 238Do strict boot via @option{strict=on} as far as firmware/BIOS 239supports it. This only effects when boot priority is changed by 240bootindex options. The default is non-strict boot. 241 242@example 243# try to boot from network first, then from hard disk 244qemu-system-i386 -boot order=nc 245# boot from CD-ROM first, switch back to default order after reboot 246qemu-system-i386 -boot once=d 247# boot with a splash picture for 5 seconds. 248qemu-system-i386 -boot menu=on,splash=/root/boot.bmp,splash-time=5000 249@end example 250 251Note: The legacy format '-boot @var{drives}' is still supported but its 252use is discouraged as it may be removed from future versions. 253ETEXI 254 255DEF("m", HAS_ARG, QEMU_OPTION_m, 256 "-m[emory] [size=]megs[,slots=n,maxmem=size]\n" 257 " configure guest RAM\n" 258 " size: initial amount of guest memory\n" 259 " slots: number of hotplug slots (default: none)\n" 260 " maxmem: maximum amount of guest memory (default: none)\n" 261 "NOTE: Some architectures might enforce a specific granularity\n", 262 QEMU_ARCH_ALL) 263STEXI 264@item -m [size=]@var{megs}[,slots=n,maxmem=size] 265@findex -m 266Sets guest startup RAM size to @var{megs} megabytes. Default is 128 MiB. 267Optionally, a suffix of ``M'' or ``G'' can be used to signify a value in 268megabytes or gigabytes respectively. Optional pair @var{slots}, @var{maxmem} 269could be used to set amount of hotpluggable memory slots and maximum amount of 270memory. Note that @var{maxmem} must be aligned to the page size. 271 272For example, the following command-line sets the guest startup RAM size to 2731GB, creates 3 slots to hotplug additional memory and sets the maximum 274memory the guest can reach to 4GB: 275 276@example 277qemu-system-x86_64 -m 1G,slots=3,maxmem=4G 278@end example 279 280If @var{slots} and @var{maxmem} are not specified, memory hotplug won't 281be enabled and the guest startup RAM will never increase. 282ETEXI 283 284DEF("mem-path", HAS_ARG, QEMU_OPTION_mempath, 285 "-mem-path FILE provide backing storage for guest RAM\n", QEMU_ARCH_ALL) 286STEXI 287@item -mem-path @var{path} 288@findex -mem-path 289Allocate guest RAM from a temporarily created file in @var{path}. 290ETEXI 291 292DEF("mem-prealloc", 0, QEMU_OPTION_mem_prealloc, 293 "-mem-prealloc preallocate guest memory (use with -mem-path)\n", 294 QEMU_ARCH_ALL) 295STEXI 296@item -mem-prealloc 297@findex -mem-prealloc 298Preallocate memory when using -mem-path. 299ETEXI 300 301DEF("k", HAS_ARG, QEMU_OPTION_k, 302 "-k language use keyboard layout (for example 'fr' for French)\n", 303 QEMU_ARCH_ALL) 304STEXI 305@item -k @var{language} 306@findex -k 307Use keyboard layout @var{language} (for example @code{fr} for 308French). This option is only needed where it is not easy to get raw PC 309keycodes (e.g. on Macs, with some X11 servers or with a VNC 310display). You don't normally need to use it on PC/Linux or PC/Windows 311hosts. 312 313The available layouts are: 314@example 315ar de-ch es fo fr-ca hu ja mk no pt-br sv 316da en-gb et fr fr-ch is lt nl pl ru th 317de en-us fi fr-be hr it lv nl-be pt sl tr 318@end example 319 320The default is @code{en-us}. 321ETEXI 322 323 324DEF("audio-help", 0, QEMU_OPTION_audio_help, 325 "-audio-help print list of audio drivers and their options\n", 326 QEMU_ARCH_ALL) 327STEXI 328@item -audio-help 329@findex -audio-help 330Will show the audio subsystem help: list of drivers, tunable 331parameters. 332ETEXI 333 334DEF("soundhw", HAS_ARG, QEMU_OPTION_soundhw, 335 "-soundhw c1,... enable audio support\n" 336 " and only specified sound cards (comma separated list)\n" 337 " use '-soundhw help' to get the list of supported cards\n" 338 " use '-soundhw all' to enable all of them\n", QEMU_ARCH_ALL) 339STEXI 340@item -soundhw @var{card1}[,@var{card2},...] or -soundhw all 341@findex -soundhw 342Enable audio and selected sound hardware. Use 'help' to print all 343available sound hardware. 344 345@example 346qemu-system-i386 -soundhw sb16,adlib disk.img 347qemu-system-i386 -soundhw es1370 disk.img 348qemu-system-i386 -soundhw ac97 disk.img 349qemu-system-i386 -soundhw hda disk.img 350qemu-system-i386 -soundhw all disk.img 351qemu-system-i386 -soundhw help 352@end example 353 354Note that Linux's i810_audio OSS kernel (for AC97) module might 355require manually specifying clocking. 356 357@example 358modprobe i810_audio clocking=48000 359@end example 360ETEXI 361 362DEF("balloon", HAS_ARG, QEMU_OPTION_balloon, 363 "-balloon none disable balloon device\n" 364 "-balloon virtio[,addr=str]\n" 365 " enable virtio balloon device (default)\n", QEMU_ARCH_ALL) 366STEXI 367@item -balloon none 368@findex -balloon 369Disable balloon device. 370@item -balloon virtio[,addr=@var{addr}] 371Enable virtio balloon device (default), optionally with PCI address 372@var{addr}. 373ETEXI 374 375DEF("device", HAS_ARG, QEMU_OPTION_device, 376 "-device driver[,prop[=value][,...]]\n" 377 " add device (based on driver)\n" 378 " prop=value,... sets driver properties\n" 379 " use '-device help' to print all possible drivers\n" 380 " use '-device driver,help' to print all possible properties\n", 381 QEMU_ARCH_ALL) 382STEXI 383@item -device @var{driver}[,@var{prop}[=@var{value}][,...]] 384@findex -device 385Add device @var{driver}. @var{prop}=@var{value} sets driver 386properties. Valid properties depend on the driver. To get help on 387possible drivers and properties, use @code{-device help} and 388@code{-device @var{driver},help}. 389 390Some drivers are: 391@item -device ipmi-bmc-sim,id=@var{id}[,slave_addr=@var{val}] 392 393Add an IPMI BMC. This is a simulation of a hardware management 394interface processor that normally sits on a system. It provides 395a watchdog and the ability to reset and power control the system. 396You need to connect this to an IPMI interface to make it useful 397 398The IPMI slave address to use for the BMC. The default is 0x20. 399This address is the BMC's address on the I2C network of management 400controllers. If you don't know what this means, it is safe to ignore 401it. 402 403@item -device ipmi-bmc-extern,id=@var{id},chardev=@var{id}[,slave_addr=@var{val}] 404 405Add a connection to an external IPMI BMC simulator. Instead of 406locally emulating the BMC like the above item, instead connect 407to an external entity that provides the IPMI services. 408 409A connection is made to an external BMC simulator. If you do this, it 410is strongly recommended that you use the "reconnect=" chardev option 411to reconnect to the simulator if the connection is lost. Note that if 412this is not used carefully, it can be a security issue, as the 413interface has the ability to send resets, NMIs, and power off the VM. 414It's best if QEMU makes a connection to an external simulator running 415on a secure port on localhost, so neither the simulator nor QEMU is 416exposed to any outside network. 417 418See the "lanserv/README.vm" file in the OpenIPMI library for more 419details on the external interface. 420 421@item -device isa-ipmi-kcs,bmc=@var{id}[,ioport=@var{val}][,irq=@var{val}] 422 423Add a KCS IPMI interafce on the ISA bus. This also adds a 424corresponding ACPI and SMBIOS entries, if appropriate. 425 426@table @option 427@item bmc=@var{id} 428The BMC to connect to, one of ipmi-bmc-sim or ipmi-bmc-extern above. 429@item ioport=@var{val} 430Define the I/O address of the interface. The default is 0xca0 for KCS. 431@item irq=@var{val} 432Define the interrupt to use. The default is 5. To disable interrupts, 433set this to 0. 434@end table 435 436@item -device isa-ipmi-bt,bmc=@var{id}[,ioport=@var{val}][,irq=@var{val}] 437 438Like the KCS interface, but defines a BT interface. The default port is 4390xe4 and the default interrupt is 5. 440 441ETEXI 442 443DEF("name", HAS_ARG, QEMU_OPTION_name, 444 "-name string1[,process=string2][,debug-threads=on|off]\n" 445 " set the name of the guest\n" 446 " string1 sets the window title and string2 the process name (on Linux)\n" 447 " When debug-threads is enabled, individual threads are given a separate name (on Linux)\n" 448 " NOTE: The thread names are for debugging and not a stable API.\n", 449 QEMU_ARCH_ALL) 450STEXI 451@item -name @var{name} 452@findex -name 453Sets the @var{name} of the guest. 454This name will be displayed in the SDL window caption. 455The @var{name} will also be used for the VNC server. 456Also optionally set the top visible process name in Linux. 457Naming of individual threads can also be enabled on Linux to aid debugging. 458ETEXI 459 460DEF("uuid", HAS_ARG, QEMU_OPTION_uuid, 461 "-uuid %08x-%04x-%04x-%04x-%012x\n" 462 " specify machine UUID\n", QEMU_ARCH_ALL) 463STEXI 464@item -uuid @var{uuid} 465@findex -uuid 466Set system UUID. 467ETEXI 468 469STEXI 470@end table 471ETEXI 472DEFHEADING() 473 474DEFHEADING(Block device options:) 475STEXI 476@table @option 477ETEXI 478 479DEF("fda", HAS_ARG, QEMU_OPTION_fda, 480 "-fda/-fdb file use 'file' as floppy disk 0/1 image\n", QEMU_ARCH_ALL) 481DEF("fdb", HAS_ARG, QEMU_OPTION_fdb, "", QEMU_ARCH_ALL) 482STEXI 483@item -fda @var{file} 484@itemx -fdb @var{file} 485@findex -fda 486@findex -fdb 487Use @var{file} as floppy disk 0/1 image (@pxref{disk_images}). 488ETEXI 489 490DEF("hda", HAS_ARG, QEMU_OPTION_hda, 491 "-hda/-hdb file use 'file' as IDE hard disk 0/1 image\n", QEMU_ARCH_ALL) 492DEF("hdb", HAS_ARG, QEMU_OPTION_hdb, "", QEMU_ARCH_ALL) 493DEF("hdc", HAS_ARG, QEMU_OPTION_hdc, 494 "-hdc/-hdd file use 'file' as IDE hard disk 2/3 image\n", QEMU_ARCH_ALL) 495DEF("hdd", HAS_ARG, QEMU_OPTION_hdd, "", QEMU_ARCH_ALL) 496STEXI 497@item -hda @var{file} 498@itemx -hdb @var{file} 499@itemx -hdc @var{file} 500@itemx -hdd @var{file} 501@findex -hda 502@findex -hdb 503@findex -hdc 504@findex -hdd 505Use @var{file} as hard disk 0, 1, 2 or 3 image (@pxref{disk_images}). 506ETEXI 507 508DEF("cdrom", HAS_ARG, QEMU_OPTION_cdrom, 509 "-cdrom file use 'file' as IDE cdrom image (cdrom is ide1 master)\n", 510 QEMU_ARCH_ALL) 511STEXI 512@item -cdrom @var{file} 513@findex -cdrom 514Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and 515@option{-cdrom} at the same time). You can use the host CD-ROM by 516using @file{/dev/cdrom} as filename (@pxref{host_drives}). 517ETEXI 518 519DEF("drive", HAS_ARG, QEMU_OPTION_drive, 520 "-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][,index=i]\n" 521 " [,cyls=c,heads=h,secs=s[,trans=t]][,snapshot=on|off]\n" 522 " [,cache=writethrough|writeback|none|directsync|unsafe][,format=f]\n" 523 " [,serial=s][,addr=A][,rerror=ignore|stop|report]\n" 524 " [,werror=ignore|stop|report|enospc][,id=name][,aio=threads|native]\n" 525 " [,readonly=on|off][,copy-on-read=on|off]\n" 526 " [,discard=ignore|unmap][,detect-zeroes=on|off|unmap]\n" 527 " [[,bps=b]|[[,bps_rd=r][,bps_wr=w]]]\n" 528 " [[,iops=i]|[[,iops_rd=r][,iops_wr=w]]]\n" 529 " [[,bps_max=bm]|[[,bps_rd_max=rm][,bps_wr_max=wm]]]\n" 530 " [[,iops_max=im]|[[,iops_rd_max=irm][,iops_wr_max=iwm]]]\n" 531 " [[,iops_size=is]]\n" 532 " [[,group=g]]\n" 533 " use 'file' as a drive image\n", QEMU_ARCH_ALL) 534STEXI 535@item -drive @var{option}[,@var{option}[,@var{option}[,...]]] 536@findex -drive 537 538Define a new drive. Valid options are: 539 540@table @option 541@item file=@var{file} 542This option defines which disk image (@pxref{disk_images}) to use with 543this drive. If the filename contains comma, you must double it 544(for instance, "file=my,,file" to use file "my,file"). 545 546Special files such as iSCSI devices can be specified using protocol 547specific URLs. See the section for "Device URL Syntax" for more information. 548@item if=@var{interface} 549This option defines on which type on interface the drive is connected. 550Available types are: ide, scsi, sd, mtd, floppy, pflash, virtio. 551@item bus=@var{bus},unit=@var{unit} 552These options define where is connected the drive by defining the bus number and 553the unit id. 554@item index=@var{index} 555This option defines where is connected the drive by using an index in the list 556of available connectors of a given interface type. 557@item media=@var{media} 558This option defines the type of the media: disk or cdrom. 559@item cyls=@var{c},heads=@var{h},secs=@var{s}[,trans=@var{t}] 560These options have the same definition as they have in @option{-hdachs}. 561@item snapshot=@var{snapshot} 562@var{snapshot} is "on" or "off" and controls snapshot mode for the given drive 563(see @option{-snapshot}). 564@item cache=@var{cache} 565@var{cache} is "none", "writeback", "unsafe", "directsync" or "writethrough" and controls how the host cache is used to access block data. 566@item aio=@var{aio} 567@var{aio} is "threads", or "native" and selects between pthread based disk I/O and native Linux AIO. 568@item discard=@var{discard} 569@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. 570@item format=@var{format} 571Specify which disk @var{format} will be used rather than detecting 572the format. Can be used to specifiy format=raw to avoid interpreting 573an untrusted format header. 574@item serial=@var{serial} 575This option specifies the serial number to assign to the device. 576@item addr=@var{addr} 577Specify the controller's PCI address (if=virtio only). 578@item werror=@var{action},rerror=@var{action} 579Specify which @var{action} to take on write and read errors. Valid actions are: 580"ignore" (ignore the error and try to continue), "stop" (pause QEMU), 581"report" (report the error to the guest), "enospc" (pause QEMU only if the 582host disk is full; report the error to the guest otherwise). 583The default setting is @option{werror=enospc} and @option{rerror=report}. 584@item readonly 585Open drive @option{file} as read-only. Guest write attempts will fail. 586@item copy-on-read=@var{copy-on-read} 587@var{copy-on-read} is "on" or "off" and enables whether to copy read backing 588file sectors into the image file. 589@item detect-zeroes=@var{detect-zeroes} 590@var{detect-zeroes} is "off", "on" or "unmap" and enables the automatic 591conversion of plain zero writes by the OS to driver specific optimized 592zero write commands. You may even choose "unmap" if @var{discard} is set 593to "unmap" to allow a zero write to be converted to an UNMAP operation. 594@end table 595 596By default, the @option{cache=writeback} mode is used. It will report data 597writes as completed as soon as the data is present in the host page cache. 598This is safe as long as your guest OS makes sure to correctly flush disk caches 599where needed. If your guest OS does not handle volatile disk write caches 600correctly and your host crashes or loses power, then the guest may experience 601data corruption. 602 603For such guests, you should consider using @option{cache=writethrough}. This 604means that the host page cache will be used to read and write data, but write 605notification will be sent to the guest only after QEMU has made sure to flush 606each write to the disk. Be aware that this has a major impact on performance. 607 608The host page cache can be avoided entirely with @option{cache=none}. This will 609attempt to do disk IO directly to the guest's memory. QEMU may still perform 610an internal copy of the data. Note that this is considered a writeback mode and 611the guest OS must handle the disk write cache correctly in order to avoid data 612corruption on host crashes. 613 614The host page cache can be avoided while only sending write notifications to 615the guest when the data has been flushed to the disk using 616@option{cache=directsync}. 617 618In case you don't care about data integrity over host failures, use 619@option{cache=unsafe}. This option tells QEMU that it never needs to write any 620data to the disk but can instead keep things in cache. If anything goes wrong, 621like your host losing power, the disk storage getting disconnected accidentally, 622etc. your image will most probably be rendered unusable. When using 623the @option{-snapshot} option, unsafe caching is always used. 624 625Copy-on-read avoids accessing the same backing file sectors repeatedly and is 626useful when the backing file is over a slow network. By default copy-on-read 627is off. 628 629Instead of @option{-cdrom} you can use: 630@example 631qemu-system-i386 -drive file=file,index=2,media=cdrom 632@end example 633 634Instead of @option{-hda}, @option{-hdb}, @option{-hdc}, @option{-hdd}, you can 635use: 636@example 637qemu-system-i386 -drive file=file,index=0,media=disk 638qemu-system-i386 -drive file=file,index=1,media=disk 639qemu-system-i386 -drive file=file,index=2,media=disk 640qemu-system-i386 -drive file=file,index=3,media=disk 641@end example 642 643You can open an image using pre-opened file descriptors from an fd set: 644@example 645qemu-system-i386 646-add-fd fd=3,set=2,opaque="rdwr:/path/to/file" 647-add-fd fd=4,set=2,opaque="rdonly:/path/to/file" 648-drive file=/dev/fdset/2,index=0,media=disk 649@end example 650 651You can connect a CDROM to the slave of ide0: 652@example 653qemu-system-i386 -drive file=file,if=ide,index=1,media=cdrom 654@end example 655 656If you don't specify the "file=" argument, you define an empty drive: 657@example 658qemu-system-i386 -drive if=ide,index=1,media=cdrom 659@end example 660 661You can connect a SCSI disk with unit ID 6 on the bus #0: 662@example 663qemu-system-i386 -drive file=file,if=scsi,bus=0,unit=6 664@end example 665 666Instead of @option{-fda}, @option{-fdb}, you can use: 667@example 668qemu-system-i386 -drive file=file,index=0,if=floppy 669qemu-system-i386 -drive file=file,index=1,if=floppy 670@end example 671 672By default, @var{interface} is "ide" and @var{index} is automatically 673incremented: 674@example 675qemu-system-i386 -drive file=a -drive file=b" 676@end example 677is interpreted like: 678@example 679qemu-system-i386 -hda a -hdb b 680@end example 681ETEXI 682 683DEF("mtdblock", HAS_ARG, QEMU_OPTION_mtdblock, 684 "-mtdblock file use 'file' as on-board Flash memory image\n", 685 QEMU_ARCH_ALL) 686STEXI 687@item -mtdblock @var{file} 688@findex -mtdblock 689Use @var{file} as on-board Flash memory image. 690ETEXI 691 692DEF("sd", HAS_ARG, QEMU_OPTION_sd, 693 "-sd file use 'file' as SecureDigital card image\n", QEMU_ARCH_ALL) 694STEXI 695@item -sd @var{file} 696@findex -sd 697Use @var{file} as SecureDigital card image. 698ETEXI 699 700DEF("pflash", HAS_ARG, QEMU_OPTION_pflash, 701 "-pflash file use 'file' as a parallel flash image\n", QEMU_ARCH_ALL) 702STEXI 703@item -pflash @var{file} 704@findex -pflash 705Use @var{file} as a parallel flash image. 706ETEXI 707 708DEF("snapshot", 0, QEMU_OPTION_snapshot, 709 "-snapshot write to temporary files instead of disk image files\n", 710 QEMU_ARCH_ALL) 711STEXI 712@item -snapshot 713@findex -snapshot 714Write to temporary files instead of disk image files. In this case, 715the raw disk image you use is not written back. You can however force 716the write back by pressing @key{C-a s} (@pxref{disk_images}). 717ETEXI 718 719DEF("hdachs", HAS_ARG, QEMU_OPTION_hdachs, \ 720 "-hdachs c,h,s[,t]\n" \ 721 " force hard disk 0 physical geometry and the optional BIOS\n" \ 722 " translation (t=none or lba) (usually QEMU can guess them)\n", 723 QEMU_ARCH_ALL) 724STEXI 725@item -hdachs @var{c},@var{h},@var{s},[,@var{t}] 726@findex -hdachs 727Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <= 728@var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS 729translation mode (@var{t}=none, lba or auto). Usually QEMU can guess 730all those parameters. This option is useful for old MS-DOS disk 731images. 732ETEXI 733 734DEF("fsdev", HAS_ARG, QEMU_OPTION_fsdev, 735 "-fsdev fsdriver,id=id[,path=path,][security_model={mapped-xattr|mapped-file|passthrough|none}]\n" 736 " [,writeout=immediate][,readonly][,socket=socket|sock_fd=sock_fd]\n", 737 QEMU_ARCH_ALL) 738 739STEXI 740 741@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}] 742@findex -fsdev 743Define a new file system device. Valid options are: 744@table @option 745@item @var{fsdriver} 746This option specifies the fs driver backend to use. 747Currently "local", "handle" and "proxy" file system drivers are supported. 748@item id=@var{id} 749Specifies identifier for this device 750@item path=@var{path} 751Specifies the export path for the file system device. Files under 752this path will be available to the 9p client on the guest. 753@item security_model=@var{security_model} 754Specifies the security model to be used for this export path. 755Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none". 756In "passthrough" security model, files are stored using the same 757credentials as they are created on the guest. This requires QEMU 758to run as root. In "mapped-xattr" security model, some of the file 759attributes like uid, gid, mode bits and link target are stored as 760file attributes. For "mapped-file" these attributes are stored in the 761hidden .virtfs_metadata directory. Directories exported by this security model cannot 762interact with other unix tools. "none" security model is same as 763passthrough except the sever won't report failures if it fails to 764set file attributes like ownership. Security model is mandatory 765only for local fsdriver. Other fsdrivers (like handle, proxy) don't take 766security model as a parameter. 767@item writeout=@var{writeout} 768This is an optional argument. The only supported value is "immediate". 769This means that host page cache will be used to read and write data but 770write notification will be sent to the guest only when the data has been 771reported as written by the storage subsystem. 772@item readonly 773Enables exporting 9p share as a readonly mount for guests. By default 774read-write access is given. 775@item socket=@var{socket} 776Enables proxy filesystem driver to use passed socket file for communicating 777with virtfs-proxy-helper 778@item sock_fd=@var{sock_fd} 779Enables proxy filesystem driver to use passed socket descriptor for 780communicating with virtfs-proxy-helper. Usually a helper like libvirt 781will create socketpair and pass one of the fds as sock_fd 782@end table 783 784-fsdev option is used along with -device driver "virtio-9p-pci". 785@item -device virtio-9p-pci,fsdev=@var{id},mount_tag=@var{mount_tag} 786Options for virtio-9p-pci driver are: 787@table @option 788@item fsdev=@var{id} 789Specifies the id value specified along with -fsdev option 790@item mount_tag=@var{mount_tag} 791Specifies the tag name to be used by the guest to mount this export point 792@end table 793 794ETEXI 795 796DEF("virtfs", HAS_ARG, QEMU_OPTION_virtfs, 797 "-virtfs local,path=path,mount_tag=tag,security_model=[mapped-xattr|mapped-file|passthrough|none]\n" 798 " [,writeout=immediate][,readonly][,socket=socket|sock_fd=sock_fd]\n", 799 QEMU_ARCH_ALL) 800 801STEXI 802 803@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}] 804@findex -virtfs 805 806The general form of a Virtual File system pass-through options are: 807@table @option 808@item @var{fsdriver} 809This option specifies the fs driver backend to use. 810Currently "local", "handle" and "proxy" file system drivers are supported. 811@item id=@var{id} 812Specifies identifier for this device 813@item path=@var{path} 814Specifies the export path for the file system device. Files under 815this path will be available to the 9p client on the guest. 816@item security_model=@var{security_model} 817Specifies the security model to be used for this export path. 818Supported security models are "passthrough", "mapped-xattr", "mapped-file" and "none". 819In "passthrough" security model, files are stored using the same 820credentials as they are created on the guest. This requires QEMU 821to run as root. In "mapped-xattr" security model, some of the file 822attributes like uid, gid, mode bits and link target are stored as 823file attributes. For "mapped-file" these attributes are stored in the 824hidden .virtfs_metadata directory. Directories exported by this security model cannot 825interact with other unix tools. "none" security model is same as 826passthrough except the sever won't report failures if it fails to 827set file attributes like ownership. Security model is mandatory only 828for local fsdriver. Other fsdrivers (like handle, proxy) don't take security 829model as a parameter. 830@item writeout=@var{writeout} 831This is an optional argument. The only supported value is "immediate". 832This means that host page cache will be used to read and write data but 833write notification will be sent to the guest only when the data has been 834reported as written by the storage subsystem. 835@item readonly 836Enables exporting 9p share as a readonly mount for guests. By default 837read-write access is given. 838@item socket=@var{socket} 839Enables proxy filesystem driver to use passed socket file for 840communicating with virtfs-proxy-helper. Usually a helper like libvirt 841will create socketpair and pass one of the fds as sock_fd 842@item sock_fd 843Enables proxy filesystem driver to use passed 'sock_fd' as the socket 844descriptor for interfacing with virtfs-proxy-helper 845@end table 846ETEXI 847 848DEF("virtfs_synth", 0, QEMU_OPTION_virtfs_synth, 849 "-virtfs_synth Create synthetic file system image\n", 850 QEMU_ARCH_ALL) 851STEXI 852@item -virtfs_synth 853@findex -virtfs_synth 854Create synthetic file system image 855ETEXI 856 857STEXI 858@end table 859ETEXI 860DEFHEADING() 861 862DEFHEADING(USB options:) 863STEXI 864@table @option 865ETEXI 866 867DEF("usb", 0, QEMU_OPTION_usb, 868 "-usb enable the USB driver (will be the default soon)\n", 869 QEMU_ARCH_ALL) 870STEXI 871@item -usb 872@findex -usb 873Enable the USB driver (will be the default soon) 874ETEXI 875 876DEF("usbdevice", HAS_ARG, QEMU_OPTION_usbdevice, 877 "-usbdevice name add the host or guest USB device 'name'\n", 878 QEMU_ARCH_ALL) 879STEXI 880 881@item -usbdevice @var{devname} 882@findex -usbdevice 883Add the USB device @var{devname}. @xref{usb_devices}. 884 885@table @option 886 887@item mouse 888Virtual Mouse. This will override the PS/2 mouse emulation when activated. 889 890@item tablet 891Pointer device that uses absolute coordinates (like a touchscreen). This 892means QEMU is able to report the mouse position without having to grab the 893mouse. Also overrides the PS/2 mouse emulation when activated. 894 895@item disk:[format=@var{format}]:@var{file} 896Mass storage device based on file. The optional @var{format} argument 897will be used rather than detecting the format. Can be used to specifiy 898@code{format=raw} to avoid interpreting an untrusted format header. 899 900@item host:@var{bus}.@var{addr} 901Pass through the host device identified by @var{bus}.@var{addr} (Linux only). 902 903@item host:@var{vendor_id}:@var{product_id} 904Pass through the host device identified by @var{vendor_id}:@var{product_id} 905(Linux only). 906 907@item serial:[vendorid=@var{vendor_id}][,productid=@var{product_id}]:@var{dev} 908Serial converter to host character device @var{dev}, see @code{-serial} for the 909available devices. 910 911@item braille 912Braille device. This will use BrlAPI to display the braille output on a real 913or fake device. 914 915@item net:@var{options} 916Network adapter that supports CDC ethernet and RNDIS protocols. 917 918@end table 919ETEXI 920 921STEXI 922@end table 923ETEXI 924DEFHEADING() 925 926DEFHEADING(Display options:) 927STEXI 928@table @option 929ETEXI 930 931DEF("display", HAS_ARG, QEMU_OPTION_display, 932 "-display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]\n" 933 " [,window_close=on|off]|curses|none|\n" 934 " gtk[,grab_on_hover=on|off]|\n" 935 " vnc=<display>[,<optargs>]\n" 936 " select display type\n", QEMU_ARCH_ALL) 937STEXI 938@item -display @var{type} 939@findex -display 940Select type of display to use. This option is a replacement for the 941old style -sdl/-curses/... options. Valid values for @var{type} are 942@table @option 943@item sdl 944Display video output via SDL (usually in a separate graphics 945window; see the SDL documentation for other possibilities). 946@item curses 947Display video output via curses. For graphics device models which 948support a text mode, QEMU can display this output using a 949curses/ncurses interface. Nothing is displayed when the graphics 950device is in graphical mode or if the graphics device does not support 951a text mode. Generally only the VGA device models support text mode. 952@item none 953Do not display video output. The guest will still see an emulated 954graphics card, but its output will not be displayed to the QEMU 955user. This option differs from the -nographic option in that it 956only affects what is done with video output; -nographic also changes 957the destination of the serial and parallel port data. 958@item gtk 959Display video output in a GTK window. This interface provides drop-down 960menus and other UI elements to configure and control the VM during 961runtime. 962@item vnc 963Start a VNC server on display <arg> 964@end table 965ETEXI 966 967DEF("nographic", 0, QEMU_OPTION_nographic, 968 "-nographic disable graphical output and redirect serial I/Os to console\n", 969 QEMU_ARCH_ALL) 970STEXI 971@item -nographic 972@findex -nographic 973Normally, QEMU uses SDL to display the VGA output. With this option, 974you can totally disable graphical output so that QEMU is a simple 975command line application. The emulated serial port is redirected on 976the console and muxed with the monitor (unless redirected elsewhere 977explicitly). Therefore, you can still use QEMU to debug a Linux kernel 978with a serial console. Use @key{C-a h} for help on switching between 979the console and monitor. 980ETEXI 981 982DEF("curses", 0, QEMU_OPTION_curses, 983 "-curses use a curses/ncurses interface instead of SDL\n", 984 QEMU_ARCH_ALL) 985STEXI 986@item -curses 987@findex -curses 988Normally, QEMU uses SDL to display the VGA output. With this option, 989QEMU can display the VGA output when in text mode using a 990curses/ncurses interface. Nothing is displayed in graphical mode. 991ETEXI 992 993DEF("no-frame", 0, QEMU_OPTION_no_frame, 994 "-no-frame open SDL window without a frame and window decorations\n", 995 QEMU_ARCH_ALL) 996STEXI 997@item -no-frame 998@findex -no-frame 999Do not use decorations for SDL windows and start them using the whole 1000available screen space. This makes the using QEMU in a dedicated desktop 1001workspace more convenient. 1002ETEXI 1003 1004DEF("alt-grab", 0, QEMU_OPTION_alt_grab, 1005 "-alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)\n", 1006 QEMU_ARCH_ALL) 1007STEXI 1008@item -alt-grab 1009@findex -alt-grab 1010Use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt). Note that this also 1011affects the special keys (for fullscreen, monitor-mode switching, etc). 1012ETEXI 1013 1014DEF("ctrl-grab", 0, QEMU_OPTION_ctrl_grab, 1015 "-ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt)\n", 1016 QEMU_ARCH_ALL) 1017STEXI 1018@item -ctrl-grab 1019@findex -ctrl-grab 1020Use Right-Ctrl to grab mouse (instead of Ctrl-Alt). Note that this also 1021affects the special keys (for fullscreen, monitor-mode switching, etc). 1022ETEXI 1023 1024DEF("no-quit", 0, QEMU_OPTION_no_quit, 1025 "-no-quit disable SDL window close capability\n", QEMU_ARCH_ALL) 1026STEXI 1027@item -no-quit 1028@findex -no-quit 1029Disable SDL window close capability. 1030ETEXI 1031 1032DEF("sdl", 0, QEMU_OPTION_sdl, 1033 "-sdl enable SDL\n", QEMU_ARCH_ALL) 1034STEXI 1035@item -sdl 1036@findex -sdl 1037Enable SDL. 1038ETEXI 1039 1040DEF("spice", HAS_ARG, QEMU_OPTION_spice, 1041 "-spice [port=port][,tls-port=secured-port][,x509-dir=<dir>]\n" 1042 " [,x509-key-file=<file>][,x509-key-password=<file>]\n" 1043 " [,x509-cert-file=<file>][,x509-cacert-file=<file>]\n" 1044 " [,x509-dh-key-file=<file>][,addr=addr][,ipv4|ipv6|unix]\n" 1045 " [,tls-ciphers=<list>]\n" 1046 " [,tls-channel=[main|display|cursor|inputs|record|playback]]\n" 1047 " [,plaintext-channel=[main|display|cursor|inputs|record|playback]]\n" 1048 " [,sasl][,password=<secret>][,disable-ticketing]\n" 1049 " [,image-compression=[auto_glz|auto_lz|quic|glz|lz|off]]\n" 1050 " [,jpeg-wan-compression=[auto|never|always]]\n" 1051 " [,zlib-glz-wan-compression=[auto|never|always]]\n" 1052 " [,streaming-video=[off|all|filter]][,disable-copy-paste]\n" 1053 " [,disable-agent-file-xfer][,agent-mouse=[on|off]]\n" 1054 " [,playback-compression=[on|off]][,seamless-migration=[on|off]]\n" 1055 " [,gl=[on|off]]\n" 1056 " enable spice\n" 1057 " at least one of {port, tls-port} is mandatory\n", 1058 QEMU_ARCH_ALL) 1059STEXI 1060@item -spice @var{option}[,@var{option}[,...]] 1061@findex -spice 1062Enable the spice remote desktop protocol. Valid options are 1063 1064@table @option 1065 1066@item port=<nr> 1067Set the TCP port spice is listening on for plaintext channels. 1068 1069@item addr=<addr> 1070Set the IP address spice is listening on. Default is any address. 1071 1072@item ipv4 1073@itemx ipv6 1074@itemx unix 1075Force using the specified IP version. 1076 1077@item password=<secret> 1078Set the password you need to authenticate. 1079 1080@item sasl 1081Require that the client use SASL to authenticate with the spice. 1082The exact choice of authentication method used is controlled from the 1083system / user's SASL configuration file for the 'qemu' service. This 1084is typically found in /etc/sasl2/qemu.conf. If running QEMU as an 1085unprivileged user, an environment variable SASL_CONF_PATH can be used 1086to make it search alternate locations for the service config. 1087While some SASL auth methods can also provide data encryption (eg GSSAPI), 1088it is recommended that SASL always be combined with the 'tls' and 1089'x509' settings to enable use of SSL and server certificates. This 1090ensures a data encryption preventing compromise of authentication 1091credentials. 1092 1093@item disable-ticketing 1094Allow client connects without authentication. 1095 1096@item disable-copy-paste 1097Disable copy paste between the client and the guest. 1098 1099@item disable-agent-file-xfer 1100Disable spice-vdagent based file-xfer between the client and the guest. 1101 1102@item tls-port=<nr> 1103Set the TCP port spice is listening on for encrypted channels. 1104 1105@item x509-dir=<dir> 1106Set the x509 file directory. Expects same filenames as -vnc $display,x509=$dir 1107 1108@item x509-key-file=<file> 1109@itemx x509-key-password=<file> 1110@itemx x509-cert-file=<file> 1111@itemx x509-cacert-file=<file> 1112@itemx x509-dh-key-file=<file> 1113The x509 file names can also be configured individually. 1114 1115@item tls-ciphers=<list> 1116Specify which ciphers to use. 1117 1118@item tls-channel=[main|display|cursor|inputs|record|playback] 1119@itemx plaintext-channel=[main|display|cursor|inputs|record|playback] 1120Force specific channel to be used with or without TLS encryption. The 1121options can be specified multiple times to configure multiple 1122channels. The special name "default" can be used to set the default 1123mode. For channels which are not explicitly forced into one mode the 1124spice client is allowed to pick tls/plaintext as he pleases. 1125 1126@item image-compression=[auto_glz|auto_lz|quic|glz|lz|off] 1127Configure image compression (lossless). 1128Default is auto_glz. 1129 1130@item jpeg-wan-compression=[auto|never|always] 1131@itemx zlib-glz-wan-compression=[auto|never|always] 1132Configure wan image compression (lossy for slow links). 1133Default is auto. 1134 1135@item streaming-video=[off|all|filter] 1136Configure video stream detection. Default is filter. 1137 1138@item agent-mouse=[on|off] 1139Enable/disable passing mouse events via vdagent. Default is on. 1140 1141@item playback-compression=[on|off] 1142Enable/disable audio stream compression (using celt 0.5.1). Default is on. 1143 1144@item seamless-migration=[on|off] 1145Enable/disable spice seamless migration. Default is off. 1146 1147@item gl=[on|off] 1148Enable/disable OpenGL context. Default is off. 1149 1150@end table 1151ETEXI 1152 1153DEF("portrait", 0, QEMU_OPTION_portrait, 1154 "-portrait rotate graphical output 90 deg left (only PXA LCD)\n", 1155 QEMU_ARCH_ALL) 1156STEXI 1157@item -portrait 1158@findex -portrait 1159Rotate graphical output 90 deg left (only PXA LCD). 1160ETEXI 1161 1162DEF("rotate", HAS_ARG, QEMU_OPTION_rotate, 1163 "-rotate <deg> rotate graphical output some deg left (only PXA LCD)\n", 1164 QEMU_ARCH_ALL) 1165STEXI 1166@item -rotate @var{deg} 1167@findex -rotate 1168Rotate graphical output some deg left (only PXA LCD). 1169ETEXI 1170 1171DEF("vga", HAS_ARG, QEMU_OPTION_vga, 1172 "-vga [std|cirrus|vmware|qxl|xenfb|tcx|cg3|virtio|none]\n" 1173 " select video card type\n", QEMU_ARCH_ALL) 1174STEXI 1175@item -vga @var{type} 1176@findex -vga 1177Select type of VGA card to emulate. Valid values for @var{type} are 1178@table @option 1179@item cirrus 1180Cirrus Logic GD5446 Video card. All Windows versions starting from 1181Windows 95 should recognize and use this graphic card. For optimal 1182performances, use 16 bit color depth in the guest and the host OS. 1183(This one is the default) 1184@item std 1185Standard VGA card with Bochs VBE extensions. If your guest OS 1186supports the VESA 2.0 VBE extensions (e.g. Windows XP) and if you want 1187to use high resolution modes (>= 1280x1024x16) then you should use 1188this option. 1189@item vmware 1190VMWare SVGA-II compatible adapter. Use it if you have sufficiently 1191recent XFree86/XOrg server or Windows guest with a driver for this 1192card. 1193@item qxl 1194QXL paravirtual graphic card. It is VGA compatible (including VESA 11952.0 VBE support). Works best with qxl guest drivers installed though. 1196Recommended choice when using the spice protocol. 1197@item tcx 1198(sun4m only) Sun TCX framebuffer. This is the default framebuffer for 1199sun4m machines and offers both 8-bit and 24-bit colour depths at a 1200fixed resolution of 1024x768. 1201@item cg3 1202(sun4m only) Sun cgthree framebuffer. This is a simple 8-bit framebuffer 1203for sun4m machines available in both 1024x768 (OpenBIOS) and 1152x900 (OBP) 1204resolutions aimed at people wishing to run older Solaris versions. 1205@item virtio 1206Virtio VGA card. 1207@item none 1208Disable VGA card. 1209@end table 1210ETEXI 1211 1212DEF("full-screen", 0, QEMU_OPTION_full_screen, 1213 "-full-screen start in full screen\n", QEMU_ARCH_ALL) 1214STEXI 1215@item -full-screen 1216@findex -full-screen 1217Start in full screen. 1218ETEXI 1219 1220DEF("g", 1, QEMU_OPTION_g , 1221 "-g WxH[xDEPTH] Set the initial graphical resolution and depth\n", 1222 QEMU_ARCH_PPC | QEMU_ARCH_SPARC) 1223STEXI 1224@item -g @var{width}x@var{height}[x@var{depth}] 1225@findex -g 1226Set the initial graphical resolution and depth (PPC, SPARC only). 1227ETEXI 1228 1229DEF("vnc", HAS_ARG, QEMU_OPTION_vnc , 1230 "-vnc display start a VNC server on display\n", QEMU_ARCH_ALL) 1231STEXI 1232@item -vnc @var{display}[,@var{option}[,@var{option}[,...]]] 1233@findex -vnc 1234Normally, QEMU uses SDL to display the VGA output. With this option, 1235you can have QEMU listen on VNC display @var{display} and redirect the VGA 1236display over the VNC session. It is very useful to enable the usb 1237tablet device when using this option (option @option{-usbdevice 1238tablet}). When using the VNC display, you must use the @option{-k} 1239parameter to set the keyboard layout if you are not using en-us. Valid 1240syntax for the @var{display} is 1241 1242@table @option 1243 1244@item @var{host}:@var{d} 1245 1246TCP connections will only be allowed from @var{host} on display @var{d}. 1247By convention the TCP port is 5900+@var{d}. Optionally, @var{host} can 1248be omitted in which case the server will accept connections from any host. 1249 1250@item unix:@var{path} 1251 1252Connections will be allowed over UNIX domain sockets where @var{path} is the 1253location of a unix socket to listen for connections on. 1254 1255@item none 1256 1257VNC is initialized but not started. The monitor @code{change} command 1258can be used to later start the VNC server. 1259 1260@end table 1261 1262Following the @var{display} value there may be one or more @var{option} flags 1263separated by commas. Valid options are 1264 1265@table @option 1266 1267@item reverse 1268 1269Connect to a listening VNC client via a ``reverse'' connection. The 1270client is specified by the @var{display}. For reverse network 1271connections (@var{host}:@var{d},@code{reverse}), the @var{d} argument 1272is a TCP port number, not a display number. 1273 1274@item websocket 1275 1276Opens an additional TCP listening port dedicated to VNC Websocket connections. 1277By definition the Websocket port is 5700+@var{display}. If @var{host} is 1278specified connections will only be allowed from this host. 1279As an alternative the Websocket port could be specified by using 1280@code{websocket}=@var{port}. 1281If no TLS credentials are provided, the websocket connection runs in 1282unencrypted mode. If TLS credentials are provided, the websocket connection 1283requires encrypted client connections. 1284 1285@item password 1286 1287Require that password based authentication is used for client connections. 1288 1289The password must be set separately using the @code{set_password} command in 1290the @ref{pcsys_monitor}. The syntax to change your password is: 1291@code{set_password <protocol> <password>} where <protocol> could be either 1292"vnc" or "spice". 1293 1294If you would like to change <protocol> password expiration, you should use 1295@code{expire_password <protocol> <expiration-time>} where expiration time could 1296be one of the following options: now, never, +seconds or UNIX time of 1297expiration, e.g. +60 to make password expire in 60 seconds, or 1335196800 1298to make password expire on "Mon Apr 23 12:00:00 EDT 2012" (UNIX time for this 1299date and time). 1300 1301You can also use keywords "now" or "never" for the expiration time to 1302allow <protocol> password to expire immediately or never expire. 1303 1304@item tls-creds=@var{ID} 1305 1306Provides the ID of a set of TLS credentials to use to secure the 1307VNC server. They will apply to both the normal VNC server socket 1308and the websocket socket (if enabled). Setting TLS credentials 1309will cause the VNC server socket to enable the VeNCrypt auth 1310mechanism. The credentials should have been previously created 1311using the @option{-object tls-creds} argument. 1312 1313The @option{tls-creds} parameter obsoletes the @option{tls}, 1314@option{x509}, and @option{x509verify} options, and as such 1315it is not permitted to set both new and old type options at 1316the same time. 1317 1318@item tls 1319 1320Require that client use TLS when communicating with the VNC server. This 1321uses anonymous TLS credentials so is susceptible to a man-in-the-middle 1322attack. It is recommended that this option be combined with either the 1323@option{x509} or @option{x509verify} options. 1324 1325This option is now deprecated in favor of using the @option{tls-creds} 1326argument. 1327 1328@item x509=@var{/path/to/certificate/dir} 1329 1330Valid if @option{tls} is specified. Require that x509 credentials are used 1331for negotiating the TLS session. The server will send its x509 certificate 1332to the client. It is recommended that a password be set on the VNC server 1333to provide authentication of the client when this is used. The path following 1334this option specifies where the x509 certificates are to be loaded from. 1335See the @ref{vnc_security} section for details on generating certificates. 1336 1337This option is now deprecated in favour of using the @option{tls-creds} 1338argument. 1339 1340@item x509verify=@var{/path/to/certificate/dir} 1341 1342Valid if @option{tls} is specified. Require that x509 credentials are used 1343for negotiating the TLS session. The server will send its x509 certificate 1344to the client, and request that the client send its own x509 certificate. 1345The server will validate the client's certificate against the CA certificate, 1346and reject clients when validation fails. If the certificate authority is 1347trusted, this is a sufficient authentication mechanism. You may still wish 1348to set a password on the VNC server as a second authentication layer. The 1349path following this option specifies where the x509 certificates are to 1350be loaded from. See the @ref{vnc_security} section for details on generating 1351certificates. 1352 1353This option is now deprecated in favour of using the @option{tls-creds} 1354argument. 1355 1356@item sasl 1357 1358Require that the client use SASL to authenticate with the VNC server. 1359The exact choice of authentication method used is controlled from the 1360system / user's SASL configuration file for the 'qemu' service. This 1361is typically found in /etc/sasl2/qemu.conf. If running QEMU as an 1362unprivileged user, an environment variable SASL_CONF_PATH can be used 1363to make it search alternate locations for the service config. 1364While some SASL auth methods can also provide data encryption (eg GSSAPI), 1365it is recommended that SASL always be combined with the 'tls' and 1366'x509' settings to enable use of SSL and server certificates. This 1367ensures a data encryption preventing compromise of authentication 1368credentials. See the @ref{vnc_security} section for details on using 1369SASL authentication. 1370 1371@item acl 1372 1373Turn on access control lists for checking of the x509 client certificate 1374and SASL party. For x509 certs, the ACL check is made against the 1375certificate's distinguished name. This is something that looks like 1376@code{C=GB,O=ACME,L=Boston,CN=bob}. For SASL party, the ACL check is 1377made against the username, which depending on the SASL plugin, may 1378include a realm component, eg @code{bob} or @code{bob@@EXAMPLE.COM}. 1379When the @option{acl} flag is set, the initial access list will be 1380empty, with a @code{deny} policy. Thus no one will be allowed to 1381use the VNC server until the ACLs have been loaded. This can be 1382achieved using the @code{acl} monitor command. 1383 1384@item lossy 1385 1386Enable lossy compression methods (gradient, JPEG, ...). If this 1387option is set, VNC client may receive lossy framebuffer updates 1388depending on its encoding settings. Enabling this option can save 1389a lot of bandwidth at the expense of quality. 1390 1391@item non-adaptive 1392 1393Disable adaptive encodings. Adaptive encodings are enabled by default. 1394An adaptive encoding will try to detect frequently updated screen regions, 1395and send updates in these regions using a lossy encoding (like JPEG). 1396This can be really helpful to save bandwidth when playing videos. Disabling 1397adaptive encodings restores the original static behavior of encodings 1398like Tight. 1399 1400@item share=[allow-exclusive|force-shared|ignore] 1401 1402Set display sharing policy. 'allow-exclusive' allows clients to ask 1403for exclusive access. As suggested by the rfb spec this is 1404implemented by dropping other connections. Connecting multiple 1405clients in parallel requires all clients asking for a shared session 1406(vncviewer: -shared switch). This is the default. 'force-shared' 1407disables exclusive client access. Useful for shared desktop sessions, 1408where you don't want someone forgetting specify -shared disconnect 1409everybody else. 'ignore' completely ignores the shared flag and 1410allows everybody connect unconditionally. Doesn't conform to the rfb 1411spec but is traditional QEMU behavior. 1412 1413@end table 1414ETEXI 1415 1416STEXI 1417@end table 1418ETEXI 1419ARCHHEADING(, QEMU_ARCH_I386) 1420 1421ARCHHEADING(i386 target only:, QEMU_ARCH_I386) 1422STEXI 1423@table @option 1424ETEXI 1425 1426DEF("win2k-hack", 0, QEMU_OPTION_win2k_hack, 1427 "-win2k-hack use it when installing Windows 2000 to avoid a disk full bug\n", 1428 QEMU_ARCH_I386) 1429STEXI 1430@item -win2k-hack 1431@findex -win2k-hack 1432Use it when installing Windows 2000 to avoid a disk full bug. After 1433Windows 2000 is installed, you no longer need this option (this option 1434slows down the IDE transfers). 1435ETEXI 1436 1437HXCOMM Deprecated by -rtc 1438DEF("rtc-td-hack", 0, QEMU_OPTION_rtc_td_hack, "", QEMU_ARCH_I386) 1439 1440DEF("no-fd-bootchk", 0, QEMU_OPTION_no_fd_bootchk, 1441 "-no-fd-bootchk disable boot signature checking for floppy disks\n", 1442 QEMU_ARCH_I386) 1443STEXI 1444@item -no-fd-bootchk 1445@findex -no-fd-bootchk 1446Disable boot signature checking for floppy disks in BIOS. May 1447be needed to boot from old floppy disks. 1448ETEXI 1449 1450DEF("no-acpi", 0, QEMU_OPTION_no_acpi, 1451 "-no-acpi disable ACPI\n", QEMU_ARCH_I386 | QEMU_ARCH_ARM) 1452STEXI 1453@item -no-acpi 1454@findex -no-acpi 1455Disable ACPI (Advanced Configuration and Power Interface) support. Use 1456it if your guest OS complains about ACPI problems (PC target machine 1457only). 1458ETEXI 1459 1460DEF("no-hpet", 0, QEMU_OPTION_no_hpet, 1461 "-no-hpet disable HPET\n", QEMU_ARCH_I386) 1462STEXI 1463@item -no-hpet 1464@findex -no-hpet 1465Disable HPET support. 1466ETEXI 1467 1468DEF("acpitable", HAS_ARG, QEMU_OPTION_acpitable, 1469 "-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" 1470 " ACPI table description\n", QEMU_ARCH_I386) 1471STEXI 1472@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}]...] 1473@findex -acpitable 1474Add ACPI table with specified header fields and context from specified files. 1475For file=, take whole ACPI table from the specified files, including all 1476ACPI headers (possible overridden by other options). 1477For data=, only data 1478portion of the table is used, all header information is specified in the 1479command line. 1480If a SLIC table is supplied to QEMU, then the SLIC's oem_id and oem_table_id 1481fields will override the same in the RSDT and the FADT (a.k.a. FACP), in order 1482to ensure the field matches required by the Microsoft SLIC spec and the ACPI 1483spec. 1484ETEXI 1485 1486DEF("smbios", HAS_ARG, QEMU_OPTION_smbios, 1487 "-smbios file=binary\n" 1488 " load SMBIOS entry from binary file\n" 1489 "-smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]\n" 1490 " [,uefi=on|off]\n" 1491 " specify SMBIOS type 0 fields\n" 1492 "-smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]\n" 1493 " [,uuid=uuid][,sku=str][,family=str]\n" 1494 " specify SMBIOS type 1 fields\n" 1495 "-smbios type=2[,manufacturer=str][,product=str][,version=str][,serial=str]\n" 1496 " [,asset=str][,location=str]\n" 1497 " specify SMBIOS type 2 fields\n" 1498 "-smbios type=3[,manufacturer=str][,version=str][,serial=str][,asset=str]\n" 1499 " [,sku=str]\n" 1500 " specify SMBIOS type 3 fields\n" 1501 "-smbios type=4[,sock_pfx=str][,manufacturer=str][,version=str][,serial=str]\n" 1502 " [,asset=str][,part=str]\n" 1503 " specify SMBIOS type 4 fields\n" 1504 "-smbios type=17[,loc_pfx=str][,bank=str][,manufacturer=str][,serial=str]\n" 1505 " [,asset=str][,part=str][,speed=%d]\n" 1506 " specify SMBIOS type 17 fields\n", 1507 QEMU_ARCH_I386 | QEMU_ARCH_ARM) 1508STEXI 1509@item -smbios file=@var{binary} 1510@findex -smbios 1511Load SMBIOS entry from binary file. 1512 1513@item -smbios type=0[,vendor=@var{str}][,version=@var{str}][,date=@var{str}][,release=@var{%d.%d}][,uefi=on|off] 1514Specify SMBIOS type 0 fields 1515 1516@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}] 1517Specify SMBIOS type 1 fields 1518 1519@item -smbios type=2[,manufacturer=@var{str}][,product=@var{str}][,version=@var{str}][,serial=@var{str}][,asset=@var{str}][,location=@var{str}][,family=@var{str}] 1520Specify SMBIOS type 2 fields 1521 1522@item -smbios type=3[,manufacturer=@var{str}][,version=@var{str}][,serial=@var{str}][,asset=@var{str}][,sku=@var{str}] 1523Specify SMBIOS type 3 fields 1524 1525@item -smbios type=4[,sock_pfx=@var{str}][,manufacturer=@var{str}][,version=@var{str}][,serial=@var{str}][,asset=@var{str}][,part=@var{str}] 1526Specify SMBIOS type 4 fields 1527 1528@item -smbios type=17[,loc_pfx=@var{str}][,bank=@var{str}][,manufacturer=@var{str}][,serial=@var{str}][,asset=@var{str}][,part=@var{str}][,speed=@var{%d}] 1529Specify SMBIOS type 17 fields 1530ETEXI 1531 1532STEXI 1533@end table 1534ETEXI 1535DEFHEADING() 1536 1537DEFHEADING(Network options:) 1538STEXI 1539@table @option 1540ETEXI 1541 1542HXCOMM Legacy slirp options (now moved to -net user): 1543#ifdef CONFIG_SLIRP 1544DEF("tftp", HAS_ARG, QEMU_OPTION_tftp, "", QEMU_ARCH_ALL) 1545DEF("bootp", HAS_ARG, QEMU_OPTION_bootp, "", QEMU_ARCH_ALL) 1546DEF("redir", HAS_ARG, QEMU_OPTION_redir, "", QEMU_ARCH_ALL) 1547#ifndef _WIN32 1548DEF("smb", HAS_ARG, QEMU_OPTION_smb, "", QEMU_ARCH_ALL) 1549#endif 1550#endif 1551 1552DEF("netdev", HAS_ARG, QEMU_OPTION_netdev, 1553#ifdef CONFIG_SLIRP 1554 "-netdev user,id=str[,net=addr[/mask]][,host=addr][,restrict=on|off]\n" 1555 " [,hostname=host][,dhcpstart=addr][,dns=addr][,dnssearch=domain][,tftp=dir]\n" 1556 " [,bootfile=f][,hostfwd=rule][,guestfwd=rule]" 1557#ifndef _WIN32 1558 "[,smb=dir[,smbserver=addr]]\n" 1559#endif 1560 " configure a user mode network backend with ID 'str',\n" 1561 " its DHCP server and optional services\n" 1562#endif 1563#ifdef _WIN32 1564 "-netdev tap,id=str,ifname=name\n" 1565 " configure a host TAP network backend with ID 'str'\n" 1566#else 1567 "-netdev tap,id=str[,fd=h][,fds=x:y:...:z][,ifname=name][,script=file][,downscript=dfile]\n" 1568 " [,helper=helper][,sndbuf=nbytes][,vnet_hdr=on|off][,vhost=on|off]\n" 1569 " [,vhostfd=h][,vhostfds=x:y:...:z][,vhostforce=on|off][,queues=n]\n" 1570 " configure a host TAP network backend with ID 'str'\n" 1571 " use network scripts 'file' (default=" DEFAULT_NETWORK_SCRIPT ")\n" 1572 " to configure it and 'dfile' (default=" DEFAULT_NETWORK_DOWN_SCRIPT ")\n" 1573 " to deconfigure it\n" 1574 " use '[down]script=no' to disable script execution\n" 1575 " use network helper 'helper' (default=" DEFAULT_BRIDGE_HELPER ") to\n" 1576 " configure it\n" 1577 " use 'fd=h' to connect to an already opened TAP interface\n" 1578 " use 'fds=x:y:...:z' to connect to already opened multiqueue capable TAP interfaces\n" 1579 " use 'sndbuf=nbytes' to limit the size of the send buffer (the\n" 1580 " default is disabled 'sndbuf=0' to enable flow control set 'sndbuf=1048576')\n" 1581 " use vnet_hdr=off to avoid enabling the IFF_VNET_HDR tap flag\n" 1582 " use vnet_hdr=on to make the lack of IFF_VNET_HDR support an error condition\n" 1583 " use vhost=on to enable experimental in kernel accelerator\n" 1584 " (only has effect for virtio guests which use MSIX)\n" 1585 " use vhostforce=on to force vhost on for non-MSIX virtio guests\n" 1586 " use 'vhostfd=h' to connect to an already opened vhost net device\n" 1587 " use 'vhostfds=x:y:...:z to connect to multiple already opened vhost net devices\n" 1588 " use 'queues=n' to specify the number of queues to be created for multiqueue TAP\n" 1589 "-netdev bridge,id=str[,br=bridge][,helper=helper]\n" 1590 " configure a host TAP network backend with ID 'str' that is\n" 1591 " connected to a bridge (default=" DEFAULT_BRIDGE_INTERFACE ")\n" 1592 " using the program 'helper (default=" DEFAULT_BRIDGE_HELPER ")\n" 1593#endif 1594#ifdef __linux__ 1595 "-netdev l2tpv3,id=str,src=srcaddr,dst=dstaddr[,srcport=srcport][,dstport=dstport]\n" 1596 " [,rxsession=rxsession],txsession=txsession[,ipv6=on/off][,udp=on/off]\n" 1597 " [,cookie64=on/off][,counter][,pincounter][,txcookie=txcookie]\n" 1598 " [,rxcookie=rxcookie][,offset=offset]\n" 1599 " configure a network backend with ID 'str' connected to\n" 1600 " an Ethernet over L2TPv3 pseudowire.\n" 1601 " Linux kernel 3.3+ as well as most routers can talk\n" 1602 " L2TPv3. This transport allows connecting a VM to a VM,\n" 1603 " VM to a router and even VM to Host. It is a nearly-universal\n" 1604 " standard (RFC3391). Note - this implementation uses static\n" 1605 " pre-configured tunnels (same as the Linux kernel).\n" 1606 " use 'src=' to specify source address\n" 1607 " use 'dst=' to specify destination address\n" 1608 " use 'udp=on' to specify udp encapsulation\n" 1609 " use 'srcport=' to specify source udp port\n" 1610 " use 'dstport=' to specify destination udp port\n" 1611 " use 'ipv6=on' to force v6\n" 1612 " L2TPv3 uses cookies to prevent misconfiguration as\n" 1613 " well as a weak security measure\n" 1614 " use 'rxcookie=0x012345678' to specify a rxcookie\n" 1615 " use 'txcookie=0x012345678' to specify a txcookie\n" 1616 " use 'cookie64=on' to set cookie size to 64 bit, otherwise 32\n" 1617 " use 'counter=off' to force a 'cut-down' L2TPv3 with no counter\n" 1618 " use 'pincounter=on' to work around broken counter handling in peer\n" 1619 " use 'offset=X' to add an extra offset between header and data\n" 1620#endif 1621 "-netdev socket,id=str[,fd=h][,listen=[host]:port][,connect=host:port]\n" 1622 " configure a network backend to connect to another network\n" 1623 " using a socket connection\n" 1624 "-netdev socket,id=str[,fd=h][,mcast=maddr:port[,localaddr=addr]]\n" 1625 " configure a network backend to connect to a multicast maddr and port\n" 1626 " use 'localaddr=addr' to specify the host address to send packets from\n" 1627 "-netdev socket,id=str[,fd=h][,udp=host:port][,localaddr=host:port]\n" 1628 " configure a network backend to connect to another network\n" 1629 " using an UDP tunnel\n" 1630#ifdef CONFIG_VDE 1631 "-netdev vde,id=str[,sock=socketpath][,port=n][,group=groupname][,mode=octalmode]\n" 1632 " configure a network backend to connect to port 'n' of a vde switch\n" 1633 " running on host and listening for incoming connections on 'socketpath'.\n" 1634 " Use group 'groupname' and mode 'octalmode' to change default\n" 1635 " ownership and permissions for communication port.\n" 1636#endif 1637#ifdef CONFIG_NETMAP 1638 "-netdev netmap,id=str,ifname=name[,devname=nmname]\n" 1639 " attach to the existing netmap-enabled network interface 'name', or to a\n" 1640 " VALE port (created on the fly) called 'name' ('nmname' is name of the \n" 1641 " netmap device, defaults to '/dev/netmap')\n" 1642#endif 1643 "-netdev vhost-user,id=str,chardev=dev[,vhostforce=on|off]\n" 1644 " configure a vhost-user network, backed by a chardev 'dev'\n" 1645 "-netdev hubport,id=str,hubid=n\n" 1646 " configure a hub port on QEMU VLAN 'n'\n", QEMU_ARCH_ALL) 1647DEF("net", HAS_ARG, QEMU_OPTION_net, 1648 "-net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]\n" 1649 " old way to create a new NIC and connect it to VLAN 'n'\n" 1650 " (use the '-device devtype,netdev=str' option if possible instead)\n" 1651 "-net dump[,vlan=n][,file=f][,len=n]\n" 1652 " dump traffic on vlan 'n' to file 'f' (max n bytes per packet)\n" 1653 "-net none use it alone to have zero network devices. If no -net option\n" 1654 " is provided, the default is '-net nic -net user'\n" 1655 "-net [" 1656#ifdef CONFIG_SLIRP 1657 "user|" 1658#endif 1659 "tap|" 1660 "bridge|" 1661#ifdef CONFIG_VDE 1662 "vde|" 1663#endif 1664#ifdef CONFIG_NETMAP 1665 "netmap|" 1666#endif 1667 "socket][,vlan=n][,option][,option][,...]\n" 1668 " old way to initialize a host network interface\n" 1669 " (use the -netdev option if possible instead)\n", QEMU_ARCH_ALL) 1670STEXI 1671@item -net nic[,vlan=@var{n}][,macaddr=@var{mac}][,model=@var{type}] [,name=@var{name}][,addr=@var{addr}][,vectors=@var{v}] 1672@findex -net 1673Create a new Network Interface Card and connect it to VLAN @var{n} (@var{n} 1674= 0 is the default). The NIC is an e1000 by default on the PC 1675target. Optionally, the MAC address can be changed to @var{mac}, the 1676device address set to @var{addr} (PCI cards only), 1677and a @var{name} can be assigned for use in monitor commands. 1678Optionally, for PCI cards, you can specify the number @var{v} of MSI-X vectors 1679that the card should have; this option currently only affects virtio cards; set 1680@var{v} = 0 to disable MSI-X. If no @option{-net} option is specified, a single 1681NIC is created. QEMU can emulate several different models of network card. 1682Valid values for @var{type} are 1683@code{virtio}, @code{i82551}, @code{i82557b}, @code{i82559er}, 1684@code{ne2k_pci}, @code{ne2k_isa}, @code{pcnet}, @code{rtl8139}, 1685@code{e1000}, @code{smc91c111}, @code{lance} and @code{mcf_fec}. 1686Not all devices are supported on all targets. Use @code{-net nic,model=help} 1687for a list of available devices for your target. 1688 1689@item -netdev user,id=@var{id}[,@var{option}][,@var{option}][,...] 1690@findex -netdev 1691@item -net user[,@var{option}][,@var{option}][,...] 1692Use the user mode network stack which requires no administrator 1693privilege to run. Valid options are: 1694 1695@table @option 1696@item vlan=@var{n} 1697Connect user mode stack to VLAN @var{n} (@var{n} = 0 is the default). 1698 1699@item id=@var{id} 1700@itemx name=@var{name} 1701Assign symbolic name for use in monitor commands. 1702 1703@item net=@var{addr}[/@var{mask}] 1704Set IP network address the guest will see. Optionally specify the netmask, 1705either in the form a.b.c.d or as number of valid top-most bits. Default is 170610.0.2.0/24. 1707 1708@item host=@var{addr} 1709Specify the guest-visible address of the host. Default is the 2nd IP in the 1710guest network, i.e. x.x.x.2. 1711 1712@item restrict=on|off 1713If this option is enabled, the guest will be isolated, i.e. it will not be 1714able to contact the host and no guest IP packets will be routed over the host 1715to the outside. This option does not affect any explicitly set forwarding rules. 1716 1717@item hostname=@var{name} 1718Specifies the client hostname reported by the built-in DHCP server. 1719 1720@item dhcpstart=@var{addr} 1721Specify the first of the 16 IPs the built-in DHCP server can assign. Default 1722is the 15th to 31st IP in the guest network, i.e. x.x.x.15 to x.x.x.31. 1723 1724@item dns=@var{addr} 1725Specify the guest-visible address of the virtual nameserver. The address must 1726be different from the host address. Default is the 3rd IP in the guest network, 1727i.e. x.x.x.3. 1728 1729@item dnssearch=@var{domain} 1730Provides an entry for the domain-search list sent by the built-in 1731DHCP server. More than one domain suffix can be transmitted by specifying 1732this option multiple times. If supported, this will cause the guest to 1733automatically try to append the given domain suffix(es) in case a domain name 1734can not be resolved. 1735 1736Example: 1737@example 1738qemu -net user,dnssearch=mgmt.example.org,dnssearch=example.org [...] 1739@end example 1740 1741@item tftp=@var{dir} 1742When using the user mode network stack, activate a built-in TFTP 1743server. The files in @var{dir} will be exposed as the root of a TFTP server. 1744The TFTP client on the guest must be configured in binary mode (use the command 1745@code{bin} of the Unix TFTP client). 1746 1747@item bootfile=@var{file} 1748When using the user mode network stack, broadcast @var{file} as the BOOTP 1749filename. In conjunction with @option{tftp}, this can be used to network boot 1750a guest from a local directory. 1751 1752Example (using pxelinux): 1753@example 1754qemu-system-i386 -hda linux.img -boot n -net user,tftp=/path/to/tftp/files,bootfile=/pxelinux.0 1755@end example 1756 1757@item smb=@var{dir}[,smbserver=@var{addr}] 1758When using the user mode network stack, activate a built-in SMB 1759server so that Windows OSes can access to the host files in @file{@var{dir}} 1760transparently. The IP address of the SMB server can be set to @var{addr}. By 1761default the 4th IP in the guest network is used, i.e. x.x.x.4. 1762 1763In the guest Windows OS, the line: 1764@example 176510.0.2.4 smbserver 1766@end example 1767must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me) 1768or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000). 1769 1770Then @file{@var{dir}} can be accessed in @file{\\smbserver\qemu}. 1771 1772Note that a SAMBA server must be installed on the host OS. 1773QEMU was tested successfully with smbd versions from Red Hat 9, 1774Fedora Core 3 and OpenSUSE 11.x. 1775 1776@item hostfwd=[tcp|udp]:[@var{hostaddr}]:@var{hostport}-[@var{guestaddr}]:@var{guestport} 1777Redirect incoming TCP or UDP connections to the host port @var{hostport} to 1778the guest IP address @var{guestaddr} on guest port @var{guestport}. If 1779@var{guestaddr} is not specified, its value is x.x.x.15 (default first address 1780given by the built-in DHCP server). By specifying @var{hostaddr}, the rule can 1781be bound to a specific host interface. If no connection type is set, TCP is 1782used. This option can be given multiple times. 1783 1784For example, to redirect host X11 connection from screen 1 to guest 1785screen 0, use the following: 1786 1787@example 1788# on the host 1789qemu-system-i386 -net user,hostfwd=tcp:127.0.0.1:6001-:6000 [...] 1790# this host xterm should open in the guest X11 server 1791xterm -display :1 1792@end example 1793 1794To redirect telnet connections from host port 5555 to telnet port on 1795the guest, use the following: 1796 1797@example 1798# on the host 1799qemu-system-i386 -net user,hostfwd=tcp::5555-:23 [...] 1800telnet localhost 5555 1801@end example 1802 1803Then when you use on the host @code{telnet localhost 5555}, you 1804connect to the guest telnet server. 1805 1806@item guestfwd=[tcp]:@var{server}:@var{port}-@var{dev} 1807@itemx guestfwd=[tcp]:@var{server}:@var{port}-@var{cmd:command} 1808Forward guest TCP connections to the IP address @var{server} on port @var{port} 1809to the character device @var{dev} or to a program executed by @var{cmd:command} 1810which gets spawned for each connection. This option can be given multiple times. 1811 1812You can either use a chardev directly and have that one used throughout QEMU's 1813lifetime, like in the following example: 1814 1815@example 1816# open 10.10.1.1:4321 on bootup, connect 10.0.2.100:1234 to it whenever 1817# the guest accesses it 1818qemu -net user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321 [...] 1819@end example 1820 1821Or you can execute a command on every TCP connection established by the guest, 1822so that QEMU behaves similar to an inetd process for that virtual server: 1823 1824@example 1825# call "netcat 10.10.1.1 4321" on every TCP connection to 10.0.2.100:1234 1826# and connect the TCP stream to its stdin/stdout 1827qemu -net 'user,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321' 1828@end example 1829 1830@end table 1831 1832Note: Legacy stand-alone options -tftp, -bootp, -smb and -redir are still 1833processed and applied to -net user. Mixing them with the new configuration 1834syntax gives undefined results. Their use for new applications is discouraged 1835as they will be removed from future versions. 1836 1837@item -netdev tap,id=@var{id}[,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}] 1838@itemx -net tap[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,ifname=@var{name}][,script=@var{file}][,downscript=@var{dfile}][,helper=@var{helper}] 1839Connect the host TAP network interface @var{name} to VLAN @var{n}. 1840 1841Use the network script @var{file} to configure it and the network script 1842@var{dfile} to deconfigure it. If @var{name} is not provided, the OS 1843automatically provides one. The default network configure script is 1844@file{/etc/qemu-ifup} and the default network deconfigure script is 1845@file{/etc/qemu-ifdown}. Use @option{script=no} or @option{downscript=no} 1846to disable script execution. 1847 1848If running QEMU as an unprivileged user, use the network helper 1849@var{helper} to configure the TAP interface. The default network 1850helper executable is @file{/path/to/qemu-bridge-helper}. 1851 1852@option{fd}=@var{h} can be used to specify the handle of an already 1853opened host TAP interface. 1854 1855Examples: 1856 1857@example 1858#launch a QEMU instance with the default network script 1859qemu-system-i386 linux.img -net nic -net tap 1860@end example 1861 1862@example 1863#launch a QEMU instance with two NICs, each one connected 1864#to a TAP device 1865qemu-system-i386 linux.img \ 1866 -net nic,vlan=0 -net tap,vlan=0,ifname=tap0 \ 1867 -net nic,vlan=1 -net tap,vlan=1,ifname=tap1 1868@end example 1869 1870@example 1871#launch a QEMU instance with the default network helper to 1872#connect a TAP device to bridge br0 1873qemu-system-i386 linux.img \ 1874 -net nic -net tap,"helper=/path/to/qemu-bridge-helper" 1875@end example 1876 1877@item -netdev bridge,id=@var{id}[,br=@var{bridge}][,helper=@var{helper}] 1878@itemx -net bridge[,vlan=@var{n}][,name=@var{name}][,br=@var{bridge}][,helper=@var{helper}] 1879Connect a host TAP network interface to a host bridge device. 1880 1881Use the network helper @var{helper} to configure the TAP interface and 1882attach it to the bridge. The default network helper executable is 1883@file{/path/to/qemu-bridge-helper} and the default bridge 1884device is @file{br0}. 1885 1886Examples: 1887 1888@example 1889#launch a QEMU instance with the default network helper to 1890#connect a TAP device to bridge br0 1891qemu-system-i386 linux.img -net bridge -net nic,model=virtio 1892@end example 1893 1894@example 1895#launch a QEMU instance with the default network helper to 1896#connect a TAP device to bridge qemubr0 1897qemu-system-i386 linux.img -net bridge,br=qemubr0 -net nic,model=virtio 1898@end example 1899 1900@item -netdev socket,id=@var{id}[,fd=@var{h}][,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}] 1901@itemx -net socket[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}] [,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}] 1902 1903Connect the VLAN @var{n} to a remote VLAN in another QEMU virtual 1904machine using a TCP socket connection. If @option{listen} is 1905specified, QEMU waits for incoming connections on @var{port} 1906(@var{host} is optional). @option{connect} is used to connect to 1907another QEMU instance using the @option{listen} option. @option{fd}=@var{h} 1908specifies an already opened TCP socket. 1909 1910Example: 1911@example 1912# launch a first QEMU instance 1913qemu-system-i386 linux.img \ 1914 -net nic,macaddr=52:54:00:12:34:56 \ 1915 -net socket,listen=:1234 1916# connect the VLAN 0 of this instance to the VLAN 0 1917# of the first instance 1918qemu-system-i386 linux.img \ 1919 -net nic,macaddr=52:54:00:12:34:57 \ 1920 -net socket,connect=127.0.0.1:1234 1921@end example 1922 1923@item -netdev socket,id=@var{id}[,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]] 1924@itemx -net socket[,vlan=@var{n}][,name=@var{name}][,fd=@var{h}][,mcast=@var{maddr}:@var{port}[,localaddr=@var{addr}]] 1925 1926Create a VLAN @var{n} shared with another QEMU virtual 1927machines using a UDP multicast socket, effectively making a bus for 1928every QEMU with same multicast address @var{maddr} and @var{port}. 1929NOTES: 1930@enumerate 1931@item 1932Several QEMU can be running on different hosts and share same bus (assuming 1933correct multicast setup for these hosts). 1934@item 1935mcast support is compatible with User Mode Linux (argument @option{eth@var{N}=mcast}), see 1936@url{http://user-mode-linux.sf.net}. 1937@item 1938Use @option{fd=h} to specify an already opened UDP multicast socket. 1939@end enumerate 1940 1941Example: 1942@example 1943# launch one QEMU instance 1944qemu-system-i386 linux.img \ 1945 -net nic,macaddr=52:54:00:12:34:56 \ 1946 -net socket,mcast=230.0.0.1:1234 1947# launch another QEMU instance on same "bus" 1948qemu-system-i386 linux.img \ 1949 -net nic,macaddr=52:54:00:12:34:57 \ 1950 -net socket,mcast=230.0.0.1:1234 1951# launch yet another QEMU instance on same "bus" 1952qemu-system-i386 linux.img \ 1953 -net nic,macaddr=52:54:00:12:34:58 \ 1954 -net socket,mcast=230.0.0.1:1234 1955@end example 1956 1957Example (User Mode Linux compat.): 1958@example 1959# launch QEMU instance (note mcast address selected 1960# is UML's default) 1961qemu-system-i386 linux.img \ 1962 -net nic,macaddr=52:54:00:12:34:56 \ 1963 -net socket,mcast=239.192.168.1:1102 1964# launch UML 1965/path/to/linux ubd0=/path/to/root_fs eth0=mcast 1966@end example 1967 1968Example (send packets from host's 1.2.3.4): 1969@example 1970qemu-system-i386 linux.img \ 1971 -net nic,macaddr=52:54:00:12:34:56 \ 1972 -net socket,mcast=239.192.168.1:1102,localaddr=1.2.3.4 1973@end example 1974 1975@item -netdev l2tpv3,id=@var{id},src=@var{srcaddr},dst=@var{dstaddr}[,srcport=@var{srcport}][,dstport=@var{dstport}],txsession=@var{txsession}[,rxsession=@var{rxsession}][,ipv6][,udp][,cookie64][,counter][,pincounter][,txcookie=@var{txcookie}][,rxcookie=@var{rxcookie}][,offset=@var{offset}] 1976@itemx -net l2tpv3[,vlan=@var{n}][,name=@var{name}],src=@var{srcaddr},dst=@var{dstaddr}[,srcport=@var{srcport}][,dstport=@var{dstport}],txsession=@var{txsession}[,rxsession=@var{rxsession}][,ipv6][,udp][,cookie64][,counter][,pincounter][,txcookie=@var{txcookie}][,rxcookie=@var{rxcookie}][,offset=@var{offset}] 1977Connect VLAN @var{n} to L2TPv3 pseudowire. L2TPv3 (RFC3391) is a popular 1978protocol to transport Ethernet (and other Layer 2) data frames between 1979two systems. It is present in routers, firewalls and the Linux kernel 1980(from version 3.3 onwards). 1981 1982This transport allows a VM to communicate to another VM, router or firewall directly. 1983 1984@item src=@var{srcaddr} 1985 source address (mandatory) 1986@item dst=@var{dstaddr} 1987 destination address (mandatory) 1988@item udp 1989 select udp encapsulation (default is ip). 1990@item srcport=@var{srcport} 1991 source udp port. 1992@item dstport=@var{dstport} 1993 destination udp port. 1994@item ipv6 1995 force v6, otherwise defaults to v4. 1996@item rxcookie=@var{rxcookie} 1997@itemx txcookie=@var{txcookie} 1998 Cookies are a weak form of security in the l2tpv3 specification. 1999Their function is mostly to prevent misconfiguration. By default they are 32 2000bit. 2001@item cookie64 2002 Set cookie size to 64 bit instead of the default 32 2003@item counter=off 2004 Force a 'cut-down' L2TPv3 with no counter as in 2005draft-mkonstan-l2tpext-keyed-ipv6-tunnel-00 2006@item pincounter=on 2007 Work around broken counter handling in peer. This may also help on 2008networks which have packet reorder. 2009@item offset=@var{offset} 2010 Add an extra offset between header and data 2011 2012For example, to attach a VM running on host 4.3.2.1 via L2TPv3 to the bridge br-lan 2013on the remote Linux host 1.2.3.4: 2014@example 2015# Setup tunnel on linux host using raw ip as encapsulation 2016# on 1.2.3.4 2017ip l2tp add tunnel remote 4.3.2.1 local 1.2.3.4 tunnel_id 1 peer_tunnel_id 1 \ 2018 encap udp udp_sport 16384 udp_dport 16384 2019ip l2tp add session tunnel_id 1 name vmtunnel0 session_id \ 2020 0xFFFFFFFF peer_session_id 0xFFFFFFFF 2021ifconfig vmtunnel0 mtu 1500 2022ifconfig vmtunnel0 up 2023brctl addif br-lan vmtunnel0 2024 2025 2026# on 4.3.2.1 2027# launch QEMU instance - if your network has reorder or is very lossy add ,pincounter 2028 2029qemu-system-i386 linux.img -net nic -net l2tpv3,src=4.2.3.1,dst=1.2.3.4,udp,srcport=16384,dstport=16384,rxsession=0xffffffff,txsession=0xffffffff,counter 2030 2031 2032@end example 2033 2034@item -netdev vde,id=@var{id}[,sock=@var{socketpath}][,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}] 2035@itemx -net vde[,vlan=@var{n}][,name=@var{name}][,sock=@var{socketpath}] [,port=@var{n}][,group=@var{groupname}][,mode=@var{octalmode}] 2036Connect VLAN @var{n} to PORT @var{n} of a vde switch running on host and 2037listening for incoming connections on @var{socketpath}. Use GROUP @var{groupname} 2038and MODE @var{octalmode} to change default ownership and permissions for 2039communication port. This option is only available if QEMU has been compiled 2040with vde support enabled. 2041 2042Example: 2043@example 2044# launch vde switch 2045vde_switch -F -sock /tmp/myswitch 2046# launch QEMU instance 2047qemu-system-i386 linux.img -net nic -net vde,sock=/tmp/myswitch 2048@end example 2049 2050@item -netdev hubport,id=@var{id},hubid=@var{hubid} 2051 2052Create a hub port on QEMU "vlan" @var{hubid}. 2053 2054The hubport netdev lets you connect a NIC to a QEMU "vlan" instead of a single 2055netdev. @code{-net} and @code{-device} with parameter @option{vlan} create the 2056required hub automatically. 2057 2058@item -netdev vhost-user,chardev=@var{id}[,vhostforce=on|off][,queues=n] 2059 2060Establish a vhost-user netdev, backed by a chardev @var{id}. The chardev should 2061be a unix domain socket backed one. The vhost-user uses a specifically defined 2062protocol to pass vhost ioctl replacement messages to an application on the other 2063end of the socket. On non-MSIX guests, the feature can be forced with 2064@var{vhostforce}. Use 'queues=@var{n}' to specify the number of queues to 2065be created for multiqueue vhost-user. 2066 2067Example: 2068@example 2069qemu -m 512 -object memory-backend-file,id=mem,size=512M,mem-path=/hugetlbfs,share=on \ 2070 -numa node,memdev=mem \ 2071 -chardev socket,path=/path/to/socket \ 2072 -netdev type=vhost-user,id=net0,chardev=chr0 \ 2073 -device virtio-net-pci,netdev=net0 2074@end example 2075 2076@item -net dump[,vlan=@var{n}][,file=@var{file}][,len=@var{len}] 2077Dump network traffic on VLAN @var{n} to file @var{file} (@file{qemu-vlan0.pcap} by default). 2078At most @var{len} bytes (64k by default) per packet are stored. The file format is 2079libpcap, so it can be analyzed with tools such as tcpdump or Wireshark. 2080Note: For devices created with '-netdev', use '-object filter-dump,...' instead. 2081 2082@item -net none 2083Indicate that no network devices should be configured. It is used to 2084override the default configuration (@option{-net nic -net user}) which 2085is activated if no @option{-net} options are provided. 2086ETEXI 2087 2088STEXI 2089@end table 2090ETEXI 2091DEFHEADING() 2092 2093DEFHEADING(Character device options:) 2094STEXI 2095 2096The general form of a character device option is: 2097@table @option 2098ETEXI 2099 2100DEF("chardev", HAS_ARG, QEMU_OPTION_chardev, 2101 "-chardev null,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2102 "-chardev socket,id=id[,host=host],port=port[,to=to][,ipv4][,ipv6][,nodelay][,reconnect=seconds]\n" 2103 " [,server][,nowait][,telnet][,reconnect=seconds][,mux=on|off]\n" 2104 " [,logfile=PATH][,logappend=on|off][,tls-creds=ID] (tcp)\n" 2105 "-chardev socket,id=id,path=path[,server][,nowait][,telnet][,reconnect=seconds]\n" 2106 " [,mux=on|off][,logfile=PATH][,logappend=on|off] (unix)\n" 2107 "-chardev udp,id=id[,host=host],port=port[,localaddr=localaddr]\n" 2108 " [,localport=localport][,ipv4][,ipv6][,mux=on|off]\n" 2109 " [,logfile=PATH][,logappend=on|off]\n" 2110 "-chardev msmouse,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2111 "-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]\n" 2112 " [,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2113 "-chardev ringbuf,id=id[,size=size][,logfile=PATH][,logappend=on|off]\n" 2114 "-chardev file,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2115 "-chardev pipe,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2116#ifdef _WIN32 2117 "-chardev console,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2118 "-chardev serial,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2119#else 2120 "-chardev pty,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2121 "-chardev stdio,id=id[,mux=on|off][,signal=on|off][,logfile=PATH][,logappend=on|off]\n" 2122#endif 2123#ifdef CONFIG_BRLAPI 2124 "-chardev braille,id=id[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2125#endif 2126#if defined(__linux__) || defined(__sun__) || defined(__FreeBSD__) \ 2127 || defined(__NetBSD__) || defined(__OpenBSD__) || defined(__DragonFly__) 2128 "-chardev serial,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2129 "-chardev tty,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2130#endif 2131#if defined(__linux__) || defined(__FreeBSD__) || defined(__DragonFly__) 2132 "-chardev parallel,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2133 "-chardev parport,id=id,path=path[,mux=on|off][,logfile=PATH][,logappend=on|off]\n" 2134#endif 2135#if defined(CONFIG_SPICE) 2136 "-chardev spicevmc,id=id,name=name[,debug=debug][,logfile=PATH][,logappend=on|off]\n" 2137 "-chardev spiceport,id=id,name=name[,debug=debug][,logfile=PATH][,logappend=on|off]\n" 2138#endif 2139 , QEMU_ARCH_ALL 2140) 2141 2142STEXI 2143@item -chardev @var{backend} ,id=@var{id} [,mux=on|off] [,@var{options}] 2144@findex -chardev 2145Backend is one of: 2146@option{null}, 2147@option{socket}, 2148@option{udp}, 2149@option{msmouse}, 2150@option{vc}, 2151@option{ringbuf}, 2152@option{file}, 2153@option{pipe}, 2154@option{console}, 2155@option{serial}, 2156@option{pty}, 2157@option{stdio}, 2158@option{braille}, 2159@option{tty}, 2160@option{parallel}, 2161@option{parport}, 2162@option{spicevmc}. 2163@option{spiceport}. 2164The specific backend will determine the applicable options. 2165 2166All devices must have an id, which can be any string up to 127 characters long. 2167It is used to uniquely identify this device in other command line directives. 2168 2169A character device may be used in multiplexing mode by multiple front-ends. 2170Specify @option{mux=on} to enable this mode. 2171A multiplexer is a "1:N" device, and here the "1" end is your specified chardev 2172backend, and the "N" end is the various parts of QEMU that can talk to a chardev. 2173If you create a chardev with @option{id=myid} and @option{mux=on}, QEMU will 2174create a multiplexer with your specified ID, and you can then configure multiple 2175front ends to use that chardev ID for their input/output. Up to four different 2176front ends can be connected to a single multiplexed chardev. (Without 2177multiplexing enabled, a chardev can only be used by a single front end.) 2178For instance you could use this to allow a single stdio chardev to be used by 2179two serial ports and the QEMU monitor: 2180 2181@example 2182-chardev stdio,mux=on,id=char0 \ 2183-mon chardev=char0,mode=readline,default \ 2184-serial chardev:char0 \ 2185-serial chardev:char0 2186@end example 2187 2188You can have more than one multiplexer in a system configuration; for instance 2189you could have a TCP port multiplexed between UART 0 and UART 1, and stdio 2190multiplexed between the QEMU monitor and a parallel port: 2191 2192@example 2193-chardev stdio,mux=on,id=char0 \ 2194-mon chardev=char0,mode=readline,default \ 2195-parallel chardev:char0 \ 2196-chardev tcp,...,mux=on,id=char1 \ 2197-serial chardev:char1 \ 2198-serial chardev:char1 2199@end example 2200 2201When you're using a multiplexed character device, some escape sequences are 2202interpreted in the input. @xref{mux_keys, Keys in the character backend 2203multiplexer}. 2204 2205Note that some other command line options may implicitly create multiplexed 2206character backends; for instance @option{-serial mon:stdio} creates a 2207multiplexed stdio backend connected to the serial port and the QEMU monitor, 2208and @option{-nographic} also multiplexes the console and the monitor to 2209stdio. 2210 2211There is currently no support for multiplexing in the other direction 2212(where a single QEMU front end takes input and output from multiple chardevs). 2213 2214Every backend supports the @option{logfile} option, which supplies the path 2215to a file to record all data transmitted via the backend. The @option{logappend} 2216option controls whether the log file will be truncated or appended to when 2217opened. 2218 2219Further options to each backend are described below. 2220 2221@item -chardev null ,id=@var{id} 2222A void device. This device will not emit any data, and will drop any data it 2223receives. The null backend does not take any options. 2224 2225@item -chardev socket ,id=@var{id} [@var{TCP options} or @var{unix options}] [,server] [,nowait] [,telnet] [,reconnect=@var{seconds}] [,tls-creds=@var{id}] 2226 2227Create a two-way stream socket, which can be either a TCP or a unix socket. A 2228unix socket will be created if @option{path} is specified. Behaviour is 2229undefined if TCP options are specified for a unix socket. 2230 2231@option{server} specifies that the socket shall be a listening socket. 2232 2233@option{nowait} specifies that QEMU should not block waiting for a client to 2234connect to a listening socket. 2235 2236@option{telnet} specifies that traffic on the socket should interpret telnet 2237escape sequences. 2238 2239@option{reconnect} sets the timeout for reconnecting on non-server sockets when 2240the remote end goes away. qemu will delay this many seconds and then attempt 2241to reconnect. Zero disables reconnecting, and is the default. 2242 2243@option{tls-creds} requests enablement of the TLS protocol for encryption, 2244and specifies the id of the TLS credentials to use for the handshake. The 2245credentials must be previously created with the @option{-object tls-creds} 2246argument. 2247 2248TCP and unix socket options are given below: 2249 2250@table @option 2251 2252@item TCP options: port=@var{port} [,host=@var{host}] [,to=@var{to}] [,ipv4] [,ipv6] [,nodelay] 2253 2254@option{host} for a listening socket specifies the local address to be bound. 2255For a connecting socket species the remote host to connect to. @option{host} is 2256optional for listening sockets. If not specified it defaults to @code{0.0.0.0}. 2257 2258@option{port} for a listening socket specifies the local port to be bound. For a 2259connecting socket specifies the port on the remote host to connect to. 2260@option{port} can be given as either a port number or a service name. 2261@option{port} is required. 2262 2263@option{to} is only relevant to listening sockets. If it is specified, and 2264@option{port} cannot be bound, QEMU will attempt to bind to subsequent ports up 2265to and including @option{to} until it succeeds. @option{to} must be specified 2266as a port number. 2267 2268@option{ipv4} and @option{ipv6} specify that either IPv4 or IPv6 must be used. 2269If neither is specified the socket may use either protocol. 2270 2271@option{nodelay} disables the Nagle algorithm. 2272 2273@item unix options: path=@var{path} 2274 2275@option{path} specifies the local path of the unix socket. @option{path} is 2276required. 2277 2278@end table 2279 2280@item -chardev udp ,id=@var{id} [,host=@var{host}] ,port=@var{port} [,localaddr=@var{localaddr}] [,localport=@var{localport}] [,ipv4] [,ipv6] 2281 2282Sends all traffic from the guest to a remote host over UDP. 2283 2284@option{host} specifies the remote host to connect to. If not specified it 2285defaults to @code{localhost}. 2286 2287@option{port} specifies the port on the remote host to connect to. @option{port} 2288is required. 2289 2290@option{localaddr} specifies the local address to bind to. If not specified it 2291defaults to @code{0.0.0.0}. 2292 2293@option{localport} specifies the local port to bind to. If not specified any 2294available local port will be used. 2295 2296@option{ipv4} and @option{ipv6} specify that either IPv4 or IPv6 must be used. 2297If neither is specified the device may use either protocol. 2298 2299@item -chardev msmouse ,id=@var{id} 2300 2301Forward QEMU's emulated msmouse events to the guest. @option{msmouse} does not 2302take any options. 2303 2304@item -chardev vc ,id=@var{id} [[,width=@var{width}] [,height=@var{height}]] [[,cols=@var{cols}] [,rows=@var{rows}]] 2305 2306Connect to a QEMU text console. @option{vc} may optionally be given a specific 2307size. 2308 2309@option{width} and @option{height} specify the width and height respectively of 2310the console, in pixels. 2311 2312@option{cols} and @option{rows} specify that the console be sized to fit a text 2313console with the given dimensions. 2314 2315@item -chardev ringbuf ,id=@var{id} [,size=@var{size}] 2316 2317Create a ring buffer with fixed size @option{size}. 2318@var{size} must be a power of two, and defaults to @code{64K}). 2319 2320@item -chardev file ,id=@var{id} ,path=@var{path} 2321 2322Log all traffic received from the guest to a file. 2323 2324@option{path} specifies the path of the file to be opened. This file will be 2325created if it does not already exist, and overwritten if it does. @option{path} 2326is required. 2327 2328@item -chardev pipe ,id=@var{id} ,path=@var{path} 2329 2330Create a two-way connection to the guest. The behaviour differs slightly between 2331Windows hosts and other hosts: 2332 2333On Windows, a single duplex pipe will be created at 2334@file{\\.pipe\@option{path}}. 2335 2336On other hosts, 2 pipes will be created called @file{@option{path}.in} and 2337@file{@option{path}.out}. Data written to @file{@option{path}.in} will be 2338received by the guest. Data written by the guest can be read from 2339@file{@option{path}.out}. QEMU will not create these fifos, and requires them to 2340be present. 2341 2342@option{path} forms part of the pipe path as described above. @option{path} is 2343required. 2344 2345@item -chardev console ,id=@var{id} 2346 2347Send traffic from the guest to QEMU's standard output. @option{console} does not 2348take any options. 2349 2350@option{console} is only available on Windows hosts. 2351 2352@item -chardev serial ,id=@var{id} ,path=@option{path} 2353 2354Send traffic from the guest to a serial device on the host. 2355 2356On Unix hosts serial will actually accept any tty device, 2357not only serial lines. 2358 2359@option{path} specifies the name of the serial device to open. 2360 2361@item -chardev pty ,id=@var{id} 2362 2363Create a new pseudo-terminal on the host and connect to it. @option{pty} does 2364not take any options. 2365 2366@option{pty} is not available on Windows hosts. 2367 2368@item -chardev stdio ,id=@var{id} [,signal=on|off] 2369Connect to standard input and standard output of the QEMU process. 2370 2371@option{signal} controls if signals are enabled on the terminal, that includes 2372exiting QEMU with the key sequence @key{Control-c}. This option is enabled by 2373default, use @option{signal=off} to disable it. 2374 2375@option{stdio} is not available on Windows hosts. 2376 2377@item -chardev braille ,id=@var{id} 2378 2379Connect to a local BrlAPI server. @option{braille} does not take any options. 2380 2381@item -chardev tty ,id=@var{id} ,path=@var{path} 2382 2383@option{tty} is only available on Linux, Sun, FreeBSD, NetBSD, OpenBSD and 2384DragonFlyBSD hosts. It is an alias for @option{serial}. 2385 2386@option{path} specifies the path to the tty. @option{path} is required. 2387 2388@item -chardev parallel ,id=@var{id} ,path=@var{path} 2389@itemx -chardev parport ,id=@var{id} ,path=@var{path} 2390 2391@option{parallel} is only available on Linux, FreeBSD and DragonFlyBSD hosts. 2392 2393Connect to a local parallel port. 2394 2395@option{path} specifies the path to the parallel port device. @option{path} is 2396required. 2397 2398@item -chardev spicevmc ,id=@var{id} ,debug=@var{debug}, name=@var{name} 2399 2400@option{spicevmc} is only available when spice support is built in. 2401 2402@option{debug} debug level for spicevmc 2403 2404@option{name} name of spice channel to connect to 2405 2406Connect to a spice virtual machine channel, such as vdiport. 2407 2408@item -chardev spiceport ,id=@var{id} ,debug=@var{debug}, name=@var{name} 2409 2410@option{spiceport} is only available when spice support is built in. 2411 2412@option{debug} debug level for spicevmc 2413 2414@option{name} name of spice port to connect to 2415 2416Connect to a spice port, allowing a Spice client to handle the traffic 2417identified by a name (preferably a fqdn). 2418ETEXI 2419 2420STEXI 2421@end table 2422ETEXI 2423DEFHEADING() 2424 2425DEFHEADING(Device URL Syntax:) 2426STEXI 2427 2428In addition to using normal file images for the emulated storage devices, 2429QEMU can also use networked resources such as iSCSI devices. These are 2430specified using a special URL syntax. 2431 2432@table @option 2433@item iSCSI 2434iSCSI support allows QEMU to access iSCSI resources directly and use as 2435images for the guest storage. Both disk and cdrom images are supported. 2436 2437Syntax for specifying iSCSI LUNs is 2438``iscsi://<target-ip>[:<port>]/<target-iqn>/<lun>'' 2439 2440By default qemu will use the iSCSI initiator-name 2441'iqn.2008-11.org.linux-kvm[:<name>]' but this can also be set from the command 2442line or a configuration file. 2443 2444Since version Qemu 2.4 it is possible to specify a iSCSI request timeout to detect 2445stalled requests and force a reestablishment of the session. The timeout 2446is specified in seconds. The default is 0 which means no timeout. Libiscsi 24471.15.0 or greater is required for this feature. 2448 2449Example (without authentication): 2450@example 2451qemu-system-i386 -iscsi initiator-name=iqn.2001-04.com.example:my-initiator \ 2452 -cdrom iscsi://192.0.2.1/iqn.2001-04.com.example/2 \ 2453 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1 2454@end example 2455 2456Example (CHAP username/password via URL): 2457@example 2458qemu-system-i386 -drive file=iscsi://user%password@@192.0.2.1/iqn.2001-04.com.example/1 2459@end example 2460 2461Example (CHAP username/password via environment variables): 2462@example 2463LIBISCSI_CHAP_USERNAME="user" \ 2464LIBISCSI_CHAP_PASSWORD="password" \ 2465qemu-system-i386 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1 2466@end example 2467 2468iSCSI support is an optional feature of QEMU and only available when 2469compiled and linked against libiscsi. 2470ETEXI 2471DEF("iscsi", HAS_ARG, QEMU_OPTION_iscsi, 2472 "-iscsi [user=user][,password=password]\n" 2473 " [,header-digest=CRC32C|CR32C-NONE|NONE-CRC32C|NONE\n" 2474 " [,initiator-name=initiator-iqn][,id=target-iqn]\n" 2475 " [,timeout=timeout]\n" 2476 " iSCSI session parameters\n", QEMU_ARCH_ALL) 2477STEXI 2478 2479iSCSI parameters such as username and password can also be specified via 2480a configuration file. See qemu-doc for more information and examples. 2481 2482@item NBD 2483QEMU supports NBD (Network Block Devices) both using TCP protocol as well 2484as Unix Domain Sockets. 2485 2486Syntax for specifying a NBD device using TCP 2487``nbd:<server-ip>:<port>[:exportname=<export>]'' 2488 2489Syntax for specifying a NBD device using Unix Domain Sockets 2490``nbd:unix:<domain-socket>[:exportname=<export>]'' 2491 2492 2493Example for TCP 2494@example 2495qemu-system-i386 --drive file=nbd:192.0.2.1:30000 2496@end example 2497 2498Example for Unix Domain Sockets 2499@example 2500qemu-system-i386 --drive file=nbd:unix:/tmp/nbd-socket 2501@end example 2502 2503@item SSH 2504QEMU supports SSH (Secure Shell) access to remote disks. 2505 2506Examples: 2507@example 2508qemu-system-i386 -drive file=ssh://user@@host/path/to/disk.img 2509qemu-system-i386 -drive file.driver=ssh,file.user=user,file.host=host,file.port=22,file.path=/path/to/disk.img 2510@end example 2511 2512Currently authentication must be done using ssh-agent. Other 2513authentication methods may be supported in future. 2514 2515@item Sheepdog 2516Sheepdog is a distributed storage system for QEMU. 2517QEMU supports using either local sheepdog devices or remote networked 2518devices. 2519 2520Syntax for specifying a sheepdog device 2521@example 2522sheepdog[+tcp|+unix]://[host:port]/vdiname[?socket=path][#snapid|#tag] 2523@end example 2524 2525Example 2526@example 2527qemu-system-i386 --drive file=sheepdog://192.0.2.1:30000/MyVirtualMachine 2528@end example 2529 2530See also @url{http://http://www.osrg.net/sheepdog/}. 2531 2532@item GlusterFS 2533GlusterFS is an user space distributed file system. 2534QEMU supports the use of GlusterFS volumes for hosting VM disk images using 2535TCP, Unix Domain Sockets and RDMA transport protocols. 2536 2537Syntax for specifying a VM disk image on GlusterFS volume is 2538@example 2539gluster[+transport]://[server[:port]]/volname/image[?socket=...] 2540@end example 2541 2542 2543Example 2544@example 2545qemu-system-x86_64 --drive file=gluster://192.0.2.1/testvol/a.img 2546@end example 2547 2548See also @url{http://www.gluster.org}. 2549 2550@item HTTP/HTTPS/FTP/FTPS/TFTP 2551QEMU supports read-only access to files accessed over http(s), ftp(s) and tftp. 2552 2553Syntax using a single filename: 2554@example 2555<protocol>://[<username>[:<password>]@@]<host>/<path> 2556@end example 2557 2558where: 2559@table @option 2560@item protocol 2561'http', 'https', 'ftp', 'ftps', or 'tftp'. 2562 2563@item username 2564Optional username for authentication to the remote server. 2565 2566@item password 2567Optional password for authentication to the remote server. 2568 2569@item host 2570Address of the remote server. 2571 2572@item path 2573Path on the remote server, including any query string. 2574@end table 2575 2576The following options are also supported: 2577@table @option 2578@item url 2579The full URL when passing options to the driver explicitly. 2580 2581@item readahead 2582The amount of data to read ahead with each range request to the remote server. 2583This value may optionally have the suffix 'T', 'G', 'M', 'K', 'k' or 'b'. If it 2584does not have a suffix, it will be assumed to be in bytes. The value must be a 2585multiple of 512 bytes. It defaults to 256k. 2586 2587@item sslverify 2588Whether to verify the remote server's certificate when connecting over SSL. It 2589can have the value 'on' or 'off'. It defaults to 'on'. 2590 2591@item cookie 2592Send this cookie (it can also be a list of cookies separated by ';') with 2593each outgoing request. Only supported when using protocols such as HTTP 2594which support cookies, otherwise ignored. 2595 2596@item timeout 2597Set the timeout in seconds of the CURL connection. This timeout is the time 2598that CURL waits for a response from the remote server to get the size of the 2599image to be downloaded. If not set, the default timeout of 5 seconds is used. 2600@end table 2601 2602Note that when passing options to qemu explicitly, @option{driver} is the value 2603of <protocol>. 2604 2605Example: boot from a remote Fedora 20 live ISO image 2606@example 2607qemu-system-x86_64 --drive media=cdrom,file=http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso,readonly 2608 2609qemu-system-x86_64 --drive media=cdrom,file.driver=http,file.url=http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso,readonly 2610@end example 2611 2612Example: boot from a remote Fedora 20 cloud image using a local overlay for 2613writes, copy-on-read, and a readahead of 64k 2614@example 2615qemu-img create -f qcow2 -o backing_file='json:@{"file.driver":"http",, "file.url":"https://dl.fedoraproject.org/pub/fedora/linux/releases/20/Images/x86_64/Fedora-x86_64-20-20131211.1-sda.qcow2",, "file.readahead":"64k"@}' /tmp/Fedora-x86_64-20-20131211.1-sda.qcow2 2616 2617qemu-system-x86_64 -drive file=/tmp/Fedora-x86_64-20-20131211.1-sda.qcow2,copy-on-read=on 2618@end example 2619 2620Example: boot from an image stored on a VMware vSphere server with a self-signed 2621certificate using a local overlay for writes, a readahead of 64k and a timeout 2622of 10 seconds. 2623@example 2624qemu-img create -f qcow2 -o backing_file='json:@{"file.driver":"https",, "file.url":"https://user:password@@vsphere.example.com/folder/test/test-flat.vmdk?dcPath=Datacenter&dsName=datastore1",, "file.sslverify":"off",, "file.readahead":"64k",, "file.timeout":10@}' /tmp/test.qcow2 2625 2626qemu-system-x86_64 -drive file=/tmp/test.qcow2 2627@end example 2628ETEXI 2629 2630STEXI 2631@end table 2632ETEXI 2633 2634DEFHEADING(Bluetooth(R) options:) 2635STEXI 2636@table @option 2637ETEXI 2638 2639DEF("bt", HAS_ARG, QEMU_OPTION_bt, \ 2640 "-bt hci,null dumb bluetooth HCI - doesn't respond to commands\n" \ 2641 "-bt hci,host[:id]\n" \ 2642 " use host's HCI with the given name\n" \ 2643 "-bt hci[,vlan=n]\n" \ 2644 " emulate a standard HCI in virtual scatternet 'n'\n" \ 2645 "-bt vhci[,vlan=n]\n" \ 2646 " add host computer to virtual scatternet 'n' using VHCI\n" \ 2647 "-bt device:dev[,vlan=n]\n" \ 2648 " emulate a bluetooth device 'dev' in scatternet 'n'\n", 2649 QEMU_ARCH_ALL) 2650STEXI 2651@item -bt hci[...] 2652@findex -bt 2653Defines the function of the corresponding Bluetooth HCI. -bt options 2654are matched with the HCIs present in the chosen machine type. For 2655example when emulating a machine with only one HCI built into it, only 2656the first @code{-bt hci[...]} option is valid and defines the HCI's 2657logic. The Transport Layer is decided by the machine type. Currently 2658the machines @code{n800} and @code{n810} have one HCI and all other 2659machines have none. 2660 2661@anchor{bt-hcis} 2662The following three types are recognized: 2663 2664@table @option 2665@item -bt hci,null 2666(default) The corresponding Bluetooth HCI assumes no internal logic 2667and will not respond to any HCI commands or emit events. 2668 2669@item -bt hci,host[:@var{id}] 2670(@code{bluez} only) The corresponding HCI passes commands / events 2671to / from the physical HCI identified by the name @var{id} (default: 2672@code{hci0}) on the computer running QEMU. Only available on @code{bluez} 2673capable systems like Linux. 2674 2675@item -bt hci[,vlan=@var{n}] 2676Add a virtual, standard HCI that will participate in the Bluetooth 2677scatternet @var{n} (default @code{0}). Similarly to @option{-net} 2678VLANs, devices inside a bluetooth network @var{n} can only communicate 2679with other devices in the same network (scatternet). 2680@end table 2681 2682@item -bt vhci[,vlan=@var{n}] 2683(Linux-host only) Create a HCI in scatternet @var{n} (default 0) attached 2684to the host bluetooth stack instead of to the emulated target. This 2685allows the host and target machines to participate in a common scatternet 2686and communicate. Requires the Linux @code{vhci} driver installed. Can 2687be used as following: 2688 2689@example 2690qemu-system-i386 [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5 2691@end example 2692 2693@item -bt device:@var{dev}[,vlan=@var{n}] 2694Emulate a bluetooth device @var{dev} and place it in network @var{n} 2695(default @code{0}). QEMU can only emulate one type of bluetooth devices 2696currently: 2697 2698@table @option 2699@item keyboard 2700Virtual wireless keyboard implementing the HIDP bluetooth profile. 2701@end table 2702ETEXI 2703 2704STEXI 2705@end table 2706ETEXI 2707DEFHEADING() 2708 2709#ifdef CONFIG_TPM 2710DEFHEADING(TPM device options:) 2711 2712DEF("tpmdev", HAS_ARG, QEMU_OPTION_tpmdev, \ 2713 "-tpmdev passthrough,id=id[,path=path][,cancel-path=path]\n" 2714 " use path to provide path to a character device; default is /dev/tpm0\n" 2715 " use cancel-path to provide path to TPM's cancel sysfs entry; if\n" 2716 " not provided it will be searched for in /sys/class/misc/tpm?/device\n", 2717 QEMU_ARCH_ALL) 2718STEXI 2719 2720The general form of a TPM device option is: 2721@table @option 2722 2723@item -tpmdev @var{backend} ,id=@var{id} [,@var{options}] 2724@findex -tpmdev 2725Backend type must be: 2726@option{passthrough}. 2727 2728The specific backend type will determine the applicable options. 2729The @code{-tpmdev} option creates the TPM backend and requires a 2730@code{-device} option that specifies the TPM frontend interface model. 2731 2732Options to each backend are described below. 2733 2734Use 'help' to print all available TPM backend types. 2735@example 2736qemu -tpmdev help 2737@end example 2738 2739@item -tpmdev passthrough, id=@var{id}, path=@var{path}, cancel-path=@var{cancel-path} 2740 2741(Linux-host only) Enable access to the host's TPM using the passthrough 2742driver. 2743 2744@option{path} specifies the path to the host's TPM device, i.e., on 2745a Linux host this would be @code{/dev/tpm0}. 2746@option{path} is optional and by default @code{/dev/tpm0} is used. 2747 2748@option{cancel-path} specifies the path to the host TPM device's sysfs 2749entry allowing for cancellation of an ongoing TPM command. 2750@option{cancel-path} is optional and by default QEMU will search for the 2751sysfs entry to use. 2752 2753Some notes about using the host's TPM with the passthrough driver: 2754 2755The TPM device accessed by the passthrough driver must not be 2756used by any other application on the host. 2757 2758Since the host's firmware (BIOS/UEFI) has already initialized the TPM, 2759the VM's firmware (BIOS/UEFI) will not be able to initialize the 2760TPM again and may therefore not show a TPM-specific menu that would 2761otherwise allow the user to configure the TPM, e.g., allow the user to 2762enable/disable or activate/deactivate the TPM. 2763Further, if TPM ownership is released from within a VM then the host's TPM 2764will get disabled and deactivated. To enable and activate the 2765TPM again afterwards, the host has to be rebooted and the user is 2766required to enter the firmware's menu to enable and activate the TPM. 2767If the TPM is left disabled and/or deactivated most TPM commands will fail. 2768 2769To create a passthrough TPM use the following two options: 2770@example 2771-tpmdev passthrough,id=tpm0 -device tpm-tis,tpmdev=tpm0 2772@end example 2773Note that the @code{-tpmdev} id is @code{tpm0} and is referenced by 2774@code{tpmdev=tpm0} in the device option. 2775 2776@end table 2777 2778ETEXI 2779 2780DEFHEADING() 2781 2782#endif 2783 2784DEFHEADING(Linux/Multiboot boot specific:) 2785STEXI 2786 2787When using these options, you can use a given Linux or Multiboot 2788kernel without installing it in the disk image. It can be useful 2789for easier testing of various kernels. 2790 2791@table @option 2792ETEXI 2793 2794DEF("kernel", HAS_ARG, QEMU_OPTION_kernel, \ 2795 "-kernel bzImage use 'bzImage' as kernel image\n", QEMU_ARCH_ALL) 2796STEXI 2797@item -kernel @var{bzImage} 2798@findex -kernel 2799Use @var{bzImage} as kernel image. The kernel can be either a Linux kernel 2800or in multiboot format. 2801ETEXI 2802 2803DEF("append", HAS_ARG, QEMU_OPTION_append, \ 2804 "-append cmdline use 'cmdline' as kernel command line\n", QEMU_ARCH_ALL) 2805STEXI 2806@item -append @var{cmdline} 2807@findex -append 2808Use @var{cmdline} as kernel command line 2809ETEXI 2810 2811DEF("initrd", HAS_ARG, QEMU_OPTION_initrd, \ 2812 "-initrd file use 'file' as initial ram disk\n", QEMU_ARCH_ALL) 2813STEXI 2814@item -initrd @var{file} 2815@findex -initrd 2816Use @var{file} as initial ram disk. 2817 2818@item -initrd "@var{file1} arg=foo,@var{file2}" 2819 2820This syntax is only available with multiboot. 2821 2822Use @var{file1} and @var{file2} as modules and pass arg=foo as parameter to the 2823first module. 2824ETEXI 2825 2826DEF("dtb", HAS_ARG, QEMU_OPTION_dtb, \ 2827 "-dtb file use 'file' as device tree image\n", QEMU_ARCH_ALL) 2828STEXI 2829@item -dtb @var{file} 2830@findex -dtb 2831Use @var{file} as a device tree binary (dtb) image and pass it to the kernel 2832on boot. 2833ETEXI 2834 2835STEXI 2836@end table 2837ETEXI 2838DEFHEADING() 2839 2840DEFHEADING(Debug/Expert options:) 2841STEXI 2842@table @option 2843ETEXI 2844 2845DEF("fw_cfg", HAS_ARG, QEMU_OPTION_fwcfg, 2846 "-fw_cfg [name=]<name>,file=<file>\n" 2847 " add named fw_cfg entry from file\n" 2848 "-fw_cfg [name=]<name>,string=<str>\n" 2849 " add named fw_cfg entry from string\n", 2850 QEMU_ARCH_ALL) 2851STEXI 2852@item -fw_cfg [name=]@var{name},file=@var{file} 2853@findex -fw_cfg 2854Add named fw_cfg entry from file. @var{name} determines the name of 2855the entry in the fw_cfg file directory exposed to the guest. 2856 2857@item -fw_cfg [name=]@var{name},string=@var{str} 2858Add named fw_cfg entry from string. 2859ETEXI 2860 2861DEF("serial", HAS_ARG, QEMU_OPTION_serial, \ 2862 "-serial dev redirect the serial port to char device 'dev'\n", 2863 QEMU_ARCH_ALL) 2864STEXI 2865@item -serial @var{dev} 2866@findex -serial 2867Redirect the virtual serial port to host character device 2868@var{dev}. The default device is @code{vc} in graphical mode and 2869@code{stdio} in non graphical mode. 2870 2871This option can be used several times to simulate up to 4 serial 2872ports. 2873 2874Use @code{-serial none} to disable all serial ports. 2875 2876Available character devices are: 2877@table @option 2878@item vc[:@var{W}x@var{H}] 2879Virtual console. Optionally, a width and height can be given in pixel with 2880@example 2881vc:800x600 2882@end example 2883It is also possible to specify width or height in characters: 2884@example 2885vc:80Cx24C 2886@end example 2887@item pty 2888[Linux only] Pseudo TTY (a new PTY is automatically allocated) 2889@item none 2890No device is allocated. 2891@item null 2892void device 2893@item chardev:@var{id} 2894Use a named character device defined with the @code{-chardev} option. 2895@item /dev/XXX 2896[Linux only] Use host tty, e.g. @file{/dev/ttyS0}. The host serial port 2897parameters are set according to the emulated ones. 2898@item /dev/parport@var{N} 2899[Linux only, parallel port only] Use host parallel port 2900@var{N}. Currently SPP and EPP parallel port features can be used. 2901@item file:@var{filename} 2902Write output to @var{filename}. No character can be read. 2903@item stdio 2904[Unix only] standard input/output 2905@item pipe:@var{filename} 2906name pipe @var{filename} 2907@item COM@var{n} 2908[Windows only] Use host serial port @var{n} 2909@item udp:[@var{remote_host}]:@var{remote_port}[@@[@var{src_ip}]:@var{src_port}] 2910This implements UDP Net Console. 2911When @var{remote_host} or @var{src_ip} are not specified 2912they default to @code{0.0.0.0}. 2913When not using a specified @var{src_port} a random port is automatically chosen. 2914 2915If you just want a simple readonly console you can use @code{netcat} or 2916@code{nc}, by starting QEMU with: @code{-serial udp::4555} and nc as: 2917@code{nc -u -l -p 4555}. Any time QEMU writes something to that port it 2918will appear in the netconsole session. 2919 2920If you plan to send characters back via netconsole or you want to stop 2921and start QEMU a lot of times, you should have QEMU use the same 2922source port each time by using something like @code{-serial 2923udp::4555@@:4556} to QEMU. Another approach is to use a patched 2924version of netcat which can listen to a TCP port and send and receive 2925characters via udp. If you have a patched version of netcat which 2926activates telnet remote echo and single char transfer, then you can 2927use the following options to step up a netcat redirector to allow 2928telnet on port 5555 to access the QEMU port. 2929@table @code 2930@item QEMU Options: 2931-serial udp::4555@@:4556 2932@item netcat options: 2933-u -P 4555 -L 0.0.0.0:4556 -t -p 5555 -I -T 2934@item telnet options: 2935localhost 5555 2936@end table 2937 2938@item tcp:[@var{host}]:@var{port}[,@var{server}][,nowait][,nodelay][,reconnect=@var{seconds}] 2939The TCP Net Console has two modes of operation. It can send the serial 2940I/O to a location or wait for a connection from a location. By default 2941the TCP Net Console is sent to @var{host} at the @var{port}. If you use 2942the @var{server} option QEMU will wait for a client socket application 2943to connect to the port before continuing, unless the @code{nowait} 2944option was specified. The @code{nodelay} option disables the Nagle buffering 2945algorithm. The @code{reconnect} option only applies if @var{noserver} is 2946set, if the connection goes down it will attempt to reconnect at the 2947given interval. If @var{host} is omitted, 0.0.0.0 is assumed. Only 2948one TCP connection at a time is accepted. You can use @code{telnet} to 2949connect to the corresponding character device. 2950@table @code 2951@item Example to send tcp console to 192.168.0.2 port 4444 2952-serial tcp:192.168.0.2:4444 2953@item Example to listen and wait on port 4444 for connection 2954-serial tcp::4444,server 2955@item Example to not wait and listen on ip 192.168.0.100 port 4444 2956-serial tcp:192.168.0.100:4444,server,nowait 2957@end table 2958 2959@item telnet:@var{host}:@var{port}[,server][,nowait][,nodelay] 2960The telnet protocol is used instead of raw tcp sockets. The options 2961work the same as if you had specified @code{-serial tcp}. The 2962difference is that the port acts like a telnet server or client using 2963telnet option negotiation. This will also allow you to send the 2964MAGIC_SYSRQ sequence if you use a telnet that supports sending the break 2965sequence. Typically in unix telnet you do it with Control-] and then 2966type "send break" followed by pressing the enter key. 2967 2968@item unix:@var{path}[,server][,nowait][,reconnect=@var{seconds}] 2969A unix domain socket is used instead of a tcp socket. The option works the 2970same as if you had specified @code{-serial tcp} except the unix domain socket 2971@var{path} is used for connections. 2972 2973@item mon:@var{dev_string} 2974This is a special option to allow the monitor to be multiplexed onto 2975another serial port. The monitor is accessed with key sequence of 2976@key{Control-a} and then pressing @key{c}. 2977@var{dev_string} should be any one of the serial devices specified 2978above. An example to multiplex the monitor onto a telnet server 2979listening on port 4444 would be: 2980@table @code 2981@item -serial mon:telnet::4444,server,nowait 2982@end table 2983When the monitor is multiplexed to stdio in this way, Ctrl+C will not terminate 2984QEMU any more but will be passed to the guest instead. 2985 2986@item braille 2987Braille device. This will use BrlAPI to display the braille output on a real 2988or fake device. 2989 2990@item msmouse 2991Three button serial mouse. Configure the guest to use Microsoft protocol. 2992@end table 2993ETEXI 2994 2995DEF("parallel", HAS_ARG, QEMU_OPTION_parallel, \ 2996 "-parallel dev redirect the parallel port to char device 'dev'\n", 2997 QEMU_ARCH_ALL) 2998STEXI 2999@item -parallel @var{dev} 3000@findex -parallel 3001Redirect the virtual parallel port to host device @var{dev} (same 3002devices as the serial port). On Linux hosts, @file{/dev/parportN} can 3003be used to use hardware devices connected on the corresponding host 3004parallel port. 3005 3006This option can be used several times to simulate up to 3 parallel 3007ports. 3008 3009Use @code{-parallel none} to disable all parallel ports. 3010ETEXI 3011 3012DEF("monitor", HAS_ARG, QEMU_OPTION_monitor, \ 3013 "-monitor dev redirect the monitor to char device 'dev'\n", 3014 QEMU_ARCH_ALL) 3015STEXI 3016@item -monitor @var{dev} 3017@findex -monitor 3018Redirect the monitor to host device @var{dev} (same devices as the 3019serial port). 3020The default device is @code{vc} in graphical mode and @code{stdio} in 3021non graphical mode. 3022Use @code{-monitor none} to disable the default monitor. 3023ETEXI 3024DEF("qmp", HAS_ARG, QEMU_OPTION_qmp, \ 3025 "-qmp dev like -monitor but opens in 'control' mode\n", 3026 QEMU_ARCH_ALL) 3027STEXI 3028@item -qmp @var{dev} 3029@findex -qmp 3030Like -monitor but opens in 'control' mode. 3031ETEXI 3032DEF("qmp-pretty", HAS_ARG, QEMU_OPTION_qmp_pretty, \ 3033 "-qmp-pretty dev like -qmp but uses pretty JSON formatting\n", 3034 QEMU_ARCH_ALL) 3035STEXI 3036@item -qmp-pretty @var{dev} 3037@findex -qmp-pretty 3038Like -qmp but uses pretty JSON formatting. 3039ETEXI 3040 3041DEF("mon", HAS_ARG, QEMU_OPTION_mon, \ 3042 "-mon [chardev=]name[,mode=readline|control][,default]\n", QEMU_ARCH_ALL) 3043STEXI 3044@item -mon [chardev=]name[,mode=readline|control][,default] 3045@findex -mon 3046Setup monitor on chardev @var{name}. 3047ETEXI 3048 3049DEF("debugcon", HAS_ARG, QEMU_OPTION_debugcon, \ 3050 "-debugcon dev redirect the debug console to char device 'dev'\n", 3051 QEMU_ARCH_ALL) 3052STEXI 3053@item -debugcon @var{dev} 3054@findex -debugcon 3055Redirect the debug console to host device @var{dev} (same devices as the 3056serial port). The debug console is an I/O port which is typically port 30570xe9; writing to that I/O port sends output to this device. 3058The default device is @code{vc} in graphical mode and @code{stdio} in 3059non graphical mode. 3060ETEXI 3061 3062DEF("pidfile", HAS_ARG, QEMU_OPTION_pidfile, \ 3063 "-pidfile file write PID to 'file'\n", QEMU_ARCH_ALL) 3064STEXI 3065@item -pidfile @var{file} 3066@findex -pidfile 3067Store the QEMU process PID in @var{file}. It is useful if you launch QEMU 3068from a script. 3069ETEXI 3070 3071DEF("singlestep", 0, QEMU_OPTION_singlestep, \ 3072 "-singlestep always run in singlestep mode\n", QEMU_ARCH_ALL) 3073STEXI 3074@item -singlestep 3075@findex -singlestep 3076Run the emulation in single step mode. 3077ETEXI 3078 3079DEF("S", 0, QEMU_OPTION_S, \ 3080 "-S freeze CPU at startup (use 'c' to start execution)\n", 3081 QEMU_ARCH_ALL) 3082STEXI 3083@item -S 3084@findex -S 3085Do not start CPU at startup (you must type 'c' in the monitor). 3086ETEXI 3087 3088DEF("realtime", HAS_ARG, QEMU_OPTION_realtime, 3089 "-realtime [mlock=on|off]\n" 3090 " run qemu with realtime features\n" 3091 " mlock=on|off controls mlock support (default: on)\n", 3092 QEMU_ARCH_ALL) 3093STEXI 3094@item -realtime mlock=on|off 3095@findex -realtime 3096Run qemu with realtime features. 3097mlocking qemu and guest memory can be enabled via @option{mlock=on} 3098(enabled by default). 3099ETEXI 3100 3101DEF("gdb", HAS_ARG, QEMU_OPTION_gdb, \ 3102 "-gdb dev wait for gdb connection on 'dev'\n", QEMU_ARCH_ALL) 3103STEXI 3104@item -gdb @var{dev} 3105@findex -gdb 3106Wait for gdb connection on device @var{dev} (@pxref{gdb_usage}). Typical 3107connections will likely be TCP-based, but also UDP, pseudo TTY, or even 3108stdio are reasonable use case. The latter is allowing to start QEMU from 3109within gdb and establish the connection via a pipe: 3110@example 3111(gdb) target remote | exec qemu-system-i386 -gdb stdio ... 3112@end example 3113ETEXI 3114 3115DEF("s", 0, QEMU_OPTION_s, \ 3116 "-s shorthand for -gdb tcp::" DEFAULT_GDBSTUB_PORT "\n", 3117 QEMU_ARCH_ALL) 3118STEXI 3119@item -s 3120@findex -s 3121Shorthand for -gdb tcp::1234, i.e. open a gdbserver on TCP port 1234 3122(@pxref{gdb_usage}). 3123ETEXI 3124 3125DEF("d", HAS_ARG, QEMU_OPTION_d, \ 3126 "-d item1,... enable logging of specified items (use '-d help' for a list of log items)\n", 3127 QEMU_ARCH_ALL) 3128STEXI 3129@item -d @var{item1}[,...] 3130@findex -d 3131Enable logging of specified items. Use '-d help' for a list of log items. 3132ETEXI 3133 3134DEF("D", HAS_ARG, QEMU_OPTION_D, \ 3135 "-D logfile output log to logfile (default stderr)\n", 3136 QEMU_ARCH_ALL) 3137STEXI 3138@item -D @var{logfile} 3139@findex -D 3140Output log in @var{logfile} instead of to stderr 3141ETEXI 3142 3143DEF("L", HAS_ARG, QEMU_OPTION_L, \ 3144 "-L path set the directory for the BIOS, VGA BIOS and keymaps\n", 3145 QEMU_ARCH_ALL) 3146STEXI 3147@item -L @var{path} 3148@findex -L 3149Set the directory for the BIOS, VGA BIOS and keymaps. 3150ETEXI 3151 3152DEF("bios", HAS_ARG, QEMU_OPTION_bios, \ 3153 "-bios file set the filename for the BIOS\n", QEMU_ARCH_ALL) 3154STEXI 3155@item -bios @var{file} 3156@findex -bios 3157Set the filename for the BIOS. 3158ETEXI 3159 3160DEF("enable-kvm", 0, QEMU_OPTION_enable_kvm, \ 3161 "-enable-kvm enable KVM full virtualization support\n", QEMU_ARCH_ALL) 3162STEXI 3163@item -enable-kvm 3164@findex -enable-kvm 3165Enable KVM full virtualization support. This option is only available 3166if KVM support is enabled when compiling. 3167ETEXI 3168 3169DEF("xen-domid", HAS_ARG, QEMU_OPTION_xen_domid, 3170 "-xen-domid id specify xen guest domain id\n", QEMU_ARCH_ALL) 3171DEF("xen-create", 0, QEMU_OPTION_xen_create, 3172 "-xen-create create domain using xen hypercalls, bypassing xend\n" 3173 " warning: should not be used when xend is in use\n", 3174 QEMU_ARCH_ALL) 3175DEF("xen-attach", 0, QEMU_OPTION_xen_attach, 3176 "-xen-attach attach to existing xen domain\n" 3177 " xend will use this when starting QEMU\n", 3178 QEMU_ARCH_ALL) 3179STEXI 3180@item -xen-domid @var{id} 3181@findex -xen-domid 3182Specify xen guest domain @var{id} (XEN only). 3183@item -xen-create 3184@findex -xen-create 3185Create domain using xen hypercalls, bypassing xend. 3186Warning: should not be used when xend is in use (XEN only). 3187@item -xen-attach 3188@findex -xen-attach 3189Attach to existing xen domain. 3190xend will use this when starting QEMU (XEN only). 3191ETEXI 3192 3193DEF("no-reboot", 0, QEMU_OPTION_no_reboot, \ 3194 "-no-reboot exit instead of rebooting\n", QEMU_ARCH_ALL) 3195STEXI 3196@item -no-reboot 3197@findex -no-reboot 3198Exit instead of rebooting. 3199ETEXI 3200 3201DEF("no-shutdown", 0, QEMU_OPTION_no_shutdown, \ 3202 "-no-shutdown stop before shutdown\n", QEMU_ARCH_ALL) 3203STEXI 3204@item -no-shutdown 3205@findex -no-shutdown 3206Don't exit QEMU on guest shutdown, but instead only stop the emulation. 3207This allows for instance switching to monitor to commit changes to the 3208disk image. 3209ETEXI 3210 3211DEF("loadvm", HAS_ARG, QEMU_OPTION_loadvm, \ 3212 "-loadvm [tag|id]\n" \ 3213 " start right away with a saved state (loadvm in monitor)\n", 3214 QEMU_ARCH_ALL) 3215STEXI 3216@item -loadvm @var{file} 3217@findex -loadvm 3218Start right away with a saved state (@code{loadvm} in monitor) 3219ETEXI 3220 3221#ifndef _WIN32 3222DEF("daemonize", 0, QEMU_OPTION_daemonize, \ 3223 "-daemonize daemonize QEMU after initializing\n", QEMU_ARCH_ALL) 3224#endif 3225STEXI 3226@item -daemonize 3227@findex -daemonize 3228Daemonize the QEMU process after initialization. QEMU will not detach from 3229standard IO until it is ready to receive connections on any of its devices. 3230This option is a useful way for external programs to launch QEMU without having 3231to cope with initialization race conditions. 3232ETEXI 3233 3234DEF("option-rom", HAS_ARG, QEMU_OPTION_option_rom, \ 3235 "-option-rom rom load a file, rom, into the option ROM space\n", 3236 QEMU_ARCH_ALL) 3237STEXI 3238@item -option-rom @var{file} 3239@findex -option-rom 3240Load the contents of @var{file} as an option ROM. 3241This option is useful to load things like EtherBoot. 3242ETEXI 3243 3244HXCOMM Silently ignored for compatibility 3245DEF("clock", HAS_ARG, QEMU_OPTION_clock, "", QEMU_ARCH_ALL) 3246 3247HXCOMM Options deprecated by -rtc 3248DEF("localtime", 0, QEMU_OPTION_localtime, "", QEMU_ARCH_ALL) 3249DEF("startdate", HAS_ARG, QEMU_OPTION_startdate, "", QEMU_ARCH_ALL) 3250 3251DEF("rtc", HAS_ARG, QEMU_OPTION_rtc, \ 3252 "-rtc [base=utc|localtime|date][,clock=host|rt|vm][,driftfix=none|slew]\n" \ 3253 " set the RTC base and clock, enable drift fix for clock ticks (x86 only)\n", 3254 QEMU_ARCH_ALL) 3255 3256STEXI 3257 3258@item -rtc [base=utc|localtime|@var{date}][,clock=host|vm][,driftfix=none|slew] 3259@findex -rtc 3260Specify @option{base} as @code{utc} or @code{localtime} to let the RTC start at the current 3261UTC or local time, respectively. @code{localtime} is required for correct date in 3262MS-DOS or Windows. To start at a specific point in time, provide @var{date} in the 3263format @code{2006-06-17T16:01:21} or @code{2006-06-17}. The default base is UTC. 3264 3265By default the RTC is driven by the host system time. This allows using of the 3266RTC as accurate reference clock inside the guest, specifically if the host 3267time is smoothly following an accurate external reference clock, e.g. via NTP. 3268If you want to isolate the guest time from the host, you can set @option{clock} 3269to @code{rt} instead. To even prevent it from progressing during suspension, 3270you can set it to @code{vm}. 3271 3272Enable @option{driftfix} (i386 targets only) if you experience time drift problems, 3273specifically with Windows' ACPI HAL. This option will try to figure out how 3274many timer interrupts were not processed by the Windows guest and will 3275re-inject them. 3276ETEXI 3277 3278DEF("icount", HAS_ARG, QEMU_OPTION_icount, \ 3279 "-icount [shift=N|auto][,align=on|off][,sleep=no,rr=record|replay,rrfile=<filename>]\n" \ 3280 " enable virtual instruction counter with 2^N clock ticks per\n" \ 3281 " instruction, enable aligning the host and virtual clocks\n" \ 3282 " or disable real time cpu sleeping\n", QEMU_ARCH_ALL) 3283STEXI 3284@item -icount [shift=@var{N}|auto][,rr=record|replay,rrfile=@var{filename}] 3285@findex -icount 3286Enable virtual instruction counter. The virtual cpu will execute one 3287instruction every 2^@var{N} ns of virtual time. If @code{auto} is specified 3288then the virtual cpu speed will be automatically adjusted to keep virtual 3289time within a few seconds of real time. 3290 3291When the virtual cpu is sleeping, the virtual time will advance at default 3292speed unless @option{sleep=no} is specified. 3293With @option{sleep=no}, the virtual time will jump to the next timer deadline 3294instantly whenever the virtual cpu goes to sleep mode and will not advance 3295if no timer is enabled. This behavior give deterministic execution times from 3296the guest point of view. 3297 3298Note that while this option can give deterministic behavior, it does not 3299provide cycle accurate emulation. Modern CPUs contain superscalar out of 3300order cores with complex cache hierarchies. The number of instructions 3301executed often has little or no correlation with actual performance. 3302 3303@option{align=on} will activate the delay algorithm which will try 3304to synchronise the host clock and the virtual clock. The goal is to 3305have a guest running at the real frequency imposed by the shift option. 3306Whenever the guest clock is behind the host clock and if 3307@option{align=on} is specified then we print a message to the user 3308to inform about the delay. 3309Currently this option does not work when @option{shift} is @code{auto}. 3310Note: The sync algorithm will work for those shift values for which 3311the guest clock runs ahead of the host clock. Typically this happens 3312when the shift value is high (how high depends on the host machine). 3313 3314When @option{rr} option is specified deterministic record/replay is enabled. 3315Replay log is written into @var{filename} file in record mode and 3316read from this file in replay mode. 3317ETEXI 3318 3319DEF("watchdog", HAS_ARG, QEMU_OPTION_watchdog, \ 3320 "-watchdog model\n" \ 3321 " enable virtual hardware watchdog [default=none]\n", 3322 QEMU_ARCH_ALL) 3323STEXI 3324@item -watchdog @var{model} 3325@findex -watchdog 3326Create a virtual hardware watchdog device. Once enabled (by a guest 3327action), the watchdog must be periodically polled by an agent inside 3328the guest or else the guest will be restarted. Choose a model for 3329which your guest has drivers. 3330 3331The @var{model} is the model of hardware watchdog to emulate. Use 3332@code{-watchdog help} to list available hardware models. Only one 3333watchdog can be enabled for a guest. 3334 3335The following models may be available: 3336@table @option 3337@item ib700 3338iBASE 700 is a very simple ISA watchdog with a single timer. 3339@item i6300esb 3340Intel 6300ESB I/O controller hub is a much more featureful PCI-based 3341dual-timer watchdog. 3342@item diag288 3343A virtual watchdog for s390x backed by the diagnose 288 hypercall 3344(currently KVM only). 3345@end table 3346ETEXI 3347 3348DEF("watchdog-action", HAS_ARG, QEMU_OPTION_watchdog_action, \ 3349 "-watchdog-action reset|shutdown|poweroff|pause|debug|none\n" \ 3350 " action when watchdog fires [default=reset]\n", 3351 QEMU_ARCH_ALL) 3352STEXI 3353@item -watchdog-action @var{action} 3354@findex -watchdog-action 3355 3356The @var{action} controls what QEMU will do when the watchdog timer 3357expires. 3358The default is 3359@code{reset} (forcefully reset the guest). 3360Other possible actions are: 3361@code{shutdown} (attempt to gracefully shutdown the guest), 3362@code{poweroff} (forcefully poweroff the guest), 3363@code{pause} (pause the guest), 3364@code{debug} (print a debug message and continue), or 3365@code{none} (do nothing). 3366 3367Note that the @code{shutdown} action requires that the guest responds 3368to ACPI signals, which it may not be able to do in the sort of 3369situations where the watchdog would have expired, and thus 3370@code{-watchdog-action shutdown} is not recommended for production use. 3371 3372Examples: 3373 3374@table @code 3375@item -watchdog i6300esb -watchdog-action pause 3376@itemx -watchdog ib700 3377@end table 3378ETEXI 3379 3380DEF("echr", HAS_ARG, QEMU_OPTION_echr, \ 3381 "-echr chr set terminal escape character instead of ctrl-a\n", 3382 QEMU_ARCH_ALL) 3383STEXI 3384 3385@item -echr @var{numeric_ascii_value} 3386@findex -echr 3387Change the escape character used for switching to the monitor when using 3388monitor and serial sharing. The default is @code{0x01} when using the 3389@code{-nographic} option. @code{0x01} is equal to pressing 3390@code{Control-a}. You can select a different character from the ascii 3391control keys where 1 through 26 map to Control-a through Control-z. For 3392instance you could use the either of the following to change the escape 3393character to Control-t. 3394@table @code 3395@item -echr 0x14 3396@itemx -echr 20 3397@end table 3398ETEXI 3399 3400DEF("virtioconsole", HAS_ARG, QEMU_OPTION_virtiocon, \ 3401 "-virtioconsole c\n" \ 3402 " set virtio console\n", QEMU_ARCH_ALL) 3403STEXI 3404@item -virtioconsole @var{c} 3405@findex -virtioconsole 3406Set virtio console. 3407 3408This option is maintained for backward compatibility. 3409 3410Please use @code{-device virtconsole} for the new way of invocation. 3411ETEXI 3412 3413DEF("show-cursor", 0, QEMU_OPTION_show_cursor, \ 3414 "-show-cursor show cursor\n", QEMU_ARCH_ALL) 3415STEXI 3416@item -show-cursor 3417@findex -show-cursor 3418Show cursor. 3419ETEXI 3420 3421DEF("tb-size", HAS_ARG, QEMU_OPTION_tb_size, \ 3422 "-tb-size n set TB size\n", QEMU_ARCH_ALL) 3423STEXI 3424@item -tb-size @var{n} 3425@findex -tb-size 3426Set TB size. 3427ETEXI 3428 3429DEF("incoming", HAS_ARG, QEMU_OPTION_incoming, \ 3430 "-incoming tcp:[host]:port[,to=maxport][,ipv4][,ipv6]\n" \ 3431 "-incoming rdma:host:port[,ipv4][,ipv6]\n" \ 3432 "-incoming unix:socketpath\n" \ 3433 " prepare for incoming migration, listen on\n" \ 3434 " specified protocol and socket address\n" \ 3435 "-incoming fd:fd\n" \ 3436 "-incoming exec:cmdline\n" \ 3437 " accept incoming migration on given file descriptor\n" \ 3438 " or from given external command\n" \ 3439 "-incoming defer\n" \ 3440 " wait for the URI to be specified via migrate_incoming\n", 3441 QEMU_ARCH_ALL) 3442STEXI 3443@item -incoming tcp:[@var{host}]:@var{port}[,to=@var{maxport}][,ipv4][,ipv6] 3444@itemx -incoming rdma:@var{host}:@var{port}[,ipv4][,ipv6] 3445@findex -incoming 3446Prepare for incoming migration, listen on a given tcp port. 3447 3448@item -incoming unix:@var{socketpath} 3449Prepare for incoming migration, listen on a given unix socket. 3450 3451@item -incoming fd:@var{fd} 3452Accept incoming migration from a given filedescriptor. 3453 3454@item -incoming exec:@var{cmdline} 3455Accept incoming migration as an output from specified external command. 3456 3457@item -incoming defer 3458Wait for the URI to be specified via migrate_incoming. The monitor can 3459be used to change settings (such as migration parameters) prior to issuing 3460the migrate_incoming to allow the migration to begin. 3461ETEXI 3462 3463DEF("nodefaults", 0, QEMU_OPTION_nodefaults, \ 3464 "-nodefaults don't create default devices\n", QEMU_ARCH_ALL) 3465STEXI 3466@item -nodefaults 3467@findex -nodefaults 3468Don't create default devices. Normally, QEMU sets the default devices like serial 3469port, parallel port, virtual console, monitor device, VGA adapter, floppy and 3470CD-ROM drive and others. The @code{-nodefaults} option will disable all those 3471default devices. 3472ETEXI 3473 3474#ifndef _WIN32 3475DEF("chroot", HAS_ARG, QEMU_OPTION_chroot, \ 3476 "-chroot dir chroot to dir just before starting the VM\n", 3477 QEMU_ARCH_ALL) 3478#endif 3479STEXI 3480@item -chroot @var{dir} 3481@findex -chroot 3482Immediately before starting guest execution, chroot to the specified 3483directory. Especially useful in combination with -runas. 3484ETEXI 3485 3486#ifndef _WIN32 3487DEF("runas", HAS_ARG, QEMU_OPTION_runas, \ 3488 "-runas user change to user id user just before starting the VM\n", 3489 QEMU_ARCH_ALL) 3490#endif 3491STEXI 3492@item -runas @var{user} 3493@findex -runas 3494Immediately before starting guest execution, drop root privileges, switching 3495to the specified user. 3496ETEXI 3497 3498DEF("prom-env", HAS_ARG, QEMU_OPTION_prom_env, 3499 "-prom-env variable=value\n" 3500 " set OpenBIOS nvram variables\n", 3501 QEMU_ARCH_PPC | QEMU_ARCH_SPARC) 3502STEXI 3503@item -prom-env @var{variable}=@var{value} 3504@findex -prom-env 3505Set OpenBIOS nvram @var{variable} to given @var{value} (PPC, SPARC only). 3506ETEXI 3507DEF("semihosting", 0, QEMU_OPTION_semihosting, 3508 "-semihosting semihosting mode\n", 3509 QEMU_ARCH_ARM | QEMU_ARCH_M68K | QEMU_ARCH_XTENSA | QEMU_ARCH_LM32 | 3510 QEMU_ARCH_MIPS) 3511STEXI 3512@item -semihosting 3513@findex -semihosting 3514Enable semihosting mode (ARM, M68K, Xtensa, MIPS only). 3515ETEXI 3516DEF("semihosting-config", HAS_ARG, QEMU_OPTION_semihosting_config, 3517 "-semihosting-config [enable=on|off][,target=native|gdb|auto][,arg=str[,...]]\n" \ 3518 " semihosting configuration\n", 3519QEMU_ARCH_ARM | QEMU_ARCH_M68K | QEMU_ARCH_XTENSA | QEMU_ARCH_LM32 | 3520QEMU_ARCH_MIPS) 3521STEXI 3522@item -semihosting-config [enable=on|off][,target=native|gdb|auto][,arg=str[,...]] 3523@findex -semihosting-config 3524Enable and configure semihosting (ARM, M68K, Xtensa, MIPS only). 3525@table @option 3526@item target=@code{native|gdb|auto} 3527Defines where the semihosting calls will be addressed, to QEMU (@code{native}) 3528or to GDB (@code{gdb}). The default is @code{auto}, which means @code{gdb} 3529during debug sessions and @code{native} otherwise. 3530@item arg=@var{str1},arg=@var{str2},... 3531Allows the user to pass input arguments, and can be used multiple times to build 3532up a list. The old-style @code{-kernel}/@code{-append} method of passing a 3533command line is still supported for backward compatibility. If both the 3534@code{--semihosting-config arg} and the @code{-kernel}/@code{-append} are 3535specified, the former is passed to semihosting as it always takes precedence. 3536@end table 3537ETEXI 3538DEF("old-param", 0, QEMU_OPTION_old_param, 3539 "-old-param old param mode\n", QEMU_ARCH_ARM) 3540STEXI 3541@item -old-param 3542@findex -old-param (ARM) 3543Old param mode (ARM only). 3544ETEXI 3545 3546DEF("sandbox", HAS_ARG, QEMU_OPTION_sandbox, \ 3547 "-sandbox <arg> Enable seccomp mode 2 system call filter (default 'off').\n", 3548 QEMU_ARCH_ALL) 3549STEXI 3550@item -sandbox @var{arg} 3551@findex -sandbox 3552Enable Seccomp mode 2 system call filter. 'on' will enable syscall filtering and 'off' will 3553disable it. The default is 'off'. 3554ETEXI 3555 3556DEF("readconfig", HAS_ARG, QEMU_OPTION_readconfig, 3557 "-readconfig <file>\n", QEMU_ARCH_ALL) 3558STEXI 3559@item -readconfig @var{file} 3560@findex -readconfig 3561Read device configuration from @var{file}. This approach is useful when you want to spawn 3562QEMU process with many command line options but you don't want to exceed the command line 3563character limit. 3564ETEXI 3565DEF("writeconfig", HAS_ARG, QEMU_OPTION_writeconfig, 3566 "-writeconfig <file>\n" 3567 " read/write config file\n", QEMU_ARCH_ALL) 3568STEXI 3569@item -writeconfig @var{file} 3570@findex -writeconfig 3571Write device configuration to @var{file}. The @var{file} can be either filename to save 3572command line and device configuration into file or dash @code{-}) character to print the 3573output to stdout. This can be later used as input file for @code{-readconfig} option. 3574ETEXI 3575DEF("nodefconfig", 0, QEMU_OPTION_nodefconfig, 3576 "-nodefconfig\n" 3577 " do not load default config files at startup\n", 3578 QEMU_ARCH_ALL) 3579STEXI 3580@item -nodefconfig 3581@findex -nodefconfig 3582Normally QEMU loads configuration files from @var{sysconfdir} and @var{datadir} at startup. 3583The @code{-nodefconfig} option will prevent QEMU from loading any of those config files. 3584ETEXI 3585DEF("no-user-config", 0, QEMU_OPTION_nouserconfig, 3586 "-no-user-config\n" 3587 " do not load user-provided config files at startup\n", 3588 QEMU_ARCH_ALL) 3589STEXI 3590@item -no-user-config 3591@findex -no-user-config 3592The @code{-no-user-config} option makes QEMU not load any of the user-provided 3593config files on @var{sysconfdir}, but won't make it skip the QEMU-provided config 3594files from @var{datadir}. 3595ETEXI 3596DEF("trace", HAS_ARG, QEMU_OPTION_trace, 3597 "-trace [[enable=]<pattern>][,events=<file>][,file=<file>]\n" 3598 " specify tracing options\n", 3599 QEMU_ARCH_ALL) 3600STEXI 3601HXCOMM This line is not accurate, as some sub-options are backend-specific but 3602HXCOMM HX does not support conditional compilation of text. 3603@item -trace [events=@var{file}][,file=@var{file}] 3604@findex -trace 3605 3606Specify tracing options. 3607 3608@table @option 3609@item [enable=]@var{pattern} 3610Immediately enable events matching @var{pattern}. 3611The file must contain one event name (as listed in the @file{trace-events} file) 3612per line; globbing patterns are accepted too. This option is only 3613available if QEMU has been compiled with the @var{simple}, @var{stderr} 3614or @var{ftrace} tracing backend. To specify multiple events or patterns, 3615specify the @option{-trace} option multiple times. 3616 3617Use @code{-trace help} to print a list of names of trace points. 3618 3619@item events=@var{file} 3620Immediately enable events listed in @var{file}. 3621The file must contain one event name (as listed in the @file{trace-events} file) 3622per line; globbing patterns are accepted too. This option is only 3623available if QEMU has been compiled with the @var{simple}, @var{stderr} or 3624@var{ftrace} tracing backend. 3625 3626@item file=@var{file} 3627Log output traces to @var{file}. 3628This option is only available if QEMU has been compiled with 3629the @var{simple} tracing backend. 3630@end table 3631ETEXI 3632 3633HXCOMM Internal use 3634DEF("qtest", HAS_ARG, QEMU_OPTION_qtest, "", QEMU_ARCH_ALL) 3635DEF("qtest-log", HAS_ARG, QEMU_OPTION_qtest_log, "", QEMU_ARCH_ALL) 3636 3637#ifdef __linux__ 3638DEF("enable-fips", 0, QEMU_OPTION_enablefips, 3639 "-enable-fips enable FIPS 140-2 compliance\n", 3640 QEMU_ARCH_ALL) 3641#endif 3642STEXI 3643@item -enable-fips 3644@findex -enable-fips 3645Enable FIPS 140-2 compliance mode. 3646ETEXI 3647 3648HXCOMM Deprecated by -machine accel=tcg property 3649DEF("no-kvm", 0, QEMU_OPTION_no_kvm, "", QEMU_ARCH_I386) 3650 3651HXCOMM Deprecated by kvm-pit driver properties 3652DEF("no-kvm-pit-reinjection", 0, QEMU_OPTION_no_kvm_pit_reinjection, 3653 "", QEMU_ARCH_I386) 3654 3655HXCOMM Deprecated (ignored) 3656DEF("no-kvm-pit", 0, QEMU_OPTION_no_kvm_pit, "", QEMU_ARCH_I386) 3657 3658HXCOMM Deprecated by -machine kernel_irqchip=on|off property 3659DEF("no-kvm-irqchip", 0, QEMU_OPTION_no_kvm_irqchip, "", QEMU_ARCH_I386) 3660 3661HXCOMM Deprecated (ignored) 3662DEF("tdf", 0, QEMU_OPTION_tdf,"", QEMU_ARCH_ALL) 3663 3664DEF("msg", HAS_ARG, QEMU_OPTION_msg, 3665 "-msg timestamp[=on|off]\n" 3666 " change the format of messages\n" 3667 " on|off controls leading timestamps (default:on)\n", 3668 QEMU_ARCH_ALL) 3669STEXI 3670@item -msg timestamp[=on|off] 3671@findex -msg 3672prepend a timestamp to each log message.(default:on) 3673ETEXI 3674 3675DEF("dump-vmstate", HAS_ARG, QEMU_OPTION_dump_vmstate, 3676 "-dump-vmstate <file>\n" 3677 " Output vmstate information in JSON format to file.\n" 3678 " Use the scripts/vmstate-static-checker.py file to\n" 3679 " check for possible regressions in migration code\n" 3680 " by comparing two such vmstate dumps.\n", 3681 QEMU_ARCH_ALL) 3682STEXI 3683@item -dump-vmstate @var{file} 3684@findex -dump-vmstate 3685Dump json-encoded vmstate information for current machine type to file 3686in @var{file} 3687ETEXI 3688 3689DEFHEADING(Generic object creation) 3690 3691DEF("object", HAS_ARG, QEMU_OPTION_object, 3692 "-object TYPENAME[,PROP1=VALUE1,...]\n" 3693 " create a new object of type TYPENAME setting properties\n" 3694 " in the order they are specified. Note that the 'id'\n" 3695 " property must be set. These objects are placed in the\n" 3696 " '/objects' path.\n", 3697 QEMU_ARCH_ALL) 3698STEXI 3699@item -object @var{typename}[,@var{prop1}=@var{value1},...] 3700@findex -object 3701Create a new object of type @var{typename} setting properties 3702in the order they are specified. Note that the 'id' 3703property must be set. These objects are placed in the 3704'/objects' path. 3705 3706@table @option 3707 3708@item -object memory-backend-file,id=@var{id},size=@var{size},mem-path=@var{dir},share=@var{on|off} 3709 3710Creates a memory file backend object, which can be used to back 3711the guest RAM with huge pages. The @option{id} parameter is a 3712unique ID that will be used to reference this memory region 3713when configuring the @option{-numa} argument. The @option{size} 3714option provides the size of the memory region, and accepts 3715common suffixes, eg @option{500M}. The @option{mem-path} provides 3716the path to either a shared memory or huge page filesystem mount. 3717The @option{share} boolean option determines whether the memory 3718region is marked as private to QEMU, or shared. The latter allows 3719a co-operating external process to access the QEMU memory region. 3720 3721@item -object rng-random,id=@var{id},filename=@var{/dev/random} 3722 3723Creates a random number generator backend which obtains entropy from 3724a device on the host. The @option{id} parameter is a unique ID that 3725will be used to reference this entropy backend from the @option{virtio-rng} 3726device. The @option{filename} parameter specifies which file to obtain 3727entropy from and if omitted defaults to @option{/dev/random}. 3728 3729@item -object rng-egd,id=@var{id},chardev=@var{chardevid} 3730 3731Creates a random number generator backend which obtains entropy from 3732an external daemon running on the host. The @option{id} parameter is 3733a unique ID that will be used to reference this entropy backend from 3734the @option{virtio-rng} device. The @option{chardev} parameter is 3735the unique ID of a character device backend that provides the connection 3736to the RNG daemon. 3737 3738@item -object tls-creds-anon,id=@var{id},endpoint=@var{endpoint},dir=@var{/path/to/cred/dir},verify-peer=@var{on|off} 3739 3740Creates a TLS anonymous credentials object, which can be used to provide 3741TLS support on network backends. The @option{id} parameter is a unique 3742ID which network backends will use to access the credentials. The 3743@option{endpoint} is either @option{server} or @option{client} depending 3744on whether the QEMU network backend that uses the credentials will be 3745acting as a client or as a server. If @option{verify-peer} is enabled 3746(the default) then once the handshake is completed, the peer credentials 3747will be verified, though this is a no-op for anonymous credentials. 3748 3749The @var{dir} parameter tells QEMU where to find the credential 3750files. For server endpoints, this directory may contain a file 3751@var{dh-params.pem} providing diffie-hellman parameters to use 3752for the TLS server. If the file is missing, QEMU will generate 3753a set of DH parameters at startup. This is a computationally 3754expensive operation that consumes random pool entropy, so it is 3755recommended that a persistent set of parameters be generated 3756upfront and saved. 3757 3758@item -object tls-creds-x509,id=@var{id},endpoint=@var{endpoint},dir=@var{/path/to/cred/dir},verify-peer=@var{on|off},passwordid=@var{id} 3759 3760Creates a TLS anonymous credentials object, which can be used to provide 3761TLS support on network backends. The @option{id} parameter is a unique 3762ID which network backends will use to access the credentials. The 3763@option{endpoint} is either @option{server} or @option{client} depending 3764on whether the QEMU network backend that uses the credentials will be 3765acting as a client or as a server. If @option{verify-peer} is enabled 3766(the default) then once the handshake is completed, the peer credentials 3767will be verified. With x509 certificates, this implies that the clients 3768must be provided with valid client certificates too. 3769 3770The @var{dir} parameter tells QEMU where to find the credential 3771files. For server endpoints, this directory may contain a file 3772@var{dh-params.pem} providing diffie-hellman parameters to use 3773for the TLS server. If the file is missing, QEMU will generate 3774a set of DH parameters at startup. This is a computationally 3775expensive operation that consumes random pool entropy, so it is 3776recommended that a persistent set of parameters be generated 3777upfront and saved. 3778 3779For x509 certificate credentials the directory will contain further files 3780providing the x509 certificates. The certificates must be stored 3781in PEM format, in filenames @var{ca-cert.pem}, @var{ca-crl.pem} (optional), 3782@var{server-cert.pem} (only servers), @var{server-key.pem} (only servers), 3783@var{client-cert.pem} (only clients), and @var{client-key.pem} (only clients). 3784 3785For the @var{server-key.pem} and @var{client-key.pem} files which 3786contain sensitive private keys, it is possible to use an encrypted 3787version by providing the @var{passwordid} parameter. This provides 3788the ID of a previously created @code{secret} object containing the 3789password for decryption. 3790 3791@item -object filter-buffer,id=@var{id},netdev=@var{netdevid},interval=@var{t}[,queue=@var{all|rx|tx}] 3792 3793Interval @var{t} can't be 0, this filter batches the packet delivery: all 3794packets arriving in a given interval on netdev @var{netdevid} are delayed 3795until the end of the interval. Interval is in microseconds. 3796 3797queue @var{all|rx|tx} is an option that can be applied to any netfilter. 3798 3799@option{all}: the filter is attached both to the receive and the transmit 3800 queue of the netdev (default). 3801 3802@option{rx}: the filter is attached to the receive queue of the netdev, 3803 where it will receive packets sent to the netdev. 3804 3805@option{tx}: the filter is attached to the transmit queue of the netdev, 3806 where it will receive packets sent by the netdev. 3807 3808@item -object filter-dump,id=@var{id},netdev=@var{dev},file=@var{filename}][,maxlen=@var{len}] 3809 3810Dump the network traffic on netdev @var{dev} to the file specified by 3811@var{filename}. At most @var{len} bytes (64k by default) per packet are stored. 3812The file format is libpcap, so it can be analyzed with tools such as tcpdump 3813or Wireshark. 3814 3815@item -object secret,id=@var{id},data=@var{string},format=@var{raw|base64}[,keyid=@var{secretid},iv=@var{string}] 3816@item -object secret,id=@var{id},file=@var{filename},format=@var{raw|base64}[,keyid=@var{secretid},iv=@var{string}] 3817 3818Defines a secret to store a password, encryption key, or some other sensitive 3819data. The sensitive data can either be passed directly via the @var{data} 3820parameter, or indirectly via the @var{file} parameter. Using the @var{data} 3821parameter is insecure unless the sensitive data is encrypted. 3822 3823The sensitive data can be provided in raw format (the default), or base64. 3824When encoded as JSON, the raw format only supports valid UTF-8 characters, 3825so base64 is recommended for sending binary data. QEMU will convert from 3826which ever format is provided to the format it needs internally. eg, an 3827RBD password can be provided in raw format, even though it will be base64 3828encoded when passed onto the RBD sever. 3829 3830For added protection, it is possible to encrypt the data associated with 3831a secret using the AES-256-CBC cipher. Use of encryption is indicated 3832by providing the @var{keyid} and @var{iv} parameters. The @var{keyid} 3833parameter provides the ID of a previously defined secret that contains 3834the AES-256 decryption key. This key should be 32-bytes long and be 3835base64 encoded. The @var{iv} parameter provides the random initialization 3836vector used for encryption of this particular secret and should be a 3837base64 encrypted string of the 32-byte IV. 3838 3839The simplest (insecure) usage is to provide the secret inline 3840 3841@example 3842 3843 # $QEMU -object secret,id=sec0,data=letmein,format=raw 3844 3845@end example 3846 3847The simplest secure usage is to provide the secret via a file 3848 3849 # echo -n "letmein" > mypasswd.txt 3850 # $QEMU -object secret,id=sec0,file=mypasswd.txt,format=raw 3851 3852For greater security, AES-256-CBC should be used. To illustrate usage, 3853consider the openssl command line tool which can encrypt the data. Note 3854that when encrypting, the plaintext must be padded to the cipher block 3855size (32 bytes) using the standard PKCS#5/6 compatible padding algorithm. 3856 3857First a master key needs to be created in base64 encoding: 3858 3859@example 3860 # openssl rand -base64 32 > key.b64 3861 # KEY=$(base64 -d key.b64 | hexdump -v -e '/1 "%02X"') 3862@end example 3863 3864Each secret to be encrypted needs to have a random initialization vector 3865generated. These do not need to be kept secret 3866 3867@example 3868 # openssl rand -base64 16 > iv.b64 3869 # IV=$(base64 -d iv.b64 | hexdump -v -e '/1 "%02X"') 3870@end example 3871 3872The secret to be defined can now be encrypted, in this case we're 3873telling openssl to base64 encode the result, but it could be left 3874as raw bytes if desired. 3875 3876@example 3877 # SECRET=$(echo -n "letmein" | 3878 openssl enc -aes-256-cbc -a -K $KEY -iv $IV) 3879@end example 3880 3881When launching QEMU, create a master secret pointing to @code{key.b64} 3882and specify that to be used to decrypt the user password. Pass the 3883contents of @code{iv.b64} to the second secret 3884 3885@example 3886 # $QEMU \ 3887 -object secret,id=secmaster0,format=base64,file=key.b64 \ 3888 -object secret,id=sec0,keyid=secmaster0,format=base64,\ 3889 data=$SECRET,iv=$(<iv.b64) 3890@end example 3891 3892@end table 3893 3894ETEXI 3895 3896 3897HXCOMM This is the last statement. Insert new options before this line! 3898STEXI 3899@end table 3900ETEXI 3901
