Unable to insert sysdig_probe module on KVM kernel

Bug #1766565 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Invalid
Undecided
Sean Feole
linux-kvm (Ubuntu)
Invalid
Undecided
Unassigned
sysdig (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The sysdig-dkms module cannot be installed on the B-KVM kernel once before (bug 1764693), but now the installation works since 4.15.0-1007

However, when you try to insert the module, it will complain about:
$ sudo modprobe sysdig-probe
modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, or unknown parameter (see dmesg)

Log in dmesg:
[ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel.
[ 1989.967924] sysdig_probe: module verification failed: signature and/or required key missing - tainting kernel
[ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 0)
[ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0)
[ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7
ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17
Uname: Linux 4.15.0-1007-kvm x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Tue Apr 24 11:31:08 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue only happens on the KVM kernel, Bionic generic works fine with it.

Po-Hsu Lin (cypressyew)
description: updated
Po-Hsu Lin (cypressyew)
summary: - Unable to insert sysdig_probe module on B-KVM kernel
+ Unable to insert sysdig_probe module on KVM kernel
tags: added: cosmic
Po-Hsu Lin (cypressyew)
tags: added: linux-kvm ubuntu-sysdig-smoke-test
tags: added: sru-20190603
Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: New → Confirmed
Sean Feole (sfeole)
Changed in ubuntu-kernel-tests:
status: Confirmed → In Progress
assignee: nobody → Sean Feole (sfeole)
Po-Hsu Lin (cypressyew)
tags: added: sru-2019-0722
tags: added: sru-20190722
removed: sru-2019-0722
Revision history for this message
Sean Feole (sfeole) wrote :

I do not see this occuring anymore on bionic / linux-kvm 4.15.0-1043.43

Revision history for this message
Sean Feole (sfeole) wrote :

latest run of ubuntu_sysdig the module now installs properly as expected, the test itself still fails due to raw data can't be found for the initial test

Revision history for this message
Sean Feole (sfeole) wrote :
Download full text (4.8 KiB)

08/29 11:20:26 DEBUG| utils:0153| [stdout] == sysdig smoke test to trace dd, cat, read and writes ==
08/29 11:20:26 DEBUG| utils:0153| [stdout] Limiting raw capture file to 16384 blocks
08/29 11:20:26 DEBUG| utils:0153| [stdout] Try 1 of 10
08/29 11:21:13 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:21:21 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:21:21 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:21:21 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:21:21 DEBUG| utils:0153| [stdout] Try 2 of 10
08/29 11:22:08 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:22:16 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:22:16 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:22:16 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:22:16 DEBUG| utils:0153| [stdout] Try 3 of 10
08/29 11:23:03 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:23:12 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:23:12 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:23:12 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:23:12 DEBUG| utils:0153| [stdout] Try 4 of 10
08/29 11:23:59 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:24:06 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:24:06 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:24:06 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:24:06 DEBUG| utils:0153| [stdout] Try 5 of 10
08/29 11:24:53 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:25:01 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:25:01 DEBUG| utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:25:01 DEBUG| utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:25:01 DEBUG| utils:0153| [stdout] Try 6 of 10
08/29 11:25:48 DEBUG| utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:25:57 ERROR| utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/defa...

Read more...

Changed in ubuntu-kernel-tests:
status: In Progress → Invalid
Changed in linux-kvm (Ubuntu):
status: New → Invalid
Changed in sysdig (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.