xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mahendra Kutare <mahendra.kutare@gmail.com>
To: "Fajar A. Nugraha" <fajar@fajar.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Is there a way to get the process tree of each VM from DOM0 or hypervisor ?
Date: Wed, 7 Jul 2010 06:19:16 -0400	[thread overview]
Message-ID: <AANLkTilC9ToZh9LLJsDgfx4ywfi4C--uxCDtxoX_XVZT@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinu9OEZ4XFSmBFwFKnp1XCrlwSQevzaBdAm1bcb@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]

Thanks Jiang and Fajar for your pointers. I will have a look at xenaccess.

Mahendra

On Tue, Jul 6, 2010 at 9:32 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:

> On Wed, Jul 7, 2010 at 2:12 AM, Mahendra Kutare
> <mahendra.kutare@gmail.com> wrote:
> > Hi All,
> >
> > I am working on a research project and as part of my investigation I am
> > trying to figure out is there a way or even possible to get the process
> tree
> > of each VM from either dom0 or hypervisor level ?
>
> Short answer: no.
>
> >
> > Even if its slightly inaccurate view or buried deep in some data
> structure I
> > would like to know if even its possible or not ?
>
> You could take a look at http://code.google.com/p/xenaccess/
>
> --
> Fajar
>

[-- Attachment #1.2: Type: text/html, Size: 1276 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-07-07 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 19:12 Is there a way to get the process tree of each VM from DOM0 or hypervisor ? Mahendra Kutare
2010-07-07  1:32 ` Fajar A. Nugraha
2010-07-07 10:19   ` Mahendra Kutare [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=AANLkTilC9ToZh9LLJsDgfx4ywfi4C--uxCDtxoX_XVZT@mail.gmail.com \
    --to=mahendra.kutare@gmail.com \
    --cc=fajar@fajar.net \
    --cc=xen-devel@lists.xensource.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).