From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50219)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <zhang.zhanghailiang@huawei.com>) id 1XfJw2-0005vV-9n
	for qemu-devel@nongnu.org; Fri, 17 Oct 2014 22:40:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <zhang.zhanghailiang@huawei.com>) id 1XfJvy-0001mp-6K
	for qemu-devel@nongnu.org; Fri, 17 Oct 2014 22:40:02 -0400
Received: from szxga02-in.huawei.com ([119.145.14.65]:4648)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <zhang.zhanghailiang@huawei.com>) id 1XfJvx-0001mU-GZ
	for qemu-devel@nongnu.org; Fri, 17 Oct 2014 22:39:58 -0400
Message-ID: <5441D2D2.4040908@huawei.com>
Date: Sat, 18 Oct 2014 10:39:14 +0800
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
MIME-Version: 1.0
References: <544137E1.7050908@profitbricks.com>	<544139F3.1030106@profitbricks.com>	<CABYiri9+8D=rTVfoJXipy3q8J_bRjnk58D7csPT6jHok4FxnHg@mail.gmail.com>
	<CALHVEJZLxJnSTb7mA9C7ucmphc70uJ-W4Kvdu-5cMbbE_t5paQ@mail.gmail.com>
In-Reply-To: <CALHVEJZLxJnSTb7mA9C7ucmphc70uJ-W4Kvdu-5cMbbE_t5paQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] memory hotplug with 2.1.2
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Mikhail Sennikovskii <mikhail.sennikovskii@profitbricks.com>, Andrey
	Korolyov <andrey@xdel.ru>
Cc: qemu-devel@nongnu.org

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 <imammedo@redhat.com>
     Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
     Acked-by: Michael S. Tsirkin <mst@redhat.com>
     Signed-off-by: Michael S. Tsirkin <mst@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 <andrey@xdel.ru> wrote:
>
>> Please try to populate basic (single-node) NUMA topology to workaround
>> this (or specify numa node for dimm).
>>
>