From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: DMA errors in guest caused by corrupted(?) disk image Date: Sat, 09 May 2009 12:31:40 +0300 Message-ID: <4A054D7C.8090109@redhat.com> References: <20090331025546.GL3955@hezmatt.org> <20090509090051.GB3054@nephtys> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: =?ISO-8859-1?Q?Ren=E9_Pfeiffer?= Return-path: Received: from mx2.redhat.com ([66.187.237.31]:50818 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbZEIJd3 (ORCPT ); Sat, 9 May 2009 05:33:29 -0400 In-Reply-To: <20090509090051.GB3054@nephtys> Sender: kvm-owner@vger.kernel.org List-ID: Ren=E9 Pfeiffer wrote: > On Mar 31, 2009 at 1355 +1100, Matthew Palmer appeared and said: > =20 >> Hi, >> >> I've just come across a somewhat strange problem that was suggested = I >> report to the list. >> >> The problem manifested itself as DMA errors and the like popping up = in the >> guest, like I'd expect to see if a disk in a physical machine was dy= ing, >> like this: >> >> hda: dma_timer_expiry: dma status =3D=3D 0x21 >> [...] >> =20 > > I've seen a similar effect on my KVM host server. There were I/O erro= rs > on one partition. When I tried to reformat the partition and restore = its > content from backups, mkfs was reporting I/O errors, always at the sa= me > block number. I added a second qcow2 file and moved the partition the= re. > > =20 It's worth trying a qemu-img convert to move the image to an LVM volum= e. --=20 I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.