From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Remy Noel <remy.noel@shadow.tech>
Cc: Maxim Levitsky <mlevitsk@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: Strange qemu6 regression cauing disabled usb controller.
Date: Thu, 30 Sep 2021 16:05:52 +0100 [thread overview]
Message-ID: <YVXSUExueN0MpEDG@redhat.com> (raw)
In-Reply-To: <20210930134844.f4kh72vpeknr2vmk@gmail.com>
On Thu, Sep 30, 2021 at 03:48:44PM +0200, Remy Noel wrote:
> Hello,
>
> I'm encountering a nagging issue with usbredir and a windows guest, but although I did pinpoint the commit that caused the issue, I have a hard time understanding it.
>
> The issue occurs when a two usbredir devices are added to a guest windows vm. When the second device is added, the UHCI usb controller is disabled by windows with an error code 43 (can be seen with in the usb adapters section of the device manager).
>
> The commit causing the issue (everything works well when reverting it) is 7bed89958bfbf40df9ca681cefbdca63abdde39d : device_core: use drain_call_rcu in in qmp_device_add.
Co-incidentally we've just had another bug report filed today that
suggests 7bed89958bfbf40df9ca681cefbdca63abdde39d as a buggy commit
causing deadlock in QEMU
https://gitlab.com/qemu-project/qemu/-/issues/650
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-09-30 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 13:48 Strange qemu6 regression cauing disabled usb controller Remy Noel
2021-09-30 15:05 ` Daniel P. Berrangé [this message]
2021-09-30 15:15 ` Remy Noel
2021-10-05 7:46 ` Remy Noel
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=YVXSUExueN0MpEDG@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=remy.noel@shadow.tech \
/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).