Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| kvm:change_memory_of_a_guest [2020/08/19 11:28] – 192.168.1.1 | kvm:change_memory_of_a_guest [2020/08/19 11:30] (current) – 192.168.1.1 |
|---|
| **WARNING:** Do not use **virsh memtune**. | **WARNING:** Do not use **virsh memtune**. |
| |
| The optional memtune element provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. For QEMU/KVM, the parameters are applied to the QEMU process as a whole. Thus, when counting them, one needs to add up guest RAM, guest video RAM, and some memory overhead of QEMU itself. The last piece is hard to determine so one needs guess and try. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <memory>. For backwards compatibility, output is always in KiB. units since 0.9.11. Possible values for all *_limit parameters are in range from 0 to VIR_DOMAIN_MEMORY_PARAM_UNLIMITED. | The optional memtune element provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. For QEMU/KVM, the parameters are applied to the QEMU process as a whole. Thus, when counting them, one needs to add up guest RAM, guest video RAM, and some memory overhead of QEMU itself. The last piece is hard to determine so one needs guess and try. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for **<memory>**. For backwards compatibility, output is always in KiB. units since 0.9.11. Possible values for all *_limit parameters are in range from 0 to VIR_DOMAIN_MEMORY_PARAM_UNLIMITED. |
| |
| See [[http://libvirt.org/formatdomain.html#elementsMemoryTuning|here]] for more details. | See [[http://libvirt.org/formatdomain.html#elementsMemoryTuning|here]] for more details. |
