What were you trying to do that didn't work?

Check the CPI with hypervisor bit

What is the impact of this issue to you?

the CPI didn't change as expected

Please provide the package NVR for which the bug is seen:

LPAR qemu version: qemu-kvm-10.1.0-5.el10.s390x

L1 qemu version: qemu-kvm-10.1.0-5.el10.s390x

kernel version: kernel-6.12.0-161.el10.s390x

libvirt version: libvirt-11.8.0-1.el10.s390x

How reproducible is this bug?:

100%

Steps to reproduce

1. Enable nested on host before boot L1 guest
2. rmmod kvm ; modprobe kvm nested=1
3. Check CPI in L1 guest
   1. # cat /sys/firmware/cpi/system_level
      1. 0x010a0200a1060c00
   2. Unknown macro: {"execute"}

      }

      1. {"return": 74874545529818112}

         which is 10a0200a1060c00 in hexadecimal byte

4. In guest load kvm module
5. rmmod kvm ; modprobe kvm nested=1
6. Check CPI in L1 guest
   1. [root@localhost ~]# cat /sys/firmware/cpi/system_level
      0x010a0200a1060c00
   2. reference to comment in https://issues.redhat.com/browse/RHEL-73008 the CPI should change to 0x110a0200a1060c00
7. Boot L2 guest on L1 guest and check CPI in L1

Expected results

the most significant bit should change to be 1 or something

Actual results

1. [root@localhost ~]# cat /sys/firmware/cpi/system_level
   0x010a0200a1060c00