Kernal Log
Posted: 15. May 2017, 20:45
Running 5.1.22 on Kubuntu 17.04.
I got curious and looked through the kernel log today. Wasn't looking specifically for anything to do with vbox, just what was there.
Ran across the following messages in the kernel log:
5/15/17 2:21 PM vboxdrv loading out-of-tree module taints kernel.
5/15/17 2:21 PM vboxdrv module verification failed: signature and/or required key missing - tainting kernel
5/15/17 2:21 PM vboxdrv Found 8 processor cores
5/15/17 2:21 PM vboxdrv TSC mode is Invariant, tentative frequency 3999979955 Hz
5/15/17 2:21 PM vboxdrv Successfully loaded version 5.1.22 (interface 0x00280000)
5/15/17 2:21 PM VBoxNetFlt Successfully started.
5/15/17 2:21 PM VBoxNetAdp Successfully started.
5/15/17 2:21 PM VBoxPciLinuxInit
5/15/17 2:21 PM vboxpci IOMMU not found (not registered)
vbox has been working very well and I'm not really concerned that anything is wrong, but ..... Those first 2 lines have me wondering if something is wrong??? verification failed signature or required key missing. Was something inadvertently left out of the deb package for 5.1.22 that I downloaded from the virtual box site? Or is this something that in known and known not to be a problem?
I got curious and looked through the kernel log today. Wasn't looking specifically for anything to do with vbox, just what was there.
Ran across the following messages in the kernel log:
5/15/17 2:21 PM vboxdrv loading out-of-tree module taints kernel.
5/15/17 2:21 PM vboxdrv module verification failed: signature and/or required key missing - tainting kernel
5/15/17 2:21 PM vboxdrv Found 8 processor cores
5/15/17 2:21 PM vboxdrv TSC mode is Invariant, tentative frequency 3999979955 Hz
5/15/17 2:21 PM vboxdrv Successfully loaded version 5.1.22 (interface 0x00280000)
5/15/17 2:21 PM VBoxNetFlt Successfully started.
5/15/17 2:21 PM VBoxNetAdp Successfully started.
5/15/17 2:21 PM VBoxPciLinuxInit
5/15/17 2:21 PM vboxpci IOMMU not found (not registered)
vbox has been working very well and I'm not really concerned that anything is wrong, but ..... Those first 2 lines have me wondering if something is wrong??? verification failed signature or required key missing. Was something inadvertently left out of the deb package for 5.1.22 that I downloaded from the virtual box site? Or is this something that in known and known not to be a problem?