Issue does not occur in latest version of QEMU anymore.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1884684
Title:
QEMU 5.0: Guest V
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please
I do get get the same backtrace in gdb every time every time when we
reproduce the hang:
(gdb) thread apply all bt
Thread 9 (Thread 0x7fd1415ff700 (LWP 3202)):
#0 0x7fd323d154bf in __GI___poll (fds=0x7fd1415fe6c0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fd3249
Link to bug on the proxmox side:
https://bugzilla.proxmox.com/show_bug.cgi?id=2781
** Bug watch added: bugzilla.proxmox.com/ #2781
https://bugzilla.proxmox.com/show_bug.cgi?id=2781
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Following reports on Proxmox forums, this is still very much seen by
multiple users with no known workaround.
I was able to run QEMU 5.0.13 (Debian) with all traces turned on and
capture the following:
- Behavior is reproducible by unbinding usb device on the host (ex. "echo '1-8'
> /sys/bus/usb
