From: Stefan Weil <sw@weilnetz.de>
To: Bug 1924912 <1924912@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Bug 1924912] VirtIO drivers don't work on Windows: "GLib: Too many handles to wait for!" crash
Date: Mon, 19 Apr 2021 17:28:32 +0200 [thread overview]
Message-ID: <1198818a-4e33-e230-9e4d-7e1926900383@weilnetz.de> (raw)
In-Reply-To: <b48d2719-d334-2c16-be32-f3df52d415c7@vivier.eu>
Am 19.04.21 um 16:30 schrieb Laurent Vivier:
> Le 19/04/2021 à 12:39, Stefan Weil a écrit :
>> I can confirm the issue also with latest official QEMU sources.
>>
>> Related issue URLs:
>>
>> https://github.com/tesseract-ocr/tesseract/issues/2838
>>
>> 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?
> Could it be related to the number of file descriptors that can differ
> between linux an windows?
>
> We have a series of patches that sets the number of queues to the number
> of vCPU:
>
> a4eef0711b2c vhost-user-blk-pci: default num_queues to -smp N
> 9445e1e15e66 virtio-blk-pci: default num_queues to -smp N
> 6a558822849f virtio-scsi-pci: default num_queues to -smp N
> 4e5163bd8444 virtio-scsi: introduce a constant for fixed virtqueues
> 1436f32a84c3 virtio-pci: add virtio_pci_optimal_num_queues() helper
>
> And I think it can have inpact on the number of open file descriptors.
>
> You can try by specifiying "num_queues=1" with the virtio interfaces on the QEMU command line.
> (ot choose a machine type earlier than 5.2)
>
> Thanks,
> Laurent
I tried different machine types. That did not help.
The full command line which did not work was this one:
qemu-system-i386 -s -m 512M -cpu max -d guest_errors -smp 2 -device
VGA,vgamem_mb=64 -drive file=_disk_image,format=raw,index=0,media=disk
-device ich9-ahci -usb -device virtio-serial -chardev
stdio,id=stdout,mux=on -device virtconsole,chardev=stdout -device
isa-debugcon,chardev=stdout -device virtio-rng-pci -soundhw pcspk
-device sb16 -netdev
user,id=breh,hostfwd=tcp:127.0.0.1:8888-10.0.2.15:8888,hostfwd=tcp:127.0.0.1:8823-10.0.2.15:23,hostfwd=tcp:127.0.0.1:8000-10.0.2.15:8000,hostfwd=tcp:127.0.0.1:2222-10.0.2.15:22
-device e1000,netdev=breh -kernel Kernel/Kernel -append hello
QEMU works nicely when I remove "-device virtio-serial" and "-device
virtconsole,chardev=stdout" from that command line. How would I have to
modify those arguments to limit the number of queues?
Thanks,
Stefan
next prev parent reply other threads:[~2021-04-19 15:29 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
2021-04-19 14:30 ` Laurent Vivier
2021-04-19 14:30 ` Laurent Vivier
2021-04-19 15:28 ` Stefan Weil [this message]
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=1198818a-4e33-e230-9e4d-7e1926900383@weilnetz.de \
--to=sw@weilnetz.de \
--cc=1924912@bugs.launchpad.net \
--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).