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