From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>, nikola.ciprich@linuxbox.cz
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 [thread overview]
Message-ID: <4A9EE6A9.1040405@redhat.com> (raw)
In-Reply-To: <20090902211403.GA4819@nik-comp.linuxbox.cz>
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.
next prev parent reply other threads:[~2009-09-02 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 17:23 both qemu-kvm-0.10.6 and kvm-88 crashing under heavy load while using scsi-backed storage Nikola Ciprich
2009-09-02 19:21 ` Avi Kivity
2009-09-02 21:14 ` Nikola Ciprich
2009-09-02 21:42 ` Avi Kivity [this message]
2009-09-03 9:59 ` Nikola Ciprich
2009-09-03 10:05 ` Avi Kivity
2009-09-03 10:18 ` Nikola Ciprich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9EE6A9.1040405@redhat.com \
--to=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.