]>
Commit | Line | Data |
---|---|---|
7f800d34 MAL |
1 | .. _Deprecated features: |
2 | ||
41fba161 PM |
3 | Deprecated features |
4 | =================== | |
5 | ||
6 | In general features are intended to be supported indefinitely once | |
7 | introduced into QEMU. In the event that a feature needs to be removed, | |
ef1f5b0a SH |
8 | it will be listed in this section. The feature will remain functional for the |
9 | release in which it was deprecated and one further release. After these two | |
10 | releases, the feature is liable to be removed. Deprecated features may also | |
11 | generate warnings on the console when QEMU starts up, or if activated via a | |
12 | monitor command, however, this is not a mandatory requirement. | |
41fba161 PM |
13 | |
14 | Prior to the 2.10.0 release there was no official policy on how | |
15 | long features would be deprecated prior to their removal, nor | |
16 | any documented list of which features were deprecated. Thus | |
17 | any features deprecated prior to 2.10.0 will be treated as if | |
18 | they were first deprecated in the 2.10.0 release. | |
19 | ||
20 | What follows is a list of all features currently marked as | |
21 | deprecated. | |
22 | ||
23 | System emulator command line arguments | |
24 | -------------------------------------- | |
25 | ||
41fba161 PM |
26 | ``QEMU_AUDIO_`` environment variables and ``-audio-help`` (since 4.0) |
27 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
28 | ||
29 | The ``-audiodev`` argument is now the preferred way to specify audio | |
30 | backend settings instead of environment variables. To ease migration to | |
31 | the new format, the ``-audiodev-help`` option can be used to convert | |
32 | the current values of the environment variables to ``-audiodev`` options. | |
33 | ||
34 | Creating sound card devices and vnc without ``audiodev=`` property (since 4.2) | |
35 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
36 | ||
37 | When not using the deprecated legacy audio config, each sound card | |
38 | should specify an ``audiodev=`` property. Additionally, when using | |
76ca4b58 | 39 | vnc, you should specify an ``audiodev=`` property if you plan to |
41fba161 PM |
40 | transmit audio through the VNC protocol. |
41 | ||
59652436 KW |
42 | ``-chardev`` backend aliases ``tty`` and ``parport`` (since 6.0) |
43 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
44 | ||
45 | ``tty`` and ``parport`` are aliases that will be removed. Instead, the | |
46 | actual backend names ``serial`` and ``parallel`` should be used. | |
47 | ||
ccd3b3b8 PB |
48 | Short-form boolean options (since 6.0) |
49 | '''''''''''''''''''''''''''''''''''''' | |
50 | ||
51 | Boolean options such as ``share=on``/``share=off`` could be written | |
52 | in short form as ``share`` and ``noshare``. This is now deprecated | |
53 | and will cause a warning. | |
a1b40bda | 54 | |
fe636424 PB |
55 | ``delay`` option for socket character devices (since 6.0) |
56 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
57 | ||
58 | The replacement for the ``nodelay`` short-form boolean option is ``nodelay=on`` | |
59 | rather than ``delay=off``. | |
60 | ||
2c933ac6 PB |
61 | Userspace local APIC with KVM (x86, since 6.0) |
62 | '''''''''''''''''''''''''''''''''''''''''''''' | |
63 | ||
64 | Using ``-M kernel-irqchip=off`` with x86 machine types that include a local | |
65 | APIC is deprecated. The ``split`` setting is supported, as is using | |
66 | ``-M kernel-irqchip=off`` with the ISA PC machine type. | |
67 | ||
f174cd33 EB |
68 | hexadecimal sizes with scaling multipliers (since 6.0) |
69 | '''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
70 | ||
71 | Input parameters that take a size value should only use a size suffix | |
72 | (such as 'k' or 'M') when the base is written in decimal, and not when | |
73 | the value is hexadecimal. That is, '0x20M' is deprecated, and should | |
74 | be written either as '32M' or as '0x2000000'. | |
75 | ||
c47c0bcb DB |
76 | ``-spice password=string`` (since 6.0) |
77 | '''''''''''''''''''''''''''''''''''''' | |
78 | ||
79 | This option is insecure because the SPICE password remains visible in | |
80 | the process listing. This is replaced by the new ``password-secret`` | |
81 | option which lets the password be securely provided on the command | |
82 | line using a ``secret`` object instance. | |
83 | ||
d12b64ea PB |
84 | ``-watchdog`` (since 6.2) |
85 | ''''''''''''''''''''''''' | |
86 | ||
87 | Use ``-device`` instead. | |
88 | ||
c2511b16 YW |
89 | ``-smp`` ("parameter=0" SMP configurations) (since 6.2) |
90 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
91 | ||
92 | Specified CPU topology parameters must be greater than zero. | |
93 | ||
94 | In the SMP configuration, users should either provide a CPU topology | |
95 | parameter with a reasonable value (greater than zero) or just omit it | |
96 | and QEMU will compute the missing value. | |
97 | ||
98 | However, historically it was implicitly allowed for users to provide | |
99 | a parameter with zero value, which is meaningless and could also possibly | |
100 | cause unexpected results in the -smp parsing. So support for this kind of | |
101 | configurations (e.g. -smp 8,sockets=0) is deprecated since 6.2 and will | |
102 | be removed in the near future, users have to ensure that all the topology | |
103 | members described with -smp are greater than zero. | |
39c4c27d | 104 | |
67f14574 MM |
105 | Plugin argument passing through ``arg=<string>`` (since 6.1) |
106 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
107 | ||
108 | Passing TCG plugins arguments through ``arg=`` is redundant is makes the | |
109 | command-line less readable, especially when the argument itself consist of a | |
110 | name and a value, e.g. ``-plugin plugin_name,arg="arg_name=arg_value"``. | |
111 | Therefore, the usage of ``arg`` is redundant. Single-word arguments are treated | |
112 | as short-form boolean values, and passed to plugins as ``arg_name=on``. | |
113 | However, short-form booleans are deprecated and full explicit ``arg_name=on`` | |
114 | form is preferred. | |
115 | ||
6b717a8d TH |
116 | ``-drive if=none`` for the sifive_u OTP device (since 6.2) |
117 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
118 | ||
119 | Using ``-drive if=none`` to configure the OTP device of the sifive_u | |
120 | RISC-V machine is deprecated. Use ``-drive if=pflash`` instead. | |
121 | ||
67f14574 | 122 | |
41fba161 PM |
123 | QEMU Machine Protocol (QMP) commands |
124 | ------------------------------------ | |
125 | ||
e2cc363b YW |
126 | ``blockdev-open-tray``, ``blockdev-close-tray`` argument ``device`` (since 2.8) |
127 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
73756ae3 MA |
128 | |
129 | Use argument ``id`` instead. | |
130 | ||
e2cc363b YW |
131 | ``eject`` argument ``device`` (since 2.8) |
132 | ''''''''''''''''''''''''''''''''''''''''' | |
73756ae3 MA |
133 | |
134 | Use argument ``id`` instead. | |
135 | ||
e2cc363b YW |
136 | ``blockdev-change-medium`` argument ``device`` (since 2.8) |
137 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
73756ae3 MA |
138 | |
139 | Use argument ``id`` instead. | |
140 | ||
e2cc363b YW |
141 | ``block_set_io_throttle`` argument ``device`` (since 2.8) |
142 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
73756ae3 MA |
143 | |
144 | Use argument ``id`` instead. | |
145 | ||
e2cc363b YW |
146 | ``blockdev-add`` empty string argument ``backing`` (since 2.10) |
147 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
73756ae3 MA |
148 | |
149 | Use argument value ``null`` instead. | |
150 | ||
e2cc363b YW |
151 | ``block-commit`` arguments ``base`` and ``top`` (since 3.1) |
152 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
73756ae3 MA |
153 | |
154 | Use arguments ``base-node`` and ``top-node`` instead. | |
155 | ||
443127e8 KW |
156 | ``nbd-server-add`` and ``nbd-server-remove`` (since 5.2) |
157 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
158 | ||
159 | Use the more generic commands ``block-export-add`` and ``block-export-del`` | |
cbad81ce EB |
160 | instead. As part of this deprecation, where ``nbd-server-add`` used a |
161 | single ``bitmap``, the new ``block-export-add`` uses a list of ``bitmaps``. | |
443127e8 | 162 | |
75ecee72 MA |
163 | ``query-qmp-schema`` return value member ``values`` (since 6.2) |
164 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
165 | ||
166 | Member ``values`` in return value elements with meta-type ``enum`` is | |
167 | deprecated. Use ``members`` instead. | |
168 | ||
1084159b VSO |
169 | ``drive-backup`` (since 6.2) |
170 | '''''''''''''''''''''''''''' | |
171 | ||
172 | Use ``blockdev-backup`` in combination with ``blockdev-add`` instead. | |
173 | This change primarily separates the creation/opening process of the backup | |
174 | target with explicit, separate steps. ``blockdev-backup`` uses mostly the | |
175 | same arguments as ``drive-backup``, except the ``format`` and ``mode`` | |
176 | options are removed in favor of using explicit ``blockdev-create`` and | |
177 | ``blockdev-add`` calls. See :doc:`/interop/live-block-operations` for | |
178 | details. | |
179 | ||
4d8b0f0a KW |
180 | Incorrectly typed ``device_add`` arguments (since 6.2) |
181 | '''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
182 | ||
183 | Due to shortcomings in the internal implementation of ``device_add``, QEMU | |
184 | incorrectly accepts certain invalid arguments: Any object or list arguments are | |
185 | silently ignored. Other argument types are not checked, but an implicit | |
186 | conversion happens, so that e.g. string values can be assigned to integer | |
187 | device properties or vice versa. | |
188 | ||
189 | This is a bug in QEMU that will be fixed in the future so that previously | |
190 | accepted incorrect commands will return an error. Users should make sure that | |
191 | all arguments passed to ``device_add`` are consistent with the documented | |
192 | property types. | |
193 | ||
a66bd91f YZ |
194 | ``query-sgx`` return value member ``section-size`` (since 7.0) |
195 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
196 | ||
197 | Member ``section-size`` in return value elements with meta-type ``uint64`` is | |
198 | deprecated. Use ``sections`` instead. | |
199 | ||
200 | ||
201 | ``query-sgx-capabilities`` return value member ``section-size`` (since 7.0) | |
202 | ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
203 | ||
204 | Member ``section-size`` in return value elements with meta-type ``uint64`` is | |
205 | deprecated. Use ``sections`` instead. | |
206 | ||
f071dc1f JY |
207 | System accelerators |
208 | ------------------- | |
209 | ||
210 | MIPS ``Trap-and-Emul`` KVM support (since 6.0) | |
211 | '''''''''''''''''''''''''''''''''''''''''''''' | |
212 | ||
213 | The MIPS ``Trap-and-Emul`` KVM host and guest support has been removed | |
214 | from Linux upstream kernel, declare it deprecated. | |
215 | ||
54ab3c3f AB |
216 | Host Architectures |
217 | ------------------ | |
218 | ||
219 | BE MIPS (since 7.2) | |
220 | ''''''''''''''''''' | |
221 | ||
222 | As Debian 10 ("Buster") moved into LTS the big endian 32 bit version of | |
223 | MIPS moved out of support making it hard to maintain our | |
224 | cross-compilation CI tests of the architecture. As we no longer have | |
225 | CI coverage support may bitrot away before the deprecation process | |
226 | completes. The little endian variants of MIPS (both 32 and 64 bit) are | |
227 | still a supported host architecture. | |
228 | ||
d43f1670 DHB |
229 | QEMU API (QAPI) events |
230 | ---------------------- | |
231 | ||
232 | ``MEM_UNPLUG_ERROR`` (since 6.2) | |
233 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
234 | ||
235 | Use the more generic event ``DEVICE_UNPLUG_GUEST_ERROR`` instead. | |
236 | ||
237 | ||
41fba161 PM |
238 | System emulator machines |
239 | ------------------------ | |
240 | ||
5242876f JD |
241 | Arm ``virt`` machine ``dtb-kaslr-seed`` property |
242 | '''''''''''''''''''''''''''''''''''''''''''''''' | |
243 | ||
244 | The ``dtb-kaslr-seed`` property on the ``virt`` board has been | |
245 | deprecated; use the new name ``dtb-randomness`` instead. The new name | |
246 | better reflects the way this property affects all random data within | |
247 | the device tree blob, not just the ``kaslr-seed`` node. | |
248 | ||
f59fb188 TH |
249 | ``pc-i440fx-1.4`` up to ``pc-i440fx-1.7`` (since 7.0) |
250 | ''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
251 | ||
252 | These old machine types are quite neglected nowadays and thus might have | |
253 | various pitfalls with regards to live migration. Use a newer machine type | |
254 | instead. | |
255 | ||
256 | ||
cdcf766d IM |
257 | Backend options |
258 | --------------- | |
259 | ||
260 | Using non-persistent backing file with pmem=on (since 6.1) | |
261 | '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |
262 | ||
263 | This option is used when ``memory-backend-file`` is consumed by emulated NVDIMM | |
264 | device. However enabling ``memory-backend-file.pmem`` option, when backing file | |
265 | is (a) not DAX capable or (b) not on a filesystem that support direct mapping | |
266 | of persistent memory, is not safe and may lead to data loss or corruption in case | |
267 | of host crash. | |
268 | Options are: | |
269 | ||
270 | - modify VM configuration to set ``pmem=off`` to continue using fake NVDIMM | |
271 | (without persistence guaranties) with backing file on non DAX storage | |
272 | - move backing file to NVDIMM storage and keep ``pmem=on`` | |
273 | (to have NVDIMM with persistence guaranties). | |
274 | ||
41fba161 PM |
275 | Device options |
276 | -------------- | |
277 | ||
278 | Emulated device options | |
279 | ''''''''''''''''''''''' | |
280 | ||
e2cc363b YW |
281 | ``-device virtio-blk,scsi=on|off`` (since 5.0) |
282 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
41fba161 PM |
283 | |
284 | The virtio-blk SCSI passthrough feature is a legacy VIRTIO feature. VIRTIO 1.0 | |
285 | and later do not support it because the virtio-scsi device was introduced for | |
286 | full SCSI support. Use virtio-scsi instead when SCSI passthrough is required. | |
287 | ||
288 | Note this also applies to ``-device virtio-blk-pci,scsi=on|off``, which is an | |
289 | alias. | |
290 | ||
7c8d295b DB |
291 | ``-device sga`` (since 6.2) |
292 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
293 | ||
294 | The ``sga`` device loads an option ROM for x86 targets which enables | |
295 | SeaBIOS to send messages to the serial console. SeaBIOS 1.11.0 onwards | |
296 | contains native support for this feature and thus use of the option | |
297 | ROM approach is obsolete. The native SeaBIOS support can be activated | |
298 | by using ``-machine graphics=off``. | |
299 | ||
36d83272 KJ |
300 | ``-device nvme-ns,eui64-default=on|off`` (since 7.1) |
301 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
302 | ||
303 | In QEMU versions 6.1, 6.2 and 7.0, the ``nvme-ns`` generates an EUI-64 | |
120f765e | 304 | identifier that is not globally unique. If an EUI-64 identifier is required, the |
36d83272 KJ |
305 | user must set it explicitly using the ``nvme-ns`` device parameter ``eui64``. |
306 | ||
8b1e59a6 KJ |
307 | ``-device nvme,use-intel-id=on|off`` (since 7.1) |
308 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
309 | ||
310 | The ``nvme`` device originally used a PCI Vendor/Device Identifier combination | |
311 | from Intel that was not properly allocated. Since version 5.2, the controller | |
312 | has used a properly allocated identifier. Deprecate the ``use-intel-id`` | |
313 | machine compatibility parameter. | |
314 | ||
7c8d295b | 315 | |
41fba161 PM |
316 | Block device options |
317 | '''''''''''''''''''' | |
318 | ||
e2cc363b YW |
319 | ``"backing": ""`` (since 2.12) |
320 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
41fba161 PM |
321 | |
322 | In order to prevent QEMU from automatically opening an image's backing | |
323 | chain, use ``"backing": null`` instead. | |
324 | ||
e2cc363b YW |
325 | ``rbd`` keyvalue pair encoded filenames: ``""`` (since 3.1) |
326 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
41fba161 PM |
327 | |
328 | Options for ``rbd`` should be specified according to its runtime options, | |
329 | like other block drivers. Legacy parsing of keyvalue pair encoded | |
330 | filenames is useful to open images with the old format for backing files; | |
331 | These image files should be updated to use the current format. | |
332 | ||
333 | Example of legacy encoding:: | |
334 | ||
335 | json:{"file.driver":"rbd", "file.filename":"rbd:rbd/name"} | |
336 | ||
337 | The above, converted to the current supported format:: | |
338 | ||
339 | json:{"file.driver":"rbd", "file.pool":"rbd", "file.image":"name"} | |
340 | ||
41fba161 PM |
341 | Backwards compatibility |
342 | ----------------------- | |
343 | ||
e2cc363b YW |
344 | Runnability guarantee of CPU models (since 4.1) |
345 | ''''''''''''''''''''''''''''''''''''''''''''''' | |
41fba161 PM |
346 | |
347 | Previous versions of QEMU never changed existing CPU models in | |
348 | ways that introduced additional host software or hardware | |
349 | requirements to the VM. This allowed management software to | |
350 | safely change the machine type of an existing VM without | |
351 | introducing new requirements ("runnability guarantee"). This | |
352 | prevented CPU models from being updated to include CPU | |
353 | vulnerability mitigations, leaving guests vulnerable in the | |
354 | default configuration. | |
355 | ||
356 | The CPU model runnability guarantee won't apply anymore to | |
357 | existing CPU models. Management software that needs runnability | |
ac9574bc | 358 | guarantees must resolve the CPU model aliases using the |
41fba161 PM |
359 | ``alias-of`` field returned by the ``query-cpu-definitions`` QMP |
360 | command. | |
361 | ||
362 | While those guarantees are kept, the return value of | |
363 | ``query-cpu-definitions`` will have existing CPU model aliases | |
364 | point to a version that doesn't break runnability guarantees | |
365 | (specifically, version 1 of those CPU models). In future QEMU | |
366 | versions, aliases will point to newer CPU model versions | |
367 | depending on the machine type, so management software must | |
368 | resolve CPU model aliases before starting a virtual machine. | |
369 | ||
34deee7b DDAG |
370 | Tools |
371 | ----- | |
372 | ||
373 | virtiofsd | |
374 | ''''''''' | |
375 | ||
376 | There is a new Rust implementation of ``virtiofsd`` at | |
377 | ``https://gitlab.com/virtio-fs/virtiofsd``; | |
378 | since this is now marked stable, new development should be done on that | |
379 | rather than the existing C version in the QEMU tree. | |
380 | The C version will still accept fixes and patches that | |
381 | are already in development for the moment, but will eventually | |
382 | be deleted from this tree. | |
383 | New deployments should use the Rust version, and existing systems | |
384 | should consider moving to it. The command line and feature set | |
385 | is very close and moving should be simple. | |
582a098e TH |
386 | |
387 | ||
388 | QEMU guest agent | |
389 | ---------------- | |
390 | ||
391 | ``--blacklist`` command line option (since 7.2) | |
392 | ''''''''''''''''''''''''''''''''''''''''''''''' | |
393 | ||
394 | ``--blacklist`` has been replaced by ``--block-rpcs`` (which is a better | |
395 | wording for what this option does). The short form ``-b`` still stays | |
396 | the same and thus is the preferred way for scripts that should run with | |
397 | both, older and future versions of QEMU. | |
398 | ||
399 | ``blacklist`` config file option (since 7.2) | |
400 | '''''''''''''''''''''''''''''''''''''''''''' | |
401 | ||
402 | The ``blacklist`` config file option has been renamed to ``block-rpcs`` | |
403 | (to be in sync with the renaming of the corresponding command line | |
404 | option). |