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