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/
Home Products Support Community News


Re: [Xen-devel] USB disk corruption on Xen 4.1.0 & Linux

To: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] USB disk corruption on Xen 4.1.0 & Linux
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 1 Jun 2011 10:23:49 -0400
Cc: Ian.Pratt@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 01 Jun 2011 07:25:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <10950255.34.1306921970059.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx>
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: <20110531145409.GN14641@xxxxxxxxxxxx> <10950255.34.1306921970059.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
> > Does the issue go away if you limit the total amount of memory visible to 
> > xen to 4GB? (mem=4096M on the xen command line)
> > 
> > If so, I suspect this is a swiotlb or latent UHCI driver issue. The easiest 
> > way of working around it is just to ensure all > dom0 memory gets allocated 
> > below 4GB, but it would be good to investigate properly.
> Yes! I put mem=4096M on the xen command line as asked and everything starts 
> working as it should yea!

<scratches his head> This is most unexpected. Do you get the same problem if 
you boot
baremetal and do 'iommu=soft' (without the mem=4G)? You should see the same 
Can you attach your lspci -vvv output too please? This is the motherboard you 
have right?

Xen-devel mailing list