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/
