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:

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:


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.)