From: Laszlo Ersek <lersek@redhat.com>
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: How to get DomU id from DomU
Date: Tue, 31 Jan 2012 11:30:38 +0100 [thread overview]
Message-ID: <4F27C2CE.30702@redhat.com> (raw)
In-Reply-To: <CAPLaKK7bMzTQ_Uw2RBOkXQcFvg4qRS1EUHpY3Qpm6RSYPeXCjg@mail.gmail.com>
On 01/31/12 11:01, Roger Pau Monné wrote:
> This is quite a trivial question, but I haven't been able to find how
> to do it. Is there anyway to get the id of a PV DomU from inside the
> (same) PV DomU?
Here's a hack (untested): one could create a loop event channel with
EVTCHNOP_bind_interdomain (passing in DOMID_SELF as remote_dom), then
query it with EVTCHNOP_status (also passing in DOMID_SELF). On return,
"interdomain.dom" (= the remote end) should have the real domid.
Laszlo
next prev parent reply other threads:[~2012-01-31 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 10:01 How to get DomU id from DomU Roger Pau Monné
2012-01-31 10:30 ` Laszlo Ersek [this message]
2012-01-31 10:35 ` Roger Pau Monné
2012-01-31 10:46 ` Ian Campbell
2012-01-31 10:43 ` Vasiliy Tolstov
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=4F27C2CE.30702@redhat.com \
--to=lersek@redhat.com \
--cc=roger.pau@entel.upc.edu \
--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).