WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/

To: Brendan Cully <brendan@xxxxxxxxx>
Subject: Re: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 02 May 2007 16:19:31 +0100
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 May 2007 08:18:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070502151135.GA21748@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceMzUgmhvK71PjAEduO2AAX8io7RQ==
Thread-topic: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)
User-agent: Microsoft-Entourage/11.3.3.061214


On 2/5/07 16:11, "Brendan Cully" <brendan@xxxxxxxxx> wrote:

>> More likely it's simply because /var/run/tap/ doesn't exist?
>> 
>> Either some startup script needs to 'mkdir -p', or blktapctrl needs to make
>> the directory on demand.
> 
> the blktap tools do create that directory on demand, and in fact
> /var/run/tap/blktap0 is properly created. What fails is the 'open',
> somewhere in the kernel I believe. Maybe this only affects
> block-attaching a device in domain 0?

The open() that's part of mkfifo()? Those FIFO files have nothing to do with
the blktap kernel module, I believe, in which case this can't have anything
to do with a mismatch of something between blktap user and blktap kernel.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel