* Collecting information from a hung qemu process
@ 2023-06-08 17:57 Richard W.M. Jones
0 siblings, 0 replies; only message in thread
From: Richard W.M. Jones @ 2023-06-08 17:57 UTC (permalink / raw)
To: qemu-devel
I filed this bug about recent Linux hanging very rarely when booting
on recent qemu:
https://gitlab.com/qemu-project/qemu/-/issues/1696
As I'm able to reproduce this bug at will (albeit I have to wait for
100s or 1000s of iterations of the test), I am able to observe the
qemu process after it hangs. Is there any information which is useful
to collect from the hung qemu, such as stack traces, etc?
I know how to collect a stack trace, but if there's other information
please give me a guide about how to collect that.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-08 17:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-06-08 17:57 Collecting information from a hung qemu process Richard W.M. Jones
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.