Re: Problem with vfs probe on Proxmox kernel

[Arkady <arkady dot miasnikov at gmail dot com>]

I am running
Systemtap translator/driver (version 2.9/0.165, Debian version
2.9-2ubuntu2 (xenial))
on
Linux ubuntu 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

and vfsread/vfswrite work fine.

On Thu, Jan 26, 2017 at 12:44 AM, Adam Guderski <a.guderski@gmail.com> wrote:
> Hello,
>
> I've got problem running sample traceio.stp script (obtained from
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/SystemTap_Beginners_Guide/#traceio2)
> on Proxmox VE 4.4 system. Proxmox is a Debian-based Linux distro which
> uses a custom Ubuntu-based kernel. The Proxmox repository does not
> provide a kernel with debug symbols, so I had to compile it from
> provided sources - version 4.4.35-2-pve, to be specific. Debian repos
> (jessie) provide systemtap in version 2.9, which from what I read does
> not support 4.4 kernels, so I compiled systemtap from sources (from
> master branch, version 3.1/0.159).
>
> With such setup, I'm able to run sample "hello world" stap script and
> couple of others, but all scripts with vfs probes fail. I attach full
> verbose (-vvv) output here: http://pastebin.com/DiWMsrtr, but I think
> the main error can be explained below. What can I do about it? I
> searched for couple of hours but did not find anything that would help.
>
> Best regards,
> Adam
>
>
> # stap -v traceio2.stp 0xfb00
> Pass 1: parsed user script and 119 library scripts using
> 71608virt/43716res/4464shr/39904data kb, in 140usr/0sys/132real ms.
> semantic error: while resolving probe point: identifier 'kernel' at
> /usr/local/share/systemtap/tapset/linux/vfs.stp:987:19
>         source: probe vfs.write = kernel.function("vfs_write")
>                                   ^
>
> semantic error: missing x86_64 kernel/module debuginfo [man
> warning::debuginfo] under '/lib/modules/4.4.35-2-pve/build'
>
> semantic error: resolution failed in alias expansion builder
>
> semantic error: while resolving probe point: identifier 'vfs' at
> traceio2.stp:14:7
>         source: probe vfs.write, vfs.read
>                       ^
>
> semantic error: no match
>
> semantic error: while resolving probe point: identifier 'kernel' at
> /usr/local/share/systemtap/tapset/linux/vfs.stp:915:18
>         source: probe vfs.read = kernel.function("vfs_read")
>                                  ^
>
> semantic error: missing x86_64 kernel/module debuginfo [man
> warning::debuginfo] under '/lib/modules/4.4.35-2-pve/build'
>
> semantic error: resolution failed in alias expansion builder
>
> semantic error: while resolving probe point: identifier 'vfs' at
> traceio2.stp:14:18
>         source: probe vfs.write, vfs.read
>                                  ^
>
> semantic error: no match
>
> Pass 2: analyzed script: 1 probe, 33 functions, 1 embed, 1 global using
> 72384virt/46080res/6016shr/40680data kb, in 40usr/100sys/146real ms.
> Pass 2: analysis failed.  [man error::pass2]