Comment # 24 on bug 1111076 from David Rankin

The reason I ask is I know I don't have to remove
kernel-default-4.12.14-lp150.12.19.2, I can just selected the "Advanced
Options" at the grub boot screen and choose
kernel-default-4.12.14-lp150.12.16.1 (the prior kernel, that's how I removed
the broken kernel), but the problem is I run Leap 15 as a HEADLESS guest, and
it takes some real gymnastics to launch the guest and then bring it up via
rdesktop in time to make the "Advanced Options" choice. 

(yes, I can make the timeout longer or simply change grub defaults to boot the
12.16 kernel, but both options defeat the primary purpose of having the new
kernel-default-4.12.14-lp150.12.19.2 install and running AND being able to boot
kernel-default-4.12.14-lp150.12.16.1 if needed, or for testing of other issues
that may arise.)

So I'm trying to understand if what you are proposing will eliminate my ability
to boot kernel-default-4.12.14-lp150.12.16.1 in the VM?  It shouldn't matter
for kernel-default-4.12.14-lp150.12.19.2 that
virtualbox-guest-kmp-default-5.2.18_k4.12.14_lp150.12.16-lp150.4.17.1.x86_64 is
installed. On Arch I have the 4.14LTS and 4.18 kernels installed, both handle
guest module generation via kms without any conflict, (they are separate module
trees) so I'm having difficulty understanding what modules you are saying need
to be removed?