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] BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open fa

To: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Subject: Re: [Xen-devel] BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 25 Jul 2010 10:42:37 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jim Fehlig <jfehlig@xxxxxxxxxx>, Dante Cinco <dantecinco@xxxxxxxxx>
Delivery-date: Sun, 25 Jul 2010 02:43:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1280050032.4626.1282.camel@xxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acsr25bZI8TfqOLQRzylVMryW9gyKgAAiBCr
Thread-topic: [Xen-devel] BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed
User-agent: Microsoft-Entourage/12.24.0.100205
On 25/07/2010 10:27, "Daniel Stodden" <daniel.stodden@xxxxxxxxxx> wrote:

>>> Uhm.. is this change intentional?
>> 
>> xen-unstable:21338 and xen-4.0-testing:21140. So yes.
> 
> That sounds like a lot of fallout on xen-users.
> Especially for people who just want their guests to boot.
> 
> Maybe the whole notation should have rather been some _optional_ blktap
> = {1|2} cfg key, only for those who actually care?
> 
> [As much as the whole disk notation should probably always just have
> been <type>:<path>, with a separately configurable <type> -> <backend>
> mapping for people who want to override backend choices (such
> file->loopback vs file->aio).]
> 
> I guess the latter cannot be fixed. But maybe the former?

I don't personally have an opinion on it. I'm pretty sure Jim was having
other problems if this distinction wasn't made in the config file. But
perhaps it was rash to backport it to 4.0-testing, all the same.

 -- Keir



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