5 What follows is a record of recently removed, formerly deprecated
6 features that serves as a record for users who have encountered
7 trouble after a recent upgrade.
9 System emulator command line arguments
10 --------------------------------------
12 ``-hdachs`` (removed in 2.12)
13 '''''''''''''''''''''''''''''
15 The 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,...``).
19 ``-net channel`` (removed in 2.12)
20 ''''''''''''''''''''''''''''''''''
22 This option has been replaced by ``-net user,guestfwd=...``.
24 ``-net dump`` (removed in 2.12)
25 '''''''''''''''''''''''''''''''
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]``.
29 Note that the new syntax works with netdev IDs instead of the old "vlan" hubs.
31 ``-no-kvm-pit`` (removed in 2.12)
32 '''''''''''''''''''''''''''''''''
34 This was just a dummy option that has been ignored, since the in-kernel PIT
35 cannot 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``.
39 ``-tdf`` (removed in 2.12)
40 ''''''''''''''''''''''''''
42 There is no replacement, the ``-tdf`` option has just been ignored since the
43 behaviour that could be changed by this option in qemu-kvm is now the default
44 when using the KVM PIT. It still can be requested explicitly using
45 ``-global kvm-pit.lost_tick_policy=delay``.
47 ``-drive secs=s``, ``-drive heads=h`` & ``-drive cyls=c`` (removed in 3.0)
48 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
50 The 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,...``).
54 ``-drive serial=``, ``-drive trans=`` & ``-drive addr=`` (removed in 3.0)
55 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
57 Use ``-device ...,drive=dr,serial=r,bios-chs-trans=t,addr=a`` instead
58 (together with ``-drive if=none,id=dr,...``).
60 ``-net ...,vlan=x`` (removed in 3.0)
61 ''''''''''''''''''''''''''''''''''''
63 The term "vlan" was very confusing for most users in this context (it's about
64 specifying a hub ID, not about IEEE 802.1Q or something similar), so this
65 has been removed. To connect one NIC frontend with a network backend, either
66 use ``-nic ...`` (e.g. for on-board NICs) or use ``-netdev ...,id=n`` together
67 with ``-device ...,netdev=n`` (for full control over pluggable NICs). To
68 connect multiple NICs or network backends via a hub device (which is what
69 vlan did), use ``-nic hubport,hubid=x,...`` or
70 ``-netdev hubport,id=n,hubid=x,...`` (with ``-device ...,netdev=n``) instead.
72 ``-no-kvm-irqchip`` (removed in 3.0)
73 ''''''''''''''''''''''''''''''''''''
75 Use ``-machine kernel_irqchip=off`` instead.
77 ``-no-kvm-pit-reinjection`` (removed in 3.0)
78 ''''''''''''''''''''''''''''''''''''''''''''
80 Use ``-global kvm-pit.lost_tick_policy=discard`` instead.
82 ``-balloon`` (removed in 3.1)
83 '''''''''''''''''''''''''''''
85 The ``-balloon virtio`` option has been replaced by ``-device virtio-balloon``.
86 The ``-balloon none`` option was a no-op and has no replacement.
88 ``-bootp`` (removed in 3.1)
89 '''''''''''''''''''''''''''
91 The ``-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).
94 The new syntax allows different settings to be provided per NIC.
96 ``-redir`` (removed in 3.1)
97 '''''''''''''''''''''''''''
99 The ``-redir [tcp|udp]:hostport:[guestaddr]:guestport`` option is replaced
101 user,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
107 ``-smb`` (removed in 3.1)
108 '''''''''''''''''''''''''
110 The ``-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).
113 The new syntax allows different settings to be provided per NIC.
115 ``-tftp`` (removed in 3.1)
116 ''''''''''''''''''''''''''
118 The ``-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).
121 The new syntax allows different settings to be provided per NIC.
123 ``-localtime`` (removed in 3.1)
124 '''''''''''''''''''''''''''''''
126 Replaced by ``-rtc base=localtime``.
128 ``-nodefconfig`` (removed in 3.1)
129 '''''''''''''''''''''''''''''''''
131 Use ``-no-user-config`` instead.
133 ``-rtc-td-hack`` (removed in 3.1)
134 '''''''''''''''''''''''''''''''''
136 Use ``-rtc driftfix=slew`` instead.
138 ``-startdate`` (removed in 3.1)
139 '''''''''''''''''''''''''''''''
141 Replaced by ``-rtc base=date``.
143 ``-vnc ...,tls=...``, ``-vnc ...,x509=...`` & ``-vnc ...,x509verify=...`` (removed in 3.1)
144 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
146 The "tls-creds" option should be used instead to point to a "tls-creds-x509"
147 object created using "-object".
149 ``-mem-path`` fallback to RAM (removed in 5.0)
150 ''''''''''''''''''''''''''''''''''''''''''''''
152 If guest RAM allocation from file pointed by ``mem-path`` failed,
153 QEMU was falling back to allocating from RAM, which might have resulted
154 in unpredictable behavior since the backing file specified by the user
155 as ignored. Currently, users are responsible for making sure the backing storage
156 specified with ``-mem-path`` can actually provide the guest RAM configured with
157 ``-m`` and QEMU fails to start up if RAM allocation is unsuccessful.
159 ``-net ...,name=...`` (removed in 5.1)
160 ''''''''''''''''''''''''''''''''''''''
162 The ``name`` parameter of the ``-net`` option was a synonym
163 for the ``id`` parameter, which should now be used instead.
165 ``-numa node,mem=...`` (removed in 5.1)
166 '''''''''''''''''''''''''''''''''''''''
168 The parameter ``mem`` of ``-numa node`` was used to assign a part of guest RAM
169 to a NUMA node. But when using it, it's impossible to manage a specified RAM
170 chunk on the host side (like bind it to a host node, setting bind policy, ...),
171 so the guest ends up with the fake NUMA configuration with suboptiomal
173 However since 2014 there is an alternative way to assign RAM to a NUMA node
174 using parameter ``memdev``, which does the same as ``mem`` and adds
175 means to actually manage node RAM on the host side. Use parameter ``memdev``
176 with *memory-backend-ram* backend as replacement for parameter ``mem``
177 to achieve the same fake NUMA effect or a properly configured
178 *memory-backend-file* backend to actually benefit from NUMA configuration.
179 New machine versions (since 5.1) will not accept the option but it will still
180 work with old machine types. User can check the QAPI schema to see if the legacy
181 option is supported by looking at MachineInfo::numa-mem-supported property.
183 ``-numa`` node (without memory specified) (removed in 5.2)
184 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
186 Splitting RAM by default between NUMA nodes had the same issues as ``mem``
187 parameter with the difference that the role of the user plays QEMU using
188 implicit generic or board specific splitting rule.
189 Use ``memdev`` with *memory-backend-ram* backend or ``mem`` (if
190 it's supported by used machine type) to define mapping explicitly instead.
191 Users of existing VMs, wishing to preserve the same RAM distribution, should
192 configure it explicitly using ``-numa node,memdev`` options. Current RAM
193 distribution can be retrieved using HMP command ``info numa`` and if separate
194 memory devices (pc|nv-dimm) are present use ``info memory-device`` and subtract
195 device memory from output of ``info numa``.
197 ``-smp`` (invalid topologies) (removed in 5.2)
198 ''''''''''''''''''''''''''''''''''''''''''''''
200 CPU topology properties should describe whole machine topology including
203 However, historically it was possible to start QEMU with an incorrect topology
204 where *n* <= *sockets* * *cores* * *threads* < *maxcpus*,
205 which could lead to an incorrect topology enumeration by the guest.
206 Support for invalid topologies is removed, the user must ensure
207 topologies described with -smp include all possible cpus, i.e.
208 *sockets* * *cores* * *threads* = *maxcpus*.
210 ``-machine enforce-config-section=on|off`` (removed in 5.2)
211 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
213 The ``enforce-config-section`` property was replaced by the
214 ``-global migration.send-configuration={on|off}`` option.
216 ``-no-kvm`` (removed in 5.2)
217 ''''''''''''''''''''''''''''
219 The ``-no-kvm`` argument was a synonym for setting ``-machine accel=tcg``.
221 ``-realtime`` (removed in 6.0)
222 ''''''''''''''''''''''''''''''
224 The ``-realtime mlock=on|off`` argument has been replaced by the
225 ``-overcommit mem-lock=on|off`` argument.
227 ``-show-cursor`` option (removed in 6.0)
228 ''''''''''''''''''''''''''''''''''''''''
230 Use ``-display sdl,show-cursor=on``, ``-display gtk,show-cursor=on``
231 or ``-display default,show-cursor=on`` instead.
233 ``-tb-size`` option (removed in 6.0)
234 ''''''''''''''''''''''''''''''''''''
236 QEMU 5.0 introduced an alternative syntax to specify the size of the translation
237 block cache, ``-accel tcg,tb-size=``.
239 ``-usbdevice audio`` (removed in 6.0)
240 '''''''''''''''''''''''''''''''''''''
242 This option lacked the possibility to specify an audio backend device.
243 Use ``-device usb-audio`` now instead (and specify a corresponding USB
244 host controller or ``-usb`` if necessary).
246 ``-vnc acl`` (removed in 6.0)
247 '''''''''''''''''''''''''''''
249 The ``acl`` option to the ``-vnc`` argument has been replaced
250 by the ``tls-authz`` and ``sasl-authz`` options.
252 ``-mon ...,control=readline,pretty=on|off`` (removed in 6.0)
253 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
255 The ``pretty=on|off`` switch has no effect for HMP monitors and
258 ``-drive file=json:{...{'driver':'file'}}`` (removed in 6.0)
259 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
261 The 'file' driver for drives is no longer appropriate for character or host
262 devices and will only accept regular files (S_IFREG). The correct driver
263 for these file types is 'host_cdrom' or 'host_device' as appropriate.
265 Floppy controllers' drive properties (removed in 6.0)
266 '''''''''''''''''''''''''''''''''''''''''''''''''''''
268 Use ``-device floppy,...`` instead. When configuring onboard floppy
272 -global isa-fdc.driveA=...
273 -global sysbus-fdc.driveA=...
274 -global SUNW,fdtwo.drive=...
279 -device floppy,unit=0,drive=...
284 -global isa-fdc.driveB=...
285 -global sysbus-fdc.driveB=...
290 -device floppy,unit=1,drive=...
292 When plugging in a floppy controller
295 -device isa-fdc,...,driveA=...
301 -device floppy,unit=0,drive=...
306 -device isa-fdc,...,driveB=...
312 -device floppy,unit=1,drive=...
314 ``-drive`` with bogus interface type (removed in 6.0)
315 '''''''''''''''''''''''''''''''''''''''''''''''''''''
317 Drives with interface types other than ``if=none`` are for onboard
318 devices. Drives the board doesn't pick up can no longer be used with
319 -device. Use ``if=none`` instead.
321 ``-usbdevice ccid`` (removed in 6.0)
322 '''''''''''''''''''''''''''''''''''''
324 This option was undocumented and not used in the field.
325 Use ``-device usb-ccid`` instead.
327 RISC-V firmware not booted by default (removed in 5.1)
328 ''''''''''''''''''''''''''''''''''''''''''''''''''''''
330 QEMU 5.1 changes the default behaviour from ``-bios none`` to ``-bios default``
331 for the RISC-V ``virt`` machine and ``sifive_u`` machine.
333 ``-no-quit`` (removed in 7.0)
334 '''''''''''''''''''''''''''''
336 The ``-no-quit`` was a synonym for ``-display ...,window-close=off`` which
337 should be used instead.
339 ``--enable-fips`` (removed in 7.1)
340 ''''''''''''''''''''''''''''''''''
342 This option restricted usage of certain cryptographic algorithms when
343 the host is operating in FIPS mode.
345 If FIPS compliance is required, QEMU should be built with the ``libgcrypt``
346 or ``gnutls`` library enabled as a cryptography provider.
348 Neither the ``nettle`` library, or the built-in cryptography provider are
349 supported on FIPS enabled hosts.
351 ``-writeconfig`` (removed in 7.1)
352 '''''''''''''''''''''''''''''''''
354 The ``-writeconfig`` option was not able to serialize the entire contents
355 of the QEMU command line. It is thus considered a failed experiment
356 and removed without a replacement.
358 ``loaded`` property of ``secret`` and ``secret_keyring`` objects (removed in 7.1)
359 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
361 The ``loaded=on`` option in the command line or QMP ``object-add`` either had
362 no effect (if ``loaded`` was the last option) or caused options to be
363 effectively ignored as if they were not given. The property is therefore
364 useless and should simply be removed.
366 ``opened`` property of ``rng-*`` objects (removed in 7.1)
367 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''
369 The ``opened=on`` option in the command line or QMP ``object-add`` either had
370 no effect (if ``opened`` was the last option) or caused errors. The property
371 is therefore useless and should simply be removed.
373 ``-display sdl,window_close=...`` (removed in 7.1)
374 ''''''''''''''''''''''''''''''''''''''''''''''''''
376 Use ``-display sdl,window-close=...`` instead (i.e. with a minus instead of
377 an underscore between "window" and "close").
379 ``-alt-grab`` and ``-display sdl,alt_grab=on`` (removed in 7.1)
380 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
382 Use ``-display sdl,grab-mod=lshift-lctrl-lalt`` instead.
384 ``-ctrl-grab`` and ``-display sdl,ctrl_grab=on`` (removed in 7.1)
385 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
387 Use ``-display sdl,grab-mod=rctrl`` instead.
389 ``-sdl`` (removed in 7.1)
390 '''''''''''''''''''''''''
392 Use ``-display sdl`` instead.
394 ``-curses`` (removed in 7.1)
395 ''''''''''''''''''''''''''''
397 Use ``-display curses`` instead.
399 Creating sound card devices using ``-soundhw`` (removed in 7.1)
400 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
402 Sound card devices should be created using ``-device`` or ``-audio``.
403 The exception is ``pcspk`` which can be activated using ``-machine
404 pcspk-audiodev=<name>``.
406 ``-watchdog`` (since 7.2)
407 '''''''''''''''''''''''''
409 Use ``-device`` instead.
411 Hexadecimal sizes with scaling multipliers (since 8.0)
412 ''''''''''''''''''''''''''''''''''''''''''''''''''''''
414 Input 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
416 the value is hexadecimal. That is, '0x20M' should be written either as
417 '32M' or as '0x2000000'.
419 ``-chardev`` backend aliases ``tty`` and ``parport`` (removed in 8.0)
420 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
422 ``tty`` and ``parport`` used to be aliases for ``serial`` and ``parallel``
423 respectively. The actual backend names should be used instead.
425 ``-drive if=none`` for the sifive_u OTP device (removed in 8.0)
426 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
428 Use ``-drive if=pflash`` to configure the OTP device of the sifive_u
429 RISC-V machine instead.
431 ``-spice password=string`` (removed in 8.0)
432 '''''''''''''''''''''''''''''''''''''''''''
434 This option was insecure because the SPICE password remained visible in
435 the process listing. This was replaced by the new ``password-secret``
436 option which lets the password be securely provided on the command
437 line using a ``secret`` object instance.
439 ``QEMU_AUDIO_`` environment variables and ``-audio-help`` (removed in 8.2)
440 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
442 The ``-audiodev`` and ``-audio`` command line options are now the only
443 way to specify audio backend settings.
445 Using ``-audiodev`` to define the default audio backend (removed in 8.2)
446 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
448 If no audiodev property is specified, previous versions would use the
449 first ``-audiodev`` command line option as a fallback. Starting with
450 version 8.2, audio backends created with ``-audiodev`` will only be
451 used by clients (sound cards, machines with embedded sound hardware, VNC)
452 that refer to it in an ``audiodev=`` property.
454 In order to configure a default audio backend, use the ``-audio``
455 command line option without specifying a ``model``; while previous
456 versions of QEMU required a model, starting with version 8.2
457 QEMU does not require a model and will not create any sound card
460 Note that the default audio backend must be configured on the command
461 line if the ``-nodefaults`` options is used.
463 ``-no-hpet`` (removed in 9.0)
464 '''''''''''''''''''''''''''''
466 The HPET setting has been turned into a machine property.
467 Use ``-machine hpet=off`` instead.
469 ``-no-acpi`` (removed in 9.0)
470 '''''''''''''''''''''''''''''
472 The ``-no-acpi`` setting has been turned into a machine property.
473 Use ``-machine acpi=off`` instead.
475 ``-async-teardown`` (removed in 9.0)
476 ''''''''''''''''''''''''''''''''''''
478 Use ``-run-with async-teardown=on`` instead.
480 ``-chroot`` (removed in 9.0)
481 ''''''''''''''''''''''''''''
483 Use ``-run-with chroot=dir`` instead.
485 ``-singlestep`` (removed in 9.0)
486 ''''''''''''''''''''''''''''''''
488 The ``-singlestep`` option has been turned into an accelerator property,
489 and given a name that better reflects what it actually does.
490 Use ``-accel tcg,one-insn-per-tb=on`` instead.
492 ``-smp`` ("parameter=0" SMP configurations) (removed in 9.0)
493 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
495 Specified CPU topology parameters must be greater than zero.
497 In the SMP configuration, users should either provide a CPU topology
498 parameter with a reasonable value (greater than zero) or just omit it
499 and QEMU will compute the missing value.
501 However, historically it was implicitly allowed for users to provide
502 a parameter with zero value, which is meaningless and could also possibly
503 cause unexpected results in the -smp parsing. So support for this kind of
504 configurations (e.g. -smp 8,sockets=0) is removed since 9.0, users have
505 to ensure that all the topology members described with -smp are greater
508 User-mode emulator command line arguments
509 -----------------------------------------
511 ``-singlestep`` (removed in 9.0)
512 ''''''''''''''''''''''''''''''''
514 The ``-singlestep`` option has been given a name that better reflects
515 what it actually does. For both linux-user and bsd-user, use the
516 ``-one-insn-per-tb`` option instead.
519 QEMU Machine Protocol (QMP) commands
520 ------------------------------------
522 ``block-dirty-bitmap-add`` "autoload" parameter (removed in 4.2)
523 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
525 The "autoload" parameter has been ignored since 2.12.0. All bitmaps
526 are automatically loaded from qcow2 images.
528 ``cpu-add`` (removed in 5.2)
529 ''''''''''''''''''''''''''''
531 Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See
532 documentation of ``query-hotpluggable-cpus`` for additional details.
534 ``change`` (removed in 6.0)
535 '''''''''''''''''''''''''''
537 Use ``blockdev-change-medium`` or ``change-vnc-password`` or
538 ``display-update`` instead.
540 ``query-events`` (removed in 6.0)
541 '''''''''''''''''''''''''''''''''
543 The ``query-events`` command has been superseded by the more powerful
544 and accurate ``query-qmp-schema`` command.
546 ``migrate_set_cache_size`` and ``query-migrate-cache-size`` (removed in 6.0)
547 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
549 Use ``migrate_set_parameter`` and ``info migrate_parameters`` instead.
551 ``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0)
552 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
554 Use ``migrate_set_parameter`` instead.
556 ``query-cpus`` (removed in 6.0)
557 '''''''''''''''''''''''''''''''
559 The ``query-cpus`` command is replaced by the ``query-cpus-fast`` command.
561 ``query-cpus-fast`` ``arch`` output member (removed in 6.0)
562 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
564 The ``arch`` output member of the ``query-cpus-fast`` command is
565 replaced by the ``target`` output member.
567 chardev client socket with ``wait`` option (removed in 6.0)
568 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
570 Character devices creating sockets in client mode should not specify
571 the 'wait' field, which is only applicable to sockets in server mode
573 ``query-named-block-nodes`` result ``encryption_key_missing`` (removed in 6.0)
574 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
576 Removed with no replacement.
578 ``query-block`` result ``inserted.encryption_key_missing`` (removed in 6.0)
579 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
581 Removed with no replacement.
583 ``query-named-block-nodes`` and ``query-block`` result dirty-bitmaps[i].status (removed in 6.0)
584 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
586 The ``status`` field of the ``BlockDirtyInfo`` structure, returned by
587 these commands is removed. Two new boolean fields, ``recording`` and
588 ``busy`` effectively replace it.
590 ``query-block`` result field ``dirty-bitmaps`` (removed in 6.0)
591 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
593 The ``dirty-bitmaps`` field of the ``BlockInfo`` structure, returned by
594 the query-block command is itself now removed. The ``dirty-bitmaps``
595 field of the ``BlockDeviceInfo`` struct should be used instead, which is the
596 type of the ``inserted`` field in query-block replies, as well as the
597 type of array items in query-named-block-nodes.
599 ``object-add`` option ``props`` (removed in 6.0)
600 ''''''''''''''''''''''''''''''''''''''''''''''''
602 Specify the properties for the object as top-level arguments instead.
604 ``query-sgx`` return value member ``section-size`` (removed in 8.0)
605 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
607 Member ``section-size`` in the return value of ``query-sgx``
608 was superseded by ``sections``.
611 ``query-sgx-capabilities`` return value member ``section-size`` (removed in 8.0)
612 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
614 Member ``section-size`` in the return value of ``query-sgx-capabilities``
615 was superseded by ``sections``.
617 Human Monitor Protocol (HMP) commands
618 -------------------------------------
620 ``usb_add`` and ``usb_remove`` (removed in 2.12)
621 ''''''''''''''''''''''''''''''''''''''''''''''''
623 Replaced by ``device_add`` and ``device_del`` (use ``device_add help`` for a
624 list of available devices).
626 ``host_net_add`` and ``host_net_remove`` (removed in 2.12)
627 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
629 Replaced by ``netdev_add`` and ``netdev_del``.
631 The ``hub_id`` parameter of ``hostfwd_add`` / ``hostfwd_remove`` (removed in 5.0)
632 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
634 The ``[hub_id name]`` parameter tuple of the 'hostfwd_add' and
635 'hostfwd_remove' HMP commands has been replaced by ``netdev_id``.
637 ``cpu-add`` (removed in 5.2)
638 ''''''''''''''''''''''''''''
640 Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See
641 documentation of ``query-hotpluggable-cpus`` for additional details.
643 ``change vnc TARGET`` (removed in 6.0)
644 ''''''''''''''''''''''''''''''''''''''
646 No replacement. The ``change vnc password`` and ``change DEVICE MEDIUM``
647 commands are not affected.
649 ``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, ``acl_remove`` (removed in 6.0)
650 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
652 The ``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, and
653 ``acl_remove`` commands were removed with no replacement. Authorization
654 for VNC should be performed using the pluggable QAuthZ objects.
656 ``migrate-set-cache-size`` and ``info migrate-cache-size`` (removed in 6.0)
657 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
659 Use ``migrate-set-parameters`` and ``info migrate-parameters`` instead.
661 ``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0)
662 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
664 Use ``migrate-set-parameters`` instead.
666 ``info cpustats`` (removed in 6.1)
667 ''''''''''''''''''''''''''''''''''
669 This command didn't produce any output already. Removed with no replacement.
671 ``singlestep`` (removed in 9.0)
672 '''''''''''''''''''''''''''''''
674 The ``singlestep`` command has been replaced by the ``one-insn-per-tb``
675 command, which has the same behaviour but a less misleading name.
680 System emulation on 32-bit Windows hosts (removed in 9.0)
681 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''
683 Windows 11 has no support for 32-bit host installs, and Windows 10 did
684 not support new 32-bit installs, only upgrades. 32-bit Windows support
685 has now been dropped by the MSYS2 project. QEMU also is deprecating
686 and dropping support for 32-bit x86 host deployments in
687 general. 32-bit Windows is therefore no longer a supported host for
688 QEMU. Since all recent x86 hardware from the past >10 years is
689 capable of the 64-bit x86 extensions, a corresponding 64-bit OS should
695 RISC-V ISA privilege specification version 1.09.1 (removed in 5.1)
696 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
698 The RISC-V ISA privilege specification version 1.09.1 has been removed.
699 QEMU supports both the newer version 1.10.0 and the ratified version 1.11.0, these
700 should be used instead of the 1.09.1 version.
705 KVM guest support on 32-bit Arm hosts (removed in 5.2)
706 ''''''''''''''''''''''''''''''''''''''''''''''''''''''
708 The Linux kernel has dropped support for allowing 32-bit Arm systems
709 to host KVM guests as of the 5.7 kernel, and was thus removed from QEMU
710 as well. Running 32-bit guests on a 64-bit Arm host remains supported.
712 RISC-V ISA Specific CPUs (removed in 5.1)
713 '''''''''''''''''''''''''''''''''''''''''
715 The RISC-V cpus with the ISA version in the CPU name have been removed. The
716 four CPUs are: ``rv32gcsu-v1.9.1``, ``rv32gcsu-v1.10.0``, ``rv64gcsu-v1.9.1`` and
717 ``rv64gcsu-v1.10.0``. Instead the version can be specified via the CPU ``priv_spec``
718 option when using the ``rv32`` or ``rv64`` CPUs.
720 RISC-V no MMU CPUs (removed in 5.1)
721 '''''''''''''''''''''''''''''''''''
723 The RISC-V no MMU cpus have been removed. The two CPUs: ``rv32imacu-nommu`` and
724 ``rv64imacu-nommu`` can no longer be used. Instead the MMU status can be specified
725 via the CPU ``mmu`` option when using the ``rv32`` or ``rv64`` CPUs.
727 ``compat`` property of server class POWER CPUs (removed in 6.0)
728 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
730 The ``max-cpu-compat`` property of the ``pseries`` machine type should be used
733 ``moxie`` CPU (removed in 6.1)
734 ''''''''''''''''''''''''''''''
736 Nobody was using this CPU emulation in QEMU, and there were no test images
737 available to make sure that the code is still working, so it has been removed
740 ``lm32`` CPUs (removed in 6.1)
741 ''''''''''''''''''''''''''''''
743 The only public user of this architecture was the milkymist project,
744 which has been dead for years; there was never an upstream Linux
745 port. Removed without replacement.
747 ``unicore32`` CPUs (removed in 6.1)
748 '''''''''''''''''''''''''''''''''''
750 Support for this CPU was removed from the upstream Linux kernel, and
751 there is no available upstream toolchain to build binaries for it.
752 Removed without replacement.
754 x86 ``Icelake-Client`` CPU (removed in 7.1)
755 '''''''''''''''''''''''''''''''''''''''''''
757 There isn't ever Icelake Client CPU, it is some wrong and imaginary one.
758 Use ``Icelake-Server`` instead.
760 Nios II CPU (removed in 9.1)
761 ''''''''''''''''''''''''''''
763 QEMU Nios II architecture was orphan; Intel has EOL'ed the Nios II
764 processor IP (see `Intel discontinuance notification`_).
769 Userspace local APIC with KVM (x86, removed in 8.0)
770 '''''''''''''''''''''''''''''''''''''''''''''''''''
772 ``-M kernel-irqchip=off`` cannot be used on KVM if the CPU model includes
773 a local APIC. The ``split`` setting is supported, as is using ``-M
774 kernel-irqchip=off`` when the CPU does not have a local APIC.
776 HAXM (``-accel hax``) (removed in 8.2)
777 ''''''''''''''''''''''''''''''''''''''
779 The HAXM project has been retired (see https://github.com/intel/haxm#status).
780 Use "whpx" (on Windows) or "hvf" (on macOS) instead.
782 MIPS "Trap-and-Emulate" KVM support (removed in 8.0)
783 ''''''''''''''''''''''''''''''''''''''''''''''''''''
785 The MIPS "Trap-and-Emulate" KVM host and guest support was removed
786 from Linux in 2021, and is not supported anymore by QEMU either.
788 System emulator machines
789 ------------------------
791 ``s390-virtio`` (removed in 2.6)
792 ''''''''''''''''''''''''''''''''
794 Use the ``s390-ccw-virtio`` machine instead.
796 The m68k ``dummy`` machine (removed in 2.9)
797 '''''''''''''''''''''''''''''''''''''''''''
799 Use the ``none`` machine with the ``loader`` device instead.
801 ``xlnx-ep108`` (removed in 3.0)
802 '''''''''''''''''''''''''''''''
804 The EP108 was an early access development board that is no longer used.
805 Use the ``xlnx-zcu102`` machine instead.
807 ``spike_v1.9.1`` and ``spike_v1.10`` (removed in 5.1)
808 '''''''''''''''''''''''''''''''''''''''''''''''''''''
810 The version specific Spike machines have been removed in favour of the
811 generic ``spike`` machine. If you need to specify an older version of the RISC-V
812 spec you can use the ``-cpu rv64gcsu,priv_spec=v1.10.0`` command line argument.
814 mips ``r4k`` platform (removed in 5.2)
815 ''''''''''''''''''''''''''''''''''''''
817 This machine type was very old and unmaintained. Users should use the ``malta``
818 machine type instead.
820 mips ``fulong2e`` machine alias (removed in 6.0)
821 ''''''''''''''''''''''''''''''''''''''''''''''''
823 This machine has been renamed ``fuloong2e``.
825 ``pc-0.10`` up to ``pc-i440fx-1.7`` (removed in 4.0 up to 8.2)
826 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
828 These machine types were very old and likely could not be used for live
829 migration from old QEMU versions anymore. Use a newer machine type instead.
831 Raspberry Pi ``raspi2`` and ``raspi3`` machines (removed in 6.2)
832 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
834 The Raspberry Pi machines come in various models (A, A+, B, B+). To be able
835 to distinguish which model QEMU is implementing, the ``raspi2`` and ``raspi3``
836 machines have been renamed ``raspi2b`` and ``raspi3b``.
838 Aspeed ``swift-bmc`` machine (removed in 7.0)
839 '''''''''''''''''''''''''''''''''''''''''''''
841 This machine was removed because it was unused. Alternative AST2500 based
842 OpenPOWER machines are ``witherspoon-bmc`` and ``romulus-bmc``.
844 ppc ``taihu`` machine (removed in 7.2)
845 '''''''''''''''''''''''''''''''''''''''''''''
847 This machine was removed because it was partially emulated and 405
848 machines are very similar. Use the ``ref405ep`` machine instead.
850 Nios II ``10m50-ghrd`` and ``nios2-generic-nommu`` machines (removed in 9.1)
851 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
853 The Nios II architecture was orphan.
858 ``tilegx`` CPUs (removed in 6.0)
859 ''''''''''''''''''''''''''''''''
861 The ``tilegx`` guest CPU support has been removed without replacement. It was
862 only implemented in linux-user mode, but support for this CPU was removed from
863 the upstream Linux kernel in 2018, and it has also been dropped from glibc, so
864 there is no new Linux development taking place with this architecture. For
865 running the old binaries, you can use older versions of QEMU.
867 ``ppc64abi32`` CPUs (removed in 7.0)
868 ''''''''''''''''''''''''''''''''''''
870 The ``ppc64abi32`` architecture has a number of issues which regularly
871 tripped up the CI testing and was suspected to be quite broken. For that
872 reason the maintainers strongly suspected no one actually used it.
874 ``nios2`` CPU (removed in 9.1)
875 ''''''''''''''''''''''''''''''
877 QEMU Nios II architecture was orphan; Intel has EOL'ed the Nios II
878 processor IP (see `Intel discontinuance notification`_).
880 TCG introspection features
881 --------------------------
883 TCG trace-events (since 6.2)
884 ''''''''''''''''''''''''''''
886 The ability to add new TCG trace points had bit rotted and as the
887 feature can be replicated with TCG plugins it was removed. If
888 any user is currently using this feature and needs help with
889 converting to using TCG plugins they should contact the qemu-devel
893 System emulator devices
894 -----------------------
896 ``spapr-pci-vfio-host-bridge`` (removed in 2.12)
897 '''''''''''''''''''''''''''''''''''''''''''''''''
899 The ``spapr-pci-vfio-host-bridge`` device type has been replaced by the
900 ``spapr-pci-host-bridge`` device type.
902 ``ivshmem`` (removed in 4.0)
903 ''''''''''''''''''''''''''''
905 Replaced by either the ``ivshmem-plain`` or ``ivshmem-doorbell``.
907 ``ide-drive`` (removed in 6.0)
908 ''''''''''''''''''''''''''''''
910 The 'ide-drive' device has been removed. Users should use 'ide-hd' or
911 'ide-cd' as appropriate to get an IDE hard disk or CD-ROM as needed.
913 ``scsi-disk`` (removed in 6.0)
914 ''''''''''''''''''''''''''''''
916 The 'scsi-disk' device has been removed. Users should use 'scsi-hd' or
917 'scsi-cd' as appropriate to get a SCSI hard disk or CD-ROM as needed.
919 ``sga`` (removed in 8.0)
920 ''''''''''''''''''''''''
922 The ``sga`` device loaded an option ROM for x86 targets which enabled
923 SeaBIOS to send messages to the serial console. SeaBIOS 1.11.0 onwards
924 contains native support for this feature and thus use of the option
925 ROM approach was obsolete. The native SeaBIOS support can be activated
926 by using ``-machine graphics=off``.
928 ``pvrdma`` and the RDMA subsystem (removed in 9.1)
929 ''''''''''''''''''''''''''''''''''''''''''''''''''
931 The 'pvrdma' device and the whole RDMA subsystem have been removed.
936 ``qemu-nbd --partition`` (removed in 5.0)
937 '''''''''''''''''''''''''''''''''''''''''
939 The ``qemu-nbd --partition $digit`` code (also spelled ``-P``)
940 could only handle MBR partitions, and never correctly handled logical
941 partitions beyond partition 5. Exporting a partition can still be
942 done by utilizing the ``--image-opts`` option with a raw blockdev
943 using the ``offset`` and ``size`` parameters layered on top of
944 any other existing blockdev. For example, if partition 1 is 100MiB
945 long starting at 1MiB, the old command::
947 qemu-nbd -t -P 1 -f qcow2 file.qcow2
949 can be rewritten as::
951 qemu-nbd -t --image-opts driver=raw,offset=1M,size=100M,file.driver=qcow2,file.file.driver=file,file.file.filename=file.qcow2
953 ``qemu-img convert -n -o`` (removed in 5.1)
954 '''''''''''''''''''''''''''''''''''''''''''
956 All options specified in ``-o`` are image creation options, so
957 they are now rejected when used with ``-n`` to skip image creation.
960 ``qemu-img create -b bad file $size`` (removed in 5.1)
961 ''''''''''''''''''''''''''''''''''''''''''''''''''''''
963 When creating an image with a backing file that could not be opened,
964 ``qemu-img create`` used to issue a warning about the failure but
965 proceed with the image creation if an explicit size was provided.
966 However, as the ``-u`` option exists for this purpose, it is safer to
967 enforce that any failure to open the backing image (including if the
968 backing file is missing or an incorrect format was specified) is an
969 error when ``-u`` is not used.
971 ``qemu-img amend`` to adjust backing file (removed in 6.1)
972 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
974 The use of ``qemu-img amend`` to modify the name or format of a qcow2
975 backing image was never fully documented or tested, and interferes
976 with other amend operations that need access to the original backing
977 image (such as deciding whether a v3 zero cluster may be left
978 unallocated when converting to a v2 image). Any changes to the
979 backing chain should be performed with ``qemu-img rebase -u`` either
980 before or after the remaining changes being performed by amend, as
983 ``qemu-img`` backing file without format (removed in 6.1)
984 '''''''''''''''''''''''''''''''''''''''''''''''''''''''''
986 The use of ``qemu-img create``, ``qemu-img rebase``, or ``qemu-img
987 convert`` to create or modify an image that depends on a backing file
988 now requires that an explicit backing format be provided. This is
989 for safety: if QEMU probes a different format than what you thought,
990 the data presented to the guest will be corrupt; similarly, presenting
991 a raw image to a guest allows a potential security exploit if a future
992 probe sees a non-raw image based on guest writes.
994 To avoid creating unsafe backing chains, you must pass ``-o
995 backing_fmt=`` (or the shorthand ``-F`` during create) to specify the
996 intended backing format. You may use ``qemu-img rebase -u`` to
997 retroactively add a backing format to an existing image. However, be
998 aware that there are already potential security risks to blindly using
999 ``qemu-img info`` to probe the format of an untrusted backing image,
1000 when deciding what format to add into an existing image.
1005 VXHS backend (removed in 5.1)
1006 '''''''''''''''''''''''''''''
1008 The VXHS code did not compile since v2.12.0. It was removed in 5.1.
1010 ``sheepdog`` driver (removed in 6.0)
1011 ''''''''''''''''''''''''''''''''''''
1013 The corresponding upstream server project is no longer maintained.
1014 Users are recommended to switch to an alternative distributed block
1015 device driver such as RBD.
1020 virtiofsd (removed in 8.0)
1021 ''''''''''''''''''''''''''
1023 There is a newer Rust implementation of ``virtiofsd`` at
1024 ``https://gitlab.com/virtio-fs/virtiofsd``; this has been
1025 stable for some time and is now widely used.
1026 The command line and feature set is very close to the removed
1029 .. _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