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/
Home Products Support Community News


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

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Wed, 2 May 2007 08:35:19 -0700
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 May 2007 08:33:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C25E6A93.E4D5%keir@xxxxxxxxxxxxx>
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>
Mail-followup-to: keir@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <20070502151135.GA21748@xxxxxxxxxxxxxxxxx> <C25E6A93.E4D5%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.15 (2007-04-24)
On Wednesday, 02 May 2007 at 16:19, Keir Fraser wrote:
> 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.

The open of blktap0 (the character device).

Xen-devel mailing list