From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41674)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjones@redhat.com>) id 1Y7Cmf-0006qO-Nj
	for qemu-devel@nongnu.org; Fri, 02 Jan 2015 19:41:38 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rjones@redhat.com>) id 1Y7Cmc-0004xr-Gt
	for qemu-devel@nongnu.org; Fri, 02 Jan 2015 19:41:37 -0500
Received: from mx1.redhat.com ([209.132.183.28]:38406)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjones@redhat.com>) id 1Y7Cmc-0004xW-98
	for qemu-devel@nongnu.org; Fri, 02 Jan 2015 19:41:34 -0500
Date: Sat, 3 Jan 2015 00:41:30 +0000
From: "Richard W.M. Jones" <rjones@redhat.com>
Message-ID: <20150103004130.GB9693@redhat.com>
References: <5497972A.4040203@gmail.com>
	<CABYiri-mpE_qD7EpFJeYuvyCz1-qfr9YhCw=JXv9WZ9a2-9DMQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABYiri-mpE_qD7EpFJeYuvyCz1-qfr9YhCw=JXv9WZ9a2-9DMQ@mail.gmail.com>
Subject: Re: [Qemu-devel] [question] How to get the guest physical memory
 usage from host?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: qemu-devel@nongnu.org

On Mon, Dec 22, 2014 at 12:41:45PM +0400, Andrey Korolyov wrote:
> On Mon, Dec 22, 2014 at 6:59 AM, Zhang Haoyu <zhhy.zhanghaoyu@gmail.com> wrote:
> > Hi,
> >
> > How to get the guest physical memory usage from host?
> > I don't want to introduce a guest-agent to get the info.
> >
> > Thanks,
> > Zhang Haoyu
> >
> 
> There`s probably one approach, simular to (currently abandoned)
> virt-dmesg, via peeking to the guest memory directly. What are reasons
> for not leaving this task to agent, as it looks much simpler?

Fixing virt-dmesg might be better since it has the machinery already
for talking to libvirt and accessing the guest kernel memory.

Of course there is approx zero chance that this approach will work
for Windows guests.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW