http://bugzilla.opensuse.org/show_bug.cgi?id=1066488
http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c39
--- Comment #39 from S. B.
Did you check whether initrd is recreated at each time you tested install/uninstall on VM? Otherwise it makes no sense.
e.g. try to install drm-kmp again and make sure rebuilding initrd there. I bet you'll hit the very same problem again.
Ah yes, I imagine that was causing the inconsistencies. I just did another quick test on a fresh VM, installed from the same Kiwi generated ISO I've been using, and I tried uninstalling drm-kmp-default and running `sudo mkinitrd`, and then rebooted. The vbox* modules still don't load, and the screen resolution is still extremely small. So I think we can safely say that drm-kmp-default has nothing to do with this issue.
Also, Larry, I'm not sure whether it makes sense to add conflicts to vbox-host kmp.
I don't think it makes sense to add conflicts. My testing seems to prove that the problem is not fixed or caused by the presence or absence of drm-kmp-default. Rather, it seems to be a problem of the kernel version that virtualbox-guest-kmp-default is built for. Right now, the Leap 42.3 kernel is at rev 4.4.103, and the virtualbox-guest-kmp-default package that doesn't work is at virtualbox-guest-kmp-default-5.1.30_k4.4.92_31-39.1.x86_64.rpm in the official update channel. To test this theory, I generated a new ISO with Kiwi using the same template as before, including the drm-kmp-default package. Except this time I added the "obs://Virtualization/openSUSE_Leap_42.3" repository. With those virtualbox* packages (especially virtualbox-guest-kmp-default-5.1.30_k4.4.103_36-362.8.x86_64.rpm) the generated image automatically loads the vbox* modules and uses the full screen resolution on the first boot. -- You are receiving this mail because: You are on the CC list for the bug.