From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: no udev events in netback domU driver domain 2.6.32.14 Date: Mon, 12 Jul 2010 11:13:22 -0400 Message-ID: <20100712151322.GE5358@phenom.dumpdata.com> References: <4C33E093.7090301@twobit.us> <20100707134505.GC4823@phenom.dumpdata.com> <4C36445C.3040907@twobit.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4C36445C.3040907@twobit.us> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: philip tricca Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > 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.