|From:||Fernando Casas Schössow|
|Subject:||Re: [Qemu-block] [Qemu-devel] Guest unresponsive after Virtqueue size exceeded error|
|Date:||Thu, 31 Jan 2019 11:32:32 +0000|
Sorry for resurrecting this thread after so long but I just upgraded the host to Qemu 3.1 and libvirt 4.10 and I'm still facing this problem.
At the moment I cannot use virtio disks (virtio-blk nor virtio-scsi) with my guests in order to avoid this issue so as a workaround I'm using SATA emulated storage which is not ideal but is perfectly stable.
Do you have any suggestions on how can I progress troubleshooting?
Qemu is not crashing so I don't have any dumps that can be analyzed. The guest is just "stuck" and all I can do is destroy it and start it again.
It's really frustrating that after all this time I couldn't find the cause for this issue so any ideas are welcome.
From: Fernando Casas Schössow <address@hidden>
Sent: Saturday, June 24, 2017 10:34 AM
To: Ladi Prosek
Subject: Re: [Qemu-devel] Guest unresponsive after Virtqueue size exceeded error
After running for about 15hrs two different guests (one Windows, one Linux) crashed with around 1 hour difference and the same error in qemu log "Virqueue size exceeded".
The Linux guest was already running on virtio_scsi and without virtio_balloon. :(
I compiled and attached gdbserver to the qemu process for this guest but when I did this I got the following warning in gdbserver:
warning: Cannot call inferior functions, Linux kernel PaX protection forbids return to non-executable pages!
The default Alpine kernel is a grsec kernel. Not sure if this will interfere with debugging or not but I suspect yes.
If you need me to replace the grsec kernel with a vanilla one (also available as an option in Alpine) let me know and I will do so.
Otherwise send me an email directly so I can share with you the host:port details so you can connect to gdbserver.
On vie, jun 23, 2017 at 8:29 , Fernando Casas Schössow <address@hidden> wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|