[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] xencommons: Attempt to load blktap driver

>>> On 16.05.12 at 10:25, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Wed, 2012-05-16 at 08:47 +0100, Jan Beulich wrote:
>> Finally, loading "blktap" here is the right thing for pvops, but
>> wrong for legacy/forward ported kernels - blktap2 would be
>> the right module name there afaict. Perhaps, if this really is to
>> go in (temporarily), loading an alias (devname: or xen-backend:,
>> though the latter apears to be missing from the pvops driver)
>> would be better here?
> There is no blktap driver at all in mainline pvops, which is part of the
> problem and the reason for falling back to qdisk. Which pvops driver do
> you mean?

The one in Jeremy's tree (on branch xen/next-2.6.32), which is
easily forward ported to current kernels.

> Perhaps the right answer is (roughly) "modprobe blktap2 || modprobe
> blktap"?

modprobe devname:xen/blktap-2/control


modprobe xen-backend:tap2

(but I now realize the former is a 2.6.35 addition [or really a
counterpart of devname: aliases added elsewhere in that
release], and the latter one done in our patches for 3.1, where
other xen-backend: aliases also got added).

So yes, looks like the only half-way compatible way would be
what you suggest (perhaps extended to redirect stderr to


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.