Ticket #10487 (closed enhancement: obsolete)

Opened 6 years ago

Last modified 21 months ago

VirtualBox upgrade should not fail, if the old kernel modules cannot be removed

Reported by: Harri Owned by:
Priority: major Component: installer
Version: VirtualBox 4.1.14 Keywords: Linux installation upgrade
Cc: Guest type: Windows
Host type: Linux


Debian Linux host (Squeeze):

If VirtualBox is running, then the postinst script does not allow to complete the upgrade to a newer version. The new user space binaries are all put into place (AFAICS), but the new kernel modules are not built and the upgrade fails.

In an enterprise environment this means a lot of additional work for the IT folks, begging the users to stop their VirtualBox sessions before leaving. Highly painful. And the users don't want to be bothered by this, either.

It would be much smarter if the postinst script wouldn't fail about this. Since the old vbox* modules are already loaded in the kernel, the module files(!) can be overwritten without affecting the running VirtualBox sessions (similar to the user space binaries).

To be on the safe side the VirtualBox startup script could check the vbox* kernel modules on the next reboot and rebuild them, if they don't match the installed VirtualBox version. This check should be trivial.

Change History

comment:1 Changed 21 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use