From: Stefan Weil <sw@weilnetz.de>
To: Bug 1924912 <1924912@bugs.launchpad.net>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Bug 1924912] VirtIO drivers don't work on Windows: "GLib: Too many handles to wait for!" crash
Date: Mon, 19 Apr 2021 13:30:41 +0200 [thread overview]
Message-ID: <6bbbd9be-487f-ba46-5a96-f58533af4d63@weilnetz.de> (raw)
In-Reply-To: <9bb9996e-d7ac-44c5-2fd3-13f2a4d1c802@weilnetz.de>
Am 19.04.21 um 12:39 schrieb Stefan Weil:
> I can confirm the issue also with latest official QEMU sources.
>
> Related issue URLs:
>
> https://github.com/tesseract-ocr/tesseract/issues/2838
Sorry, that URL was a copy+paste error. The correct one is
https://github.com/SerenityOS/serenity/issues/6422.
>
> https://bugs.launchpad.net/qemu/+bug/1924912
>
> Instructions and files required to reproduce the issue:
>
> https://qemu.weilnetz.de/test/bugs/1924912/
>
> Michael, Laurent, maybe you have an idea how to narrow down this issue?
>
> Regards
>
> Stefan
>
>
>
next prev parent reply other threads:[~2021-04-19 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 13:16 [Bug 1924912] [NEW] VirtIO drivers don't work on Windows: "GLib: Too many handles to wait for!" crash kleines Filmröllchen
2021-04-18 13:35 ` [Bug 1924912] " Stefan Weil
2021-04-18 14:34 ` kleines Filmröllchen
2021-04-19 10:39 ` [Bug 1924912] " Stefan Weil
2021-04-19 11:30 ` Stefan Weil [this message]
2021-04-19 14:30 ` Laurent Vivier
2021-04-19 14:30 ` Laurent Vivier
2021-04-19 15:28 ` Stefan Weil
2021-05-26 9:47 ` Michael S. Tsirkin
2021-05-26 9:47 ` mst
2021-05-26 10:16 ` Laurent Vivier
2021-04-19 14:30 ` [Bug 1924912] " Laurent Vivier
2021-05-15 11:20 ` Thomas Huth
2021-05-17 14:56 ` kleines Filmröllchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bbbd9be-487f-ba46-5a96-f58533af4d63@weilnetz.de \
--to=sw@weilnetz.de \
--cc=1924912@bugs.launchpad.net \
--cc=laurent@vivier.eu \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).