RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When a VM with a hot plugged memory is suspended, then resumed and then the previously hot plugged memory is unplugged, the DIMM remains in the domain XML despite the memory is successfully removed from the guest OS.

Version-Release number of selected component (if applicable):

libvirt-daemon-7.10.0-1.module+el8.6.0+13502+4f24a11d.x86_64
qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949.x86_64
kernel-4.18.0-357.el8.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Start a VM.
2. Hot plug 256 MB memory to it.
3. Suspend the VM.
4. Resume the VM.
5. Hot unplug the previously unplugged memory.

Actual results:

The memory is unplugged from the guest OS but the domain XML keeps reporting the old amount of memory and the given DIMM is still present, even after a long time.

Expected results:

The memory is unplugged from the guest OS and is removed from the domain XML.

Additional info:

This is apparently a regression, started being observed after a recent update to QEMU 6.2. It happens in RHV/oVirt environments.

*** This bug has been marked as a duplicate of bug 2035237 ***

All hot-unplug of devices which were cold-plugged is broken.