Re: [Xen-users] BLKTAP under Debian Lenny - not working

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Tue, Feb 23, 2010 at 03:51:42PM +0100, Darko Petrovi? wrote:
>    It works now. Updating the hypervisor and the tools solved the problem.
> 

Ok.. what version of hypervisor and tools works for you? What version didn't 
work? 

-- Pasi

>    Darko
> 
>    2010/2/23 Darko PetroviÃ* <[1]darko.b.petrovic@xxxxxxxxx>
> 
>      Thanks for your reply. I've updated the sources today (using git pull),
>      and then I compiled the kernel again... so it should be the most recent
>      2.6.31.6 from the Jeremy's repository.Ã  Now I tried to pull again, but
>      it says "Already up-to-date." Meanwhile, I have also tried to compile
>      with CONFIG_XEN_BLKDEV_TAP2=y (and CONFIG_XEN_BLKDEV_TAP=y remained),
>      but still no result.
> 
>      Any ideas?
> 
>      Darko
> 
>      2010/2/23 Pasi KÃârkkÃâinen <[2]pasik@xxxxxx>
> 
>        On Tue, Feb 23, 2010 at 11:48:20AM +0100, Darko Petrovi? wrote:
>        > Ã  Ã Hi all,
>        >
>        > Ã  Ã When I try to use tap:aio configuration I get the following
>        error message
>        > Ã  Ã upon executing xm create:
>        > Ã  Ã Error: Failed to create device.
>        > Ã  Ã  Ã  Ã stdout: unrecognized child response
>        > Ã  Ã  Ã  Ã stderr:
>        > Ã  Ã Check that target "/dev/vg0/lvol0" exists and that blktap2
>        driver
>        > Ã  Ã installed in dom0.
>        >
>        > Ã  Ã This is what I find in /var/log/syslog:
>        > Ã  Ã Feb 23 11:37:38 xen-1 tapdisk2[3523]: Created
>        /dev/xen/blktap-2/blktap2
>        > Ã  Ã device
>        > Ã  Ã Feb 23 11:37:38 xen-1 tapdisk2[3523]: Created
>        /dev/xen/blktap-2/tapdev2
>        > Ã  Ã device
>        > Ã  Ã Feb 23 11:37:38 xen-1 tapdisk2[3523]: new interface: ring: 252,
>        device:
>        > Ã  Ã 254, minor: 2
>        > Ã  Ã Feb 23 11:37:38 xen-1 tapdisk2[3523]: I/O queue driver: lio
>        > Ã  Ã Feb 23 11:37:38 xen-1 tapdisk2[3523]: Incorrect magic in shared
>        info.
>        > Ã  Ã Feb 23 11:37:38 xen-1 tapdisk2[3523]: Failed to open shared
>        info.
>        > Ã  Ã Feb 23 11:37:38 xen-1 kernel: [ 1002.545721]
>        blktap_sysfs_create: adding
>        > Ã  Ã attributes for dev ec6f00c0
>        > Ã  Ã Feb 23 11:37:38 xen-1 kernel: [ 1002.545728]
>        blktap_control_allocate_tap:
>        > Ã  Ã allocated tap c1ef8800
>        > Ã  Ã Feb 23 11:37:38 xen-1 kernel: [ 1002.547589] tapdisk2[3523]:
>        segfault at
>        > Ã  Ã 10 ip b758aa00 sp bfd07dd4 error 4 in
>        [1][3]libpthread-2.7.so[b7583000+15000]
>        > Ã  Ã Feb 23 11:37:38 xen-1 logger:
>        /etc/xen/scripts/xen-hotplug-cleanup:
>        > Ã  Ã XENBUS_PATH=backend/vkbd/4/0
>        > Ã  Ã Feb 23 11:37:38 xen-1 logger:
>        /etc/xen/scripts/xen-hotplug-cleanup:
>        > Ã  Ã XENBUS_PATH=backend/vfb/4/0
>        >
>        > Ã  Ã Here is also the corresponding part of my DomU configuration
>        file:
>        > Ã  Ã disk =
>        ['tap:aio:/dev/vg0/lvol0,xvda,w','tap:aio:/dev/vg0/swap,xvdb,w']
>        >
>        > Ã  Ã The pv_ops dom0 kernel is compiled with
>        CONFIG_XEN_BLKDEV_TAP=y. Both
>        > Ã  Ã lvol0 and swap do exist, I've double-checked it (namely, they
>        work with
>        > Ã  Ã phy: instead of tap:aio).
>        > Ã  Ã What could be wrong?
>        >
> 
>        What's your pv_ops dom0 version? when did you check it out?
>        Only the very recent (as of a couple of days ago) pv_ops dom0
>        kernels have working blktap2.
>        -- Pasi
> 
> References
> 
>    Visible links
>    1. mailto:darko.b.petrovic@xxxxxxxxx
>    2. mailto:pasik@xxxxxx
>    3. http://libpthread-2.7.so/

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