[opensuse-factory] Leap 15.1 Build 417.2 - update problem in VBox
Good evening, I just wanted to run an upgrade from 15.0 on one of my virtual machines, and see the following issue: localhost:/etc/tryton # zypper dup -l --allow-vendor-change Distributions-Aktualisierungen werden verarbeitet... 3 Probleme: Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Lösung 1: Deinstallation von virtualbox-guest-kmp- default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 Lösung 2: veraltetes virtualbox-guest-kmp- default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 beibehalten Lösung 3: virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19- lp151.4.36.x86_64 durch Ignorieren einiger Abhängigkeiten brechen Any recommendation? Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/22/19 3:12 PM, Axel Braun wrote:
Good evening,
I just wanted to run an upgrade from 15.0 on one of my virtual machines, and see the following issue:
localhost:/etc/tryton # zypper dup -l --allow-vendor-change Distributions-Aktualisierungen werden verarbeitet... 3 Probleme: Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt
Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Lösung 1: Deinstallation von virtualbox-guest-kmp- default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 Lösung 2: veraltetes virtualbox-guest-kmp- default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 beibehalten Lösung 3: virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19- lp151.4.36.x86_64 durch Ignorieren einiger Abhängigkeiten brechen
I have no idea why the guest kmp package should need ksym. Actually, I have no idea what ksym actually is. "kernel symbols" would be my best guess. Note that 15.0 is running VB version 5.2.22, but 15.1 is only running 5.2.10! When openSUSE backported a number of kernel changes, they broke the simple determination of the API based merely on kernel version. That makes a nightmare for maintainers of out-of-kernel drivers such as the VB kmps. I have a package that builds, but since Oracle has gone to VB 6.0.X, there are changes in the programs that need SUID. To accommodate those changes, the permissions package needs to be updated. The Security Group has made those changes in Factory/TW, but they are not (yet) in Leap 15.1. Until that happens, I cannot provide this new version. I will investigate supplying 5.2.24 on an interim basis. To answer your specific question, I think that "Lösung 3" would be the correct choice. I do not see that ignoring the dependency on ksym would break anything. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Feb 22, 2019 at 04:56:19PM -0600, Larry Finger wrote:
On 2/22/19 3:12 PM, Axel Braun wrote:
I just wanted to run an upgrade from 15.0 on one of my virtual machines, and see the following issue:
localhost:/etc/tryton # zypper dup -l --allow-vendor-change Distributions-Aktualisierungen werden verarbeitet... 3 Probleme: Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt
Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Lösung 1: Deinstallation von virtualbox-guest-kmp- default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 Lösung 2: veraltetes virtualbox-guest-kmp- default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 beibehalten Lösung 3: virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19- lp151.4.36.x86_64 durch Ignorieren einiger Abhängigkeiten brechen
I have no idea why the guest kmp package should need ksym. Actually, I have no idea what ksym actually is. "kernel symbols" would be my best guess.
AFAIK it should be the symversion, i.e. essentially a hash calculated from some canonical description of the symbol ABI (structure layout or function header signature). IIUC this error says that caller in the KMP expects different symversion (structure layout or function signature) than available kernel package has. As we have symversion check enabled, the module would refuse to load anyway (which is still better than to ignore the incompatibility and end up with mysterious runtime crashes). I don't think using symversions in kernel package and KMP metadata is new, IIRC we have been using that for some time. I guess the problem here is that SLE15-SP1 kernel (which openSUSE-15.1 shares sources with) does not have kABI frozen yet so that symversions can change any time and KMPs depending on them need to be rebuilt. (In other words, 15.1 still behaves like Tumbleweed in this regard.) I'm not sure why this doesn't happen automatically in OBS - or maybe Axel was just unlucky to hit the window between kernel kABI change and KMP being rebuilt to match. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 23. Februar 2019, 10:15:11 CET schrieb Michal Kubecek:
On Fri, Feb 22, 2019 at 04:56:19PM -0600, Larry Finger wrote:
On 2/22/19 3:12 PM, Axel Braun wrote:
I just wanted to run an upgrade from 15.0 on one of my virtual machines, and see the following issue:
localhost:/etc/tryton # zypper dup -l --allow-vendor-change Distributions-Aktualisierungen werden verarbeitet... 3 Probleme: Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt
Problem: ksym(default:__cpuhp_remove_state) = 325d7cf0 benötigt von virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-lp151.4.36.x86_64 wird nirgends zur Verfügung gestellt
Lösung 1: Deinstallation von virtualbox-guest-kmp-
default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64
Lösung 2: veraltetes virtualbox-guest-kmp-
default-5.2.22_k4.12.14_lp150.12.25-lp150.4.23.1.x86_64 beibehalten
Lösung 3: virtualbox-guest-kmp-default-5.2.10_k4.12.14_lp151.19-
lp151.4.36.x86_64 durch Ignorieren einiger Abhängigkeiten brechen
I have no idea why the guest kmp package should need ksym. Actually, I have no idea what ksym actually is. "kernel symbols" would be my best guess.
AFAIK it should be the symversion, i.e. essentially a hash calculated from some canonical description of the symbol ABI (structure layout or function header signature). IIUC this error says that caller in the KMP expects different symversion (structure layout or function signature) than available kernel package has. As we have symversion check enabled, the module would refuse to load anyway (which is still better than to ignore the incompatibility and end up with mysterious runtime crashes).
I don't think using symversions in kernel package and KMP metadata is new, IIRC we have been using that for some time. I guess the problem here is that SLE15-SP1 kernel (which openSUSE-15.1 shares sources with) does not have kABI frozen yet so that symversions can change any time and KMPs depending on them need to be rebuilt. (In other words, 15.1 still behaves like Tumbleweed in this regard.) I'm not sure why this doesn't happen automatically in OBS - or maybe Axel was just unlucky to hit the window between kernel kABI change and KMP being rebuilt to match.
Thanks, Michael, for the explanation. Chosing option 3 (keep and ignore broken dependencies) made a quick upgrade, but afterwards the VM came up in VGA resolution, and a somewhat distorted mouse alignment - means I cant reach all areays on the desktop, esp, not the taskbar at the bottom of the screen. So, this installation is..broken. I will return to a backup point and wait before filing a bug, just in case a rebuild fixes the issue. Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Feb 23, 2019 at 02:00:04PM +0100, Axel Braun wrote:
Am Samstag, 23. Februar 2019, 10:15:11 CET schrieb Michal Kubecek:
On Fri, Feb 22, 2019 at 04:56:19PM -0600, Larry Finger wrote:
I have no idea why the guest kmp package should need ksym. Actually, I have no idea what ksym actually is. "kernel symbols" would be my best guess.
AFAIK it should be the symversion, i.e. essentially a hash calculated from some canonical description of the symbol ABI (structure layout or function header signature). IIUC this error says that caller in the KMP expects different symversion (structure layout or function signature) than available kernel package has. As we have symversion check enabled, the module would refuse to load anyway (which is still better than to ignore the incompatibility and end up with mysterious runtime crashes).
I don't think using symversions in kernel package and KMP metadata is new, IIRC we have been using that for some time. I guess the problem here is that SLE15-SP1 kernel (which openSUSE-15.1 shares sources with) does not have kABI frozen yet so that symversions can change any time and KMPs depending on them need to be rebuilt. (In other words, 15.1 still behaves like Tumbleweed in this regard.) I'm not sure why this doesn't happen automatically in OBS - or maybe Axel was just unlucky to hit the window between kernel kABI change and KMP being rebuilt to match.
Thanks, Michael, for the explanation. Chosing option 3 (keep and ignore broken dependencies) made a quick upgrade, but afterwards the VM came up in VGA resolution, and a somewhat distorted mouse alignment - means I cant reach all areays on the desktop, esp, not the taskbar at the bottom of the screen.
That would match the expectation that even if you override the package dependencies, the module still wouldn't load because it wouldn't pass the symversion check. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/23/19 12:17 PM, Michal Kubecek wrote:
On Sat, Feb 23, 2019 at 02:00:04PM +0100, Axel Braun wrote:
Am Samstag, 23. Februar 2019, 10:15:11 CET schrieb Michal Kubecek:
Thanks, Michael, for the explanation. Chosing option 3 (keep and ignore broken dependencies) made a quick upgrade, but afterwards the VM came up in VGA resolution, and a somewhat distorted mouse alignment - means I cant reach all areays on the desktop, esp, not the taskbar at the bottom of the screen.
That would match the expectation that even if you override the package dependencies, the module still wouldn't load because it wouldn't pass the symversion check.
I did an upgrade of a Leap 15.0 VM to Leap 15.1 and ran into the same problem. Fortunately, I had finished the revisions needed for VB 5.2.24 to build locally with osc, and on OBS with project home:lwfinger:branches:openSUSE:Leap:15.1:Update/virtualbox. Although it was a pain working with that 640x480 screen, I was able to download the guest packages and the virtualbox package to the VM, select the download directory as an additional repo, and install the necessary packages using YaST. The tests were successful, and I now have all the VB enhancements working. That update has now been pushed with request id 678434. Once that makes its way to the 15.1 updates, the problem should be fixed. If anyone wants to access the RPMs before that, the URL is https://build.opensuse.org/package/binaries/home:lwfinger:branches:openSUSE:.... Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 23. Februar 2019, 22:29:57 CET schrieb Larry Finger:
On 2/23/19 12:17 PM, Michal Kubecek wrote:
On Sat, Feb 23, 2019 at 02:00:04PM +0100, Axel Braun wrote:
Am Samstag, 23. Februar 2019, 10:15:11 CET schrieb Michal Kubecek:
Thanks, Michael, for the explanation. Chosing option 3 (keep and ignore broken dependencies) made a quick upgrade, but afterwards the VM came up in VGA resolution, and a somewhat distorted mouse alignment - means I cant reach all areays on the desktop, esp, not the taskbar at the bottom of the screen.
That would match the expectation that even if you override the package dependencies, the module still wouldn't load because it wouldn't pass the symversion check.
I did an upgrade of a Leap 15.0 VM to Leap 15.1 and ran into the same problem. Fortunately, I had finished the revisions needed for VB 5.2.24 to build locally with osc, and on OBS with project home:lwfinger:branches:openSUSE:Leap:15.1:Update/virtualbox.
Although it was a pain working with that 640x480 screen, I was able to download the guest packages and the virtualbox package to the VM, select the download directory as an additional repo, and install the necessary packages using YaST. The tests were successful, and I now have all the VB enhancements working.
That update has now been pushed with request id 678434. Once that makes its way to the 15.1 updates, the problem should be fixed. If anyone wants to access the RPMs before that, the URL is https://build.opensuse.org/package/binaries/home:lwfinger:branches:openSUSE: Leap:15.1:Update/virtualbox/standard.
Thanks Larry, these packages helped a lot! VBox works as expected now. Best, Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/22/2019 04:56 PM, Larry Finger wrote:
but since Oracle has gone to VB 6.0.X, there are changes in the programs that need SUID
Side note, may help in the interim, Oracle will support the 5.2 branch through 2020 due to issues left to be resolved with the 6.0 branch. Especially regarding headless use. 5.2.26 is the current 5.2 release -- if that helps. Currently 6.0 is unusable as a VM for guests accessed headless over a LAN. SIGABRT (core dumped) Discussed on the VBox-users list. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Axel Braun -
David C. Rankin -
Larry Finger -
Michal Kubecek