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: Brendan Cully <brendan@xxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
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 13:51:32 +0100
Delivery-date: Wed, 02 May 2007 05:50:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070502024827.GC18424@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: AceMuJva2p+om/irEduO2AAX8io7RQ==
Thread-topic: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)
User-agent: Microsoft-Entourage/
On 2/5/07 03:48, "Brendan Cully" <brendan@xxxxxxxxx> wrote:

> I don't know why I'm the only one to see this, but blktap hasn't been
> working for me since 14895:800aa9f5cec9. Opening /var/run/tap/blktap0
> fails. I think this is because the kernel defines BLKTAP_DEV_DIR as
> /dev/xen in drivers/xen/blktap/blktap.c, but in that changeset the
> tools define it as /var/run/tap in tools/blktap/lib/blktaplib.h.
> Reverting the change to blktaplib.h gives me blktap devices
> again. Reads and writes don't seem to make any progress. I'll keep
> investigating, but any clues would be welcome.

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.

 -- Keir

Xen-devel mailing list