From: Ryan Harper Subject: Re: lsi_scsi: error: Bad Status move errors with kvm-79 Date: Thu, 4 Dec 2008 09:26:35 -0600 Message-ID: <20081204152635.GG13481@us.ibm.com> References: <20081204143842.GA11469@aketzu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: Anssi Kolehmainen Return-path: Received: from e5.ny.us.ibm.com ([32.97.182.145]:47691 "EHLO e5.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754471AbYLDP0m (ORCPT ); Thu, 4 Dec 2008 10:26:42 -0500 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e5.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id mB4FQExQ029140 for ; Thu, 4 Dec 2008 10:26:14 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mB4FQf5W176328 for ; Thu, 4 Dec 2008 10:26:41 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mB4FQf4n025487 for ; Thu, 4 Dec 2008 10:26:41 -0500 Content-Disposition: inline In-Reply-To: <20081204143842.GA11469@aketzu.net> Sender: kvm-owner@vger.kernel.org List-ID: * Anssi Kolehmainen [2008-12-04 08:51]: > Hi, > > I have kvm environment with linux-2.6.28-rc7 x86_64 (Xeon), kvm-79 host > and bunch of Win2K3 guests. Sometimes I get 'lsi_scsi: error: Bad Status > move' from kvm (qemu) and in Windows event log "The device, > \Device\Scsi\sym_hi1, did not respond within the timeout period." These > errors come somewhat at random, usually with 10-30 second intervals when > there is enough disk usage in the guest (seems that installing Bea > Weblogic or Oracle database is pretty nice for causing these errors). > > Usually windows is able to recover from these but sometimes (=too often) > I get random delays and hangups. Also I have gotten BSOD 0x77 (0x02, > 0x00, 0x00, 0x5f4000) about once a day. > > Any ideas how to debug / fix this problem? Current KVM userspace has a bogus line in the scsi code relating to the DBC register which looks like is what is tripping up the Bad Status, or could be anyhow. Try out with this patch applied to your qemu dir: http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg00043.html You can also try older KVM releases, kvm 76 at least doesn't have that line present. That might be easier than applying the patch. You can also enable debugging in qemu/hw/lsi53c895a.c and in qemu/hw/scsi-disk.c Sending that output here would be helpful if we're still tracking it. If you can recreate with the patch applied or on an older KVM that doesn't have that line in there, I'll try to reproduce. Are there free/downloadable copies of Bae or Oracle that I can use to recreate? -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh@us.ibm.com