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 508User-mode emulator command line arguments 509----------------------------------------- 510 511``-singlestep`` (removed in 9.0) 512'''''''''''''''''''''''''''''''' 513 514The ``-singlestep`` option has been given a name that better reflects 515what it actually does. For both linux-user and bsd-user, use the 516``-one-insn-per-tb`` option instead. 517 518 519QEMU Machine Protocol (QMP) commands 520------------------------------------ 521 522``block-dirty-bitmap-add`` "autoload" parameter (removed in 4.2) 523'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 524 525The "autoload" parameter has been ignored since 2.12.0. All bitmaps 526are automatically loaded from qcow2 images. 527 528``cpu-add`` (removed in 5.2) 529'''''''''''''''''''''''''''' 530 531Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See 532documentation of ``query-hotpluggable-cpus`` for additional details. 533 534``change`` (removed in 6.0) 535''''''''''''''''''''''''''' 536 537Use ``blockdev-change-medium`` or ``change-vnc-password`` or 538``display-update`` instead. 539 540``query-events`` (removed in 6.0) 541''''''''''''''''''''''''''''''''' 542 543The ``query-events`` command has been superseded by the more powerful 544and accurate ``query-qmp-schema`` command. 545 546``migrate_set_cache_size`` and ``query-migrate-cache-size`` (removed in 6.0) 547'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 548 549Use ``migrate_set_parameter`` and ``info migrate_parameters`` instead. 550 551``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0) 552''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 553 554Use ``migrate_set_parameter`` instead. 555 556``query-cpus`` (removed in 6.0) 557''''''''''''''''''''''''''''''' 558 559The ``query-cpus`` command is replaced by the ``query-cpus-fast`` command. 560 561``query-cpus-fast`` ``arch`` output member (removed in 6.0) 562''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 563 564The ``arch`` output member of the ``query-cpus-fast`` command is 565replaced by the ``target`` output member. 566 567chardev client socket with ``wait`` option (removed in 6.0) 568''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 569 570Character devices creating sockets in client mode should not specify 571the 'wait' field, which is only applicable to sockets in server mode 572 573``query-named-block-nodes`` result ``encryption_key_missing`` (removed in 6.0) 574'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 575 576Removed with no replacement. 577 578``query-block`` result ``inserted.encryption_key_missing`` (removed in 6.0) 579''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 580 581Removed with no replacement. 582 583``query-named-block-nodes`` and ``query-block`` result dirty-bitmaps[i].status (removed in 6.0) 584''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 585 586The ``status`` field of the ``BlockDirtyInfo`` structure, returned by 587these commands is removed. Two new boolean fields, ``recording`` and 588``busy`` effectively replace it. 589 590``query-block`` result field ``dirty-bitmaps`` (removed in 6.0) 591''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 592 593The ``dirty-bitmaps`` field of the ``BlockInfo`` structure, returned by 594the query-block command is itself now removed. The ``dirty-bitmaps`` 595field of the ``BlockDeviceInfo`` struct should be used instead, which is the 596type of the ``inserted`` field in query-block replies, as well as the 597type of array items in query-named-block-nodes. 598 599``object-add`` option ``props`` (removed in 6.0) 600'''''''''''''''''''''''''''''''''''''''''''''''' 601 602Specify the properties for the object as top-level arguments instead. 603 604``query-sgx`` return value member ``section-size`` (removed in 8.0) 605''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 606 607Member ``section-size`` in the return value of ``query-sgx`` 608was superseded by ``sections``. 609 610 611``query-sgx-capabilities`` return value member ``section-size`` (removed in 8.0) 612'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 613 614Member ``section-size`` in the return value of ``query-sgx-capabilities`` 615was superseded by ``sections``. 616 617``query-migrate`` return value member ``skipped`` (removed in 9.1) 618'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 619 620Member ``skipped`` of the ``MigrationStats`` struct hasn't been used 621for more than 10 years. Removed with no replacement. 622 623``migrate`` command option ``inc`` (removed in 9.1) 624''''''''''''''''''''''''''''''''''''''''''''''''''' 625 626Use blockdev-mirror with NBD instead. See "QMP invocation for live 627storage migration with ``blockdev-mirror`` + NBD" in 628docs/interop/live-block-operations.rst for a detailed explanation. 629 630``migrate`` command option ``blk`` (removed in 9.1) 631''''''''''''''''''''''''''''''''''''''''''''''''''' 632 633Use blockdev-mirror with NBD instead. See "QMP invocation for live 634storage migration with ``blockdev-mirror`` + NBD" in 635docs/interop/live-block-operations.rst for a detailed explanation. 636 637Human Monitor Protocol (HMP) commands 638------------------------------------- 639 640``usb_add`` and ``usb_remove`` (removed in 2.12) 641'''''''''''''''''''''''''''''''''''''''''''''''' 642 643Replaced by ``device_add`` and ``device_del`` (use ``device_add help`` for a 644list of available devices). 645 646``host_net_add`` and ``host_net_remove`` (removed in 2.12) 647'''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 648 649Replaced by ``netdev_add`` and ``netdev_del``. 650 651The ``hub_id`` parameter of ``hostfwd_add`` / ``hostfwd_remove`` (removed in 5.0) 652''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 653 654The ``[hub_id name]`` parameter tuple of the 'hostfwd_add' and 655'hostfwd_remove' HMP commands has been replaced by ``netdev_id``. 656 657``cpu-add`` (removed in 5.2) 658'''''''''''''''''''''''''''' 659 660Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See 661documentation of ``query-hotpluggable-cpus`` for additional details. 662 663``change vnc TARGET`` (removed in 6.0) 664'''''''''''''''''''''''''''''''''''''' 665 666No replacement. The ``change vnc password`` and ``change DEVICE MEDIUM`` 667commands are not affected. 668 669``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, ``acl_remove`` (removed in 6.0) 670''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 671 672The ``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, and 673``acl_remove`` commands were removed with no replacement. Authorization 674for VNC should be performed using the pluggable QAuthZ objects. 675 676``migrate-set-cache-size`` and ``info migrate-cache-size`` (removed in 6.0) 677''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 678 679Use ``migrate-set-parameters`` and ``info migrate-parameters`` instead. 680 681``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0) 682''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 683 684Use ``migrate-set-parameters`` instead. 685 686``info cpustats`` (removed in 6.1) 687'''''''''''''''''''''''''''''''''' 688 689This command didn't produce any output already. Removed with no replacement. 690 691``singlestep`` (removed in 9.0) 692''''''''''''''''''''''''''''''' 693 694The ``singlestep`` command has been replaced by the ``one-insn-per-tb`` 695command, which has the same behaviour but a less misleading name. 696 697``migrate`` command ``-i`` option (removed in 9.1) 698'''''''''''''''''''''''''''''''''''''''''''''''''' 699 700Use blockdev-mirror with NBD instead. See "QMP invocation for live 701storage migration with ``blockdev-mirror`` + NBD" in 702docs/interop/live-block-operations.rst for a detailed explanation. 703 704``migrate`` command ``-b`` option (removed in 9.1) 705'''''''''''''''''''''''''''''''''''''''''''''''''' 706 707Use blockdev-mirror with NBD instead. See "QMP invocation for live 708storage migration with ``blockdev-mirror`` + NBD" in 709docs/interop/live-block-operations.rst for a detailed explanation. 710 711Host Architectures 712------------------ 713 714System emulation on 32-bit Windows hosts (removed in 9.0) 715''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 716 717Windows 11 has no support for 32-bit host installs, and Windows 10 did 718not support new 32-bit installs, only upgrades. 32-bit Windows support 719has now been dropped by the MSYS2 project. QEMU also is deprecating 720and dropping support for 32-bit x86 host deployments in 721general. 32-bit Windows is therefore no longer a supported host for 722QEMU. Since all recent x86 hardware from the past >10 years is 723capable of the 64-bit x86 extensions, a corresponding 64-bit OS should 724be used instead. 725 726Guest Emulator ISAs 727------------------- 728 729RISC-V ISA privilege specification version 1.09.1 (removed in 5.1) 730'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 731 732The RISC-V ISA privilege specification version 1.09.1 has been removed. 733QEMU supports both the newer version 1.10.0 and the ratified version 1.11.0, these 734should be used instead of the 1.09.1 version. 735 736System emulator CPUS 737-------------------- 738 739KVM guest support on 32-bit Arm hosts (removed in 5.2) 740'''''''''''''''''''''''''''''''''''''''''''''''''''''' 741 742The Linux kernel has dropped support for allowing 32-bit Arm systems 743to host KVM guests as of the 5.7 kernel, and was thus removed from QEMU 744as well. Running 32-bit guests on a 64-bit Arm host remains supported. 745 746RISC-V ISA Specific CPUs (removed in 5.1) 747''''''''''''''''''''''''''''''''''''''''' 748 749The RISC-V cpus with the ISA version in the CPU name have been removed. The 750four CPUs are: ``rv32gcsu-v1.9.1``, ``rv32gcsu-v1.10.0``, ``rv64gcsu-v1.9.1`` and 751``rv64gcsu-v1.10.0``. Instead the version can be specified via the CPU ``priv_spec`` 752option when using the ``rv32`` or ``rv64`` CPUs. 753 754RISC-V no MMU CPUs (removed in 5.1) 755''''''''''''''''''''''''''''''''''' 756 757The RISC-V no MMU cpus have been removed. The two CPUs: ``rv32imacu-nommu`` and 758``rv64imacu-nommu`` can no longer be used. Instead the MMU status can be specified 759via the CPU ``mmu`` option when using the ``rv32`` or ``rv64`` CPUs. 760 761``compat`` property of server class POWER CPUs (removed in 6.0) 762''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 763 764The ``max-cpu-compat`` property of the ``pseries`` machine type should be used 765instead. 766 767``moxie`` CPU (removed in 6.1) 768'''''''''''''''''''''''''''''' 769 770Nobody was using this CPU emulation in QEMU, and there were no test images 771available to make sure that the code is still working, so it has been removed 772without replacement. 773 774``lm32`` CPUs (removed in 6.1) 775'''''''''''''''''''''''''''''' 776 777The only public user of this architecture was the milkymist project, 778which has been dead for years; there was never an upstream Linux 779port. Removed without replacement. 780 781``unicore32`` CPUs (removed in 6.1) 782''''''''''''''''''''''''''''''''''' 783 784Support for this CPU was removed from the upstream Linux kernel, and 785there is no available upstream toolchain to build binaries for it. 786Removed without replacement. 787 788x86 ``Icelake-Client`` CPU (removed in 7.1) 789''''''''''''''''''''''''''''''''''''''''''' 790 791There isn't ever Icelake Client CPU, it is some wrong and imaginary one. 792Use ``Icelake-Server`` instead. 793 794Nios II CPU (removed in 9.1) 795'''''''''''''''''''''''''''' 796 797QEMU Nios II architecture was orphan; Intel has EOL'ed the Nios II 798processor IP (see `Intel discontinuance notification`_). 799 800System accelerators 801------------------- 802 803Userspace local APIC with KVM (x86, removed in 8.0) 804''''''''''''''''''''''''''''''''''''''''''''''''''' 805 806``-M kernel-irqchip=off`` cannot be used on KVM if the CPU model includes 807a local APIC. The ``split`` setting is supported, as is using ``-M 808kernel-irqchip=off`` when the CPU does not have a local APIC. 809 810HAXM (``-accel hax``) (removed in 8.2) 811'''''''''''''''''''''''''''''''''''''' 812 813The HAXM project has been retired (see https://github.com/intel/haxm#status). 814Use "whpx" (on Windows) or "hvf" (on macOS) instead. 815 816MIPS "Trap-and-Emulate" KVM support (removed in 8.0) 817'''''''''''''''''''''''''''''''''''''''''''''''''''' 818 819The MIPS "Trap-and-Emulate" KVM host and guest support was removed 820from Linux in 2021, and is not supported anymore by QEMU either. 821 822System emulator machines 823------------------------ 824 825``s390-virtio`` (removed in 2.6) 826'''''''''''''''''''''''''''''''' 827 828Use the ``s390-ccw-virtio`` machine instead. 829 830The m68k ``dummy`` machine (removed in 2.9) 831''''''''''''''''''''''''''''''''''''''''''' 832 833Use the ``none`` machine with the ``loader`` device instead. 834 835``xlnx-ep108`` (removed in 3.0) 836''''''''''''''''''''''''''''''' 837 838The EP108 was an early access development board that is no longer used. 839Use the ``xlnx-zcu102`` machine instead. 840 841``spike_v1.9.1`` and ``spike_v1.10`` (removed in 5.1) 842''''''''''''''''''''''''''''''''''''''''''''''''''''' 843 844The version specific Spike machines have been removed in favour of the 845generic ``spike`` machine. If you need to specify an older version of the RISC-V 846spec you can use the ``-cpu rv64gcsu,priv_spec=v1.10.0`` command line argument. 847 848mips ``r4k`` platform (removed in 5.2) 849'''''''''''''''''''''''''''''''''''''' 850 851This machine type was very old and unmaintained. Users should use the ``malta`` 852machine type instead. 853 854mips ``fulong2e`` machine alias (removed in 6.0) 855'''''''''''''''''''''''''''''''''''''''''''''''' 856 857This machine has been renamed ``fuloong2e``. 858 859``pc-0.10`` up to ``pc-i440fx-1.7`` (removed in 4.0 up to 8.2) 860'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 861 862These machine types were very old and likely could not be used for live 863migration from old QEMU versions anymore. Use a newer machine type instead. 864 865Raspberry Pi ``raspi2`` and ``raspi3`` machines (removed in 6.2) 866'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 867 868The Raspberry Pi machines come in various models (A, A+, B, B+). To be able 869to distinguish which model QEMU is implementing, the ``raspi2`` and ``raspi3`` 870machines have been renamed ``raspi2b`` and ``raspi3b``. 871 872Aspeed ``swift-bmc`` machine (removed in 7.0) 873''''''''''''''''''''''''''''''''''''''''''''' 874 875This machine was removed because it was unused. Alternative AST2500 based 876OpenPOWER machines are ``witherspoon-bmc`` and ``romulus-bmc``. 877 878ppc ``taihu`` machine (removed in 7.2) 879''''''''''''''''''''''''''''''''''''''''''''' 880 881This machine was removed because it was partially emulated and 405 882machines are very similar. Use the ``ref405ep`` machine instead. 883 884Nios II ``10m50-ghrd`` and ``nios2-generic-nommu`` machines (removed in 9.1) 885'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 886 887The Nios II architecture was orphan. 888 889linux-user mode CPUs 890-------------------- 891 892``tilegx`` CPUs (removed in 6.0) 893'''''''''''''''''''''''''''''''' 894 895The ``tilegx`` guest CPU support has been removed without replacement. It was 896only implemented in linux-user mode, but support for this CPU was removed from 897the upstream Linux kernel in 2018, and it has also been dropped from glibc, so 898there is no new Linux development taking place with this architecture. For 899running the old binaries, you can use older versions of QEMU. 900 901``ppc64abi32`` CPUs (removed in 7.0) 902'''''''''''''''''''''''''''''''''''' 903 904The ``ppc64abi32`` architecture has a number of issues which regularly 905tripped up the CI testing and was suspected to be quite broken. For that 906reason the maintainers strongly suspected no one actually used it. 907 908``nios2`` CPU (removed in 9.1) 909'''''''''''''''''''''''''''''' 910 911QEMU Nios II architecture was orphan; Intel has EOL'ed the Nios II 912processor IP (see `Intel discontinuance notification`_). 913 914TCG introspection features 915-------------------------- 916 917TCG trace-events (since 6.2) 918'''''''''''''''''''''''''''' 919 920The ability to add new TCG trace points had bit rotted and as the 921feature can be replicated with TCG plugins it was removed. If 922any user is currently using this feature and needs help with 923converting to using TCG plugins they should contact the qemu-devel 924mailing list. 925 926 927System emulator devices 928----------------------- 929 930``spapr-pci-vfio-host-bridge`` (removed in 2.12) 931''''''''''''''''''''''''''''''''''''''''''''''''' 932 933The ``spapr-pci-vfio-host-bridge`` device type has been replaced by the 934``spapr-pci-host-bridge`` device type. 935 936``ivshmem`` (removed in 4.0) 937'''''''''''''''''''''''''''' 938 939Replaced by either the ``ivshmem-plain`` or ``ivshmem-doorbell``. 940 941``ide-drive`` (removed in 6.0) 942'''''''''''''''''''''''''''''' 943 944The 'ide-drive' device has been removed. Users should use 'ide-hd' or 945'ide-cd' as appropriate to get an IDE hard disk or CD-ROM as needed. 946 947``scsi-disk`` (removed in 6.0) 948'''''''''''''''''''''''''''''' 949 950The 'scsi-disk' device has been removed. Users should use 'scsi-hd' or 951'scsi-cd' as appropriate to get a SCSI hard disk or CD-ROM as needed. 952 953``sga`` (removed in 8.0) 954'''''''''''''''''''''''' 955 956The ``sga`` device loaded an option ROM for x86 targets which enabled 957SeaBIOS to send messages to the serial console. SeaBIOS 1.11.0 onwards 958contains native support for this feature and thus use of the option 959ROM approach was obsolete. The native SeaBIOS support can be activated 960by using ``-machine graphics=off``. 961 962``pvrdma`` and the RDMA subsystem (removed in 9.1) 963'''''''''''''''''''''''''''''''''''''''''''''''''' 964 965The 'pvrdma' device and the whole RDMA subsystem have been removed. 966 967Related binaries 968---------------- 969 970``qemu-nbd --partition`` (removed in 5.0) 971''''''''''''''''''''''''''''''''''''''''' 972 973The ``qemu-nbd --partition $digit`` code (also spelled ``-P``) 974could only handle MBR partitions, and never correctly handled logical 975partitions beyond partition 5. Exporting a partition can still be 976done by utilizing the ``--image-opts`` option with a raw blockdev 977using the ``offset`` and ``size`` parameters layered on top of 978any other existing blockdev. For example, if partition 1 is 100MiB 979long starting at 1MiB, the old command:: 980 981 qemu-nbd -t -P 1 -f qcow2 file.qcow2 982 983can be rewritten as:: 984 985 qemu-nbd -t --image-opts driver=raw,offset=1M,size=100M,file.driver=qcow2,file.file.driver=file,file.file.filename=file.qcow2 986 987``qemu-img convert -n -o`` (removed in 5.1) 988''''''''''''''''''''''''''''''''''''''''''' 989 990All options specified in ``-o`` are image creation options, so 991they are now rejected when used with ``-n`` to skip image creation. 992 993 994``qemu-img create -b bad file $size`` (removed in 5.1) 995'''''''''''''''''''''''''''''''''''''''''''''''''''''' 996 997When creating an image with a backing file that could not be opened, 998``qemu-img create`` used to issue a warning about the failure but 999proceed with the image creation if an explicit size was provided. 1000However, as the ``-u`` option exists for this purpose, it is safer to 1001enforce that any failure to open the backing image (including if the 1002backing file is missing or an incorrect format was specified) is an 1003error when ``-u`` is not used. 1004 1005``qemu-img amend`` to adjust backing file (removed in 6.1) 1006'''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 1007 1008The use of ``qemu-img amend`` to modify the name or format of a qcow2 1009backing image was never fully documented or tested, and interferes 1010with other amend operations that need access to the original backing 1011image (such as deciding whether a v3 zero cluster may be left 1012unallocated when converting to a v2 image). Any changes to the 1013backing chain should be performed with ``qemu-img rebase -u`` either 1014before or after the remaining changes being performed by amend, as 1015appropriate. 1016 1017``qemu-img`` backing file without format (removed in 6.1) 1018''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 1019 1020The use of ``qemu-img create``, ``qemu-img rebase``, or ``qemu-img 1021convert`` to create or modify an image that depends on a backing file 1022now requires that an explicit backing format be provided. This is 1023for safety: if QEMU probes a different format than what you thought, 1024the data presented to the guest will be corrupt; similarly, presenting 1025a raw image to a guest allows a potential security exploit if a future 1026probe sees a non-raw image based on guest writes. 1027 1028To avoid creating unsafe backing chains, you must pass ``-o 1029backing_fmt=`` (or the shorthand ``-F`` during create) to specify the 1030intended backing format. You may use ``qemu-img rebase -u`` to 1031retroactively add a backing format to an existing image. However, be 1032aware that there are already potential security risks to blindly using 1033``qemu-img info`` to probe the format of an untrusted backing image, 1034when deciding what format to add into an existing image. 1035 1036Block devices 1037------------- 1038 1039VXHS backend (removed in 5.1) 1040''''''''''''''''''''''''''''' 1041 1042The VXHS code did not compile since v2.12.0. It was removed in 5.1. 1043 1044``sheepdog`` driver (removed in 6.0) 1045'''''''''''''''''''''''''''''''''''' 1046 1047The corresponding upstream server project is no longer maintained. 1048Users are recommended to switch to an alternative distributed block 1049device driver such as RBD. 1050 1051Tools 1052----- 1053 1054virtiofsd (removed in 8.0) 1055'''''''''''''''''''''''''' 1056 1057There is a newer Rust implementation of ``virtiofsd`` at 1058``https://gitlab.com/virtio-fs/virtiofsd``; this has been 1059stable for some time and is now widely used. 1060The command line and feature set is very close to the removed 1061C implementation. 1062 1063.. _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 1064