From: Mikhail Sennikovskii <mikhail.sennikovskii@profitbricks.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] memory hotplug with 2.1.2
Date: Fri, 17 Oct 2014 17:38:09 +0200 [thread overview]
Message-ID: <544137E1.7050908@profitbricks.com> (raw)
Hi all,
Trying to hotplug RAM with qemu 2.1.2 using
object_add memory-backend-ram,id=ram1,size=128M
device_add pc-dimm,id=dimm1,memdev=ram1
gives the following error:
{{{
'DIMM property node has value 0' which exceeds the number of numa nodes: 0
Device 'pc-dimm' could not be initialized
}}}
which goes away if I add a "dummy" numa node via command line at VM
creation -numa node,nodeid=0
This behavior was introduced by the commit
9a72433843d912a45046959b1953861211d1838d, and disabling the check makes
the hotplug work again for me.
Is this a regression, or just some memory hotplug semantic change? And
in the latter case, could you specify the proper semantic I should use?
Thanks,
Mikhail
next reply other threads:[~2014-10-17 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 15:38 Mikhail Sennikovskii [this message]
2014-10-17 15:46 ` [Qemu-devel] memory hotplug with 2.1.2 Mikhail Sennikovskii
[not found] ` <CABYiri9+8D=rTVfoJXipy3q8J_bRjnk58D7csPT6jHok4FxnHg@mail.gmail.com>
2014-10-17 17:11 ` Mikhail Sennikovskii
2014-10-18 2:39 ` zhanghailiang
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=544137E1.7050908@profitbricks.com \
--to=mikhail.sennikovskii@profitbricks.com \
--cc=qemu-devel@nongnu.org \
/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.