-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
None
-
In Progress
-
Known Issue
-
-
None
-
None
-
None
-
None
[Note that this is more of a tracking issue for OCP Virt doc purposes. The original issue is : RHEL-79805 ]
Description of problem:
When we create a VM using bootable disks (container disk images) of rhel8 or rhel9 for s390x arch using OCPVirt, we are seeing Call Traces on VM Console related to virtio_balloon as in attached screenshot
The call trace message is appearing once in every ~120s. When we disabled the same with below command, we don't see the issue even waiting for 30mins.
echo "blacklist virtio_balloon" > /etc/modprobe.d/virtio_balloon.conf
dracut -f
reboot
MemoryBallooning is by default enabled in kubevirt for every vm created. In the VM spec we disabled this using a parameter. autoattachMemBalloon set to false. This way also made Call traces to NOT appear.
spec:
architecture: s390x
domain:
devices:
autoattachMemBalloon: false
The bootable images I'm referring are obtained from https://catalog.redhat.com/search?gs&q=rhel-guest-image
Additional info:
These traces are not seen in cases:VM created with rhel x86 bootable disk image.VM created with fedora s390x bootable disk images.VM created with rhel9.5 s390x qcow2 image using qemu-kvm command directly.