From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>
Cc: qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] nvdimm: disable balloon
Date: Wed, 20 Jan 2016 23:41:36 +0800 [thread overview]
Message-ID: <569FAAB0.5000606@linux.intel.com> (raw)
In-Reply-To: <569F712E.3030106@virtuozzo.com>
On 01/20/2016 07:36 PM, Vladimir Sementsov-Ogievskiy wrote:
> On 19.01.2016 11:53, Xiao Guangrong wrote:
>>
>>
>> On 01/18/2016 07:42 PM, Denis V. Lunev wrote:
>>> From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>>
>>> NVDIMM for now is planned to use as a backing store for DAX filesystem
>>> in the guest and thus this memory is excluded from guest memory management
>>> and LRUs.
>>>
>>> In this case libvirt running QEMU along with configured ballon almost
>>> immediately inflates balloon and effectively kill the guest as
>>> qemu counts nvdimm as part of the ram.
>>>
>>
>> It looks good me.
>>
>> However, it is not related to this patch, why not use the 'total memory' reported
>> by guest instead? It is more precise as a) BIOS and other components will occupy
>> available memory and b) guest may limit the memory size it can use...
>
> What do you mean? fix virtio_balloon_set_config instead of get_current_ram_size ? Or what?
No. I just thrown the question and hoped some one can figure it out, it is not about
this patch.
next prev parent reply other threads:[~2016-01-20 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 11:42 [Qemu-devel] [PATCH 1/1] nvdimm: disable balloon Denis V. Lunev
2016-01-19 8:53 ` Xiao Guangrong
2016-01-20 11:36 ` Vladimir Sementsov-Ogievskiy
2016-01-20 15:41 ` Xiao Guangrong [this message]
2016-01-25 15:24 ` Vladimir Sementsov-Ogievskiy
2016-01-20 4:59 ` Eric Blake
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=569FAAB0.5000606@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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.