http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c2 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637@gmail.com Assignee|kernel-maintainers@forge.pr |Larry.Finger@lwfinger.net |ovo.novell.com | Flags| |needinfo?(sb56637@gmail.com | |) --- Comment #2 from Andreas Stieger --- Are you using VirtualBox as distributed by openSUSE? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c4 --- Comment #4 from S. B. --- (In reply to Andreas Stieger from comment #2)

Are you using VirtualBox as distributed by openSUSE?

Hi, yes, all official packages. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 S. B. changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sb56637@gmail.com | |) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c7 --- Comment #7 from Larry Finger --- Yes, please issue a rebuild. Whenever the kernel changes from 4.4.X to 4.4.Y, such a rebuild is necessary. It is true that VB 5.1.30 contains fixes for the API changes is openSUSE 42.3 kernels, just as we have fixes for those in Leap 15; however, we have patches to handle all such cases, at least as soon as build failures are reported. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c9 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS Flags| |needinfo?(sb56637@gmail.com | |) --- Comment #9 from Andreas Stieger --- Processed for maintenance. Test packages will appear first in: http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7450/ http://download.opensuse.org/update/leap/42.3-test/ http://download.opensuse.org/update/leap/42.2-test/ Reporter, when these are built, can you please try them out and confirm? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c14 --- Comment #14 from S. B. --- (In reply to Larry Finger from comment #13)

All the modules from http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7450/ openSUSE_Leap_42.3_Update/x86_64/ OK for me in a Leap 42.3 VM. I have no idea why yours had problems with the symbols.loaded

Hmm, not sure, I created a fresh new live ISO with Kiwi using the virtualbox* packages from http://download.opensuse.org/update/leap/42.3-test/ , which I assume is the same thing as your Maintenance repo. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c16 --- Comment #16 from S. B. --- (In reply to Andreas Stieger from comment #15)

Please use the kmp version and build numbers to avoid confusion.

Released in 42.3: 5.1.28_k4.4.87_25-34.1 For testing: 5.1.28_k4.4.92_31-37.1

Hi, yes, I am definitely using 5.1.28_k4.4.92_31-37.1. I'll attach a screenshot too. Would this have anything to do with the fact that I have the drm-kmp-default package installed? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c19 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Flags|needinfo?(sb56637@gmail.com | |) | --- Comment #19 from Andreas Stieger --- closing -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c21 --- Comment #21 from S. B. --- Created attachment 754235 --> http://bugzilla.opensuse.org/attachment.cgi?id=754235&action=edit kernel 4.4.103, vbox modules at k4.4.92 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c24 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #24 from Takashi Iwai --- Possibly installing both drm-kmp and vbox kmp conflicts with each other. If so, it's no kernel regression. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c26 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sb56637@gmail.com | |) --- Comment #26 from Takashi Iwai --- drm-kmp overrides the whole DRM stack while the vbox module is also linked with the original drm stack. That is, installing both does always conflict, no matter how we keep kABI in the kernel itself. So, could you check whether you installed drm-kmp-default package on vbox guest VM? If yes, try to uninstall it. Maybe drm-kmp got installed unnecessarily time by time in the past, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 S. B. changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sb56637@gmail.com | |) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c29 --- Comment #29 from Larry Finger --- I will add "Conflicts: drm-kmp-default" to both host and guest kmp sections of the vbox spec file. That will probably not fix the problem completely. For some reason, the vbox rebuild is not triggered when the kernel changes. I have ask how to fix this on the openSUSE-Factory mailing list with little success. One response referred me to the bb-switch project. I made the vbox spec file references to the kernel be the same as that code, but I still end up with the kernel modules depending on kernel-default, rather than "kernel-default-<some version>". A second response said that I did not need to worry about this problem with Leap as there was no need to rebuild the kernel modules as long as the kernel API did not change! That is obviously wrong. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c31 --- Comment #31 from S. B. --- Created attachment 754381 --> http://bugzilla.opensuse.org/attachment.cgi?id=754381&action=edit Uninstalled drm-kmp-default and rebooted; Still can't load vbox* modules. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c33 --- Comment #33 from S. B. --- Created attachment 754383 --> http://bugzilla.opensuse.org/attachment.cgi?id=754383&action=edit Reinstalled drm-kmp-default and rebooted; vbox* modules still load correctly. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c35 --- Comment #35 from S. B. --- Created attachment 754388 --> http://bugzilla.opensuse.org/attachment.cgi?id=754388&action=edit And now I reverted the virtualbox* packages to the stock openSUSE versions, and the modules still continue to load after rebooting even with drm-kmp-default installed. ???? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c37 --- Comment #37 from S. B. --- (In reply to Larry Finger from comment #36)

OK. The previous conclusions about drm-kmp-default were bogus. The real problem is that a kernel update fails to trigger a rebuild of the virtualbox kmp's. As I previously noted, I was assured by a senior developer that such a rebuild was not necessary!! Be car3eful which experts you believe.

Thanks for looking into it Larry. I have already tested the virtualbox* packages here: https://build.opensuse.org/package/show/Virtualization/virtualbox and they work fine. So it should just be a matter of pulling from there? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c39 --- Comment #39 from S. B. --- (In reply to Takashi Iwai from comment #38)

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.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c40 --- Comment #40 from S. B. --- (In reply to S. B. from comment #39)

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.

OK, a little more weirdness to report on this last part: Specifically, upon booting and installing to the virtual disk the new ISO that was generated with virtualbox-guest-kmp-default-5.1.30_k4.4.103_36-362.8.x86_64.rpm and the drm-kmp-default package included, only the "vboxguest" kernel module was loaded. When I tried to manually load "vboxvideo" it said it wasn't found, and there were a bunch of wrong symbol errors in dmesg similar/identical to what I attached earlier in this bug report. ************ But even without the "vboxvideo" module, I still have full screen resolution in the guest VM, apparently thanks to the "vboxguest" module, which is the most important one. ************ So then I tried uninstalling the drm-kmp-default package, `sudo mkinitrd` and a reboot. Now, both the "vboxguest" AND the "vboxvideo" modules load automatically. But after re-installing drm-kmp-default and regenerating the initrd several times and rebooting several times, both the "vboxguest" AND the "vboxvideo" modules continue to load automatically. So that's weird, but at any rate I don't think anything should be marked as conflicting with drm-kmp-default. I think it would be good enough to simply update the kernel version of virtualbox-guest-kmp-default. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c41 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sb56637@gmail.com | |) --- Comment #41 from Takashi Iwai --- It may be still the case with conflicts of KMPs. Try to re-install vbox client kmp *after* uninstalling drm-kmp. I bet that this would make system working. If my guess is correct, the reason is that weak-update link of vbox kmp fails because of the conflict with drm-kmp. So, even if you uninstall drm-kmp, it doesn't retrigger the weak update link, thus vbox client isn't enabled. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1066488 http://bugzilla.opensuse.org/show_bug.cgi?id=1066488#c43 --- Comment #43 from Takashi Iwai --- (In reply to Larry Finger from comment #42)

The vboxvideo part has not been needed since Xorg was modified to run in user space, which was some time ago. Until VirtualBox 5.2.x, the only effect of leaving it in the build was a little extra time. With 5.2.0 and later, it did not build, thus it has been removed in the Factory version. I have no plans to change Leap 42.{2,3} to anything other than 5.1.x, thus vboxvideo will continue to be built there even though it is not used.

OK, so 42.2/3 need the conflicts, but not for TW. I guess we can put the conflicts tag in drm-kmp in that case.

If the weak-update link for the vbox kmp is not triggered, what would cause that? That may be the real problem.

The reason is that the weak-update is generated only at installing a KMP while we still have the conflicts at installing vbox kmp. The weak-modules2 script tries to determine whether the new module can be loaded cleanly on the target system. When vbox client kmp is installed on a system with drm-kmp, this check fails because of the conflicts, and weak-modules2 script gives up. Even after uninstalling drm-kmp, the weak-modules2 won't be retriggered, thus the weak link isn't created any longer. You need to re-install vbox client kmp again for retriggering the script. -- You are receiving this mail because: You are on the CC list for the bug.