qemu-deprecated.texi

   1 @node Deprecated features
   2 @appendix Deprecated features
   3
   4 In general features are intended to be supported indefinitely once
   5 introduced into QEMU. In the event that a feature needs to be removed,
   6 it will be listed in this appendix. The feature will remain functional
   7 for 2 releases prior to actual removal. Deprecated features may also
   8 generate warnings on the console when QEMU starts up, or if activated
   9 via a monitor command, however, this is not a mandatory requirement.
  10
  11 Prior to the 2.10.0 release there was no official policy on how
  12 long features would be deprecated prior to their removal, nor
  13 any documented list of which features were deprecated. Thus
  14 any features deprecated prior to 2.10.0 will be treated as if
  15 they were first deprecated in the 2.10.0 release.
  16
  17 What follows is a list of all features currently marked as
  18 deprecated.
  19
  20 @section Build options
  21
  22 @subsection GTK 2.x
  23
  24 Previously QEMU has supported building against both GTK 2.x
  25 and 3.x series APIs. Support for the GTK 2.x builds will be
  26 discontinued, so maintainers should switch to using GTK 3.x,
  27 which is the default.
  28
  29 @subsection SDL 1.2
  30
  31 Previously QEMU has supported building against both SDL 1.2
  32 and 2.0 series APIs. Support for the SDL 1.2 builds will be
  33 discontinued, so maintainers should switch to using SDL 2.0,
  34 which is the default.
  35
  36 @section System emulator command line arguments
  37
  38 @subsection -no-kvm (since 1.3.0)
  39
  40 The ``-no-kvm'' argument is now a synonym for setting
  41 ``-machine accel=tcg''.
  42
  43 @subsection -usbdevice (since 2.10.0)
  44
  45 The ``-usbdevice DEV'' argument is now a synonym for setting
  46 the ``-device usb-DEV'' argument instead. The deprecated syntax
  47 would automatically enable USB support on the machine type.
  48 If using the new syntax, USB support must be explicitly
  49 enabled via the ``-machine usb=on'' argument.
  50
  51 @subsection -fsdev handle (since 2.12.0)
  52
  53 The ``handle'' fsdev backend does not support symlinks and causes the 9p
  54 filesystem in the guest to fail a fair amount of tests from the PJD POSIX
  55 filesystem test suite. Also it requires the CAP_DAC_READ_SEARCH capability,
  56 which is not the recommended way to run QEMU. This backend should not be
  57 used and it will be removed with no replacement.
  58
  59 @subsection -no-frame (since 2.12.0)
  60
  61 The @code{--no-frame} argument works with SDL 1.2 only. The other user
  62 interfaces never implemented this in the first place. So this will be
  63 removed together with SDL 1.2 support.
  64
  65 @subsection -virtioconsole (since 3.0.0)
  66
  67 Option @option{-virtioconsole} has been replaced by
  68 @option{-device virtconsole}.
  69
  70 @subsection -clock (since 3.0.0)
  71
  72 The @code{-clock} option is ignored since QEMU version 1.7.0. There is no
  73 replacement since it is not needed anymore.
  74
  75 @subsection -enable-hax (since 3.0.0)
  76
  77 The @option{-enable-hax} option has been replaced by @option{-accel hax}.
  78 Both options have been introduced in QEMU version 2.9.0.
  79
  80 @subsection -drive file=json:@{...@{'driver':'file'@}@} (since 3.0)
  81
  82 The 'file' driver for drives is no longer appropriate for character or host
  83 devices and will only accept regular files (S_IFREG). The correct driver
  84 for these file types is 'host_cdrom' or 'host_device' as appropriate.
  85
  86 @subsection -net ...,name=@var{name} (since 3.1)
  87
  88 The @option{name} parameter of the @option{-net} option is a synonym
  89 for the @option{id} parameter, which should now be used instead.
  90
  91 @section QEMU Machine Protocol (QMP) commands
  92
  93 @subsection block-dirty-bitmap-add "autoload" parameter (since 2.12.0)
  94
  95 "autoload" parameter is now ignored. All bitmaps are automatically loaded
  96 from qcow2 images.
  97
  98 @subsection query-cpus (since 2.12.0)
  99
 100 The ``query-cpus'' command is replaced by the ``query-cpus-fast'' command.
 101
 102 @subsection query-cpus-fast "arch" output member (since 3.0.0)
 103
 104 The ``arch'' output member of the ``query-cpus-fast'' command is
 105 replaced by the ``target'' output member.
 106
 107 @section System emulator devices
 108
 109 @subsection ivshmem (since 2.6.0)
 110
 111 The ``ivshmem'' device type is replaced by either the ``ivshmem-plain''
 112 or ``ivshmem-doorbell`` device types.
 113
 114 @section System emulator machines
 115
 116 @subsection pc-0.10 and pc-0.11 (since 3.0)
 117
 118 These machine types are very old and likely can not be used for live migration
 119 from old QEMU versions anymore. A newer machine type should be used instead.
 120
 121 @subsection prep (PowerPC) (since 3.1)
 122
 123 This machine type uses an unmaintained firmware, broken in lots of ways,
 124 and unable to start post-2004 operating systems. 40p machine type should be
 125 used instead.
 126
 127 @section Device options
 128
 129 @subsection Block device options
 130
 131 @subsubsection "backing": "" (since 2.12.0)
 132
 133 In order to prevent QEMU from automatically opening an image's backing
 134 chain, use ``"backing": null'' instead.
 135
 136 @subsubsection rbd keyvalue pair encoded filenames: "" (since 3.1.0)
 137
 138 Options for ``rbd'' should be specified according to its runtime options,
 139 like other block drivers.  Legacy parsing of keyvalue pair encoded
 140 filenames is useful to open images with the old format for backing files;
 141 These image files should be updated to use the current format.
 142
 143 Example of legacy encoding:
 144
 145 @code{json:@{"file.driver":"rbd", "file.filename":"rbd:rbd/name"@}}
 146
 147 The above, converted to the current supported format:
 148
 149 @code{json:@{"file.driver":"rbd", "file.pool":"rbd", "file.image":"name"@}}
 150
 151 @subsection vio-spapr-device device options
 152
 153 @subsubsection "irq": "" (since 3.0.0)
 154
 155 The ``irq'' property is obsoleted.