Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 is the RHEL8 version of BZ2225347

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/getting-started-with-virtualization-in-rhel-8_configuring-and-managing-virtualization#assembly_creating-virtual-machines_virt-getting-started

Section Number and Name: 
2.2. Creating virtual machines

Describe the issue: 

Assume the following scenario:

Host OS:  RHEL9, supports CPU models X Y Z from Vendor A
Guest OS: RHEL7, only supports CPU models X and Y from Vendor A

If the hardware has model Z (assume a newer model released after hardware enablement for RHEL7 finished), it is possible to configure the VM with a cpu-model of Z, or with host-model or passthrough, all of which will expose CPU features to the Guest OS that its OS may not be able to handle properly. This is not tested, and may produce undesired results.

Suggestions for improvement: 

Document that the Guest OS version must also support the CPU model and features defined in the Guest XML, when creating/editing a VM, not just the Host OS.

Certified CPUs by RHEL version can be found at https://catalog.redhat.com/hardware/search?type=Component|CPU%20Collection&p=1