From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Jinesh M.K" <mkjinesh@gmail.com>
Cc: Xen-devel@lists.xensource.com
Subject: Re: Memory location of Vm
Date: Wed, 7 Sep 2011 12:53:11 -0400 [thread overview]
Message-ID: <20110907165310.GG32190@dumpdata.com> (raw)
In-Reply-To: <CAKx7_gzR+4=FEDd+d5e+0rZWOdK7gLheG-gq8+pQbhH_ArpSqw@mail.gmail.com>
On Sat, Sep 03, 2011 at 02:55:03PM +0530, Jinesh M.K wrote:
> HAi,
> how to identify the memory location of each vm (start and end location)from
> dom0?
Take a look at the migration tools - they do a lot of looking
at the frame numbers. Keep in mind that the memory for the guests
are not contingous at all.
>
> Thanks in advance
>
> Thanking you,
> Jinesh
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-09-07 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 9:25 Memory location of Vm Jinesh M.K
2011-09-07 16:53 ` Konrad Rzeszutek Wilk [this message]
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=20110907165310.GG32190@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mkjinesh@gmail.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).