diff for duplicates of <20210526054632-mutt-send-email-mst@kernel.org>
diff --git a/a/1.txt b/N1/1.txt
index 171893f..9d8d23c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -41,4 +41,80 @@ On Mon, Apr 19, 2021 at 04:30:23PM +0200, Laurent Vivier wrote:
> (ot choose a machine type earlier than 5.2)
>
> Thanks,
-> Laurent
\ No newline at end of file
+> Laurent
+
+--
+You received this bug notification because you are a member of qemu-
+devel-ml, which is subscribed to QEMU.
+https://bugs.launchpad.net/bugs/1924912
+
+Title:
+ VirtIO drivers don't work on Windows: "GLib: Too many handles to wait
+ for!" crash
+
+Status in QEMU:
+ Fix Released
+
+Bug description:
+ I ran SerenityOS <https://github.com/SerenityOS/serenity> out of WSL2
+ with native Windows QEMU. The system runs fine on the Linux QEMU (with
+ Windows X-Server). However, with Windows QEMU I get a hard crash after
+ the following output:
+
+ ```
+ [#0 colonel(0:0)]: Scheduler[0]: idle loop running
+ [init_stage2(2:2)]: PCI [0000:00:00:00] PCI::ID [8086:1237]
+ [init_stage2(2:2)]: PCI [0000:00:01:00] PCI::ID [8086:7000]
+ [init_stage2(2:2)]: PCI [0000:00:01:01] PCI::ID [8086:7010]
+ [init_stage2(2:2)]: PCI [0000:00:01:02] PCI::ID [8086:7020]
+ [init_stage2(2:2)]: PCI [0000:00:01:03] PCI::ID [8086:7113]
+ [init_stage2(2:2)]: PCI [0000:00:02:00] PCI::ID [1234:1111]
+ [init_stage2(2:2)]: PCI [0000:00:03:00] PCI::ID [8086:2922]
+ [init_stage2(2:2)]: PCI [0000:00:04:00] PCI::ID [1af4:1003]
+ [init_stage2(2:2)]: PCI [0000:00:05:00] PCI::ID [1af4:1005]
+ [init_stage2(2:2)]: PCI [0000:00:06:00] PCI::ID [8086:100e]
+ [#0 init_stage2(2:2)]: BXVGA: framebuffer @ P0xf8000000
+ [#0 init_stage2(2:2)]: BXVGADevice resolution set to 1024x768 (pitch=4096)
+ [init_stage2(2:2)]: UHCI: Controller found PCI::ID [8086:7020] @ PCI [0000:00:01:02]
+ [init_stage2(2:2)]: UHCI: I/O base IO c080
+ [init_stage2(2:2)]: UHCI: Interrupt line: 11
+ [#0 init_stage2(2:2)]: UHCI: Allocated framelist at physical address P0x00e40000
+ [#0 init_stage2(2:2)]: UHCI: Framelist is at virtual address V0xc115d000
+ [#0 init_stage2(2:2)]: UHCI: QH(0xc115f000) @ 14946304: link_ptr=14946338, element_link_ptr=1
+ [#0 init_stage2(2:2)]: UHCI: QH(0xc115f020) @ 14946336: link_ptr=14946370, element_link_ptr=1
+ [#0 init_stage2(2:2)]: UHCI: QH(0xc115f040) @ 14946368: link_ptr=14946402, element_link_ptr=1
+ [#0 init_stage2(2:2)]: UHCI: QH(0xc115f060) @ 14946400: link_ptr=14946434, element_link_ptr=1
+ [#0 init_stage2(2:2)]: UHCI: QH(0xc115f080) @ 14946432: link_ptr=14958593, element_link_ptr=1
+ [#0 init_stage2(2:2)]: UHCI: Reset completed
+ [#0 init_stage2(2:2)]: UHCI: Started
+ [#0 init_stage2(2:2)]: DMIExpose: SMBIOS 32bit Entry point @ P0x000f5870
+ [#0 init_stage2(2:2)]: DMIExpose: Data table @ P0x000f5890
+ [#0 init_stage2(2:2)]: VirtIOConsole: Found @ PCI [0000:00:04:00]
+ [#0 init_stage2(2:2)]: Trying to unregister unused handler (?)
+ [#0 init_stage2(2:2)]: VirtIOConsole: Multi port is not yet supported!
+ [#0 init_stage2(2:2)]: VirtIOConsole: cols: 0, rows: 0, max nr ports 0
+ qemu-system-i386.exe: warning: GLib: Too many handles to wait for!
+ ```
+
+ The lines starting with [ are SerenityOS output; QEMU warns "GLib: Too
+ many handles to wait for!" and crashes right after (can't even Ctrl-C
+ in the WSL command line, force-close in Windows necessary). A window
+ is still spawned but as the OS already switched out of text mode, just
+ a black screen is visible as QEMU crashes.
+
+ I first thought this to be an issue with SerenityOS and reported it
+ over there: <https://github.com/SerenityOS/serenity/issues/6422>. The
+ kernel devs pointed out that this seems to be a VirtIO driver/device
+ issue on the Windows build of QEMU, because the Serenity kernel tries
+ to initialize VirtIO devices which apparently crashes QEMU. There will
+ be mitigations from the SerenityOS side (by allowing to disable VirtIO
+ on boot) but it would of course be great if QEMU handled this
+ properly.
+
+ Version info: Both QEMU 6.0.0-rc3 and 5.2.0 exhibit this issue.
+ Windows release is 20H2, WSL2 is running Debian 10.9. SerenityOS has
+ no proper version but it was reproduced on the most current commits as
+ of 18/04/2021.
+
+To manage notifications about this bug go to:
+https://bugs.launchpad.net/qemu/+bug/1924912/+subscriptions
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index 132970f..28b7d4f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,31 +1,20 @@
[
"ref\000161875180735.23175.14682430598239905387.malonedeb\@wampee.canonical.com\0"
]
-[
- "ref\000161875645795.6320.1996793877758730269.malone\@soybean.canonical.com\0"
-]
-[
- "ref\0009bb9996e-d7ac-44c5-2fd3-13f2a4d1c802\@weilnetz.de\0"
-]
[
"ref\0b48d2719-d334-2c16-be32-f3df52d415c7\@vivier.eu\0"
]
[
- "From\0Michael S. Tsirkin <mst\@redhat.com>\0"
+ "From\0mst <1924912\@bugs.launchpad.net>\0"
]
[
"Subject\0Re: [Bug 1924912] VirtIO drivers don't work on Windows: \"GLib: Too many handles to wait for!\" crash\0"
]
[
- "Date\0Wed, 26 May 2021 05:47:59 -0400\0"
+ "Date\0Wed, 26 May 2021 09:47:59 -0000\0"
]
[
- "To\0Laurent Vivier <laurent\@vivier.eu>\0"
-]
-[
- "Cc\0Stefan Weil <sw\@weilnetz.de>",
- " Bug 1924912 <1924912\@bugs.launchpad.net>",
- " qemu-devel\@nongnu.org\0"
+ "To\0qemu-devel\@nongnu.org\0"
]
[
"\0000:1\0"
@@ -77,7 +66,83 @@
"> (ot choose a machine type earlier than 5.2)\n",
"> \n",
"> Thanks,\n",
- "> Laurent"
+ "> Laurent\n",
+ "\n",
+ "-- \n",
+ "You received this bug notification because you are a member of qemu-\n",
+ "devel-ml, which is subscribed to QEMU.\n",
+ "https://bugs.launchpad.net/bugs/1924912\n",
+ "\n",
+ "Title:\n",
+ " VirtIO drivers don't work on Windows: \"GLib: Too many handles to wait\n",
+ " for!\" crash\n",
+ "\n",
+ "Status in QEMU:\n",
+ " Fix Released\n",
+ "\n",
+ "Bug description:\n",
+ " I ran SerenityOS <https://github.com/SerenityOS/serenity> out of WSL2\n",
+ " with native Windows QEMU. The system runs fine on the Linux QEMU (with\n",
+ " Windows X-Server). However, with Windows QEMU I get a hard crash after\n",
+ " the following output:\n",
+ "\n",
+ " ```\n",
+ " [#0 colonel(0:0)]: Scheduler[0]: idle loop running\n",
+ " [init_stage2(2:2)]: PCI [0000:00:00:00] PCI::ID [8086:1237]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:01:00] PCI::ID [8086:7000]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:01:01] PCI::ID [8086:7010]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:01:02] PCI::ID [8086:7020]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:01:03] PCI::ID [8086:7113]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:02:00] PCI::ID [1234:1111]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:03:00] PCI::ID [8086:2922]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:04:00] PCI::ID [1af4:1003]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:05:00] PCI::ID [1af4:1005]\n",
+ " [init_stage2(2:2)]: PCI [0000:00:06:00] PCI::ID [8086:100e]\n",
+ " [#0 init_stage2(2:2)]: BXVGA: framebuffer \@ P0xf8000000\n",
+ " [#0 init_stage2(2:2)]: BXVGADevice resolution set to 1024x768 (pitch=4096)\n",
+ " [init_stage2(2:2)]: UHCI: Controller found PCI::ID [8086:7020] \@ PCI [0000:00:01:02]\n",
+ " [init_stage2(2:2)]: UHCI: I/O base IO c080\n",
+ " [init_stage2(2:2)]: UHCI: Interrupt line: 11\n",
+ " [#0 init_stage2(2:2)]: UHCI: Allocated framelist at physical address P0x00e40000\n",
+ " [#0 init_stage2(2:2)]: UHCI: Framelist is at virtual address V0xc115d000\n",
+ " [#0 init_stage2(2:2)]: UHCI: QH(0xc115f000) \@ 14946304: link_ptr=14946338, element_link_ptr=1\n",
+ " [#0 init_stage2(2:2)]: UHCI: QH(0xc115f020) \@ 14946336: link_ptr=14946370, element_link_ptr=1\n",
+ " [#0 init_stage2(2:2)]: UHCI: QH(0xc115f040) \@ 14946368: link_ptr=14946402, element_link_ptr=1\n",
+ " [#0 init_stage2(2:2)]: UHCI: QH(0xc115f060) \@ 14946400: link_ptr=14946434, element_link_ptr=1\n",
+ " [#0 init_stage2(2:2)]: UHCI: QH(0xc115f080) \@ 14946432: link_ptr=14958593, element_link_ptr=1\n",
+ " [#0 init_stage2(2:2)]: UHCI: Reset completed\n",
+ " [#0 init_stage2(2:2)]: UHCI: Started\n",
+ " [#0 init_stage2(2:2)]: DMIExpose: SMBIOS 32bit Entry point \@ P0x000f5870\n",
+ " [#0 init_stage2(2:2)]: DMIExpose: Data table \@ P0x000f5890\n",
+ " [#0 init_stage2(2:2)]: VirtIOConsole: Found \@ PCI [0000:00:04:00]\n",
+ " [#0 init_stage2(2:2)]: Trying to unregister unused handler (?)\n",
+ " [#0 init_stage2(2:2)]: VirtIOConsole: Multi port is not yet supported!\n",
+ " [#0 init_stage2(2:2)]: VirtIOConsole: cols: 0, rows: 0, max nr ports 0\n",
+ " qemu-system-i386.exe: warning: GLib: Too many handles to wait for!\n",
+ " ```\n",
+ "\n",
+ " The lines starting with [ are SerenityOS output; QEMU warns \"GLib: Too\n",
+ " many handles to wait for!\" and crashes right after (can't even Ctrl-C\n",
+ " in the WSL command line, force-close in Windows necessary). A window\n",
+ " is still spawned but as the OS already switched out of text mode, just\n",
+ " a black screen is visible as QEMU crashes.\n",
+ "\n",
+ " I first thought this to be an issue with SerenityOS and reported it\n",
+ " over there: <https://github.com/SerenityOS/serenity/issues/6422>. The\n",
+ " kernel devs pointed out that this seems to be a VirtIO driver/device\n",
+ " issue on the Windows build of QEMU, because the Serenity kernel tries\n",
+ " to initialize VirtIO devices which apparently crashes QEMU. There will\n",
+ " be mitigations from the SerenityOS side (by allowing to disable VirtIO\n",
+ " on boot) but it would of course be great if QEMU handled this\n",
+ " properly.\n",
+ "\n",
+ " Version info: Both QEMU 6.0.0-rc3 and 5.2.0 exhibit this issue.\n",
+ " Windows release is 20H2, WSL2 is running Debian 10.9. SerenityOS has\n",
+ " no proper version but it was reproduced on the most current commits as\n",
+ " of 18/04/2021.\n",
+ "\n",
+ "To manage notifications about this bug go to:\n",
+ "https://bugs.launchpad.net/qemu/+bug/1924912/+subscriptions"
]
-0c296fb79998cf826f54dae04bd1d3357396f5c0f02142dfb878da01f9ba18a2
+6f6aa63858bf1ce4922a1a680bae434042fce9915a163b2373ecf59c4c03c7d9
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).