Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-143372

[Dual Kernel Validation] qemu-trace-stap reports Systemtap parsing error

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-9.8, rhel-10.2
    • systemtap
    • None
    • Low
    • rhel-pt-perf-tools
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

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

      In a dual kernel environment, i.e. RHEL 9.8 userspace and RHEL 10.2 kernel, on a RHEL VM live migration scenario, if the qemu-trace-stap tool is invoked to gather how much data is left or has been transferred a parsing error is obtaining from Systemtap.

      parse error: expected literal string or number
              saw: operator '*' at /usr/share/systemtap/tapset/libvirt_probes-64.stp:204:3
          source:   *cert = user_string($arg4);
      

      Furthermore, next victim is gcc, which also reports some unrecognized command options, likely due to previous parsing error.

      gcc: error: unrecognized command-line option '-ftrivial-auto-var-init=zero'
      gcc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
      make[1]: *** [scripts/Makefile.build:229: /tmp/stappm7mGi/stap_6ab018d768302cf40efc883f6a4dcd18_3054_src.o] Error 1
      make: *** [Makefile:1994: /tmp/stapVBsTTW] Error 2
      WARNING: kbuild exited with status: 2
      Pass 4: compilation failed.  [man error::pass4]
      Kernel version 6.12.0 is within tested range 3.10 ... 6.18-rc

      While this is probably expected due to this particular environment setup, we want to track it and get some feedback/advice if possible

      What is the impact of this issue to you?

      In a dual kernel environment I am not able to use qemu-trace-stap tool

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

      RHEL 9.8 kernel
      kernel-5.14.0-661.el9.x86_64

      RHEL 10.2 kernel
      kernel-6.12.0-183.el10.x86_64

      qemu-kvm-10.1.0-11.el9.x86_64
      libvirt-11.10.0-3.el9.x86_64
      systemtap-runtime-5.4-4.el9.x86_64
      gcc-11.5.0-14.el9.x86_64

      VM
      RHEL 9.8

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1. Install RHEL 10.2 kernel on top of RHEL 9.8 userspace environment
      2. Boot up a VM using QEMU
      3. Execute qemu-trace-stap with some options, e.g.
      qemu-trace-stap run --pid=$(pidof qemu-kvm) /usr/libexec/qemu-kvm migrate_pending_exact

      Expected results

      Not sure Probably it's expected but we want to get confirmation.

      Actual results

      Systemtap complains and throws a parsing unhandled error

              rhtorsys Frank Eigler
              mcasquer@redhat.com Mario Casquero
              Frank Eigler Frank Eigler
              Martin Cermak Martin Cermak
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: