linux-modules-extra breaks virtualbox guest modules

Bug #1783267 reported by Kolargol00
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned
virtualbox-hwe (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs 5.1.34):

$ modinfo /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko
filename: /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko
license: GPL and additional rights
description: Oracle VM VirtualBox Graphics Card
author: Oracle Corporation
srcversion: 689EDF1E50DE15779B4F930
alias: pci:v000080EEd0000BEEFsv*sd*bc*sc*i*
depends: drm,drm_kms_helper,ttm
staging: Y
retpoline: Y
intree: Y
name: vboxvideo
vermagic: 4.15.0-29-generic SMP mod_unload
parm: modeset:Disable/Enable modesetting (int)

$ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko
filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko
version: 5.2.8_KernelUbuntu r120774
alias: fs-vboxsf
license: GPL
author: Oracle Corporation
description: Oracle VM VirtualBox VFS Module for Host File System Access
srcversion: AF89497125574B5225F9B6A
depends: vboxguest
retpoline: Y
intree: Y
name: vboxsf
vermagic: 4.15.0-29-generic SMP mod_unload
parm: follow_symlinks:Let host resolve symlinks rather than showing them (int)

$ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko
filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko
version: 5.2.8_KernelUbuntu r120774
license: GPL
description: Oracle VM VirtualBox Guest Additions for Linux Module
author: Oracle Corporation
srcversion: F2E5886E3B0544500D404A1
alias: pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i*
depends:
retpoline: Y
intree: Y
name: vboxguest
vermagic: 4.15.0-29-generic SMP mod_unload

Thus installation with dkms fails (while attempting `apt-get install --reinstall virtualbox-guest-dkms-hwe`):

Building initial module for 4.15.0-29-generic
Done.

vboxguest:
Running module version sanity check.
Error! Module version 5.1.34_Ubuntu for vboxguest.ko
is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu).
You may override by specifying --force.

vboxsf.ko:
Running module version sanity check.
Error! Module version 5.1.34_Ubuntu for vboxsf.ko
is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu).
You may override by specifying --force.

vboxvideo.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/

depmod....

DKMS: install completed.

My system does not start correctly with kernel 4.15 and I had to fall back to 4.13 which has working virtualbox guest modules.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jul 24 08:33:57 2018
InstallationDate: Installed on 2015-02-04 (1265 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: linux-hwe
UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago)
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dyslimet 3006 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4
InstallationDate: Installed on 2015-02-04 (1266 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 docker0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 80ee:0022 VirtualBox
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
Package: virtualbox-hwe
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-45-generic root=UUID=552e699c-33c9-440e-b026-637f24f6a1bb ro verbose nosplash
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-45-generic N/A
 linux-backports-modules-4.13.0-45-generic N/A
 linux-firmware 1.157.20
RfKill:

Tags: xenial
Uname: Linux 4.13.0-45-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-08-02 (721 days ago)
UserGroups: adm cdrom debarchiver dip docker lpadmin netdev plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Kolargol00 (kolargol00) wrote :
affects: linux-hwe (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1783267

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic
Revision history for this message
Kolargol00 (kolargol00) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Kolargol00 (kolargol00) wrote : CRDA.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : Lspci.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : ProcEnviron.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : ProcModules.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : PulseList.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : UdevDb.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote : WifiSyslog.txt

apport information

Revision history for this message
Kolargol00 (kolargol00) wrote :

@ubuntu-kernel-bot uploaded logs as requested
Since I can't boot with kernel 4.15, these logs are from my running system with 4.13.

I've just upgraded virtualbox-guest-dkms-hwe, virtualbox-guest-utils-hwe and virtualbox-guest-x11-hwe from version 5.1.34-dfsg-0ubuntu1.16.04.2 to 5.1.38-dfsg-0ubuntu1.16.04.1, but the problem still persists:

Setting up virtualbox-guest-utils-hwe (5.1.38-dfsg-0ubuntu1.16.04.1) ...
Installing new version of config file /etc/init.d/virtualbox-guest-utils-hwe ...
Setting up virtualbox-guest-x11-hwe (5.1.38-dfsg-0ubuntu1.16.04.1) ...
Setting up virtualbox-guest-dkms-hwe (5.1.38-dfsg-0ubuntu1.16.04.1) ...
Loading new virtualbox-guest-5.1.38 DKMS files...
Building for 4.13.0-45-generic and 4.15.0-29-generic
Building initial module for 4.13.0-45-generic
Done.

vboxguest:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.13.0-45-generic/updates/dkms/

vboxsf.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.13.0-45-generic/updates/dkms/

vboxvideo.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.13.0-45-generic/updates/dkms/

depmod....

DKMS: install completed.
Building initial module for 4.15.0-29-generic
Done.

vboxguest:
Running module version sanity check.
Error! Module version 5.1.38_Ubuntu for vboxguest.ko
is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu).
You may override by specifying --force.

vboxsf.ko:
Running module version sanity check.
Error! Module version 5.1.38_Ubuntu for vboxsf.ko
is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu).
You may override by specifying --force.

vboxvideo.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/

depmod....

DKMS: install completed.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

ok the DKMS failure, but does everything work as expected?

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

You shouldn't install virtualbox-guest-dkms-hwe, but only virtualbox-guest-x11-hwe and virtualbox-guest-utils-hwe.

Revision history for this message
Kolargol00 (kolargol00) wrote :

Hey Gianfranco, thanks for looking into this. :)

> ok the DKMS failure, but does everything work as expected?

No, my system does not finish booting with kernel 4.15. systemd reports that virtualbox-guest-utils-hwe.service failed and, after a few other services, stops loading more. I never get to the login screen.

Why shouldn't I install virtualbox-guest-dkms-hwe? It was automatically installed when I installed virtualbox-guest-utils-hwe:

$ aptitude why virtualbox-guest-dkms-hwe
i virtualbox-guest-utils-hwe Recommends virtualbox-guest-dkms-hwe (= 5.1.38-dfsg-0ubuntu1.16.04.1) | virtualbox-guest-source-hwe (= 5.1.38-dfsg-0ubuntu1.16.04.1) | virtualbox-guest-modules-hwe

This all started when linux-image-4.15.0-29-generic was installed (as an upgrade) and pulled linux-modules-4.15.0-29-generic (which contains virtualbox modules) as a dependency. linux-image-4.13.0-45-generic doesn't do that.

Revision history for this message
Kolargol00 (kolargol00) wrote :

I tried your suggestion in #17 and uninstalled (purged) virtualbox-guest-dkms-hwe and rebooted on kernel 4.15.0-30. Result: my system is just as broken as before, virtualbox-guest-utils-hwe.service also fails to start and my screen remains black after that (I suppose X doesn't start either). So there is definitely an incompatibility between virtualbox-guest-*-hwe packages and the latest HWE kernel on xenial now.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

can you please try a systemctl cat virtualbox-guest-utils-hwe when the system is not starting?

Revision history for this message
Kolargol00 (kolargol00) wrote :

There you go!

$ systemctl cat virtualbox-guest-utils-hwe
# /lib/systemd/system/virtualbox-guest-utils-hwe.service
[Unit]
Description=Virtualbox guest utils
Conflicts=systemd-timesyncd.service

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/virtualbox-guest-utils-hwe start
ExecStop=/etc/init.d/virtualbox-guest-utils-hwe stop

[Install]
WantedBy=multi-user.target

FWIW, I get exactly the same result when running with kernel 4.4.0-134-generic.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox-hwe (Ubuntu):
status: New → Confirmed
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

This looks like a regression in the kernel builtin module, nothing I can fix in virtualbox side.
There have been breaking changes in newer 5.2+ virtualbox kernel modules, I suggest to avoid having them in 16.04, and to move to 18.04 if you want a newer codebase

Changed in virtualbox-hwe (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.