Comment 1 for bug 2033193

Thanks for the report.
Given the versions the only affected release i Jammy and =>Lunar are already Fixed.

The patches you referred:
- #1 & #2 got agreed
- #3 got challenged and not accepted (https://<email address hidden>/msg872376.html)
- neither of them ever landed upstream, they seem to only ever made it to the downstreams

By that I'm not as sure about "fixed in qemu 7.0". Maybe it went through a lot of changes and I couldn't spot it easily, since you mentioned "fixed in Qemu 7.0" do you have a pointer to the change that actually went into qemu 7.0?

I've spotted it in the downstream though:
https://git.centos.org/rpms/qemu-kvm/blob/24c15060b5a0a922f6472e49b2087ad174ffb63d/f/SOURCES/kvm-pci-expose-TYPE_XIO3130_DOWNSTREAM-name.patch
https://git.centos.org/rpms/qemu-kvm/blob/24c15060b5a0a922f6472e49b2087ad174ffb63d/f/SOURCES/kvm-acpi-pcihp-pcie-set-power-on-cap-on-parent-slot.patch

And I agree that there it was dropped in the move to 7.0 - but there was no reference by what it was replaced.

I have not hit the same issue in Jammy when migrating instances.
Therefore I think "can hit this bug currently when running OpenStack on top of Ubuntu 22.04" is a bit too generic.
Therefore a few questions that shall help with the later SRU [1] processing:
1. Is there any special device or anything else that you use to be exposed and see that issue?
2. How does your guest XML look like?
3. Bug https://bugzilla.redhat.com/show_bug.cgi?id=2053584 speaks of a virtio-serial-port, is that something you are using as well?
4. Is it then also a guest soft lockup or some other symptom for you?

Note: The upstream bug https://bugzilla.redhat.com/show_bug.cgi?id=2053584 has repro ideas that could be useful as well.

Further question, if one would - for trying - provide you with a PPA of jammy plus those fixes, could you easily test this in your environment?

[1]: https://wiki.ubuntu.com/StableReleaseUpdates