This reverts bug 1547502
verified on 4.3.0-0.5.alpha1.el7 POWER9 cluster level exist and work correctly with P9 machines
Michal, Reading the doc_text, here's what I understand: There's now support for running IBM POWER9 hosts on top of a virtual machine, where the virtual machine has RHEL-ALT as the OS and the CPU type for the virtual machine is POWER9. Is that right? Or should the text say one of the following: (1) This update adds support for virtual machines with a RHEL-ALT operating system and an IBM POWER9 or POWER8 virtual CPU on a host with a POWER9 CPU. It also adds support for live migration of virtual machines with POWER8 virtual CPUs between hosts with either POWER8 or POWER9 CPUs. OR, should it be: (2) This update adds support for virtual machines with a RHEL-ALT operating system and IBM POWER9 virtual CPU on a host with a POWER9 CPU. It also adds support for virtual machines with a POWER8 virtual CPU on a host with a POWER9 CPU. It also adds support for live migration of virtual machines with POWER8 virtual CPUs between hosts with either POWER8 or POWER9 CPUs.
no, sorry, there probably should have been a comma in that sentence. This update adds support for IBM POWER9 hypervisors on RHEL-ALT. RHEL-ALT is th ehost operating system. On POWER9 hypervisor we then support POWER9 VM guests (it may sound obvious but it's not that automatic on POWER. Tahts' why I also specifically mention POWER8 guests on POWER9 hosts) Hope it's more clear now and sorry for the confusion
What is a POWER9 hypervisor? Do you mean: This update adds support for bare-metal machines based on IBM POWER9 CPUs running hypervisors on the RHEL-ALT host operating system. These hypervisors can run virtual machines with POWER8 or POWER9 virtual CPUs. This update also adds support for live migration of virtual machines with POWER8 virtual CPUs between hosts based on either POWER8 or POWER9 CPUs.
if that's the phrasing we have elsewhere then yes, I think it's fine
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1046