Re: [Xen-devel] BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

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.

> 
> [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