Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-51113

Tracking ENGCMP-5141: Getting Call Traces on VM console related to virtio_balloon for s390x RHEL container disk images

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.18.0
    • HyperShift
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • None
    • None
    • In Progress
    • Known Issue
    • Hide
      When you create a VM by using Red Hat Enterprise Linux (RHEL) container disk images for s390x architecture, call traces referencing virtio_balloon free page reporting print to the VM console. This is due to a kernel bug. (OCPBUGS-51113)
      As a workaround, disable memory ballooning for the VM by adding the following parameter to the VM YAML configuration: spec.domain.devices.autoattachMemBalloon: false.
      You can also disable free page reporting of memory ballooning for all new VMs. To do so, edit the HyperConverged CR and add the parameter spec.virtualMachineOptions.disableFreePageReporting: true.
      Show
      When you create a VM by using Red Hat Enterprise Linux (RHEL) container disk images for s390x architecture, call traces referencing virtio_balloon free page reporting print to the VM console. This is due to a kernel bug. ( OCPBUGS-51113 ) As a workaround, disable memory ballooning for the VM by adding the following parameter to the VM YAML configuration: spec.domain.devices.autoattachMemBalloon: false. You can also disable free page reporting of memory ballooning for all new VMs. To do so, edit the HyperConverged CR and add the parameter spec.virtualMachineOptions.disableFreePageReporting: true.
    • 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.

              ctomasko Catherine Tomasko
              cmerla Chandra Merla
              None
              None
              Yu Li Yu Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: