Comment # 12 on bug 1104616 from Stefan Seyfried

Larry, kernel-default-base is not supposed to be installed if you install
kernel-default, it's a "smaller version" of kernel-default, so just leave it
out.

I'm running virtualbox 5.2.16 on Windows 10 (no idea which exact version).
I'll not be in the office tomorrow, so can only get more info on Wednesday.

The original oops from comment#1 is no longer reproducible, now I'm seeing the
BUG: messages from comment#7 *if* i let the vboxguest/vboxsf load by udev or
whatever loads them early.
If vboxguest is blacklisted and thus only loaded later by init script/systemd
service, then everything is fine.

As Takashi suggested the original oops might be from memory corruption and the
now appearing BUG: messages also point to memory corruption problems (at least
to my untrained eye...), my guess was that this is some hidden incompatibility
of the virtualbox-guest-kmp-default built against a slightly older kernel
version that might have changed some internal KABI unnoticed or exposed a now
fixed bug, thus my suggestion to rebuild virtualbox-guest-kmp against the
current update kernel.