From: Igor Mammedov <imammedo@redhat.com>
To: Yi Wang <up2wing@gmail.com>
Cc: wang.yi59@zte.com.cn, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] creating vm fails if maxMemory equals to memory, but hotplug same will success
Date: Thu, 8 Oct 2015 11:27:28 +0200 [thread overview]
Message-ID: <20151008112728.645a5b13@nial.brq.redhat.com> (raw)
In-Reply-To: <CAN35MuQh2QcPtm4NKNBUktnvnVLv2Au9KgOPRPGd+boTUPZN9g@mail.gmail.com>
On Wed, 7 Oct 2015 23:29:07 +0800
Yi Wang <up2wing@gmail.com> wrote:
> Hi, all
> When I create a vm using virsh, it will fail if maxMemory(2G) equals
> to memory(2G) in XML:
> error: Failed to create domain from vm1.xml
> error: internal error: process exited while connecting to monitor:
> qemu-kvm: -msg timestamp=on: invalid value of -m option maxmem: memory
> slots were specified but maximum memory size (0x80000000) is equal to
> the initial memory size (0x80000000)
-m initial_memory[,slots=X,maxmem=Y]
By design 'initial_memory' is not hotplugable and slots,maxmem should be
used if hotplug is needed and maxmem should be greater than initial_memory.
There isn't point specifying maxmem == initial_memory (i.e. 0-sized hotplug
space) and that's what QEMU is complaining about.
>
> However, if I allocate 1G memory for the guest at boot time(maxMemory
> is still 2G), and then hotplug 1G to it, and it will success! Now
> total memory is 2G and it equals to maxMemory. Is this a bug? if so, I
> would be happy to work on a patch to fix this. Please tell me how this
> designs if this is not a bug.
>
> Thanks a lot.
>
prev parent reply other threads:[~2015-10-08 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 15:29 [Qemu-devel] creating vm fails if maxMemory equals to memory, but hotplug same will success Yi Wang
2015-10-08 9:27 ` Igor Mammedov [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=20151008112728.645a5b13@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=up2wing@gmail.com \
--cc=wang.yi59@zte.com.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).