xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: philip tricca <flihp@twobit.us>
Cc: xen-devel@lists.xensource.com
Subject: Re: no udev events in netback domU driver domain 2.6.32.14
Date: Mon, 12 Jul 2010 11:13:22 -0400	[thread overview]
Message-ID: <20100712151322.GE5358@phenom.dumpdata.com> (raw)
In-Reply-To: <4C36445C.3040907@twobit.us>

> it to return status information to dom0:
> /local/domain/X/backend/vif/Y/Z/hotplug-status
> The xenstore is completely inaccessible from my driver domain
> however. I've installed the xenstored daemon in the driver domain
> which requires running it with the --no-domain-init option to keep
> it from trying to execute privileged operations (it's not dom0).

You should be able to read it? At least for your domain entry?
> 
> Even with the xenstored daemon running though I (and the networking
> scripts) still can't access then xenstore.

Well, you can't access all of it b/c there is an ownership of the
/local/domain/0 being under Dom0. Not under DomU. AFAICT the backends
use those entries (for example, netback detects via watches that
somebody wrote in /local/domain/0/backend/vif and calls its .probe
function), they will interogate the XenStore and then create udev events
which are fired off to userspace.

  reply	other threads:[~2010-07-12 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  2:04 no udev events in netback domU driver domain 2.6.32.14 philip tricca
2010-07-07 13:45 ` Konrad Rzeszutek Wilk
2010-07-08 21:34   ` philip tricca
2010-07-12 15:13     ` Konrad Rzeszutek Wilk [this message]
2010-07-14 21:16       ` philip tricca
  -- strict thread matches above, loose matches on Subject: below --
2010-07-09 19:27 no udev events in netback domU driver domain, 2.6.32.14 Steven Harp

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=20100712151322.GE5358@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=flihp@twobit.us \
    --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).