From: Jim Minter <jminter@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] sda abort with virtio-scsi
Date: Mon, 8 Feb 2016 20:02:00 +0000 [thread overview]
Message-ID: <56B8F438.9090907@redhat.com> (raw)
In-Reply-To: <56B3550C.1010003@redhat.com>
Again FWIW:
No recurrence of the SCSI abort notices since increasing the timeout,
but still getting guest userspace lockups. Guest kernel logs show RCU
"detected stalls" messages and triggering NMIs across the CPUs. These
consistently indicate CPU 2 sitting in the CFS scheduler via the timer
interrupt, appearing to make some progress (i.e. RIP changes over time),
and the other CPUs all sitting idle. Although the guest kernel keeps
going and logging these issues out, none of the guest userspace
processes make any progress at all over several hours.
I'm upgrading to the QEMU version shipped with RHEV
(qemu-kvm-rhev-2.3.0-31.el7_2.7) to see if that helps - so far so good.
My best guess is that there's a missing bugfix in the RHEL 7 qemu
1.5.3 codebase, but which is fixed upstream and in the RHEV QEMU release.
Cheers,
Jim
On 04/02/16 13:41, Jim Minter wrote:
> FWIW, I've now done:
>
> echo 300 >/sys/block/sda/device/timeout
>
> Not entirely sure whether it would help or not, but so far I haven't had
> a recurrence.
>
> Cheers,
>
> Jim
>
next prev parent reply other threads:[~2016-02-08 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:46 [Qemu-devel] sda abort with virtio-scsi Jim Minter
2016-02-03 23:19 ` Paolo Bonzini
2016-02-03 23:34 ` Jim Minter
2016-02-04 10:23 ` Paolo Bonzini
2016-02-04 11:00 ` Denis V. Lunev
2016-02-04 13:41 ` Jim Minter
2016-02-04 13:54 ` Hannes Reinecke
2016-02-04 15:03 ` Paolo Bonzini
2016-02-04 15:11 ` Hannes Reinecke
2016-02-08 20:02 ` Jim Minter [this message]
2016-02-04 6:59 ` Hannes Reinecke
2016-02-04 11:27 ` Paolo Bonzini
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=56B8F438.9090907@redhat.com \
--to=jminter@redhat.com \
--cc=hare@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).