Hi,
Have you tried the latest qemu (you can git clone from
http://git.qemu.org/qemu.git).
Actually, i have posted a patch fc50ff0666315be5120c70ad00cd0b0097484b84
pc-dimm: Don't check dimm->node when there is non-NUMA config
It should not break memory hotplug feature if there is non-NUMA option.
This patch would also allow to use pc-dimm as replacement for initial memory
for non-NUMA configs.
Note: After this patch, the memory hotplug can work normally for Linux
guest OS
when there is non-NUMA option and NUMA option. But not support Windows
guest OS
to hotplug memory with no-NUMA config, actully, it's Windows limitation.
Reviewed-By: Igor Mammedov <imamm...@redhat.com>
Signed-off-by: zhanghailiang <zhang.zhanghaili...@huawei.com>
Acked-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
I think this will fix your problem, it will support hotplug a pc-dimm without
configure numa node.
Hope this can help you, Thanks
Best Regards,
zhanghailiang
On 2014/10/18 1:11, Mikhail Sennikovskii wrote:
Hi Andrey, thank you for your answer.
I know I can work around this by specifying a numa node.
My question is though is the current behaviour considered to be a bug, or
not. And if yes, when it is expected to get fixed.
Thanks,
Mikhail
On Fri, Oct 17, 2014 at 5:54 PM, Andrey Korolyov <and...@xdel.ru> wrote:
Please try to populate basic (single-node) NUMA topology to workaround
this (or specify numa node for dimm).
