@@ -95,23 +95,6 @@ error in the future.
95
95
The ``-realtime mlock=on|off `` argument has been replaced by the
96
96
``-overcommit mem-lock=on|off `` argument.
97
97
98
- ``-numa node,mem= ``\ *size * (since 4.1)
99
- '''''''''''''''''''''''''''''''''''''''
100
-
101
- The parameter ``mem `` of ``-numa node `` is used to assign a part of
102
- guest RAM to a NUMA node. But when using it, it's impossible to manage specified
103
- RAM chunk on the host side (like bind it to a host node, setting bind policy, ...),
104
- so guest end-ups with the fake NUMA configuration with suboptiomal performance.
105
- However since 2014 there is an alternative way to assign RAM to a NUMA node
106
- using parameter ``memdev ``, which does the same as ``mem `` and adds
107
- means to actualy manage node RAM on the host side. Use parameter ``memdev ``
108
- with *memory-backend-ram * backend as an replacement for parameter ``mem ``
109
- to achieve the same fake NUMA effect or a properly configured
110
- *memory-backend-file * backend to actually benefit from NUMA configuration.
111
- In future new machine versions will not accept the option but it will still
112
- work with old machine types. User can check QAPI schema to see if the legacy
113
- option is supported by looking at MachineInfo::numa-mem-supported property.
114
-
115
98
``-numa `` node (without memory specified) (since 4.1)
116
99
'''''''''''''''''''''''''''''''''''''''''''''''''''''
117
100
@@ -553,3 +536,23 @@ long starting at 1MiB, the old command::
553
536
can be rewritten as::
554
537
555
538
qemu-nbd -t --image-opts driver=raw,offset=1M,size=100M,file.driver=qcow2,file.file.driver=file,file.file.filename=file.qcow2
539
+
540
+ Command line options
541
+ --------------------
542
+
543
+ ``-numa node,mem= ``\ *size * (removed in 5.1)
544
+ ''''''''''''''''''''''''''''''''''''''''''''
545
+
546
+ The parameter ``mem `` of ``-numa node `` was used to assign a part of
547
+ guest RAM to a NUMA node. But when using it, it's impossible to manage a specified
548
+ RAM chunk on the host side (like bind it to a host node, setting bind policy, ...),
549
+ so the guest ends up with the fake NUMA configuration with suboptiomal performance.
550
+ However since 2014 there is an alternative way to assign RAM to a NUMA node
551
+ using parameter ``memdev ``, which does the same as ``mem `` and adds
552
+ means to actually manage node RAM on the host side. Use parameter ``memdev ``
553
+ with *memory-backend-ram * backend as replacement for parameter ``mem ``
554
+ to achieve the same fake NUMA effect or a properly configured
555
+ *memory-backend-file * backend to actually benefit from NUMA configuration.
556
+ New machine versions (since 5.1) will not accept the option but it will still
557
+ work with old machine types. User can check the QAPI schema to see if the legacy
558
+ option is supported by looking at MachineInfo::numa-mem-supported property.
0 commit comments