If you're cc'ed, you added a section to docs/system/deprecated.rst that is old enough to permit removal. This is *not* a demand to remove, it's a polite request to consider whether the time for removal has come. Extra points for telling us in a reply. "We should remove, but I can't do it myself right now" is a valid answer. Let's review the file:
System emulator command line arguments -------------------------------------- Kővágó, Zoltán: ``QEMU_AUDIO_`` environment variables and ``-audio-help`` (since 4.0) ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' The ``-audiodev`` argument is now the preferred way to specify audio backend settings instead of environment variables. To ease migration to the new format, the ``-audiodev-help`` option can be used to convert the current values of the environment variables to ``-audiodev`` options. Kővágó, Zoltán: Creating sound card devices and vnc without ``audiodev=`` property (since 4.2) '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' When not using the deprecated legacy audio config, each sound card should specify an ``audiodev=`` property. Additionally, when using vnc, you should specify an ``audiodev=`` property if you plan to transmit audio through the VNC protocol. Gerd Hoffmann: Creating sound card devices using ``-soundhw`` (since 5.1) '''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Sound card devices should be created using ``-device`` instead. The names are the same for most devices. The exceptions are ``hda`` which needs two devices (``-device intel-hda -device hda-duplex``) and ``pcspk`` which can be activated using ``-machine pcspk-audiodev=<name>``. [...] Alistair Francis: RISC-V ``-bios`` (since 5.1) '''''''''''''''''''''''''''' QEMU 4.1 introduced support for the -bios option in QEMU for RISC-V for the RISC-V virt machine and sifive_u machine. QEMU 4.1 had no changes to the default behaviour to avoid breakages. QEMU 5.1 changes the default behaviour from ``-bios none`` to ``-bios default``. QEMU 5.1 has three options: 1. ``-bios default`` - This is the current default behavior if no -bios option is included. This option will load the default OpenSBI firmware automatically. The firmware is included with the QEMU release and no user interaction is required. All a user needs to do is specify the kernel they want to boot with the -kernel option 2. ``-bios none`` - QEMU will not automatically load any firmware. It is up to the user to load all the images they need. 3. ``-bios <file>`` - Tells QEMU to load the specified file as the firmwrae. [...] QEMU Machine Protocol (QMP) commands ------------------------------------ Myself, but I only documented it; it's actually Kevin Wolf: ``blockdev-open-tray``, ``blockdev-close-tray`` argument ``device`` (since 2.8.0) ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Use argument ``id`` instead. ``eject`` argument ``device`` (since 2.8.0) ''''''''''''''''''''''''''''''''''''''''''' Use argument ``id`` instead. ``blockdev-change-medium`` argument ``device`` (since 2.8.0) '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Use argument ``id`` instead. ``block_set_io_throttle`` argument ``device`` (since 2.8.0) ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Use argument ``id`` instead. Myself: ``blockdev-add`` empty string argument ``backing`` (since 2.10.0) ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Use argument value ``null`` instead. Myself, but I only documented it; it's actually Kevin Wolf: ``block-commit`` arguments ``base`` and ``top`` (since 3.1.0) ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Use arguments ``base-node`` and ``top-node`` instead. Kevin Wolf: ``nbd-server-add`` and ``nbd-server-remove`` (since 5.2) '''''''''''''''''''''''''''''''''''''''''''''''''''''''' Use the more generic commands ``block-export-add`` and ``block-export-del`` instead. As part of this deprecation, where ``nbd-server-add`` used a single ``bitmap``, the new ``block-export-add`` uses a list of ``bitmaps``. [...] System emulator CPUS -------------------- Thomas Huth: ``moxie`` CPU (since 5.2.0) ''''''''''''''''''''''''''' The ``moxie`` guest CPU support is deprecated and will be removed in a future version of QEMU. It's unclear whether anybody is still using CPU emulation in QEMU, and there are no test images available to make sure that the code is still working. ``lm32`` CPUs (since 5.2.0) ''''''''''''''''''''''''''' The ``lm32`` guest CPU support is deprecated and will be removed in a future version of QEMU. The only public user of this architecture was the milkymist project, which has been dead for years; there was never an upstream Linux port. ``unicore32`` CPUs (since 5.2.0) '''''''''''''''''''''''''''''''' The ``unicore32`` guest CPU support is deprecated and will be removed in a future version of QEMU. Support for this CPU was removed from the upstream Linux kernel, and there is no available upstream toolchain to build binaries for it. Robert Hoo: ``Icelake-Client`` CPU Model (since 5.2.0) '''''''''''''''''''''''''''''''''''''''''' ``Icelake-Client`` CPU Models are deprecated. Use ``Icelake-Server`` CPU Models instead. Philippe Mathieu-Daudé: MIPS ``I7200`` CPU Model (since 5.2) '''''''''''''''''''''''''''''''''''' The ``I7200`` guest CPU relies on the nanoMIPS ISA, which is deprecated (the ISA has never been upstreamed to a compiler toolchain). Therefore this CPU is also deprecated. System emulator machines ------------------------ Philippe Mathieu-Daudé: Raspberry Pi ``raspi2`` and ``raspi3`` machines (since 5.2) ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' The Raspberry Pi machines come in various models (A, A+, B, B+). To be able to distinguish which model QEMU is implementing, the ``raspi2`` and ``raspi3`` machines have been renamed ``raspi2b`` and ``raspi3b``. Device options -------------- Emulated device options ''''''''''''''''''''''' Stefan Hajnoczi: ``-device virtio-blk,scsi=on|off`` (since 5.0.0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The virtio-blk SCSI passthrough feature is a legacy VIRTIO feature. VIRTIO 1.0 and later do not support it because the virtio-scsi device was introduced for full SCSI support. Use virtio-scsi instead when SCSI passthrough is required. Note this also applies to ``-device virtio-blk-pci,scsi=on|off``, which is an alias. Block device options '''''''''''''''''''' Myself: ``"backing": ""`` (since 2.12.0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In order to prevent QEMU from automatically opening an image's backing chain, use ``"backing": null`` instead. Myself: ``rbd`` keyvalue pair encoded filenames: ``""`` (since 3.1.0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Options for ``rbd`` should be specified according to its runtime options, like other block drivers. Legacy parsing of keyvalue pair encoded filenames is useful to open images with the old format for backing files; These image files should be updated to use the current format. Example of legacy encoding:: json:{"file.driver":"rbd", "file.filename":"rbd:rbd/name"} The above, converted to the current supported format:: json:{"file.driver":"rbd", "file.pool":"rbd", "file.image":"name"} Daniel P. Berrangé: ``sheepdog`` driver (since 5.2.0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The ``sheepdog`` block device driver is deprecated. The corresponding upstream server project is no longer actively maintained. Users are recommended to switch to an alternative distributed block device driver such as RBD. The ``qemu-img convert`` command can be used to liberate existing data by moving it out of sheepdog volumes into an alternative storage backend. linux-user mode CPUs -------------------- Alex Bennée: ``ppc64abi32`` CPUs (since 5.2.0) ''''''''''''''''''''''''''''''''' The ``ppc64abi32`` architecture has a number of issues which regularly trip up our CI testing and is suspected to be quite broken. For that reason the maintainers strongly suspect no one actually uses it. MIPS ``I7200`` CPU (since 5.2) '''''''''''''''''''''''''''''' The ``I7200`` guest CPU relies on the nanoMIPS ISA, which is deprecated (the ISA has never been upstreamed to a compiler toolchain). Therefore this CPU is also deprecated. Related binaries ---------------- Eric Blake: qemu-img amend to adjust backing file (since 5.1) ''''''''''''''''''''''''''''''''''''''''''''''''' The use of ``qemu-img amend`` to modify the name or format of a qcow2 backing image is deprecated; this functionality was never fully documented or tested, and interferes with other amend operations that need access to the original backing image (such as deciding whether a v3 zero cluster may be left unallocated when converting to a v2 image). Rather, any changes to the backing chain should be performed with ``qemu-img rebase -u`` either before or after the remaining changes being performed by amend, as appropriate. qemu-img backing file without format (since 5.1) '''''''''''''''''''''''''''''''''''''''''''''''' The use of ``qemu-img create``, ``qemu-img rebase``, or ``qemu-img convert`` to create or modify an image that depends on a backing file now recommends that an explicit backing format be provided. This is for safety: if QEMU probes a different format than what you thought, the data presented to the guest will be corrupt; similarly, presenting a raw image to a guest allows a potential security exploit if a future probe sees a non-raw image based on guest writes. To avoid the warning message, or even future refusal to create an unsafe image, you must pass ``-o backing_fmt=`` (or the shorthand ``-F`` during create) to specify the intended backing format. You may use ``qemu-img rebase -u`` to retroactively add a backing format to an existing image. However, be aware that there are already potential security risks to blindly using ``qemu-img info`` to probe the format of an untrusted backing image, when deciding what format to add into an existing image. Backwards compatibility ----------------------- I'm not sure there's anything to remove here, but anyway, Peter Maydell: Runnability guarantee of CPU models (since 4.1.0) ''''''''''''''''''''''''''''''''''''''''''''''''' Previous versions of QEMU never changed existing CPU models in ways that introduced additional host software or hardware requirements to the VM. This allowed management software to safely change the machine type of an existing VM without introducing new requirements ("runnability guarantee"). This prevented CPU models from being updated to include CPU vulnerability mitigations, leaving guests vulnerable in the default configuration. The CPU model runnability guarantee won't apply anymore to existing CPU models. Management software that needs runnability guarantees must resolve the CPU model aliases using the ``alias-of`` field returned by the ``query-cpu-definitions`` QMP command. While those guarantees are kept, the return value of ``query-cpu-definitions`` will have existing CPU model aliases point to a version that doesn't break runnability guarantees (specifically, version 1 of those CPU models). In future QEMU versions, aliases will point to newer CPU model versions depending on the machine type, so management software must resolve CPU model aliases before starting a virtual machine. Guest Emulator ISAs ------------------- Philippe Mathieu-Daudé: nanoMIPS ISA '''''''''''' The ``nanoMIPS`` ISA has never been upstreamed to any compiler toolchain. As it is hard to generate binaries for it, declare it deprecated.