From: Eduardo Habkost <ehabkost@redhat.com>
To: linzhecheng <linzhecheng@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
weifuqiang <weifuqiang@huawei.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: [Qemu-devel] issue about numa configure
Date: Fri, 20 Jul 2018 16:44:37 -0300 [thread overview]
Message-ID: <20180720194437.GB22694@dhcppc11> (raw)
In-Reply-To: <D9DE8DBB19F2A24080482022C1DE758302CC60EF@DGGEMM529-MBX.china.huawei.com>
Hi,
On Thu, Jul 19, 2018 at 09:21:36AM +0000, linzhecheng wrote:
> Hi, all
> I found that qemu has a constraint in function numa_node_parse now:
> If (node->has_memdev != have_memdevs) {
> Error_setg(errp, "qemu: memdev option must be specified for either "
> "all or no nodes");
> Return;
> }
> This restricts us from being able to configure an empty numa node (without memory and cpus). But if I delete these codes, I can start a VM with cmdline:
> qemu-system-x86_64 --enable-kvm -m size=2G,slots=256,maxmem=300G -smp 2,maxcpus=4,sockets=4,cores=1,threads=1 -numa node,nodeid=0,cpus=0-1,mem=2048 -numa node,nodeid=1,cpus=2-3 ...
> We can see only one numa node inside the VM(I have tested both linux and windows) after beginning.
> And if I hot-plug the dimm memory devices into the empty node, vm will present a new numa node inside and the new memory is online then.
> I'm wondering if you have any related issue before? Or can we remove this constraint?
> Looking forward to your answers, thanks.
The check is there because memory_region_allocate_system_memory()
doesn't know how to allocate memory correctly if only some nodes
use memdev.
I wouldn't remove the check completely, but just skip it if
"mem=0" is specified explicitly.
--
Eduardo
prev parent reply other threads:[~2018-07-20 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 9:21 [Qemu-devel] issue about numa configure linzhecheng
2018-07-20 19:44 ` Eduardo Habkost [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180720194437.GB22694@dhcppc11 \
--to=ehabkost@redhat.com \
--cc=linzhecheng@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weifuqiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.