1 2Removed features 3================ 4 5What follows is a record of recently removed, formerly deprecated 6features that serves as a record for users who have encountered 7trouble after a recent upgrade. 8 9System emulator command line arguments 10-------------------------------------- 11 12``-hdachs`` (removed in 2.12) 13''''''''''''''''''''''''''''' 14 15The geometry defined by ``-hdachs c,h,s,t`` should now be specified via 16``-device ide-hd,drive=dr,cyls=c,heads=h,secs=s,bios-chs-trans=t`` 17(together with ``-drive if=none,id=dr,...``). 18 19``-net channel`` (removed in 2.12) 20'''''''''''''''''''''''''''''''''' 21 22This option has been replaced by ``-net user,guestfwd=...``. 23 24``-net dump`` (removed in 2.12) 25''''''''''''''''''''''''''''''' 26 27``-net dump[,vlan=n][,file=filename][,len=maxlen]`` has been replaced by 28``-object filter-dump,id=id,netdev=dev[,file=filename][,maxlen=maxlen]``. 29Note that the new syntax works with netdev IDs instead of the old "vlan" hubs. 30 31``-no-kvm-pit`` (removed in 2.12) 32''''''''''''''''''''''''''''''''' 33 34This was just a dummy option that has been ignored, since the in-kernel PIT 35cannot be disabled separately from the irqchip anymore. A similar effect 36(which also disables the KVM IOAPIC) can be obtained with 37``-M kernel_irqchip=split``. 38 39``-tdf`` (removed in 2.12) 40'''''''''''''''''''''''''' 41 42There is no replacement, the ``-tdf`` option has just been ignored since the 43behaviour that could be changed by this option in qemu-kvm is now the default 44when using the KVM PIT. It still can be requested explicitly using 45``-global kvm-pit.lost_tick_policy=delay``. 46 47``-drive secs=s``, ``-drive heads=h`` & ``-drive cyls=c`` (removed in 3.0) 48'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 49 50The drive geometry should now be specified via 51``-device ...,drive=dr,cyls=c,heads=h,secs=s`` (together with 52``-drive if=none,id=dr,...``). 53 54``-drive serial=``, ``-drive trans=`` & ``-drive addr=`` (removed in 3.0) 55''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 56 57Use ``-device ...,drive=dr,serial=r,bios-chs-trans=t,addr=a`` instead 58(together with ``-drive if=none,id=dr,...``). 59 60``-net ...,vlan=x`` (removed in 3.0) 61'''''''''''''''''''''''''''''''''''' 62 63The term "vlan" was very confusing for most users in this context (it's about 64specifying a hub ID, not about IEEE 802.1Q or something similar), so this 65has been removed. To connect one NIC frontend with a network backend, either 66use ``-nic ...`` (e.g. for on-board NICs) or use ``-netdev ...,id=n`` together 67with ``-device ...,netdev=n`` (for full control over pluggable NICs). To 68connect multiple NICs or network backends via a hub device (which is what 69vlan did), use ``-nic hubport,hubid=x,...`` or 70``-netdev hubport,id=n,hubid=x,...`` (with ``-device ...,netdev=n``) instead. 71 72``-no-kvm-irqchip`` (removed in 3.0) 73'''''''''''''''''''''''''''''''''''' 74 75Use ``-machine kernel_irqchip=off`` instead. 76 77``-no-kvm-pit-reinjection`` (removed in 3.0) 78'''''''''''''''''''''''''''''''''''''''''''' 79 80Use ``-global kvm-pit.lost_tick_policy=discard`` instead. 81 82``-balloon`` (removed in 3.1) 83''''''''''''''''''''''''''''' 84 85The ``-balloon virtio`` option has been replaced by ``-device virtio-balloon``. 86The ``-balloon none`` option was a no-op and has no replacement. 87 88``-bootp`` (removed in 3.1) 89''''''''''''''''''''''''''' 90 91The ``-bootp /some/file`` argument is replaced by either 92``-netdev user,id=x,bootp=/some/file`` (for pluggable NICs, accompanied with 93``-device ...,netdev=x``), or ``-nic user,bootp=/some/file`` (for on-board NICs). 94The new syntax allows different settings to be provided per NIC. 95 96``-redir`` (removed in 3.1) 97''''''''''''''''''''''''''' 98 99The ``-redir [tcp|udp]:hostport:[guestaddr]:guestport`` option is replaced 100by either ``-netdev 101user,id=x,hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport`` 102(for pluggable NICs, accompanied with ``-device ...,netdev=x``) or by the option 103``-nic user,hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport`` 104(for on-board NICs). The new syntax allows different settings to be provided 105per NIC. 106 107``-smb`` (removed in 3.1) 108''''''''''''''''''''''''' 109 110The ``-smb /some/dir`` argument is replaced by either 111``-netdev user,id=x,smb=/some/dir`` (for pluggable NICs, accompanied with 112``-device ...,netdev=x``), or ``-nic user,smb=/some/dir`` (for on-board NICs). 113The new syntax allows different settings to be provided per NIC. 114 115``-tftp`` (removed in 3.1) 116'''''''''''''''''''''''''' 117 118The ``-tftp /some/dir`` argument is replaced by either 119``-netdev user,id=x,tftp=/some/dir`` (for pluggable NICs, accompanied with 120``-device ...,netdev=x``), or ``-nic user,tftp=/some/dir`` (for embedded NICs). 121The new syntax allows different settings to be provided per NIC. 122 123``-localtime`` (removed in 3.1) 124''''''''''''''''''''''''''''''' 125 126Replaced by ``-rtc base=localtime``. 127 128``-nodefconfig`` (removed in 3.1) 129''''''''''''''''''''''''''''''''' 130 131Use ``-no-user-config`` instead. 132 133``-rtc-td-hack`` (removed in 3.1) 134''''''''''''''''''''''''''''''''' 135 136Use ``-rtc driftfix=slew`` instead. 137 138``-startdate`` (removed in 3.1) 139''''''''''''''''''''''''''''''' 140 141Replaced by ``-rtc base=date``. 142 143``-vnc ...,tls=...``, ``-vnc ...,x509=...`` & ``-vnc ...,x509verify=...`` (removed in 3.1) 144'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 145 146The "tls-creds" option should be used instead to point to a "tls-creds-x509" 147object created using "-object". 148 149``-mem-path`` fallback to RAM (removed in 5.0) 150'''''''''''''''''''''''''''''''''''''''''''''' 151 152If guest RAM allocation from file pointed by ``mem-path`` failed, 153QEMU was falling back to allocating from RAM, which might have resulted 154in unpredictable behavior since the backing file specified by the user 155as ignored. Currently, users are responsible for making sure the backing storage 156specified with ``-mem-path`` can actually provide the guest RAM configured with 157``-m`` and QEMU fails to start up if RAM allocation is unsuccessful. 158 159``-net ...,name=...`` (removed in 5.1) 160'''''''''''''''''''''''''''''''''''''' 161 162The ``name`` parameter of the ``-net`` option was a synonym 163for the ``id`` parameter, which should now be used instead. 164 165``-numa node,mem=...`` (removed in 5.1) 166''''''''''''''''''''''''''''''''''''''' 167 168The parameter ``mem`` of ``-numa node`` was used to assign a part of guest RAM 169to a NUMA node. But when using it, it's impossible to manage a specified RAM 170chunk on the host side (like bind it to a host node, setting bind policy, ...), 171so the guest ends up with the fake NUMA configuration with suboptiomal 172performance. 173However since 2014 there is an alternative way to assign RAM to a NUMA node 174using parameter ``memdev``, which does the same as ``mem`` and adds 175means to actually manage node RAM on the host side. Use parameter ``memdev`` 176with *memory-backend-ram* backend as replacement for parameter ``mem`` 177to achieve the same fake NUMA effect or a properly configured 178*memory-backend-file* backend to actually benefit from NUMA configuration. 179New machine versions (since 5.1) will not accept the option but it will still 180work with old machine types. User can check the QAPI schema to see if the legacy 181option is supported by looking at MachineInfo::numa-mem-supported property. 182 183``-numa`` node (without memory specified) (removed in 5.2) 184'''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 185 186Splitting RAM by default between NUMA nodes had the same issues as ``mem`` 187parameter with the difference that the role of the user plays QEMU using 188implicit generic or board specific splitting rule. 189Use ``memdev`` with *memory-backend-ram* backend or ``mem`` (if 190it's supported by used machine type) to define mapping explicitly instead. 191Users of existing VMs, wishing to preserve the same RAM distribution, should 192configure it explicitly using ``-numa node,memdev`` options. Current RAM 193distribution can be retrieved using HMP command ``info numa`` and if separate 194memory devices (pc|nv-dimm) are present use ``info memory-device`` and subtract 195device memory from output of ``info numa``. 196 197``-smp`` (invalid topologies) (removed in 5.2) 198'''''''''''''''''''''''''''''''''''''''''''''' 199 200CPU topology properties should describe whole machine topology including 201possible CPUs. 202 203However, historically it was possible to start QEMU with an incorrect topology 204where *n* <= *sockets* * *cores* * *threads* < *maxcpus*, 205which could lead to an incorrect topology enumeration by the guest. 206Support for invalid topologies is removed, the user must ensure 207topologies described with -smp include all possible cpus, i.e. 208*sockets* * *cores* * *threads* = *maxcpus*. 209 210``-machine enforce-config-section=on|off`` (removed in 5.2) 211''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 212 213The ``enforce-config-section`` property was replaced by the 214``-global migration.send-configuration={on|off}`` option. 215 216``-no-kvm`` (removed in 5.2) 217'''''''''''''''''''''''''''' 218 219The ``-no-kvm`` argument was a synonym for setting ``-machine accel=tcg``. 220 221``-realtime`` (removed in 6.0) 222'''''''''''''''''''''''''''''' 223 224The ``-realtime mlock=on|off`` argument has been replaced by the 225``-overcommit mem-lock=on|off`` argument. 226 227``-show-cursor`` option (removed in 6.0) 228'''''''''''''''''''''''''''''''''''''''' 229 230Use ``-display sdl,show-cursor=on``, ``-display gtk,show-cursor=on`` 231or ``-display default,show-cursor=on`` instead. 232 233``-tb-size`` option (removed in 6.0) 234'''''''''''''''''''''''''''''''''''' 235 236QEMU 5.0 introduced an alternative syntax to specify the size of the translation 237block cache, ``-accel tcg,tb-size=``. 238 239``-usbdevice audio`` (removed in 6.0) 240''''''''''''''''''''''''''''''''''''' 241 242This option lacked the possibility to specify an audio backend device. 243Use ``-device usb-audio`` now instead (and specify a corresponding USB 244host controller or ``-usb`` if necessary). 245 246``-vnc acl`` (removed in 6.0) 247''''''''''''''''''''''''''''' 248 249The ``acl`` option to the ``-vnc`` argument has been replaced 250by the ``tls-authz`` and ``sasl-authz`` options. 251 252``-mon ...,control=readline,pretty=on|off`` (removed in 6.0) 253'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 254 255The ``pretty=on|off`` switch has no effect for HMP monitors and 256its use is rejected. 257 258``-drive file=json:{...{'driver':'file'}}`` (removed in 6.0) 259'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 260 261The 'file' driver for drives is no longer appropriate for character or host 262devices and will only accept regular files (S_IFREG). The correct driver 263for these file types is 'host_cdrom' or 'host_device' as appropriate. 264 265Floppy controllers' drive properties (removed in 6.0) 266''''''''''''''''''''''''''''''''''''''''''''''''''''' 267 268Use ``-device floppy,...`` instead. When configuring onboard floppy 269controllers 270:: 271 272 -global isa-fdc.driveA=... 273 -global sysbus-fdc.driveA=... 274 -global SUNW,fdtwo.drive=... 275 276become 277:: 278 279 -device floppy,unit=0,drive=... 280 281and 282:: 283 284 -global isa-fdc.driveB=... 285 -global sysbus-fdc.driveB=... 286 287become 288:: 289 290 -device floppy,unit=1,drive=... 291 292When plugging in a floppy controller 293:: 294 295 -device isa-fdc,...,driveA=... 296 297becomes 298:: 299 300 -device isa-fdc,... 301 -device floppy,unit=0,drive=... 302 303and 304:: 305 306 -device isa-fdc,...,driveB=... 307 308becomes 309:: 310 311 -device isa-fdc,... 312 -device floppy,unit=1,drive=... 313 314``-drive`` with bogus interface type (removed in 6.0) 315''''''''''''''''''''''''''''''''''''''''''''''''''''' 316 317Drives with interface types other than ``if=none`` are for onboard 318devices. Drives the board doesn't pick up can no longer be used with 319-device. Use ``if=none`` instead. 320 321``-usbdevice ccid`` (removed in 6.0) 322''''''''''''''''''''''''''''''''''''' 323 324This option was undocumented and not used in the field. 325Use ``-device usb-ccid`` instead. 326 327RISC-V firmware not booted by default (removed in 5.1) 328'''''''''''''''''''''''''''''''''''''''''''''''''''''' 329 330QEMU 5.1 changes the default behaviour from ``-bios none`` to ``-bios default`` 331for the RISC-V ``virt`` machine and ``sifive_u`` machine. 332 333``-no-quit`` (removed in 7.0) 334''''''''''''''''''''''''''''' 335 336The ``-no-quit`` was a synonym for ``-display ...,window-close=off`` which 337should be used instead. 338 339``--enable-fips`` (removed in 7.1) 340'''''''''''''''''''''''''''''''''' 341 342This option restricted usage of certain cryptographic algorithms when 343the host is operating in FIPS mode. 344 345If FIPS compliance is required, QEMU should be built with the ``libgcrypt`` 346or ``gnutls`` library enabled as a cryptography provider. 347 348Neither the ``nettle`` library, or the built-in cryptography provider are 349supported on FIPS enabled hosts. 350 351``-writeconfig`` (removed in 7.1) 352''''''''''''''''''''''''''''''''' 353 354The ``-writeconfig`` option was not able to serialize the entire contents 355of the QEMU command line. It is thus considered a failed experiment 356and removed without a replacement. 357 358``loaded`` property of ``secret`` and ``secret_keyring`` objects (removed in 7.1) 359''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 360 361The ``loaded=on`` option in the command line or QMP ``object-add`` either had 362no effect (if ``loaded`` was the last option) or caused options to be 363effectively ignored as if they were not given. The property is therefore 364useless and should simply be removed. 365 366``opened`` property of ``rng-*`` objects (removed in 7.1) 367''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 368 369The ``opened=on`` option in the command line or QMP ``object-add`` either had 370no effect (if ``opened`` was the last option) or caused errors. The property 371is therefore useless and should simply be removed. 372 373``-display sdl,window_close=...`` (removed in 7.1) 374'''''''''''''''''''''''''''''''''''''''''''''''''' 375 376Use ``-display sdl,window-close=...`` instead (i.e. with a minus instead of 377an underscore between "window" and "close"). 378 379``-alt-grab`` and ``-display sdl,alt_grab=on`` (removed in 7.1) 380''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 381 382Use ``-display sdl,grab-mod=lshift-lctrl-lalt`` instead. 383 384``-ctrl-grab`` and ``-display sdl,ctrl_grab=on`` (removed in 7.1) 385''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 386 387Use ``-display sdl,grab-mod=rctrl`` instead. 388 389``-sdl`` (removed in 7.1) 390''''''''''''''''''''''''' 391 392Use ``-display sdl`` instead. 393 394``-curses`` (removed in 7.1) 395'''''''''''''''''''''''''''' 396 397Use ``-display curses`` instead. 398 399Creating sound card devices using ``-soundhw`` (removed in 7.1) 400''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 401 402Sound card devices should be created using ``-device`` or ``-audio``. 403The exception is ``pcspk`` which can be activated using ``-machine 404pcspk-audiodev=<name>``. 405 406``-watchdog`` (since 7.2) 407''''''''''''''''''''''''' 408 409Use ``-device`` instead. 410 411Hexadecimal sizes with scaling multipliers (since 8.0) 412'''''''''''''''''''''''''''''''''''''''''''''''''''''' 413 414Input parameters that take a size value should only use a size suffix 415(such as 'k' or 'M') when the base is written in decimal, and not when 416the value is hexadecimal. That is, '0x20M' should be written either as 417'32M' or as '0x2000000'. 418 419``-chardev`` backend aliases ``tty`` and ``parport`` (removed in 8.0) 420''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 421 422``tty`` and ``parport`` used to be aliases for ``serial`` and ``parallel`` 423respectively. The actual backend names should be used instead. 424 425``-drive if=none`` for the sifive_u OTP device (removed in 8.0) 426''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 427 428Use ``-drive if=pflash`` to configure the OTP device of the sifive_u 429RISC-V machine instead. 430 431``-spice password=string`` (removed in 8.0) 432''''''''''''''''''''''''''''''''''''''''''' 433 434This option was insecure because the SPICE password remained visible in 435the process listing. This was replaced by the new ``password-secret`` 436option which lets the password be securely provided on the command 437line using a ``secret`` object instance. 438 439``QEMU_AUDIO_`` environment variables and ``-audio-help`` (removed in 8.2) 440'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 441 442The ``-audiodev`` and ``-audio`` command line options are now the only 443way to specify audio backend settings. 444 445Using ``-audiodev`` to define the default audio backend (removed in 8.2) 446'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 447 448If no audiodev property is specified, previous versions would use the 449first ``-audiodev`` command line option as a fallback. Starting with 450version 8.2, audio backends created with ``-audiodev`` will only be 451used by clients (sound cards, machines with embedded sound hardware, VNC) 452that refer to it in an ``audiodev=`` property. 453 454In order to configure a default audio backend, use the ``-audio`` 455command line option without specifying a ``model``; while previous 456versions of QEMU required a model, starting with version 8.2 457QEMU does not require a model and will not create any sound card 458in this case. 459 460Note that the default audio backend must be configured on the command 461line if the ``-nodefaults`` options is used. 462 463``-no-hpet`` (removed in 9.0) 464''''''''''''''''''''''''''''' 465 466The HPET setting has been turned into a machine property. 467Use ``-machine hpet=off`` instead. 468 469``-no-acpi`` (removed in 9.0) 470''''''''''''''''''''''''''''' 471 472The ``-no-acpi`` setting has been turned into a machine property. 473Use ``-machine acpi=off`` instead. 474 475``-async-teardown`` (removed in 9.0) 476'''''''''''''''''''''''''''''''''''' 477 478Use ``-run-with async-teardown=on`` instead. 479 480``-chroot`` (removed in 9.0) 481'''''''''''''''''''''''''''' 482 483Use ``-run-with chroot=dir`` instead. 484 485``-singlestep`` (removed in 9.0) 486'''''''''''''''''''''''''''''''' 487 488The ``-singlestep`` option has been turned into an accelerator property, 489and given a name that better reflects what it actually does. 490Use ``-accel tcg,one-insn-per-tb=on`` instead. 491 492``-smp`` ("parameter=0" SMP configurations) (removed in 9.0) 493'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 494 495Specified CPU topology parameters must be greater than zero. 496 497In the SMP configuration, users should either provide a CPU topology 498parameter with a reasonable value (greater than zero) or just omit it 499and QEMU will compute the missing value. 500 501However, historically it was implicitly allowed for users to provide 502a parameter with zero value, which is meaningless and could also possibly 503cause unexpected results in the -smp parsing. So support for this kind of 504configurations (e.g. -smp 8,sockets=0) is removed since 9.0, users have 505to ensure that all the topology members described with -smp are greater 506than zero. 507 508``-global migration.decompress-error-check`` (removed in 9.1) 509''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 510 511Removed along with the ``compression`` migration capability. 512 513User-mode emulator command line arguments 514----------------------------------------- 515 516``-singlestep`` (removed in 9.0) 517'''''''''''''''''''''''''''''''' 518 519The ``-singlestep`` option has been given a name that better reflects 520what it actually does. For both linux-user and bsd-user, use the 521``-one-insn-per-tb`` option instead. 522 523 524QEMU Machine Protocol (QMP) commands 525------------------------------------ 526 527``block-dirty-bitmap-add`` "autoload" parameter (removed in 4.2) 528'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 529 530The "autoload" parameter has been ignored since 2.12.0. All bitmaps 531are automatically loaded from qcow2 images. 532 533``cpu-add`` (removed in 5.2) 534'''''''''''''''''''''''''''' 535 536Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See 537documentation of ``query-hotpluggable-cpus`` for additional details. 538 539``change`` (removed in 6.0) 540''''''''''''''''''''''''''' 541 542Use ``blockdev-change-medium`` or ``change-vnc-password`` or 543``display-update`` instead. 544 545``query-events`` (removed in 6.0) 546''''''''''''''''''''''''''''''''' 547 548The ``query-events`` command has been superseded by the more powerful 549and accurate ``query-qmp-schema`` command. 550 551``migrate_set_cache_size`` and ``query-migrate-cache-size`` (removed in 6.0) 552'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 553 554Use ``migrate_set_parameter`` and ``info migrate_parameters`` instead. 555 556``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0) 557''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 558 559Use ``migrate_set_parameter`` instead. 560 561``query-cpus`` (removed in 6.0) 562''''''''''''''''''''''''''''''' 563 564The ``query-cpus`` command is replaced by the ``query-cpus-fast`` command. 565 566``query-cpus-fast`` ``arch`` output member (removed in 6.0) 567''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 568 569The ``arch`` output member of the ``query-cpus-fast`` command is 570replaced by the ``target`` output member. 571 572chardev client socket with ``wait`` option (removed in 6.0) 573''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 574 575Character devices creating sockets in client mode should not specify 576the 'wait' field, which is only applicable to sockets in server mode 577 578``query-named-block-nodes`` result ``encryption_key_missing`` (removed in 6.0) 579'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 580 581Removed with no replacement. 582 583``query-block`` result ``inserted.encryption_key_missing`` (removed in 6.0) 584''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 585 586Removed with no replacement. 587 588``query-named-block-nodes`` and ``query-block`` result dirty-bitmaps[i].status (removed in 6.0) 589''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 590 591The ``status`` field of the ``BlockDirtyInfo`` structure, returned by 592these commands is removed. Two new boolean fields, ``recording`` and 593``busy`` effectively replace it. 594 595``query-block`` result field ``dirty-bitmaps`` (removed in 6.0) 596''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 597 598The ``dirty-bitmaps`` field of the ``BlockInfo`` structure, returned by 599the query-block command is itself now removed. The ``dirty-bitmaps`` 600field of the ``BlockDeviceInfo`` struct should be used instead, which is the 601type of the ``inserted`` field in query-block replies, as well as the 602type of array items in query-named-block-nodes. 603 604``object-add`` option ``props`` (removed in 6.0) 605'''''''''''''''''''''''''''''''''''''''''''''''' 606 607Specify the properties for the object as top-level arguments instead. 608 609``query-sgx`` return value member ``section-size`` (removed in 8.0) 610''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 611 612Member ``section-size`` in the return value of ``query-sgx`` 613was superseded by ``sections``. 614 615 616``query-sgx-capabilities`` return value member ``section-size`` (removed in 8.0) 617'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 618 619Member ``section-size`` in the return value of ``query-sgx-capabilities`` 620was superseded by ``sections``. 621 622``query-migrate`` return value member ``skipped`` (removed in 9.1) 623'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 624 625Member ``skipped`` of the ``MigrationStats`` struct hasn't been used 626for more than 10 years. Removed with no replacement. 627 628``migrate`` command option ``inc`` (removed in 9.1) 629''''''''''''''''''''''''''''''''''''''''''''''''''' 630 631Use blockdev-mirror with NBD instead. See "QMP invocation for live 632storage migration with ``blockdev-mirror`` + NBD" in 633docs/interop/live-block-operations.rst for a detailed explanation. 634 635``migrate`` command option ``blk`` (removed in 9.1) 636''''''''''''''''''''''''''''''''''''''''''''''''''' 637 638Use blockdev-mirror with NBD instead. See "QMP invocation for live 639storage migration with ``blockdev-mirror`` + NBD" in 640docs/interop/live-block-operations.rst for a detailed explanation. 641 642``migrate-set-capabilities`` ``block`` option (removed in 9.1) 643'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 644 645Block migration has been removed. For a replacement, see "QMP 646invocation for live storage migration with ``blockdev-mirror`` + NBD" 647in docs/interop/live-block-operations.rst. 648 649``migrate-set-parameter`` ``compress-level`` option (removed in 9.1) 650'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 651 652Use ``multifd-zlib-level`` or ``multifd-zstd-level`` instead. 653 654``migrate-set-parameter`` ``compress-threads`` option (removed in 9.1) 655'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 656 657Use ``multifd-channels`` instead. 658 659``migrate-set-parameter`` ``compress-wait-thread`` option (removed in 9.1) 660'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 661 662Removed with no replacement. 663 664``migrate-set-parameter`` ``decompress-threads`` option (removed in 9.1) 665'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 666 667Use ``multifd-channels`` instead. 668 669``migrate-set-capability`` ``compress`` option (removed in 9.1) 670''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 671 672Use ``multifd-compression`` instead. 673 674QEMU Machine Protocol (QMP) events 675---------------------------------- 676 677``MEM_UNPLUG_ERROR`` (removed in 9.1) 678''''''''''''''''''''''''''''''''''''' 679 680MEM_UNPLUG_ERROR has been replaced by the more generic ``DEVICE_UNPLUG_GUEST_ERROR`` event. 681 682 683Human Monitor Protocol (HMP) commands 684------------------------------------- 685 686``usb_add`` and ``usb_remove`` (removed in 2.12) 687'''''''''''''''''''''''''''''''''''''''''''''''' 688 689Replaced by ``device_add`` and ``device_del`` (use ``device_add help`` for a 690list of available devices). 691 692``host_net_add`` and ``host_net_remove`` (removed in 2.12) 693'''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 694 695Replaced by ``netdev_add`` and ``netdev_del``. 696 697The ``hub_id`` parameter of ``hostfwd_add`` / ``hostfwd_remove`` (removed in 5.0) 698''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 699 700The ``[hub_id name]`` parameter tuple of the 'hostfwd_add' and 701'hostfwd_remove' HMP commands has been replaced by ``netdev_id``. 702 703``cpu-add`` (removed in 5.2) 704'''''''''''''''''''''''''''' 705 706Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See 707documentation of ``query-hotpluggable-cpus`` for additional details. 708 709``change vnc TARGET`` (removed in 6.0) 710'''''''''''''''''''''''''''''''''''''' 711 712No replacement. The ``change vnc password`` and ``change DEVICE MEDIUM`` 713commands are not affected. 714 715``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, ``acl_remove`` (removed in 6.0) 716''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 717 718The ``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, and 719``acl_remove`` commands were removed with no replacement. Authorization 720for VNC should be performed using the pluggable QAuthZ objects. 721 722``migrate-set-cache-size`` and ``info migrate-cache-size`` (removed in 6.0) 723''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 724 725Use ``migrate-set-parameters`` and ``info migrate-parameters`` instead. 726 727``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0) 728''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 729 730Use ``migrate-set-parameters`` instead. 731 732``info cpustats`` (removed in 6.1) 733'''''''''''''''''''''''''''''''''' 734 735This command didn't produce any output already. Removed with no replacement. 736 737``singlestep`` (removed in 9.0) 738''''''''''''''''''''''''''''''' 739 740The ``singlestep`` command has been replaced by the ``one-insn-per-tb`` 741command, which has the same behaviour but a less misleading name. 742 743``migrate`` command ``-i`` option (removed in 9.1) 744'''''''''''''''''''''''''''''''''''''''''''''''''' 745 746Use blockdev-mirror with NBD instead. See "QMP invocation for live 747storage migration with ``blockdev-mirror`` + NBD" in 748docs/interop/live-block-operations.rst for a detailed explanation. 749 750``migrate`` command ``-b`` option (removed in 9.1) 751'''''''''''''''''''''''''''''''''''''''''''''''''' 752 753Use blockdev-mirror with NBD instead. See "QMP invocation for live 754storage migration with ``blockdev-mirror`` + NBD" in 755docs/interop/live-block-operations.rst for a detailed explanation. 756 757``migrate_set_capability`` ``block`` option (removed in 9.1) 758'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 759 760Block migration has been removed. For a replacement, see "QMP 761invocation for live storage migration with ``blockdev-mirror`` + NBD" 762in docs/interop/live-block-operations.rst. 763 764``migrate_set_parameter`` ``compress-level`` option (removed in 9.1) 765'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 766 767Use ``multifd-zlib-level`` or ``multifd-zstd-level`` instead. 768 769``migrate_set_parameter`` ``compress-threads`` option (removed in 9.1) 770'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 771 772Use ``multifd-channels`` instead. 773 774``migrate_set_parameter`` ``compress-wait-thread`` option (removed in 9.1) 775'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 776 777Removed with no replacement. 778 779``migrate_set_parameter`` ``decompress-threads`` option (removed in 9.1) 780'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 781 782Use ``multifd-channels`` instead. 783 784``migrate_set_capability`` ``compress`` option (removed in 9.1) 785''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 786 787Use ``multifd-compression`` instead. 788 789Host Architectures 790------------------ 791 792System emulation on 32-bit Windows hosts (removed in 9.0) 793''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 794 795Windows 11 has no support for 32-bit host installs, and Windows 10 did 796not support new 32-bit installs, only upgrades. 32-bit Windows support 797has now been dropped by the MSYS2 project. QEMU also is deprecating 798and dropping support for 32-bit x86 host deployments in 799general. 32-bit Windows is therefore no longer a supported host for 800QEMU. Since all recent x86 hardware from the past >10 years is 801capable of the 64-bit x86 extensions, a corresponding 64-bit OS should 802be used instead. 803 804Guest Emulator ISAs 805------------------- 806 807RISC-V ISA privilege specification version 1.09.1 (removed in 5.1) 808'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 809 810The RISC-V ISA privilege specification version 1.09.1 has been removed. 811QEMU supports both the newer version 1.10.0 and the ratified version 1.11.0, these 812should be used instead of the 1.09.1 version. 813 814System emulator CPUS 815-------------------- 816 817KVM guest support on 32-bit Arm hosts (removed in 5.2) 818'''''''''''''''''''''''''''''''''''''''''''''''''''''' 819 820The Linux kernel has dropped support for allowing 32-bit Arm systems 821to host KVM guests as of the 5.7 kernel, and was thus removed from QEMU 822as well. Running 32-bit guests on a 64-bit Arm host remains supported. 823 824RISC-V ISA Specific CPUs (removed in 5.1) 825''''''''''''''''''''''''''''''''''''''''' 826 827The RISC-V cpus with the ISA version in the CPU name have been removed. The 828four CPUs are: ``rv32gcsu-v1.9.1``, ``rv32gcsu-v1.10.0``, ``rv64gcsu-v1.9.1`` and 829``rv64gcsu-v1.10.0``. Instead the version can be specified via the CPU ``priv_spec`` 830option when using the ``rv32`` or ``rv64`` CPUs. 831 832RISC-V no MMU CPUs (removed in 5.1) 833''''''''''''''''''''''''''''''''''' 834 835The RISC-V no MMU cpus have been removed. The two CPUs: ``rv32imacu-nommu`` and 836``rv64imacu-nommu`` can no longer be used. Instead the MMU status can be specified 837via the CPU ``mmu`` option when using the ``rv32`` or ``rv64`` CPUs. 838 839``compat`` property of server class POWER CPUs (removed in 6.0) 840''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 841 842The ``max-cpu-compat`` property of the ``pseries`` machine type should be used 843instead. 844 845``moxie`` CPU (removed in 6.1) 846'''''''''''''''''''''''''''''' 847 848Nobody was using this CPU emulation in QEMU, and there were no test images 849available to make sure that the code is still working, so it has been removed 850without replacement. 851 852``lm32`` CPUs (removed in 6.1) 853'''''''''''''''''''''''''''''' 854 855The only public user of this architecture was the milkymist project, 856which has been dead for years; there was never an upstream Linux 857port. Removed without replacement. 858 859``unicore32`` CPUs (removed in 6.1) 860''''''''''''''''''''''''''''''''''' 861 862Support for this CPU was removed from the upstream Linux kernel, and 863there is no available upstream toolchain to build binaries for it. 864Removed without replacement. 865 866x86 ``Icelake-Client`` CPU (removed in 7.1) 867''''''''''''''''''''''''''''''''''''''''''' 868 869There isn't ever Icelake Client CPU, it is some wrong and imaginary one. 870Use ``Icelake-Server`` instead. 871 872Nios II CPU (removed in 9.1) 873'''''''''''''''''''''''''''' 874 875QEMU Nios II architecture was orphan; Intel has EOL'ed the Nios II 876processor IP (see `Intel discontinuance notification`_). 877 878System accelerators 879------------------- 880 881Userspace local APIC with KVM (x86, removed in 8.0) 882''''''''''''''''''''''''''''''''''''''''''''''''''' 883 884``-M kernel-irqchip=off`` cannot be used on KVM if the CPU model includes 885a local APIC. The ``split`` setting is supported, as is using ``-M 886kernel-irqchip=off`` when the CPU does not have a local APIC. 887 888HAXM (``-accel hax``) (removed in 8.2) 889'''''''''''''''''''''''''''''''''''''' 890 891The HAXM project has been retired (see https://github.com/intel/haxm#status). 892Use "whpx" (on Windows) or "hvf" (on macOS) instead. 893 894MIPS "Trap-and-Emulate" KVM support (removed in 8.0) 895'''''''''''''''''''''''''''''''''''''''''''''''''''' 896 897The MIPS "Trap-and-Emulate" KVM host and guest support was removed 898from Linux in 2021, and is not supported anymore by QEMU either. 899 900System emulator machines 901------------------------ 902 903``s390-virtio`` (removed in 2.6) 904'''''''''''''''''''''''''''''''' 905 906Use the ``s390-ccw-virtio`` machine instead. 907 908The m68k ``dummy`` machine (removed in 2.9) 909''''''''''''''''''''''''''''''''''''''''''' 910 911Use the ``none`` machine with the ``loader`` device instead. 912 913``xlnx-ep108`` (removed in 3.0) 914''''''''''''''''''''''''''''''' 915 916The EP108 was an early access development board that is no longer used. 917Use the ``xlnx-zcu102`` machine instead. 918 919``spike_v1.9.1`` and ``spike_v1.10`` (removed in 5.1) 920''''''''''''''''''''''''''''''''''''''''''''''''''''' 921 922The version specific Spike machines have been removed in favour of the 923generic ``spike`` machine. If you need to specify an older version of the RISC-V 924spec you can use the ``-cpu rv64gcsu,priv_spec=v1.10.0`` command line argument. 925 926mips ``r4k`` platform (removed in 5.2) 927'''''''''''''''''''''''''''''''''''''' 928 929This machine type was very old and unmaintained. Users should use the ``malta`` 930machine type instead. 931 932mips ``fulong2e`` machine alias (removed in 6.0) 933'''''''''''''''''''''''''''''''''''''''''''''''' 934 935This machine has been renamed ``fuloong2e``. 936 937``pc-0.10`` up to ``pc-i440fx-1.7`` (removed in 4.0 up to 8.2) 938'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 939 940These machine types were very old and likely could not be used for live 941migration from old QEMU versions anymore. Use a newer machine type instead. 942 943Raspberry Pi ``raspi2`` and ``raspi3`` machines (removed in 6.2) 944'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 945 946The Raspberry Pi machines come in various models (A, A+, B, B+). To be able 947to distinguish which model QEMU is implementing, the ``raspi2`` and ``raspi3`` 948machines have been renamed ``raspi2b`` and ``raspi3b``. 949 950Aspeed ``swift-bmc`` machine (removed in 7.0) 951''''''''''''''''''''''''''''''''''''''''''''' 952 953This machine was removed because it was unused. Alternative AST2500 based 954OpenPOWER machines are ``witherspoon-bmc`` and ``romulus-bmc``. 955 956ppc ``taihu`` machine (removed in 7.2) 957''''''''''''''''''''''''''''''''''''''''''''' 958 959This machine was removed because it was partially emulated and 405 960machines are very similar. Use the ``ref405ep`` machine instead. 961 962Nios II ``10m50-ghrd`` and ``nios2-generic-nommu`` machines (removed in 9.1) 963'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 964 965The Nios II architecture was orphan. 966 967linux-user mode CPUs 968-------------------- 969 970``tilegx`` CPUs (removed in 6.0) 971'''''''''''''''''''''''''''''''' 972 973The ``tilegx`` guest CPU support has been removed without replacement. It was 974only implemented in linux-user mode, but support for this CPU was removed from 975the upstream Linux kernel in 2018, and it has also been dropped from glibc, so 976there is no new Linux development taking place with this architecture. For 977running the old binaries, you can use older versions of QEMU. 978 979``ppc64abi32`` CPUs (removed in 7.0) 980'''''''''''''''''''''''''''''''''''' 981 982The ``ppc64abi32`` architecture has a number of issues which regularly 983tripped up the CI testing and was suspected to be quite broken. For that 984reason the maintainers strongly suspected no one actually used it. 985 986``nios2`` CPU (removed in 9.1) 987'''''''''''''''''''''''''''''' 988 989QEMU Nios II architecture was orphan; Intel has EOL'ed the Nios II 990processor IP (see `Intel discontinuance notification`_). 991 992TCG introspection features 993-------------------------- 994 995TCG trace-events (since 6.2) 996'''''''''''''''''''''''''''' 997 998The ability to add new TCG trace points had bit rotted and as the 999feature can be replicated with TCG plugins it was removed. If 1000any user is currently using this feature and needs help with 1001converting to using TCG plugins they should contact the qemu-devel 1002mailing list. 1003 1004 1005System emulator devices 1006----------------------- 1007 1008``spapr-pci-vfio-host-bridge`` (removed in 2.12) 1009''''''''''''''''''''''''''''''''''''''''''''''''' 1010 1011The ``spapr-pci-vfio-host-bridge`` device type has been replaced by the 1012``spapr-pci-host-bridge`` device type. 1013 1014``ivshmem`` (removed in 4.0) 1015'''''''''''''''''''''''''''' 1016 1017Replaced by either the ``ivshmem-plain`` or ``ivshmem-doorbell``. 1018 1019``ide-drive`` (removed in 6.0) 1020'''''''''''''''''''''''''''''' 1021 1022The 'ide-drive' device has been removed. Users should use 'ide-hd' or 1023'ide-cd' as appropriate to get an IDE hard disk or CD-ROM as needed. 1024 1025``scsi-disk`` (removed in 6.0) 1026'''''''''''''''''''''''''''''' 1027 1028The 'scsi-disk' device has been removed. Users should use 'scsi-hd' or 1029'scsi-cd' as appropriate to get a SCSI hard disk or CD-ROM as needed. 1030 1031``sga`` (removed in 8.0) 1032'''''''''''''''''''''''' 1033 1034The ``sga`` device loaded an option ROM for x86 targets which enabled 1035SeaBIOS to send messages to the serial console. SeaBIOS 1.11.0 onwards 1036contains native support for this feature and thus use of the option 1037ROM approach was obsolete. The native SeaBIOS support can be activated 1038by using ``-machine graphics=off``. 1039 1040``pvrdma`` and the RDMA subsystem (removed in 9.1) 1041'''''''''''''''''''''''''''''''''''''''''''''''''' 1042 1043The 'pvrdma' device and the whole RDMA subsystem have been removed. 1044 1045Related binaries 1046---------------- 1047 1048``qemu-nbd --partition`` (removed in 5.0) 1049''''''''''''''''''''''''''''''''''''''''' 1050 1051The ``qemu-nbd --partition $digit`` code (also spelled ``-P``) 1052could only handle MBR partitions, and never correctly handled logical 1053partitions beyond partition 5. Exporting a partition can still be 1054done by utilizing the ``--image-opts`` option with a raw blockdev 1055using the ``offset`` and ``size`` parameters layered on top of 1056any other existing blockdev. For example, if partition 1 is 100MiB 1057long starting at 1MiB, the old command:: 1058 1059 qemu-nbd -t -P 1 -f qcow2 file.qcow2 1060 1061can be rewritten as:: 1062 1063 qemu-nbd -t --image-opts driver=raw,offset=1M,size=100M,file.driver=qcow2,file.file.driver=file,file.file.filename=file.qcow2 1064 1065``qemu-img convert -n -o`` (removed in 5.1) 1066''''''''''''''''''''''''''''''''''''''''''' 1067 1068All options specified in ``-o`` are image creation options, so 1069they are now rejected when used with ``-n`` to skip image creation. 1070 1071 1072``qemu-img create -b bad file $size`` (removed in 5.1) 1073'''''''''''''''''''''''''''''''''''''''''''''''''''''' 1074 1075When creating an image with a backing file that could not be opened, 1076``qemu-img create`` used to issue a warning about the failure but 1077proceed with the image creation if an explicit size was provided. 1078However, as the ``-u`` option exists for this purpose, it is safer to 1079enforce that any failure to open the backing image (including if the 1080backing file is missing or an incorrect format was specified) is an 1081error when ``-u`` is not used. 1082 1083``qemu-img amend`` to adjust backing file (removed in 6.1) 1084'''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 1085 1086The use of ``qemu-img amend`` to modify the name or format of a qcow2 1087backing image was never fully documented or tested, and interferes 1088with other amend operations that need access to the original backing 1089image (such as deciding whether a v3 zero cluster may be left 1090unallocated when converting to a v2 image). Any changes to the 1091backing chain should be performed with ``qemu-img rebase -u`` either 1092before or after the remaining changes being performed by amend, as 1093appropriate. 1094 1095``qemu-img`` backing file without format (removed in 6.1) 1096''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 1097 1098The use of ``qemu-img create``, ``qemu-img rebase``, or ``qemu-img 1099convert`` to create or modify an image that depends on a backing file 1100now requires that an explicit backing format be provided. This is 1101for safety: if QEMU probes a different format than what you thought, 1102the data presented to the guest will be corrupt; similarly, presenting 1103a raw image to a guest allows a potential security exploit if a future 1104probe sees a non-raw image based on guest writes. 1105 1106To avoid creating unsafe backing chains, you must pass ``-o 1107backing_fmt=`` (or the shorthand ``-F`` during create) to specify the 1108intended backing format. You may use ``qemu-img rebase -u`` to 1109retroactively add a backing format to an existing image. However, be 1110aware that there are already potential security risks to blindly using 1111``qemu-img info`` to probe the format of an untrusted backing image, 1112when deciding what format to add into an existing image. 1113 1114Block devices 1115------------- 1116 1117VXHS backend (removed in 5.1) 1118''''''''''''''''''''''''''''' 1119 1120The VXHS code did not compile since v2.12.0. It was removed in 5.1. 1121 1122``sheepdog`` driver (removed in 6.0) 1123'''''''''''''''''''''''''''''''''''' 1124 1125The corresponding upstream server project is no longer maintained. 1126Users are recommended to switch to an alternative distributed block 1127device driver such as RBD. 1128 1129Tools 1130----- 1131 1132virtiofsd (removed in 8.0) 1133'''''''''''''''''''''''''' 1134 1135There is a newer Rust implementation of ``virtiofsd`` at 1136``https://gitlab.com/virtio-fs/virtiofsd``; this has been 1137stable for some time and is now widely used. 1138The command line and feature set is very close to the removed 1139C implementation. 1140 1141.. _Intel discontinuance notification: https://www.intel.com/content/www/us/en/content-details/781327/intel-is-discontinuing-ip-ordering-codes-listed-in-pdn2312-for-nios-ii-ip.html 1142