From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1359394 <1359394@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1359394] [NEW] virtio block device hangs after "virtio_blk virtio3: requests:id 0 is not a head!"
Date: Thu, 28 Aug 2014 11:52:15 +0100 [thread overview]
Message-ID: <20140828105215.GF26741@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20140820203746.5581.233.malonedeb@gac.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On Wed, Aug 20, 2014 at 08:37:46PM -0000, Slava Pestov wrote:
> The virtual machine is running block layer workloads, interrupted by
> unclean reboots (echo b > /proc/sysrq-trigger). Kernel version is 3.14.
>
> Sometimes, I get this message on boot:
>
> "virtio_blk virtio3: requests:id 0 is not a head!"
>
> Then, I/O to the virtio block devices just hangs.
>
> Unfortunately I don't have a test case and this is kind of hard to
> reproduce, but it seems related to having I/O in flight when the kernel
> is forced to reboot.
Hi Slava,
Sounds like the virtio device was not reset properly.
The guest kernel is looking for completed responses from the host. The
host has indicated that descriptor 0 is the next completed response but
the guest does not remember having submitted it.
Do you have a kernel stack trace when this was encountered?
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-28 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 20:37 [Qemu-devel] [Bug 1359394] [NEW] virtio block device hangs after "virtio_blk virtio3: requests:id 0 is not a head!" Slava Pestov
2014-08-28 10:52 ` Stefan Hajnoczi [this message]
2014-08-28 22:09 ` [Qemu-devel] [Bug 1359394] " Slava Pestov
2017-08-08 6:06 ` Thomas Huth
2017-10-08 4:17 ` Launchpad Bug Tracker
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=20140828105215.GF26741@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=1359394@bugs.launchpad.net \
--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).