[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1359394] Re: virtio block device hangs after "virtio_b
From: |
Launchpad Bug Tracker |
Subject: |
[Qemu-devel] [Bug 1359394] Re: virtio block device hangs after "virtio_blk virtio3: requests:id 0 is not a head!" |
Date: |
Sun, 08 Oct 2017 04:17:23 -0000 |
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1359394
Title:
virtio block device hangs after "virtio_blk virtio3: requests:id 0 is
not a head!"
Status in QEMU:
Expired
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1359394/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1359394] Re: virtio block device hangs after "virtio_blk virtio3: requests:id 0 is not a head!",
Launchpad Bug Tracker <=