]>
Commit | Line | Data |
---|---|---|
2c5060cd TH |
1 | |
2 | Removed features | |
3 | ================ | |
4 | ||
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. | |
8 | ||
9 | System emulator command line arguments | |
10 | -------------------------------------- | |
11 | ||
3d9c7ec9 TH |
12 | ``-hdachs`` (removed in 2.12) |
13 | ''''''''''''''''''''''''''''' | |
14 | ||
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,...``). | |
18 | ||
19 | ``-net channel`` (removed in 2.12) | |
20 | '''''''''''''''''''''''''''''''''' | |
21 | ||
22 | This 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]``. | |
29 | Note 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 | ||
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``. | |
38 | ||
39 | ``-tdf`` (removed in 2.12) | |
40 | '''''''''''''''''''''''''' | |
41 | ||
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``. | |
46 | ||
8cc461c1 TH |
47 | ``-drive secs=s``, ``-drive heads=h`` & ``-drive cyls=c`` (removed in 3.0) |
48 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
49 | ||
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,...``). | |
53 | ||
54 | ``-drive serial=``, ``-drive trans=`` & ``-drive addr=`` (removed in 3.0) | |
55 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
56 | ||
57 | Use ``-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 | ||
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. | |
71 | ||
72 | ``-no-kvm-irqchip`` (removed in 3.0) | |
73 | '''''''''''''''''''''''''''''''''''' | |
74 | ||
75 | Use ``-machine kernel_irqchip=off`` instead. | |
76 | ||
77 | ``-no-kvm-pit-reinjection`` (removed in 3.0) | |
78 | '''''''''''''''''''''''''''''''''''''''''''' | |
79 | ||
80 | Use ``-global kvm-pit.lost_tick_policy=discard`` instead. | |
81 | ||
29e04475 TH |
82 | ``-balloon`` (removed in 3.1) |
83 | ''''''''''''''''''''''''''''' | |
84 | ||
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. | |
87 | ||
88 | ``-bootp`` (removed in 3.1) | |
89 | ''''''''''''''''''''''''''' | |
90 | ||
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. | |
95 | ||
96 | ``-redir`` (removed in 3.1) | |
97 | ''''''''''''''''''''''''''' | |
98 | ||
99 | The ``-redir [tcp|udp]:hostport:[guestaddr]:guestport`` option is replaced | |
100 | by either ``-netdev | |
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 | |
105 | per NIC. | |
106 | ||
107 | ``-smb`` (removed in 3.1) | |
108 | ''''''''''''''''''''''''' | |
109 | ||
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. | |
114 | ||
115 | ``-tftp`` (removed in 3.1) | |
116 | '''''''''''''''''''''''''' | |
117 | ||
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. | |
122 | ||
123 | ``-localtime`` (removed in 3.1) | |
124 | ''''''''''''''''''''''''''''''' | |
125 | ||
126 | Replaced by ``-rtc base=localtime``. | |
127 | ||
128 | ``-nodefconfig`` (removed in 3.1) | |
129 | ''''''''''''''''''''''''''''''''' | |
130 | ||
131 | Use ``-no-user-config`` instead. | |
132 | ||
133 | ``-rtc-td-hack`` (removed in 3.1) | |
134 | ''''''''''''''''''''''''''''''''' | |
135 | ||
136 | Use ``-rtc driftfix=slew`` instead. | |
137 | ||
138 | ``-startdate`` (removed in 3.1) | |
139 | ''''''''''''''''''''''''''''''' | |
140 | ||
141 | Replaced by ``-rtc base=date``. | |
142 | ||
7f697d7b YW |
143 | ``-vnc ...,tls=...``, ``-vnc ...,x509=...`` & ``-vnc ...,x509verify=...`` (removed in 3.1) |
144 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
29e04475 TH |
145 | |
146 | The "tls-creds" option should be used instead to point to a "tls-creds-x509" | |
147 | object created using "-object". | |
148 | ||
41f421e0 TH |
149 | ``-mem-path`` fallback to RAM (removed in 5.0) |
150 | '''''''''''''''''''''''''''''''''''''''''''''' | |
151 | ||
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. | |
158 | ||
3d9c7ec9 TH |
159 | ``-net ...,name=...`` (removed in 5.1) |
160 | '''''''''''''''''''''''''''''''''''''' | |
2c5060cd TH |
161 | |
162 | The ``name`` parameter of the ``-net`` option was a synonym | |
163 | for the ``id`` parameter, which should now be used instead. | |
164 | ||
41f421e0 TH |
165 | ``-numa node,mem=...`` (removed in 5.1) |
166 | ''''''''''''''''''''''''''''''''''''''' | |
167 | ||
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 | |
172 | performance. | |
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. | |
182 | ||
183 | ``-numa`` node (without memory specified) (removed in 5.2) | |
184 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
185 | ||
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``. | |
196 | ||
197 | ``-smp`` (invalid topologies) (removed in 5.2) | |
198 | '''''''''''''''''''''''''''''''''''''''''''''' | |
199 | ||
200 | CPU topology properties should describe whole machine topology including | |
201 | possible CPUs. | |
202 | ||
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*. | |
209 | ||
210 | ``-machine enforce-config-section=on|off`` (removed in 5.2) | |
211 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
212 | ||
213 | The ``enforce-config-section`` property was replaced by the | |
214 | ``-global migration.send-configuration={on|off}`` option. | |
215 | ||
2c5060cd TH |
216 | ``-no-kvm`` (removed in 5.2) |
217 | '''''''''''''''''''''''''''' | |
218 | ||
219 | The ``-no-kvm`` argument was a synonym for setting ``-machine accel=tcg``. | |
220 | ||
c8c9dc42 TH |
221 | ``-realtime`` (removed in 6.0) |
222 | '''''''''''''''''''''''''''''' | |
223 | ||
224 | The ``-realtime mlock=on|off`` argument has been replaced by the | |
225 | ``-overcommit mem-lock=on|off`` argument. | |
226 | ||
e2680403 TH |
227 | ``-show-cursor`` option (removed in 6.0) |
228 | '''''''''''''''''''''''''''''''''''''''' | |
90d6a086 TH |
229 | |
230 | Use ``-display sdl,show-cursor=on``, ``-display gtk,show-cursor=on`` | |
231 | or ``-display default,show-cursor=on`` instead. | |
232 | ||
2c5060cd TH |
233 | ``-tb-size`` option (removed in 6.0) |
234 | '''''''''''''''''''''''''''''''''''' | |
235 | ||
236 | QEMU 5.0 introduced an alternative syntax to specify the size of the translation | |
237 | block cache, ``-accel tcg,tb-size=``. | |
238 | ||
6db34277 TH |
239 | ``-usbdevice audio`` (removed in 6.0) |
240 | ''''''''''''''''''''''''''''''''''''' | |
241 | ||
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). | |
245 | ||
5994dcb8 DB |
246 | ``-vnc acl`` (removed in 6.0) |
247 | ''''''''''''''''''''''''''''' | |
248 | ||
249 | The ``acl`` option to the ``-vnc`` argument has been replaced | |
250 | by the ``tls-authz`` and ``sasl-authz`` options. | |
6db34277 | 251 | |
283d845c DB |
252 | ``-mon ...,control=readline,pretty=on|off`` (removed in 6.0) |
253 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
254 | ||
255 | The ``pretty=on|off`` switch has no effect for HMP monitors and | |
256 | its use is rejected. | |
257 | ||
e2cc363b YW |
258 | ``-drive file=json:{...{'driver':'file'}}`` (removed in 6.0) |
259 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
8d17adf3 DB |
260 | |
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. | |
264 | ||
36585e2b MA |
265 | Floppy controllers' drive properties (removed in 6.0) |
266 | ''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
267 | ||
268 | Use ``-device floppy,...`` instead. When configuring onboard floppy | |
269 | controllers | |
270 | :: | |
271 | ||
272 | -global isa-fdc.driveA=... | |
273 | -global sysbus-fdc.driveA=... | |
274 | -global SUNW,fdtwo.drive=... | |
275 | ||
276 | become | |
277 | :: | |
278 | ||
279 | -device floppy,unit=0,drive=... | |
280 | ||
281 | and | |
282 | :: | |
283 | ||
284 | -global isa-fdc.driveB=... | |
285 | -global sysbus-fdc.driveB=... | |
286 | ||
287 | become | |
288 | :: | |
289 | ||
290 | -device floppy,unit=1,drive=... | |
291 | ||
292 | When plugging in a floppy controller | |
293 | :: | |
294 | ||
295 | -device isa-fdc,...,driveA=... | |
296 | ||
297 | becomes | |
298 | :: | |
299 | ||
300 | -device isa-fdc,... | |
301 | -device floppy,unit=0,drive=... | |
302 | ||
303 | and | |
304 | :: | |
305 | ||
306 | -device isa-fdc,...,driveB=... | |
307 | ||
308 | becomes | |
309 | :: | |
310 | ||
311 | -device isa-fdc,... | |
312 | -device floppy,unit=1,drive=... | |
313 | ||
fe9f70a1 MA |
314 | ``-drive`` with bogus interface type (removed in 6.0) |
315 | ''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
316 | ||
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. | |
320 | ||
d2aea775 TH |
321 | ``-usbdevice ccid`` (removed in 6.0) |
322 | ''''''''''''''''''''''''''''''''''''' | |
323 | ||
324 | This option was undocumented and not used in the field. | |
1662ea9f | 325 | Use ``-device usb-ccid`` instead. |
d2aea775 | 326 | |
6debd840 AF |
327 | RISC-V firmware not booted by default (removed in 5.1) |
328 | '''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
329 | ||
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. | |
fe86fe23 TH |
332 | |
333 | ``-no-quit`` (removed in 7.0) | |
334 | ''''''''''''''''''''''''''''' | |
335 | ||
336 | The ``-no-quit`` was a synonym for ``-display ...,window-close=off`` which | |
337 | should be used instead. | |
338 | ||
c6b310b3 DB |
339 | ``--enable-fips`` (removed in 7.1) |
340 | '''''''''''''''''''''''''''''''''' | |
341 | ||
342 | This option restricted usage of certain cryptographic algorithms when | |
343 | the host is operating in FIPS mode. | |
344 | ||
345 | If FIPS compliance is required, QEMU should be built with the ``libgcrypt`` | |
346 | or ``gnutls`` library enabled as a cryptography provider. | |
347 | ||
348 | Neither the ``nettle`` library, or the built-in cryptography provider are | |
349 | supported on FIPS enabled hosts. | |
36585e2b | 350 | |
e960a7ee PB |
351 | ``-writeconfig`` (removed in 7.1) |
352 | ''''''''''''''''''''''''''''''''' | |
353 | ||
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. | |
357 | ||
0310641c PB |
358 | ``loaded`` property of ``secret`` and ``secret_keyring`` objects (removed in 7.1) |
359 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
360 | ||
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. | |
365 | ||
6e577937 PB |
366 | ``opened`` property of ``rng-*`` objects (removed in 7.1) |
367 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
368 | ||
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. | |
0310641c | 372 | |
a743d60b TH |
373 | ``-display sdl,window_close=...`` (removed in 7.1) |
374 | '''''''''''''''''''''''''''''''''''''''''''''''''' | |
375 | ||
376 | Use ``-display sdl,window-close=...`` instead (i.e. with a minus instead of | |
377 | an underscore between "window" and "close"). | |
378 | ||
379 | ``-alt-grab`` and ``-display sdl,alt_grab=on`` (removed in 7.1) | |
380 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
381 | ||
382 | Use ``-display sdl,grab-mod=lshift-lctrl-lalt`` instead. | |
383 | ||
384 | ``-ctrl-grab`` and ``-display sdl,ctrl_grab=on`` (removed in 7.1) | |
385 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
386 | ||
387 | Use ``-display sdl,grab-mod=rctrl`` instead. | |
388 | ||
707d93d4 TH |
389 | ``-sdl`` (removed in 7.1) |
390 | ''''''''''''''''''''''''' | |
391 | ||
392 | Use ``-display sdl`` instead. | |
393 | ||
394 | ``-curses`` (removed in 7.1) | |
395 | '''''''''''''''''''''''''''' | |
396 | ||
397 | Use ``-display curses`` instead. | |
398 | ||
9878fbf3 TH |
399 | Creating sound card devices using ``-soundhw`` (removed in 7.1) |
400 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
401 | ||
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>``. | |
405 | ||
5433af76 PB |
406 | ``-watchdog`` (since 7.2) |
407 | ''''''''''''''''''''''''' | |
408 | ||
409 | Use ``-device`` instead. | |
410 | ||
8b902e3d PB |
411 | Hexadecimal sizes with scaling multipliers (since 8.0) |
412 | '''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
413 | ||
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'. | |
418 | ||
6f9f6308 PB |
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`` | |
423 | respectively. The actual backend names should be used instead. | |
a743d60b | 424 | |
e803a7f9 TH |
425 | ``-drive if=none`` for the sifive_u OTP device (removed in 8.0) |
426 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
427 | ||
428 | Use ``-drive if=pflash`` to configure the OTP device of the sifive_u | |
429 | RISC-V machine instead. | |
430 | ||
36debafd DB |
431 | ``-spice password=string`` (removed in 8.0) |
432 | ''''''''''''''''''''''''''''''''''''''''''' | |
433 | ||
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. | |
e803a7f9 | 438 | |
2c5060cd TH |
439 | QEMU Machine Protocol (QMP) commands |
440 | ------------------------------------ | |
441 | ||
e2cc363b YW |
442 | ``block-dirty-bitmap-add`` "autoload" parameter (removed in 4.2) |
443 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
2c5060cd TH |
444 | |
445 | The "autoload" parameter has been ignored since 2.12.0. All bitmaps | |
446 | are automatically loaded from qcow2 images. | |
447 | ||
448 | ``cpu-add`` (removed in 5.2) | |
449 | '''''''''''''''''''''''''''' | |
450 | ||
451 | Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See | |
452 | documentation of ``query-hotpluggable-cpus`` for additional details. | |
453 | ||
0afec757 PB |
454 | ``change`` (removed in 6.0) |
455 | ''''''''''''''''''''''''''' | |
456 | ||
abea1946 VSO |
457 | Use ``blockdev-change-medium`` or ``change-vnc-password`` or |
458 | ``display-update`` instead. | |
0afec757 | 459 | |
8becb360 DB |
460 | ``query-events`` (removed in 6.0) |
461 | ''''''''''''''''''''''''''''''''' | |
462 | ||
463 | The ``query-events`` command has been superseded by the more powerful | |
464 | and accurate ``query-qmp-schema`` command. | |
465 | ||
cbde7be9 DB |
466 | ``migrate_set_cache_size`` and ``query-migrate-cache-size`` (removed in 6.0) |
467 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
468 | ||
469 | Use ``migrate_set_parameter`` and ``info migrate_parameters`` instead. | |
470 | ||
471 | ``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0) | |
472 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
473 | ||
474 | Use ``migrate_set_parameter`` instead. | |
475 | ||
8af54b91 DB |
476 | ``query-cpus`` (removed in 6.0) |
477 | ''''''''''''''''''''''''''''''' | |
478 | ||
479 | The ``query-cpus`` command is replaced by the ``query-cpus-fast`` command. | |
480 | ||
445a5b40 DB |
481 | ``query-cpus-fast`` ``arch`` output member (removed in 6.0) |
482 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
483 | ||
484 | The ``arch`` output member of the ``query-cpus-fast`` command is | |
485 | replaced by the ``target`` output member. | |
486 | ||
24e13a4d DB |
487 | chardev client socket with ``wait`` option (removed in 6.0) |
488 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
489 | ||
490 | Character devices creating sockets in client mode should not specify | |
491 | the 'wait' field, which is only applicable to sockets in server mode | |
492 | ||
ad1324e0 DB |
493 | ``query-named-block-nodes`` result ``encryption_key_missing`` (removed in 6.0) |
494 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
495 | ||
496 | Removed with no replacement. | |
497 | ||
498 | ``query-block`` result ``inserted.encryption_key_missing`` (removed in 6.0) | |
499 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
500 | ||
501 | Removed with no replacement. | |
502 | ||
81cbfd50 DB |
503 | ``query-named-block-nodes`` and ``query-block`` result dirty-bitmaps[i].status (removed in 6.0) |
504 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
505 | ||
506 | The ``status`` field of the ``BlockDirtyInfo`` structure, returned by | |
507 | these commands is removed. Two new boolean fields, ``recording`` and | |
508 | ``busy`` effectively replace it. | |
509 | ||
e67d8e29 DB |
510 | ``query-block`` result field ``dirty-bitmaps`` (removed in 6.0) |
511 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
512 | ||
513 | The ``dirty-bitmaps`` field of the ``BlockInfo`` structure, returned by | |
514 | the query-block command is itself now removed. The ``dirty-bitmaps`` | |
515 | field of the ``BlockDeviceInfo`` struct should be used instead, which is the | |
516 | type of the ``inserted`` field in query-block replies, as well as the | |
517 | type of array items in query-named-block-nodes. | |
518 | ||
50243407 KW |
519 | ``object-add`` option ``props`` (removed in 6.0) |
520 | '''''''''''''''''''''''''''''''''''''''''''''''' | |
521 | ||
522 | Specify the properties for the object as top-level arguments instead. | |
523 | ||
fb418b51 PB |
524 | ``query-sgx`` return value member ``section-size`` (removed in 8.0) |
525 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
526 | ||
527 | Member ``section-size`` in the return value of ``query-sgx`` | |
528 | was superseded by ``sections``. | |
529 | ||
530 | ||
531 | ``query-sgx-capabilities`` return value member ``section-size`` (removed in 8.0) | |
532 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
533 | ||
534 | Member ``section-size`` in the return value of ``query-sgx-capabilities`` | |
535 | was superseded by ``sections``. | |
536 | ||
2c5060cd TH |
537 | Human Monitor Protocol (HMP) commands |
538 | ------------------------------------- | |
539 | ||
5d82c101 TH |
540 | ``usb_add`` and ``usb_remove`` (removed in 2.12) |
541 | '''''''''''''''''''''''''''''''''''''''''''''''' | |
542 | ||
543 | Replaced by ``device_add`` and ``device_del`` (use ``device_add help`` for a | |
544 | list of available devices). | |
545 | ||
546 | ``host_net_add`` and ``host_net_remove`` (removed in 2.12) | |
547 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
548 | ||
549 | Replaced by ``netdev_add`` and ``netdev_del``. | |
550 | ||
2c5060cd TH |
551 | The ``hub_id`` parameter of ``hostfwd_add`` / ``hostfwd_remove`` (removed in 5.0) |
552 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
553 | ||
554 | The ``[hub_id name]`` parameter tuple of the 'hostfwd_add' and | |
555 | 'hostfwd_remove' HMP commands has been replaced by ``netdev_id``. | |
556 | ||
557 | ``cpu-add`` (removed in 5.2) | |
558 | '''''''''''''''''''''''''''' | |
559 | ||
560 | Use ``device_add`` for hotplugging vCPUs instead of ``cpu-add``. See | |
561 | documentation of ``query-hotpluggable-cpus`` for additional details. | |
562 | ||
cfb5387a PB |
563 | ``change vnc TARGET`` (removed in 6.0) |
564 | '''''''''''''''''''''''''''''''''''''' | |
565 | ||
566 | No replacement. The ``change vnc password`` and ``change DEVICE MEDIUM`` | |
567 | commands are not affected. | |
568 | ||
5994dcb8 DB |
569 | ``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, ``acl_remove`` (removed in 6.0) |
570 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
571 | ||
572 | The ``acl_show``, ``acl_reset``, ``acl_policy``, ``acl_add``, and | |
573 | ``acl_remove`` commands were removed with no replacement. Authorization | |
574 | for VNC should be performed using the pluggable QAuthZ objects. | |
575 | ||
cbde7be9 DB |
576 | ``migrate-set-cache-size`` and ``info migrate-cache-size`` (removed in 6.0) |
577 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
578 | ||
579 | Use ``migrate-set-parameters`` and ``info migrate-parameters`` instead. | |
580 | ||
581 | ``migrate_set_downtime`` and ``migrate_set_speed`` (removed in 6.0) | |
582 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
583 | ||
584 | Use ``migrate-set-parameters`` instead. | |
585 | ||
ca24b0b9 BL |
586 | ``info cpustats`` (removed in 6.1) |
587 | '''''''''''''''''''''''''''''''''' | |
588 | ||
589 | This command didn't produce any output already. Removed with no replacement. | |
590 | ||
2c5060cd TH |
591 | Guest Emulator ISAs |
592 | ------------------- | |
593 | ||
594 | RISC-V ISA privilege specification version 1.09.1 (removed in 5.1) | |
595 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
596 | ||
597 | The RISC-V ISA privilege specification version 1.09.1 has been removed. | |
598 | QEMU supports both the newer version 1.10.0 and the ratified version 1.11.0, these | |
599 | should be used instead of the 1.09.1 version. | |
600 | ||
601 | System emulator CPUS | |
602 | -------------------- | |
603 | ||
604 | KVM guest support on 32-bit Arm hosts (removed in 5.2) | |
605 | '''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
606 | ||
607 | The Linux kernel has dropped support for allowing 32-bit Arm systems | |
9d3f8b32 PB |
608 | to host KVM guests as of the 5.7 kernel, and was thus removed from QEMU |
609 | as well. Running 32-bit guests on a 64-bit Arm host remains supported. | |
2c5060cd TH |
610 | |
611 | RISC-V ISA Specific CPUs (removed in 5.1) | |
612 | ''''''''''''''''''''''''''''''''''''''''' | |
613 | ||
614 | The RISC-V cpus with the ISA version in the CPU name have been removed. The | |
615 | four CPUs are: ``rv32gcsu-v1.9.1``, ``rv32gcsu-v1.10.0``, ``rv64gcsu-v1.9.1`` and | |
616 | ``rv64gcsu-v1.10.0``. Instead the version can be specified via the CPU ``priv_spec`` | |
617 | option when using the ``rv32`` or ``rv64`` CPUs. | |
618 | ||
619 | RISC-V no MMU CPUs (removed in 5.1) | |
620 | ''''''''''''''''''''''''''''''''''' | |
621 | ||
622 | The RISC-V no MMU cpus have been removed. The two CPUs: ``rv32imacu-nommu`` and | |
623 | ``rv64imacu-nommu`` can no longer be used. Instead the MMU status can be specified | |
624 | via the CPU ``mmu`` option when using the ``rv32`` or ``rv64`` CPUs. | |
625 | ||
a058b895 GK |
626 | ``compat`` property of server class POWER CPUs (removed in 6.0) |
627 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
628 | ||
629 | The ``max-cpu-compat`` property of the ``pseries`` machine type should be used | |
630 | instead. | |
631 | ||
875bb7e3 TH |
632 | ``moxie`` CPU (removed in 6.1) |
633 | '''''''''''''''''''''''''''''' | |
634 | ||
635 | Nobody was using this CPU emulation in QEMU, and there were no test images | |
636 | available to make sure that the code is still working, so it has been removed | |
637 | without replacement. | |
638 | ||
e2cc363b YW |
639 | ``lm32`` CPUs (removed in 6.1) |
640 | '''''''''''''''''''''''''''''' | |
9d49bcf6 MA |
641 | |
642 | The only public user of this architecture was the milkymist project, | |
643 | which has been dead for years; there was never an upstream Linux | |
644 | port. Removed without replacement. | |
645 | ||
e2cc363b YW |
646 | ``unicore32`` CPUs (removed in 6.1) |
647 | ''''''''''''''''''''''''''''''''''' | |
43692239 MA |
648 | |
649 | Support for this CPU was removed from the upstream Linux kernel, and | |
650 | there is no available upstream toolchain to build binaries for it. | |
651 | Removed without replacement. | |
652 | ||
6df39f5e RH |
653 | x86 ``Icelake-Client`` CPU (removed in 7.1) |
654 | ''''''''''''''''''''''''''''''''''''''''''' | |
655 | ||
656 | There isn't ever Icelake Client CPU, it is some wrong and imaginary one. | |
657 | Use ``Icelake-Server`` instead. | |
658 | ||
eaaaf8ab PB |
659 | System accelerators |
660 | ------------------- | |
661 | ||
662 | Userspace local APIC with KVM (x86, removed 8.0) | |
663 | '''''''''''''''''''''''''''''''''''''''''''''''' | |
664 | ||
665 | ``-M kernel-irqchip=off`` cannot be used on KVM if the CPU model includes | |
666 | a local APIC. The ``split`` setting is supported, as is using ``-M | |
667 | kernel-irqchip=off`` when the CPU does not have a local APIC. | |
668 | ||
a8448735 PB |
669 | System accelerators |
670 | ------------------- | |
671 | ||
672 | MIPS "Trap-and-Emulate" KVM support (removed in 8.0) | |
673 | '''''''''''''''''''''''''''''''''''''''''''''''''''' | |
674 | ||
675 | The MIPS "Trap-and-Emulate" KVM host and guest support was removed | |
676 | from Linux in 2021, and is not supported anymore by QEMU either. | |
677 | ||
2c5060cd TH |
678 | System emulator machines |
679 | ------------------------ | |
680 | ||
36b50899 TH |
681 | ``s390-virtio`` (removed in 2.6) |
682 | '''''''''''''''''''''''''''''''' | |
683 | ||
684 | Use the ``s390-ccw-virtio`` machine instead. | |
685 | ||
686 | The m68k ``dummy`` machine (removed in 2.9) | |
687 | ''''''''''''''''''''''''''''''''''''''''''' | |
688 | ||
689 | Use the ``none`` machine with the ``loader`` device instead. | |
690 | ||
691 | ``xlnx-ep108`` (removed in 3.0) | |
692 | ''''''''''''''''''''''''''''''' | |
693 | ||
694 | The EP108 was an early access development board that is no longer used. | |
695 | Use the ``xlnx-zcu102`` machine instead. | |
696 | ||
2c5060cd TH |
697 | ``spike_v1.9.1`` and ``spike_v1.10`` (removed in 5.1) |
698 | ''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
699 | ||
700 | The version specific Spike machines have been removed in favour of the | |
701 | generic ``spike`` machine. If you need to specify an older version of the RISC-V | |
702 | spec you can use the ``-cpu rv64gcsu,priv_spec=v1.10.0`` command line argument. | |
703 | ||
704 | mips ``r4k`` platform (removed in 5.2) | |
705 | '''''''''''''''''''''''''''''''''''''' | |
706 | ||
707 | This machine type was very old and unmaintained. Users should use the ``malta`` | |
708 | machine type instead. | |
709 | ||
cd669e20 PMD |
710 | mips ``fulong2e`` machine alias (removed in 6.0) |
711 | '''''''''''''''''''''''''''''''''''''''''''''''' | |
712 | ||
713 | This machine has been renamed ``fuloong2e``. | |
714 | ||
36b50899 TH |
715 | ``pc-0.10`` up to ``pc-1.3`` (removed in 4.0 up to 6.0) |
716 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
f862ddbb TH |
717 | |
718 | These machine types were very old and likely could not be used for live | |
719 | migration from old QEMU versions anymore. Use a newer machine type instead. | |
720 | ||
57469ed3 PMD |
721 | Raspberry Pi ``raspi2`` and ``raspi3`` machines (removed in 6.2) |
722 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
723 | ||
724 | The Raspberry Pi machines come in various models (A, A+, B, B+). To be able | |
725 | to distinguish which model QEMU is implementing, the ``raspi2`` and ``raspi3`` | |
726 | machines have been renamed ``raspi2b`` and ``raspi3b``. | |
727 | ||
50f97a0e JS |
728 | Aspeed ``swift-bmc`` machine (removed in 7.0) |
729 | ''''''''''''''''''''''''''''''''''''''''''''' | |
730 | ||
731 | This machine was removed because it was unused. Alternative AST2500 based | |
732 | OpenPOWER machines are ``witherspoon-bmc`` and ``romulus-bmc``. | |
2cc1a901 | 733 | |
1335caf3 CLG |
734 | ppc ``taihu`` machine (removed in 7.2) |
735 | ''''''''''''''''''''''''''''''''''''''''''''' | |
736 | ||
737 | This machine was removed because it was partially emulated and 405 | |
738 | machines are very similar. Use the ``ref405ep`` machine instead. | |
739 | ||
2cc1a901 TH |
740 | linux-user mode CPUs |
741 | -------------------- | |
742 | ||
743 | ``tilegx`` CPUs (removed in 6.0) | |
744 | '''''''''''''''''''''''''''''''' | |
745 | ||
746 | The ``tilegx`` guest CPU support has been removed without replacement. It was | |
747 | only implemented in linux-user mode, but support for this CPU was removed from | |
748 | the upstream Linux kernel in 2018, and it has also been dropped from glibc, so | |
749 | there is no new Linux development taking place with this architecture. For | |
750 | running the old binaries, you can use older versions of QEMU. | |
751 | ||
74154d7e TH |
752 | ``ppc64abi32`` CPUs (removed in 7.0) |
753 | '''''''''''''''''''''''''''''''''''' | |
754 | ||
755 | The ``ppc64abi32`` architecture has a number of issues which regularly | |
756 | tripped up the CI testing and was suspected to be quite broken. For that | |
757 | reason the maintainers strongly suspected no one actually used it. | |
758 | ||
759 | ||
d9a6bad5 AB |
760 | TCG introspection features |
761 | -------------------------- | |
762 | ||
763 | TCG trace-events (since 6.2) | |
764 | '''''''''''''''''''''''''''' | |
765 | ||
766 | The ability to add new TCG trace points had bit rotted and as the | |
767 | feature can be replicated with TCG plugins it was removed. If | |
768 | any user is currently using this feature and needs help with | |
769 | converting to using TCG plugins they should contact the qemu-devel | |
770 | mailing list. | |
771 | ||
772 | ||
b5010183 DB |
773 | System emulator devices |
774 | ----------------------- | |
775 | ||
5643fcdd TH |
776 | ``spapr-pci-vfio-host-bridge`` (removed in 2.12) |
777 | ''''''''''''''''''''''''''''''''''''''''''''''''' | |
778 | ||
779 | The ``spapr-pci-vfio-host-bridge`` device type has been replaced by the | |
780 | ``spapr-pci-host-bridge`` device type. | |
781 | ||
782 | ``ivshmem`` (removed in 4.0) | |
783 | '''''''''''''''''''''''''''' | |
784 | ||
785 | Replaced by either the ``ivshmem-plain`` or ``ivshmem-doorbell``. | |
786 | ||
b5010183 DB |
787 | ``ide-drive`` (removed in 6.0) |
788 | '''''''''''''''''''''''''''''' | |
789 | ||
790 | The 'ide-drive' device has been removed. Users should use 'ide-hd' or | |
791 | 'ide-cd' as appropriate to get an IDE hard disk or CD-ROM as needed. | |
2cc1a901 | 792 | |
879be3af DB |
793 | ``scsi-disk`` (removed in 6.0) |
794 | '''''''''''''''''''''''''''''' | |
795 | ||
796 | The 'scsi-disk' device has been removed. Users should use 'scsi-hd' or | |
797 | 'scsi-cd' as appropriate to get a SCSI hard disk or CD-ROM as needed. | |
798 | ||
b482fb43 TH |
799 | ``sga`` (removed in 8.0) |
800 | '''''''''''''''''''''''' | |
801 | ||
802 | The ``sga`` device loaded an option ROM for x86 targets which enabled | |
803 | SeaBIOS to send messages to the serial console. SeaBIOS 1.11.0 onwards | |
804 | contains native support for this feature and thus use of the option | |
805 | ROM approach was obsolete. The native SeaBIOS support can be activated | |
806 | by using ``-machine graphics=off``. | |
807 | ||
808 | ||
2c5060cd TH |
809 | Related binaries |
810 | ---------------- | |
811 | ||
812 | ``qemu-nbd --partition`` (removed in 5.0) | |
813 | ''''''''''''''''''''''''''''''''''''''''' | |
814 | ||
815 | The ``qemu-nbd --partition $digit`` code (also spelled ``-P``) | |
816 | could only handle MBR partitions, and never correctly handled logical | |
817 | partitions beyond partition 5. Exporting a partition can still be | |
818 | done by utilizing the ``--image-opts`` option with a raw blockdev | |
819 | using the ``offset`` and ``size`` parameters layered on top of | |
820 | any other existing blockdev. For example, if partition 1 is 100MiB | |
821 | long starting at 1MiB, the old command:: | |
822 | ||
823 | qemu-nbd -t -P 1 -f qcow2 file.qcow2 | |
824 | ||
825 | can be rewritten as:: | |
826 | ||
827 | qemu-nbd -t --image-opts driver=raw,offset=1M,size=100M,file.driver=qcow2,file.file.driver=file,file.file.filename=file.qcow2 | |
828 | ||
829 | ``qemu-img convert -n -o`` (removed in 5.1) | |
830 | ''''''''''''''''''''''''''''''''''''''''''' | |
831 | ||
832 | All options specified in ``-o`` are image creation options, so | |
833 | they are now rejected when used with ``-n`` to skip image creation. | |
834 | ||
835 | ||
836 | ``qemu-img create -b bad file $size`` (removed in 5.1) | |
837 | '''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
838 | ||
839 | When creating an image with a backing file that could not be opened, | |
840 | ``qemu-img create`` used to issue a warning about the failure but | |
841 | proceed with the image creation if an explicit size was provided. | |
842 | However, as the ``-u`` option exists for this purpose, it is safer to | |
843 | enforce that any failure to open the backing image (including if the | |
844 | backing file is missing or an incorrect format was specified) is an | |
845 | error when ``-u`` is not used. | |
846 | ||
c5ba6219 PMD |
847 | ``qemu-img amend`` to adjust backing file (removed in 6.1) |
848 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
5a385bf5 EB |
849 | |
850 | The use of ``qemu-img amend`` to modify the name or format of a qcow2 | |
851 | backing image was never fully documented or tested, and interferes | |
852 | with other amend operations that need access to the original backing | |
853 | image (such as deciding whether a v3 zero cluster may be left | |
854 | unallocated when converting to a v2 image). Any changes to the | |
855 | backing chain should be performed with ``qemu-img rebase -u`` either | |
856 | before or after the remaining changes being performed by amend, as | |
857 | appropriate. | |
858 | ||
c5ba6219 PMD |
859 | ``qemu-img`` backing file without format (removed in 6.1) |
860 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
497a30db EB |
861 | |
862 | The use of ``qemu-img create``, ``qemu-img rebase``, or ``qemu-img | |
863 | convert`` to create or modify an image that depends on a backing file | |
864 | now requires that an explicit backing format be provided. This is | |
865 | for safety: if QEMU probes a different format than what you thought, | |
866 | the data presented to the guest will be corrupt; similarly, presenting | |
867 | a raw image to a guest allows a potential security exploit if a future | |
868 | probe sees a non-raw image based on guest writes. | |
869 | ||
870 | To avoid creating unsafe backing chains, you must pass ``-o | |
871 | backing_fmt=`` (or the shorthand ``-F`` during create) to specify the | |
872 | intended backing format. You may use ``qemu-img rebase -u`` to | |
873 | retroactively add a backing format to an existing image. However, be | |
874 | aware that there are already potential security risks to blindly using | |
875 | ``qemu-img info`` to probe the format of an untrusted backing image, | |
876 | when deciding what format to add into an existing image. | |
877 | ||
2c5060cd TH |
878 | Block devices |
879 | ------------- | |
880 | ||
881 | VXHS backend (removed in 5.1) | |
882 | ''''''''''''''''''''''''''''' | |
883 | ||
884 | The VXHS code did not compile since v2.12.0. It was removed in 5.1. | |
09ec8517 MA |
885 | |
886 | ``sheepdog`` driver (removed in 6.0) | |
887 | '''''''''''''''''''''''''''''''''''' | |
888 | ||
889 | The corresponding upstream server project is no longer maintained. | |
890 | Users are recommended to switch to an alternative distributed block | |
891 | device driver such as RBD. | |
a6bfdaed DDAG |
892 | |
893 | Tools | |
894 | ----- | |
895 | ||
896 | virtiofsd (removed in 8.0) | |
897 | '''''''''''''''''''''''''' | |
898 | ||
899 | There is a newer Rust implementation of ``virtiofsd`` at | |
900 | ``https://gitlab.com/virtio-fs/virtiofsd``; this has been | |
901 | stable for some time and is now widely used. | |
902 | The command line and feature set is very close to the removed | |
903 | C implementation. | |
904 |