|
From: | Fernando Casas Schössow |
Subject: | Re: [Qemu-block] [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests) |
Date: | Thu, 18 Oct 2018 12:25:56 +0000 |
Hi Stefan,
I hope this email finds you well and I apologize in advance for resurrecting this thread.
I'm currently running on qemu 2.12.1 and I'm still having this issue every few days but now I managed to get a core dump generated (without including the guest memory).
Would you take a look at the dump? Please let me know how do you prefer me to share it. The file is around 290MB as is but I can try to compress it.
Looking forward your reply.
Thanks
Kind regards,
Fernando
From: Stefan Hajnoczi <address@hidden>
Sent: Monday, January 29, 2018 5:01 PM To: Fernando Casas Schössow Cc: qemu-devel; address@hidden; Jeff Cody Subject: Re: [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests) On Wed, Dec 13, 2017 at 03:33:01PM +0000, Fernando Casas Schössow wrote:
> Maybe I’m missing something here but, if I recall correctly, the qemu process for the guest is terminated when this problem happens. So how a debugger will be attached to a process that is gone? Sorry, this got lost in my inbox. assert(false) sends SIGABRT to the process. The default behavior is to dump a core file that can be analyzed later with GDB. Your system must have core dumps enabled (i.e. ulimit -c unlimited). Also, various pieces of software like systemd's coredumpctl can influence where and how core dumps are stored. But in short, an assertion failure produces a core dump. Stefan |
[Prev in Thread] | Current Thread | [Next in Thread] |