Verified:
ovirt-engine-4.4.10.2-0.1.el8ev
vdsm-4.40.90.4-1.el8ev.x86_64
qemu-kvm-6.0.0-33.module+el8.5.0+13041+05be2dc6.x86_64
libvirt-daemon-7.6.0-6.module+el8.5.0+13051+7ddbe958.x86_64
Verification scenario:
1. Create VM with VFIO and 16 total virtual CPUs (1 socket and 16 cores per socket)
2. Run VM and verify VM is running.
3. Observe VM xml and verify caching=on:
<iommu model="intel">
<driver caching_mode="on" eim="on" intremap="on" />
</iommu>
4. Repeat steps 1-3, this time use 24 CPus and 32 CPUs.
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 (RHV Manager (ovirt-engine) [ovirt-4.4.10]), 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/RHBA-2022:0461
Verified: ovirt-engine-4.4.10.2-0.1.el8ev vdsm-4.40.90.4-1.el8ev.x86_64 qemu-kvm-6.0.0-33.module+el8.5.0+13041+05be2dc6.x86_64 libvirt-daemon-7.6.0-6.module+el8.5.0+13051+7ddbe958.x86_64 Verification scenario: 1. Create VM with VFIO and 16 total virtual CPUs (1 socket and 16 cores per socket) 2. Run VM and verify VM is running. 3. Observe VM xml and verify caching=on: <iommu model="intel"> <driver caching_mode="on" eim="on" intremap="on" /> </iommu> 4. Repeat steps 1-3, this time use 24 CPus and 32 CPUs.