为什么 oVirt 4.1 RedHat 包含一个类型 "maximum memory" 并在主机上保留它，阻止创建另一台机器
Why oVirt 4.1 RedHat contain a type "maximum memory" and reserved this on Host, blocking create another machines
为什么 oVirt 4.1 RedHat 上的虚拟机包含 "memory, and maximum memory"。默认情况下，所有最大内存都是 2x 内存，这会占用主机上的内存 space。此阻止创建另一个虚拟机。在 oVirt 3.5 中，这个 "Max memory" 不存在。
对应libvirt的新特性，可热插拔的最大内存：
maxMemory
The run time maximum memory allocation of the guest. The initial memory specified by either the element or the NUMA cell size configuration can be increased by hot-plugging of memory to the limit specified by this element. The unit attribute behaves the same as for . The slots attribute specifies the number of slots available for adding memory to the guest. The bounds are hypervisor specific. Note that due to alignment of the memory chunks added via memory hotplug the full size allocation specified by this element may be impossible to achieve. Since 1.2.14 supported by the QEMU driver.
为什么 oVirt 4.1 RedHat 上的虚拟机包含 "memory, and maximum memory"。默认情况下，所有最大内存都是 2x 内存，这会占用主机上的内存 space。此阻止创建另一个虚拟机。在 oVirt 3.5 中，这个 "Max memory" 不存在。
对应libvirt的新特性，可热插拔的最大内存：
maxMemory
The run time maximum memory allocation of the guest. The initial memory specified by either the element or the NUMA cell size configuration can be increased by hot-plugging of memory to the limit specified by this element. The unit attribute behaves the same as for . The slots attribute specifies the number of slots available for adding memory to the guest. The bounds are hypervisor specific. Note that due to alignment of the memory chunks added via memory hotplug the full size allocation specified by this element may be impossible to achieve. Since 1.2.14 supported by the QEMU driver.