qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Wu <wudxw@linux.vnet.ibm.com>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: "Cao, Bing Bu" <mars@linux.vnet.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Cao, Bing Bu" <caobingbu@gmail.com>
Subject: Re: [Qemu-devel] windows guest virtio serial and balloon driver test issues
Date: Tue, 29 Nov 2011 10:43:26 +0800	[thread overview]
Message-ID: <4ED446CE.1090605@linux.vnet.ibm.com> (raw)
In-Reply-To: <1322203344.2493.20.camel@vadimr.dell>


> 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.

  parent reply	other threads:[~2011-11-29  2:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  8:39 [Qemu-devel] windows guest virtio serial and balloon driver test issues Cao,Bing Bu
2011-11-21 10:33 ` Arkady Frenkel
2011-11-25  1:59   ` Cao,Bing Bu
2011-11-25  6:42     ` Vadim Rozenfeld
2011-11-29  0:58       ` Cao,Bing Bu
2011-11-29 12:36         ` Vadim Rozenfeld
2011-12-05  2:44           ` Cao,Bing Bu
2011-11-29  2:43       ` Mark Wu [this message]
2011-11-29 13:46         ` Vadim Rozenfeld

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=4ED446CE.1090605@linux.vnet.ibm.com \
    --to=wudxw@linux.vnet.ibm.com \
    --cc=caobingbu@gmail.com \
    --cc=mars@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vrozenfe@redhat.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 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).