|
@@ -104,6 +104,14 @@ In future new machine versions will not accept the option but it will still
|
|
|
work with old machine types. User can check QAPI schema to see if the legacy
|
|
|
option is supported by looking at MachineInfo::numa-mem-supported property.
|
|
|
|
|
|
+@subsection -numa node (without memory specified) (since 4.1)
|
|
|
+
|
|
|
+Splitting RAM by default between NUMA nodes has the same issues as @option{mem}
|
|
|
+parameter described above with the difference that the role of the user plays
|
|
|
+QEMU using implicit generic or board specific splitting rule.
|
|
|
+Use @option{memdev} with @var{memory-backend-ram} backend or @option{mem} (if
|
|
|
+it's supported by used machine type) to define mapping explictly instead.
|
|
|
+
|
|
|
@section QEMU Machine Protocol (QMP) commands
|
|
|
|
|
|
@subsection block-dirty-bitmap-add "autoload" parameter (since 2.12.0)
|