WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] RE: freezing when using GPLPV drivers (including Dom0)

To: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] RE: freezing when using GPLPV drivers (including Dom0)
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>
Date: Wed, 31 Dec 2008 09:21:38 -0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Wed, 31 Dec 2008 01:22:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0155013E@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01550137@trantor><0A882F4D99BBF6449D58E61AAFD7EDD603BB4A32@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><AEC6C66638C05B468B556EA548C1A77D01550139@trantor><0A882F4D99BBF6449D58E61AAFD7EDD603BB4A33@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><AEC6C66638C05B468B556EA548C1A77D0155013A@trantor><0A882F4D99BBF6449D58E61AAFD7EDD603BB4A34@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0155013E@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aclq8extx1AIvKo+Ql6WikxbNr/6rgAAnnFwAAA7aNAAAFVNQAAAjkcQAAD8FiAAAWb/8AAJnyfA
Thread-topic: [Xen-devel] RE: freezing when using GPLPV drivers (including Dom0)
> One other thing I didn't mention - I am using sparse files as my disk
> images, using 'file:' under Xen. Again, not the highest performing
> configuration, but the restore process we are using needs to see disks
> at least as big as those that were backed up originally, and I just
> don't have 2TB of disk lying around! The data access is DomU ->
blkback
> -> /dev/loopX -> file(sparse) -> filesystem(xfs) -> LVM -> E200...
> that's a lot of room for stuff to go wrong in isn't it?

Which loop driver are you using? The std loop driver is well known to
deadlock under high write load. I think this may have been fixed with
loop-ng, but you'd likely be better off using tap:aio.

Ian

 
> I could try switching to tap:aio but I don't think that my GPLPV
> drivers
> work in that configuration... maybe time to find out why :)
> 
> Thanks
> 
> James
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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