From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LAQyP-0005jp-Ff for qemu-devel@nongnu.org; Wed, 10 Dec 2008 10:27:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LAQyO-0005j6-RW for qemu-devel@nongnu.org; Wed, 10 Dec 2008 10:27:37 -0500 Received: from [199.232.76.173] (port=59250 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LAQyO-0005j1-OX for qemu-devel@nongnu.org; Wed, 10 Dec 2008 10:27:36 -0500 Received: from mail-qy0-f20.google.com ([209.85.221.20]:58863) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LAQyO-0002jQ-Hu for qemu-devel@nongnu.org; Wed, 10 Dec 2008 10:27:36 -0500 Received: by qyk13 with SMTP id 13so993389qyk.10 for ; Wed, 10 Dec 2008 07:27:33 -0800 (PST) Message-ID: <493FDFE1.3030606@codemonkey.ws> Date: Wed, 10 Dec 2008 09:27:29 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Hanging VM: Fix block I/O hang patch could help? References: <20081210005131.5e4ea956@brennin.fionavar.dd> In-Reply-To: <20081210005131.5e4ea956@brennin.fionavar.dd> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Daniel Dickinson wrote: > Hello, > > I have been experiencing VM hangs for some time (anything after > 0.8.2 on debian) with a Windows 98 SE guest (where I can can > So this hang happens with current SVN? > consistently hang it by a certain part of the install procedure) as > well as various Ubuntu guests (where it will hang but is 'just random'). > > From Debian bug #474386, quoting myself > > I have done the bisect and narrowed it down to three commits. Two of > the commits do not compile so could be the problem and the third is the > first bad commit that does compile. > > The last good revision is 2072 (git > d62ca2669be6d6af2c0cbda47abd7e51548060bf) > > The first known bad commit is 2075 (git > 83f640910acd7cd13ff8a603f29c46033c4fb00) > These commits are ancient. The code has changed dramatically. Please try the latest SVN. Regards, Anthony Liguori