qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Haoyu <zhhy.zhanghaoyu@gmail.com>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [question] How to get the guest physical memory usage from host?
Date: Mon, 22 Dec 2014 17:22:45 +0800	[thread overview]
Message-ID: <5497E2E5.3030805@gmail.com> (raw)
In-Reply-To: <CABYiri9+d+UG=X1iagC+oCTRF--5LL5bt_UQKtjX7RYuS8JsTQ@mail.gmail.com>


On 2014/12/22 17:16, Andrey Korolyov wrote:
> On Mon, Dec 22, 2014 at 11:57 AM, Zhang Haoyu <zhhy.zhanghaoyu@gmail.com> wrote:
>>
>> On 2014/12/22 16:41, 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?
>>>
>> In some cases, we are not permitted to install anything in customer's guest environment.
>>
>> Thanks,
>> Zhang Haoyu
> 
> Ok, looks like memory peeking techniques are only a choice then. And,
> of course, this approach tends to be less flexible, because it depends
> on a relatively strict requirements for running kernel in a guest.
> 
Yes, it should depends on guest os implementation,
because physical memory is managed by OS, which have the full knowledge of memory usage,
so I'm afraid that windows dose not friendly support it.
Could you detail the peeking techniques mentioned above?

Thanks,
Zhang Haoyu

  reply	other threads:[~2014-12-22  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22  3:59 [Qemu-devel] [question] How to get the guest physical memory usage from host? Zhang Haoyu
2014-12-22  8:41 ` Andrey Korolyov
2014-12-22  8:57   ` Zhang Haoyu
2014-12-22  9:16     ` Andrey Korolyov
2014-12-22  9:22       ` Zhang Haoyu [this message]
2014-12-22  9:33         ` Andrey Korolyov
2014-12-23  2:06           ` Zhang Haoyu
2015-01-03  0:41   ` Richard W.M. Jones

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=5497E2E5.3030805@gmail.com \
    --to=zhhy.zhanghaoyu@gmail.com \
    --cc=andrey@xdel.ru \
    --cc=qemu-devel@nongnu.org \
    /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).