All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Andrew D. Ball" <aball@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU reading its own xenstore home directory from userspace
Date: Fri, 02 Dec 2005 17:07:54 -0600	[thread overview]
Message-ID: <4390D3CA.7030900@us.ibm.com> (raw)
In-Reply-To: <1133556311.9532.38.camel@localhost.localdomain>

This documentation is old and at the time referred to the Xenbus code, 
not the userspace interface (there wasn't even such an interface at the 
time).

Are you having problems using libxenstore from within a domU on recent 
builds?

Regards,

Anthony Liguori

Andrew D. Ball wrote:

>What does this statement in the xenbus documentation on the xen wiki
>mean: "The DomU kernel interface is structured in such a way that nodes
>in the "home directory" of the domain cannot be addressed, and therefore
>cannot be read from or written to. Tools may use this space to store
>data that should not be accessed by the domain itself." ?
>[ from http://wiki.xensource.com/xenwiki/XenBus , toward the bottom ]
>
>I thought domU kernels must read data in the domU's home directory or is
>the data that drivers watch somewhere else?
>
>I want to read this data from domU userspace that that a domU can find
>out what it's UUID is.  This is important for correlating domU's with
>the dom0's they run on for management tools.  Reading a UUID from a
>domU's xenstore home directory from domU userspace is the cleanest way
>to do this that I can think of at the moment.
>
>Thanks for your help.
>
>Andrew
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

  reply	other threads:[~2005-12-02 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 20:45 domU reading its own xenstore home directory from userspace Andrew D. Ball
2005-12-02 23:07 ` Anthony Liguori [this message]
2005-12-05 13:06 ` Ewan Mellor
2006-01-16 16:34   ` Charles Duffy

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=4390D3CA.7030900@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=aball@us.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.