[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1820247
Title:
QEMU random
** Bug watch removed: Red Hat Bugzilla #980714
https://bugzilla.redhat.com/show_bug.cgi?id=980714
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1820247
Title:
QEMU random crash caused by libspic
The QEMU project is currently considering to move 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 you still think this bug report here is valid, then please switch the
Hi,
the warnings around "duplicate channel type 2 id 0" where present in the other
bug as well.
And since that often means it passes the same area of code I wanted to suggest
to provide the same debug data.
The actual crash is a different one for sure as the stack traces look
different and also
Hi Christian,
thanks for reply, chmmm, what makes you think there are similarities? To me
it looks like a different problem.
Regards,
Premysl
On Mon, Mar 18, 2019 at 8:15 AM Christian Ehrhardt <
1820...@bugs.launchpad.net> wrote:
> Hi Premysl,
> this has similarities to [1] which was fixed l
Hi Premysl,
this has similarities to [1] which was fixed long ago.
In case it is reproducible for you - as it was asked back then - it might be
helpful attaching SPICE_DEBUG=1 log, using remote-viewer.
And if reproducible in general also worth a quick check to try with the
latest qemu version whi
