From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLv0F-0007ui-L7 for qemu-devel@nongnu.org; Wed, 20 Jan 2016 10:49:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLv0A-00071q-Nl for qemu-devel@nongnu.org; Wed, 20 Jan 2016 10:48:59 -0500 Received: from mga01.intel.com ([192.55.52.88]:35436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLv0A-00071f-I6 for qemu-devel@nongnu.org; Wed, 20 Jan 2016 10:48:54 -0500 References: <1453117322-30191-1-git-send-email-den@openvz.org> <569DF99C.3040700@linux.intel.com> <569F712E.3030106@virtuozzo.com> From: Xiao Guangrong Message-ID: <569FAAB0.5000606@linux.intel.com> Date: Wed, 20 Jan 2016 23:41:36 +0800 MIME-Version: 1.0 In-Reply-To: <569F712E.3030106@virtuozzo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] nvdimm: disable balloon List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladimir Sementsov-Ogievskiy , "Denis V. Lunev" Cc: qemu-devel@nongnu.org, Igor Mammedov , Markus Armbruster , Stefan Hajnoczi , "Michael S. Tsirkin" 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 >>> >>> 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.