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.

+++ This bug was initially created as a clone of Bug #1660711 +++

Description of problem:
The cpu model fallback changed after restart libvirtd

Version-Release number of selected component (if applicable):
# rpm -q qemu-kvm libvirt
qemu-kvm-2.12.0-44.module+el8+2259+6d80f0a6.ppc64le
libvirt-4.5.0-14.module+el8+2210+474b8474.ppc64le

How reproducible:
100%

Steps to Reproduce:
1.
Prepare a guest with the cpu model element.
<cpu mode='host-model' check='partial'>
    <model fallback='forbid'>power9</model>
</cpu>
2.
Start the guest and check the guest xml
virsh start test
virsh dumpxml test
The fallback is forbid now
3.
Restart libvirtd and check the guest xml
systemctl restart libvirtd
virsh dumpxml test
The fallback is changed to allow now

Actual results:
The fallback is changed

Expected results:
The fallback should not be changed

Additional info:
Could  be reproduced on POWER8/9, could not be reproduced on x86_64

Reproduce with libvirt-4.5.0-12.virtcov.el7.ppc64le in RHEL-7.7

Lets deal with this in next major version.