mirrors/qemu
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Cleanup "'-mem-path' fallback to RAM" deprecation text

Browse Source 
it was actually removed in 5.0,
commit 68a86dc15c (numa: remove deprecated -mem-path fallback to anonymous RAM)
clean up forgotten remnants in docs.

Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <20200911084410.788171-3-imammedo@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Igor Mammedov 2020-09-11 04:44:09 -04:00 committed by Paolo Bonzini
parent b21aa7e01e
commit c01f250cb8
1 changed files with 21 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
docs/system/deprecated.rst
View File

@ -92,17 +92,6 @@ error in the future.
The ``-realtime mlock=on|off`` argument has been replaced by the The ``-realtime mlock=on|off`` argument has been replaced by the
``-overcommit mem-lock=on|off`` argument. ``-overcommit mem-lock=on|off`` argument.
``-mem-path`` fallback to RAM (since 4.1)
'''''''''''''''''''''''''''''''''''''''''
Currently if guest RAM allocation from file pointed by ``mem-path``
fails, QEMU falls back to allocating from RAM, which might result
in unpredictable behavior since the backing file specified by the user
is ignored. In the future, users will be responsible for making sure
the backing storage specified with ``-mem-path`` can actually provide
the guest RAM configured with ``-m`` and QEMU will fail to start up if
RAM allocation is unsuccessful.
RISC-V ``-bios`` (since 5.1) RISC-V ``-bios`` (since 5.1)
'''''''''''''''''''''''''''' ''''''''''''''''''''''''''''
@ -603,6 +592,19 @@ error when ``-u`` is not used.
Command line options Command line options
-------------------- --------------------
``-smp`` (invalid topologies) (removed 5.2)
'''''''''''''''''''''''''''''''''''''''''''
CPU topology properties should describe whole machine topology including
possible CPUs.
However, historically it was possible to start QEMU with an incorrect topology
where *n* <= *sockets* * *cores* * *threads* < *maxcpus*,
which could lead to an incorrect topology enumeration by the guest.
Support for invalid topologies is removed, the user must ensure
topologies described with -smp include all possible cpus, i.e.
*sockets* * *cores* * *threads* = *maxcpus*.
``-numa`` node (without memory specified) (removed 5.2) ``-numa`` node (without memory specified) (removed 5.2)
''''''''''''''''''''''''''''''''''''''''''''''''''''''' '''''''''''''''''''''''''''''''''''''''''''''''''''''''
@ -634,18 +636,15 @@ New machine versions (since 5.1) will not accept the option but it will still
work with old machine types. User can check the QAPI schema to see if the legacy work with old machine types. User can check the QAPI schema to see if the legacy
option is supported by looking at MachineInfo::numa-mem-supported property. option is supported by looking at MachineInfo::numa-mem-supported property.
``-smp`` (invalid topologies) (removed 5.2) ``-mem-path`` fallback to RAM (removed in 5.0)
''''''''''''''''''''''''''''''''''''''''''' ''''''''''''''''''''''''''''''''''''''''''''''
CPU topology properties should describe whole machine topology including If guest RAM allocation from file pointed by ``mem-path`` failed,
possible CPUs. QEMU was falling back to allocating from RAM, which might have resulted
in unpredictable behavior since the backing file specified by the user
However, historically it was possible to start QEMU with an incorrect topology as ignored. Currently, users are responsible for making sure the backing storage
where *n* <= *sockets* * *cores* * *threads* < *maxcpus*, specified with ``-mem-path`` can actually provide the guest RAM configured with
which could lead to an incorrect topology enumeration by the guest. ``-m`` and QEMU fails to start up if RAM allocation is unsuccessful.
Support for invalid topologies is removed, the user must ensure
topologies described with -smp include all possible cpus, i.e.
*sockets* * *cores* * *threads* = *maxcpus*.
Block devices Block devices
------------- -------------