Description of problem: tests/vmi_configuration_test.go:2950 the virtlogd process is taking too much RAM! (17468Ki > 17Mi). All processes: &map[libvirtd:{{28876800 0} {<nil>} BinarySI} qemu-kvm:{{454934528 0} {<nil>} BinarySI} virt-launcher:{{61800448 0} {<nil>} BinarySI} virt-launcher-monitor:{{19357696 0} {<nil>} BinarySI} virtlogd:{{17887232 0} {<nil>} 17468Ki BinarySI}] Expected <int>: 1 to equal <int>: -1 tests/vmi_configuration_test.go:3000 Version-Release number of selected component (if applicable): 4.11 How reproducible: Sometimes Steps to Reproduce: 1. Run a VM 2. 3. Actual results: Expected results: Additional info:
Verified on v4.12.0-548 - all processes below the limits: virt-launcher-monitor - 18Mb (limit - 25Mb) virt-launcher - 62Mb (limit 100Mb) virtlogd - 17.5Mb (limit 18Mb) libvirtd - 28.5Mb (limit 35Mb)
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 (Important: OpenShift Virtualization 4.12.0 Images security update), 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-2023:0408