From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RVDfb-0001kC-00 for qemu-devel@nongnu.org; Mon, 28 Nov 2011 21:43:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RVDfZ-0003is-1V for qemu-devel@nongnu.org; Mon, 28 Nov 2011 21:43:42 -0500 Received: from e28smtp03.in.ibm.com ([122.248.162.3]:58763) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RVDfY-0003gE-Fn for qemu-devel@nongnu.org; Mon, 28 Nov 2011 21:43:41 -0500 Received: from /spool/local by e28smtp03.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 29 Nov 2011 08:13:32 +0530 Received: from d28av04.in.ibm.com (d28av04.in.ibm.com [9.184.220.66]) by d28relay05.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pAT2hSR32232374 for ; Tue, 29 Nov 2011 08:13:29 +0530 Received: from d28av04.in.ibm.com (loopback [127.0.0.1]) by d28av04.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pAT2hRWe012836 for ; Tue, 29 Nov 2011 13:43:28 +1100 Message-ID: <4ED446CE.1090605@linux.vnet.ibm.com> Date: Tue, 29 Nov 2011 10:43:26 +0800 From: Mark Wu MIME-Version: 1.0 References: <4ECA0E46.1020400@linux.vnet.ibm.com> <4ECA2902.4000307@redhat.com> <4ECEF67E.6040805@gmail.com> <1322203344.2493.20.camel@vadimr.dell> In-Reply-To: <1322203344.2493.20.camel@vadimr.dell> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] windows guest virtio serial and balloon driver test issues List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vadim Rozenfeld Cc: "Cao, Bing Bu" , QEMU Developers , "Cao, Bing Bu" > Total physical memory on Windows will always be the same, > because we don't hot-plug/unplug physical memory. > Balloon driver works with non-paged pool memory instead. > So, every time you inflate or deflate balloon in your system, > you should see "Available memory" is changing, while physical > will always be the same. But the behaviour of virtio-balloon is different on Linux guest. It updates the totalram_pages on deflate/inflate. Therefore the total physical memory will be updated in the system management interface even though it doesn't really hot-plug/unplug any physical memory. If we just use 'info balloon' to query the balloon status, that should be fine. But if the VM management tool also collects memory information from guest, it will become confusing. Actually, I am not sure which one make more sense. I just think that it should have unified behaviour on both Linux and Windows guests.