From: "Annie.li" <annie.li@oracle.com>
To: qemu-devel@nongnu.org, jusual@redhat.com
Cc: ani@anisinha.ca, "imammedo@redhat.com" <imammedo@redhat.com>
Subject: Re: Failure of hot plugging secondary virtio_blk into q35 Windows 2019
Date: Mon, 8 Nov 2021 17:56:45 -0500 [thread overview]
Message-ID: <4be352af-f3fc-0ef3-1d97-cd3eafbbb98f@oracle.com> (raw)
In-Reply-To: <31c8012c-234f-2bb8-7db2-f7fee7bd311f@oracle.com>
Update:
I've tested q35 guest w/o OVMF, the APCI PCI hot-plugging works well in
q35 guest. Seems this issue only happens in q35 guest w/ OVMF.
Looks that there is already a bug filed against this hotplug issue in
q35 guest w/ OVMF,
https://bugzilla.redhat.com/show_bug.cgi?id=2004829
In this bug, it is recommended to add "-global
ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off \" on qemu command for
6.1. However, with this option for 6.1(PCIe native hotplug), there still
are kinds of issues. For example, one of them is the deleted virtio_blk
device still shows in the Device Manager in Windows q35 guest, the
operation of re-scanning new hardware takes forever there. This means
both PCIe native hotplug and ACPI hotplug all have issues in q35 guests.
Per comments in this bug, changes in both OVMF and QEMU are necessary to
support ACPI hot plug in q35 guest. The fixes may likely be available in
QEMU 6.2.0. I am wondering if someone is already working on this?
Thanks
Annie
next prev parent reply other threads:[~2021-11-08 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 14:06 Failure of hot plugging secondary virtio_blk into q35 Windows 2019 Annie.li
2021-11-08 18:53 ` Annie.li
2021-11-08 22:56 ` Annie.li [this message]
2021-11-09 7:11 ` Ani Sinha
2021-11-09 9:52 ` Daniel P. Berrangé
2021-11-09 11:10 ` Ani Sinha
2021-11-09 11:19 ` Daniel P. Berrangé
2021-11-09 17:01 ` Annie.li
2021-11-09 18:32 ` Daniel P. Berrangé
2021-11-10 18:12 ` Annie.li
2021-11-19 21:29 ` Annie.li
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=4be352af-f3fc-0ef3-1d97-cd3eafbbb98f@oracle.com \
--to=annie.li@oracle.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=jusual@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).