From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?J=E9r=F4me_Petazzoni?= Subject: Re: xen+drbd (partial?) success story Date: Thu, 28 Apr 2005 19:23:21 +0200 Message-ID: <42711C09.1000407@enix.org> References: <42710694.1080500@enix.org> <4271180B.2010300@enix.org> <1114708213.15408.569.camel@plym.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1114708213.15408.569.camel@plym.cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: James Bulpin List-Id: xen-devel@lists.xenproject.org >>Badness in blk_plug_device at drivers/block/ll_rw_blk.c:1217 >> [] blk_plug_device+0x80/0x90 >> [] drbd_make_request_common+0x727/0x8f0 [drbd] >> >> > >Did you compile the drbd module with ARCH=xen? > > That's it ! Thanks a lot. I had compiled with Debian's module-assistant and dumbly assumed that it would reuse the correct ARCH setting from the specified source tree. I was wrong, andre-building the module package the correct flags (MAKEFLAGS="ARCH=xen") gave me a different module, which worked perfectly, without those messages. By the way, performance of drbd-backed root device in a domU seems now equal to performance of raw access in dom0. Great !