You mean a kernel stack trace when the message was printed? I don't have
that but I guess I could add a dump_stack() call in there.
--
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:
Public bug reported:
Hi all,
I can reproduce this with kernel 3.14 and 3.17rc1. I suspect it is a
qemu issue, but I'm not sure. The test case is the following script:
qemu-system-x86_64 -machine accel=kvm -pidfile /tmp/pid$$ -m 512M -smp
8,sockets=8 -kernel vmlinuz -append init=/sbin/reboot -f
Public bug reported:
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
Why are you guys merging requests in qemu at all? Just submit them to the
kernel and let the kernel do it.
On Wed, Jul 30, 2014 at 1:11 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Tue, Jul 29, 2014 at 4:11 PM, Eric Blake ebl...@redhat.com wrote:
On 07/29/2014 06:41 AM, Stefan Hajnoczi
