11.01.2020 14:19, Matti Hamalainen wrote: > Source: qemu > Severity: normal > Tags: upstream > > Dear Maintainer, > > After upgrading Qemu to 4.2-1 as packaged in Debian Testing, I encountered a > 100% reproducible complete hang/freeze of Qemu/KVM while running a Windows 7 > guest and starting Skype inside it. The Qemu GTK window would stop redrawing > and the program could only be ended with "kill -9". Obviously this is not > good, > and can result in data loss inside the guest. > > I took the effort to check if this issue appeared with upstream GIT Qemu and > it > did, and doing a bisect I found that the first broken upstream commit was: > > commit 286a5d201e432ed2963e5d860f239bb276edffeb
That's a great bugreport really, thank you for your work! Can you please try one more thing here, - namely, getting a backtrace? Qemu being unresponsible means it is the main thread which is blocked, so getting a backtrace should be easy - please install the qemu-system-x86 debug package (after adding something like this to sources.list: deb http://deb.debian.org/debian-debug/ stable-debug main , see https://wiki.debian.org/AutomaticDebugPackages), and get a backtrace using gdb, like this: gdb /usr/bin/qemu-system-x86_64 -p <pid-of-the-qemu-process> and do a `bt' command in there, posting the results from it. Thank you! /mjt
