xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Steven Harp <steven.harp@adventiumlabs.org>
To: flihp@twobit.us
Cc: xen-devel@lists.xensource.com
Subject: Re: no udev events in netback domU driver domain, 2.6.32.14
Date: Fri, 09 Jul 2010 14:27:57 -0500	[thread overview]
Message-ID: <4C37783D.9070506@adventiumlabs.org> (raw)

> I am now getting the right udev events (the same ones Konrad shows) in 
> both my driver domain and in the client.  The problem I am still having 
> is related to the xenstore.
> 
> The network scripts run by udev access data in the xen store and use 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).
> 
> Even with the xenstored daemon running though I (and the networking 
> scripts) still can't access then xenstore.
> 
> I'm making progress but I could use a hint if someone's got one.

Possibly not related, but I have seen it hang in a similar place.
It turned out that my driver domain had failed to prepare a /var/log/xen
(where the scripts want to log errors).

Adding this did the trick here.

// Steve Harp

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 19:27 Steven Harp [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2010-07-14 21:16       ` philip tricca

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=4C37783D.9070506@adventiumlabs.org \
    --to=steven.harp@adventiumlabs.org \
    --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).