Re: [Xen-devel] Kernel aio bug in Debian 2.6.32-5-xen kernel?

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Thu, Apr 26, 2012 at 2:46 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Thu, 2012-04-26 at 14:43 +0100, George Dunlap wrote:
>> On Thu, Apr 26, 2012 at 2:24 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> 
>> wrote:
>> > On Thu, 2012-04-26 at 14:14 +0100, George Dunlap wrote:
>> >> On Thu, Apr 26, 2012 at 1:07 PM, Stefano Stabellini
>> >> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
>> >> >> However this kernel does have blktap so why is qemu based AIO being 
>> >> >> used
>> >> >> at all?
>> >> >
>> >> > If blktap is present and working then libxl only uses QEMU for
>> >> > qcow/qcow2 disk images.
>> >>
>> >> Hmm -- except that the process that's dying is clearly QEMU, and the
>> >> disk images are definitely not qcow*, and Ian seems to think this
>> >> kernel has blktap (how could I tell?), so something's not right.
>> >
>> > It looks like it is a module -- lsmod should confirm, maybe it's a
>> > simple as loading it?
>> >
>> > (if so let me know and I'll be sure to include that when I write up
>> > "installing a Debian Dom0")
>>
>> Indeed, blktap was *not* loaded, and "modprobe blktap" seems make things 
>> work.
>>
>> Should this be done in one of the initscripts?  Or perhaps by xl?
>
> xencommons should do it, IMHO.

Just re-ran into this problem.  Is the preferred solution to just add
"modprobe blktap" (without error checking) to the xencommons
initscript?

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel