virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)

Bug #1818148 reported by Norbert on 2019-02-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
virtualbox (Ubuntu)
Undecided
Unassigned

Bug Description

Steps to reproduce:
1. Have 16.04 LTS installed
2. Enable xenial-proposed repository
3. Install `virtualbox-guest-x11` package

Expected results:
* virtualbox-guest-x11 is working as before

Actual results:
* virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED"
* unable to use shared clipboard and drag and drop fuctionalty

Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
Uname: Linux 4.4.0-143-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Mar 1 00:38:30 2019
InstallationDate: Installed on 2018-08-07 (205 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: virtualbox
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: xenial 1850 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2018-01-04 (420 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp0s3 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: virtualbox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-143-generic N/A
 linux-backports-modules-4.4.0-143-generic N/A
 linux-firmware 1.157.21
RfKill:

Tags: xenial
Uname: Linux 4.4.0-143-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_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.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: xenial 1936 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
IwConfig:
 enp0s3 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: virtualbox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-142-generic N/A
 linux-backports-modules-4.4.0-142-generic N/A
 linux-firmware 1.157.21
RfKill:

Tags: xenial
Uname: Linux 4.4.0-142-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_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.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Norbert (nrbrtx) wrote :
description: updated
Norbert (nrbrtx) wrote :

The previous 4.4.0-143-generic is also affected.

affects: linux-meta (Ubuntu) → linux (Ubuntu)

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 1818148

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
Norbert (nrbrtx) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Norbert (nrbrtx) wrote : CRDA.txt

apport information

apport information

Norbert (nrbrtx) wrote : Lspci.txt

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in virtualbox (Ubuntu):
status: New → Confirmed

In the following messages I'll try to include log-files for 4.4.0-142-generic kernel.

apport information

description: updated
Norbert (nrbrtx) wrote : CRDA.txt

apport information

apport information

Norbert (nrbrtx) wrote : Lspci.txt

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Norbert (nrbrtx) wrote : UdevDb.txt

apport information

apport information

summary: - virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-
- proposed
+ virtualbox-guest-x11 does not work with 4.4.0-142-generic and with
+ 4.4.0-143-generic (from xenial-proposed)
description: updated

Am I correct in saying that this is probably due to the kernel module not being built correctly? I'm marking as duplicate

Akima (8-me-w) wrote :

Writing to report that the following upgrade (taken from /var/log/apt/history.log) has resolved my Virtualbox issue:

> Upgrade: virtualbox:amd64 (4.3.36-dfsg-1+deb8u1ubuntu1.14.04.2, 4.3.40-dfsg-0ubuntu14.04.1), virtualbox-dkms:amd64 (4.3.36-dfsg-1+deb8u1ubuntu1.14.04.2, 4.3.40-dfsg-0ubuntu14.04.1), virtualbox-qt:amd64 (4.3.36-dfsg-1+deb8u1ubuntu1.14.04.2, 4.3.40-dfsg-0ubuntu14.04.1)

I am now able to launch Virtualbox virtual machines on this system:

> $ uname -a
> Linux hostname 4.4.0-143-generic #169~14.04.2-Ubuntu SMP Wed Feb 13 15:00:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

> $ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 14.04.6 LTS
> Release: 14.04
> Codename: trusty

Note: before applying the Virtualbox updates, I made sure to first reboot back into the 4.4.0-143-generic kernel to be sure that the Virtualbox kernel module(s) were built against the correct kernel. Regarding the others here that have found that the latest Virtualbox updates haven't resolved the issue for them, is it possible that they were not booted into the latest generic kernel when they applied the Virtualbox updates? Perhaps the kernel modules are only built for the running kernel.

Akima (8-me-w) wrote :

Sorry. You can delete my last comment & this comment if you like. I have reposted my comment on the following bug report where it is more appropriate:

bug link: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049
bug title: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers