From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Harp Subject: Re: no udev events in netback domU driver domain, 2.6.32.14 Date: Fri, 09 Jul 2010 14:27:57 -0500 Message-ID: <4C37783D.9070506@adventiumlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: flihp@twobit.us Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > 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