Running LinuxMint 17.1:

uname -a
Linux Jimbo 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

dmesg:
vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
vboxdrv: Found 4 processor cores.
vboxdrv: fAsync=0 offMin=0x240 offMax=0x295c
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.3.18_Ubuntu (interface 0x001a0008).
vboxpci: IOMMU found

VirtualBox appears to be functioning properly but I sure don't like this error message. I've done a fair amount of searching around but I haven't found any workable solutions. There are even posts here that are over a year old with no solution. Hope someone can lend a hand on this one. I would rather stick with VirtualBox than switch to vmware.

Thanx for your time.
Jimbone

Does your installation uses secure boot or UEFI?

UEFI

Perhaps every secure boot (UEFI) enabled kernels have their modules signed. Perhaps the VirtualBox module doesn't has that sign or it's not signed by key.

That message is nothing to worry about, and has absolutely NOTHING to do with secure boot or UEFI. All that means, is that you're loading a kernel module that hasn't been fully tested/integrated with the kernel you're running. This message was intended to identify conditions which may make it difficult to properly troubleshoot a kernel problem. For example, loading a proprietary module can make kernel debug output unreliable because kernel developers don't have access to the module's source code (like the nVidia or ATI proprietary drivers), and can't determine what that module may have done to the kernel. Likewise, if the kernel had previously experienced an error condition or if a serious hardware error had occurred, the debug information generated by the kernel may not be reliable.

The WORST case, is that any kernel errors you encounter will be ignored by the kernel developers, until the authors of that module have fixed it. If things are running fine, you're in good shape, and there's nothing really to worry about. This is covered with a better explanation:
https://www.kernel.org/doc/Documenta...ps-tracing.txt

---------- Post added 02-09-15 at 11:05 AM ----------

Wrong on both counts; please don't give people misleading or incorrect information.

1 members found this post helpful.

Thanks, TBOne!

These two pages may be of help.

Page1

page2

One is for Gentoo (the OP is using Mint), and the other is from 2 years ago. NEITHER addresses the OP's question or concern.

Do gentoo have their kernel developed by someone other than Linus and friends.

I realize I marked this as solved but I found a wonderful doc on kernel.org that talks about kernel signing.
See the link: https://www.kernel.org/doc/Documenta...le-signing.txt

They customize their own kernel, based on their needs, as do all the OTHER developers. Since you say you've installed LFS, you should know this.

Thanks TBOne, no discenable problems with my machine it just showed up after dmesg | grep failed