[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failure of hot plugging secondary virtio_blk into q35 Windows 2019

From: Annie.li
Subject: Re: Failure of hot plugging secondary virtio_blk into q35 Windows 2019
Date: Tue, 9 Nov 2021 12:01:30 -0500
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0

On 11/9/2021 6:19 AM, Daniel P. Berrangé wrote:
On Tue, Nov 09, 2021 at 04:40:10PM +0530, Ani Sinha wrote:
On Tue, Nov 9, 2021 at 3:23 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
On Tue, Nov 09, 2021 at 12:41:39PM +0530, Ani Sinha wrote:

On Mon, 8 Nov 2021, Annie.li wrote:


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,


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.
This is sad.

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
So we are in soft code freeze for 6.2:

I am curious about Gerd's comment #10:
"The 6.2 rebase should make hotplug work
again with the default configuration."

Sadly I have not seen any public discussion on what we want to do
for the issues with acpi hotplug for bridges in q35.
I've raised one of the problems a week ago and there's a promised

  is the same as

isn't it?
Yes, one upstream, one downstream.

Thanks for the info.

So q35 guests with either OVMF or SeaBIOS have different ACPI hotplug issues in QEMU 6.1.

As Ani mentioned earlier, QEMU 6.2 is in soft code freeze.
Today(Nov 9) is the date of hard feature freeze.

I suppose this means the fix for the issue with SeaBIOS or the feature to cooperate
with the coming change in OVMF won't happen in 6.2?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]