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](https://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:[ 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.)vboxdrv: loading out-of-tree module taints kernel]( vboxdrv: loading out-of-tree module taints kernel. )

[QUOTE=Tuner;2902930]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](https://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:[
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…vboxdrv: loading out-of-tree module taints kernel]( vboxdrv: loading out-of-tree module taints kernel. )

Thanks, Malcolm. I’ll ignore the messages.