Results 1 to 3 of 3

Thread: Any concern re 'taints kernel' vbox message with VBox 6.04 and 5.1.2 kernel?

  1. #1

    Default Any concern re 'taints kernel' vbox message with VBox 6.04 and 5.1.2 kernel?

    I locked Virtualbox at version 6.0.4, so I can continue to use my Windows 7 VM while waiting for a fixed ACPI.

    (As per the messages in this thread:

    https://forums.opensuse.org/showthread.php/535667-VirtualBox-6-0-4_SUSE-r128164-Win-7-quot-the-BIOS-in-this-system-is-not-fully-ACPI-compliant-quot/page3 )

    Today's zypper dup to the 20190516 snapshot brought in kernel 5.1.2. I had expected that this wouldn't work with VirtualBox 6.0.4, and was pleasantly surprised to find out that it does. However, when I ran /sbin/vboxconfig as root, vboxconfig reported:

    Code:
    Building kernel modules...
    Kernel modules built correctly.  They will now be installed
    insmod /lib/modules/5.1.2-1-deafault/misc/vboxdrv.ko
    [    61.092791] vboxdrv: loading out-of-tree module taints kernel.
    [    61.093340] vboxdrv: module verification failed: signature and/or required key missing
    [    61.119865] vboxdrv: TSC mode is Invariant, tentative frequency 3999987052 Hz
    insmod /lib/modules/5.1.2-1-default/misc/vboxnetflt.ko
    [       61.121347] VoxNetFlt: Successfully started.
    insmod /lib/modules/5.1.2-1-default/misc/vboxnetadp.ko
    [       61.122405] VBoxNetAdp: Successfully started.
    insmod /lib/modules/5.1.2-1-default/misc/vboxpci.ko
    [       61.123508] VboxPciLinbuxInit
    [       61.123707] vboxpci: IOMMU not found (not registered)
    Kernel modules are installed and loaded.
    A google search for vboxdrv: loading out-of-tree module taints kernel turned up this thread:

    https://forums.virtualbox.org/viewtopic.php?f=7&t=83108

    which suggests to me that I can yawn and ignore these messages. My VMs seem to be working fine. That said: if anyone thinks I should be concerned about these messages, I hope they'll enlighten me here.

    (If not, I suppose I can keep VBox locked at 6.0.4 for kernel 5.1's lifespan in Tumbleweed. I assume that ACPI will be fixed long before zypper dup brings in kernel 5.2.)

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,130
    Blog Entries
    15

    Default Re: Any concern re 'taints kernel' vbox message with VBox 6.04 and 5.1.2 kernel?

    Quote Originally Posted by Tuner View Post
    I locked Virtualbox at version 6.0.4, so I can continue to use my Windows 7 VM while waiting for a fixed ACPI.

    (As per the messages in this thread:

    https://forums.opensuse.org/showthread.php/535667-VirtualBox-6-0-4_SUSE-r128164-Win-7-quot-the-BIOS-in-this-system-is-not-fully-ACPI-compliant-quot/page3 )

    Today's zypper dup to the 20190516 snapshot brought in kernel 5.1.2. I had expected that this wouldn't work with VirtualBox 6.0.4, and was pleasantly surprised to find out that it does. However, when I ran /sbin/vboxconfig as root, vboxconfig reported:

    Code:
    Building kernel modules...
    Kernel modules built correctly.  They will now be installed
    insmod /lib/modules/5.1.2-1-deafault/misc/vboxdrv.ko
    [    61.092791] vboxdrv: loading out-of-tree module taints kernel.
    [    61.093340] vboxdrv: module verification failed: signature and/or required key missing
    [    61.119865] vboxdrv: TSC mode is Invariant, tentative frequency 3999987052 Hz
    insmod /lib/modules/5.1.2-1-default/misc/vboxnetflt.ko
    [       61.121347] VoxNetFlt: Successfully started.
    insmod /lib/modules/5.1.2-1-default/misc/vboxnetadp.ko
    [       61.122405] VBoxNetAdp: Successfully started.
    insmod /lib/modules/5.1.2-1-default/misc/vboxpci.ko
    [       61.123508] VboxPciLinbuxInit
    [       61.123707] vboxpci: IOMMU not found (not registered)
    Kernel modules are installed and loaded.
    A google search for vboxdrv: loading out-of-tree module taints kernel turned up this thread:

    https://forums.virtualbox.org/viewtopic.php?f=7&t=83108

    which suggests to me that I can yawn and ignore these messages. My VMs seem to be working fine. That said: if anyone thinks I should be concerned about these messages, I hope they'll enlighten me here.

    (If not, I suppose I can keep VBox locked at 6.0.4 for kernel 5.1's lifespan in Tumbleweed. I assume that ACPI will be fixed long before zypper dup brings in kernel 5.2.)
    Hi
    There are numerous out of kernel tree modules that will taint it (eg broadcom-wl). The only problem with it being tainted is if you have a kernel issue and wish to create a bug report, they will all need to be removed and then duplicate the issue before a bug report will/may be accepted...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Default Re: Any concern re 'taints kernel' vbox message with VBox 6.04 and 5.1.2 kernel?

    Thanks, Malcolm. I'll ignore the messages.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •