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


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

To: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Tue, 1 May 2007 19:48:27 -0700
Delivery-date: Tue, 01 May 2007 19:47:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.15 (2007-04-24)
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.

Xen-devel mailing list