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: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed, tap: vs. tap2:
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 27 Jul 2010 09:21:01 +0300
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jim Fehlig <jfehlig@xxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Daniel Stodden <daniel.stodden@xxxxxxxxxx>, Dante Cinco <dantecinco@xxxxxxxxx>
Delivery-date: Mon, 26 Jul 2010 23:21:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1280140584.5872.6977.camel@xxxxxxxxxxxxxxxxxxxxxx>
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>
References: <C86EFE38.1B5DA%keir.fraser@xxxxxxxxxxxxx> <1280050032.4626.1282.camel@xxxxxxxxxxxxxxxxxxx> <1280140584.5872.6977.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Jul 26, 2010 at 11:36:24AM +0100, Ian Campbell wrote:
> On Sun, 2010-07-25 at 10:27 +0100, Daniel Stodden wrote:
> > On Fri, 2010-07-23 at 03:07 -0400, Keir Fraser wrote:
> > > On 22/07/2010 22:10, "Pasi Kärkkäinen" <pasik@xxxxxx> wrote:
> > > 
> > > >> You got it right with tap2 (instead of tap). That's the key.
> > > >> 
> > > >> So with Xen 4.0.0 and 2.6.32.14 it's: disk = [
> > > >> 'tap:tapdisk:vhd:/mnt/win2008sp2.vhd,xvda:sda1,w' ]
> > > >> 
> > > >> and with Xen 4.0.1-rc4 and 2.6.32.16 it's: disk = [
> > > >> 'tap2:tapdisk:vhd:/mnt/win2008sp2.vhd,xvda:sda1,w' ]
> > > >> 
> > > >> Very subtle change but makes a world of difference. My Windows 2008
> > > >> domU is now booting from a VHD file.
> > > >> 
> > > > 
> > > > 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?
> 
> FWIW, I completely agree with this.
> 

Yeah, especially when blktap2 is the only available on in pvops dom0 kernels..
All the users have tap:something in their cfgfiles currently..

-- Pasi

> > 
> > [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?
> > 
> > Daniel
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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