From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: both qemu-kvm-0.10.6 and kvm-88 crashing under heavy load while using scsi-backed storage Date: Thu, 03 Sep 2009 00:42:01 +0300 Message-ID: <4A9EE6A9.1040405@redhat.com> References: <20090902172342.GA6090@nik-comp.linuxbox.cz> <4A9EC5A6.1040307@redhat.com> <20090902211403.GA4819@nik-comp.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list , nikola.ciprich@linuxbox.cz To: Nikola Ciprich Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45753 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752141AbZIBVlg (ORCPT ); Wed, 2 Sep 2009 17:41:36 -0400 In-Reply-To: <20090902211403.GA4819@nik-comp.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: On 09/03/2009 12:14 AM, Nikola Ciprich wrote: > Hello Avi, thnaks for reply. > > >> scsi is hardly tested, so this isn't surprising. >> > well, but if it's still the most safe way to go, then there's not much other > choices, is it? > > If it crashes, it isn't the safest way. >> AMD or Intel? Uni or smp guests? >> > intel, SMP guests. sorry for not reporting this right away.. > > > >> The host crash is of course more worrying. Can you capture dmesg? >> > there's absolutely no output, just immediate reboot :( > > Not even through netconsole? It's on just one host, right? >> It's in the scsi driver, so it's probable our scsi emulation is broken. >> Or maybe (unlikely) a bug in the driver. >> > Well, I guess it'll be in emulation as well, as the driver is quite old > so it should be well tested. > Any hints on how could I futher debug it? > > Add printk()s in the driver and see why it's confused. Maybe it will tell us something about the bug in the device. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.