group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #10600
[Bug 1629870] Re: [SRU] Trouble installing mainline kernel 4.8: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build
This bug was fixed in the package virtualbox-guest-additions-iso -
5.0.32-0ubuntu1.16.04.2
---------------
virtualbox-guest-additions-iso (5.0.32-0ubuntu1.16.04.2) xenial; urgency=medium
* Update to the latest minor release for xenial (LP: #1629870)
-- Gianfranco Costamagna <locutusofborg@xxxxxxxxxx> Wed, 11 Jan 2017
12:43:32 +0100
** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: virtualbox-ext-pack (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1629870
Title:
[SRU] Trouble installing mainline kernel 4.8: virtualbox-dkms 5.0.24
-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build
Status in virtualbox package in Ubuntu:
Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
Fix Released
Status in virtualbox source package in Xenial:
Fix Released
Status in virtualbox-ext-pack source package in Xenial:
Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
Fix Released
Bug description:
[SRU Template ]
* the virtualbox kernel module needs some tweaks for the new kernel 4.8.
Using 5.0.24 and patching it is not quite easy, because we get less testing and diverge from upstream.
* We already did some minor release bump on xenial, without issues, and I think 5.0.30 is the best candidate to go in updates right now, fixing only bugs since 5.0.24 and keeping the kernel modules up-to-date.
ext-pack and guest-additions should follow the same way
(a 5.1 upload would be nice, but too many changes)
CHANGES since the last version:
VirtualBox 5.0.32 (released 2017-01-17)
This is a maintenance release. The following items were fixed and/or
added:
GUI: fixed a problem where the new version detected dialog was covered by the appliance import dialog (Mac OS X hosts only; bug #16238)
Storage: fixed a problem with the LsiLogic SCSI controller where requests could be lost with SMP guests
OVF: when importing appliances, make sure that the version of the embedded VirtualBox specific settings is processed, to get the default settings handling right
Linux hosts: automatically disable asynchronous I/O on Linux 2.6.18 kernels as high I/O load may trigger kernel oopses on these kernels if this feature is enabled
API: don't crash when sanitizing certain VM names (bug #16299)
Linux hosts / guests: Linux 2.6.28 compile fix (bug #16267)
Linux hosts: compile Linux 4.9 compile fix (bug #16286)
Linux hosts: Linux 4.10 fixes
Linux Additions: fixed protocol error during certain operations on shared folders (bug #8463)
VirtualBox 5.0.30 (released 2016-11-23)
Storage: fixed resizing VDI images resulting in an unbootable image under certain circumstances (bug #15983)
NAT: fixed several 5.0.28 regressions on Mac OS X and Windows hosts (bug #16084)
Audio: fixed recording glitches (Mac OS X hosts)
Audio: fixed stream re-initialization on audio device change (Mac OS X hosts)
Windows hosts: hardening fix for Windows 10 build 14971 (bug #16202)
Linux hosts / guests: Linux 4.8 and 4.9 fixes (bugs #16081, #16132 and #16116)
VirtualBox 5.0.28 (released 2016-10-18)
NAT: Don't exceed the maximum number of "search" suffixes. Patch from bug #15948.
NAT: fixed parsing of port-forwarding rules with a name which contains a slash (bug #16002)
NAT Network: when the host has only loopback nameserver that cannot be mapped to the guests (e.g. dnsmasq running on 127.0.1.1), make DHCP supply NAT Network DNS proxy as nameserver.
Bridged Network: prevent flooding syslog with packet allocation error messages (bug #15569)
USB: fixed a possible crash when detaching a USB device
Audio: fixes for recording (Mac OS X hosts only)
Audio: now using Audio Queues on Mac OS X hosts
OVF: improve importing of VMs created by VirtualBox 5.1
VHDX: fixed cloning images with VBoxManage clonehd (bug #14288)
Storage: Fixed broken bandwidth limitation when the limit is very low (bug #14982)
Serial: Fixed high CPU usage with certain USB to serial converters on Linux hosts (bug #7796)
BIOS: fixed 4bpp scanline calculation (bug #15787)
VBoxManage: Don't try to set the medium type if there is no change (bug #13850)
API: fixed initialization of SAS controllers (bug #15972)
Linux hosts: don't use 32-bit legacy capabilities
Linux hosts / guests: fix for kernels with CONFIG_CPUMASK_OFFSTACK set (bug #16020)
Linux Additions: several fixes for X11 guests running non-root X servers
Linux Additions: fix for Linux 4.7 (bug #15769)
Linux Additions: fix for the display kmod driver with Linux 4.8 (bugs #15890 and #15896)
Windows Additions: auto-resizing fixes for Windows 10 guests (bug #15257)
Windows Additions: fixes for arranging the guest screens in multi-screen scenarios
Windows Additions / VGA: if the guest's power management turns a virtual screen off, blank the corresponding VM window rather than hide the VM window
Windows Additions: fixed a generic bug which could lead to freezing shared folders (bug #15662)
VirtualBox 5.0.26 (released 2016-07-18)
VMM: fixed a bug in the task switching code (ticket #15571)
GUI: allow to overwrite an existing file when saving a log file (bug #8034)
GUI: fixed screenshot if the VM is started in separate mode
Audio: improved recording from USB headsets and other sources which might need conversion of captured data
Audio: fixed regression of not having any audio available on Solaris hosts
VGA: fixed an occasional hang when running Windows guests with 3D enabled
Storage: fixed a possible endless reconnect loop for the iSCSI backend if connecting to the target succeeds but further I/O requests cause a disconnect
Storage: fixed a bug when resizing certain VDI images which resulted in using the whole disk on the host (bug #15582)
EFI: fixed access to devices attached to SATA port 2 and higher (bug #15607)
API: fixed video recording with VBoxHeadless (bug #15443)
API: don't crash if there is no graphics controller configured (bug #15628)
VBoxSVC: fixed several memory leaks when handling .dmg images
Solaris hosts: fixed a crash on hosts with certain CPU configurations
Windows hosts: properly fall back to NDIS5 on pre-Vista hosts on silent installations
[Impact]
Installed mainline kernel 4.8 on Ubuntu 16.04.1 x64 and got this error. Should I uninstall and return to 4.7.6?
[ Regression Potential ]
* it should be minimal, even if the debdiff looks scary, upstream has testsuites and a lot of people testing it.
Not diverging from upstream makes me more confident about the sanity of the upload.
(I would be more scared about cherry-picking individual patches because the kernel module might affect the interation with the virtulabox code, and it is not trivial to extract such patches)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DKMSKernelVersion: 4.8.0-040800-generic
Date: Mon Oct 3 15:03:11 2016
DuplicateSignature: dkms:virtualbox-dkms:5.0.24-dfsg-0ubuntu1.16.04.1:/var/lib/dkms/virtualbox/5.0.24/build/vboxdrv/r0drv/linux/timer-r0drv-linux.c:364:13: error: implicit declaration of function ‘mod_timer_pinned’ [-Werror=implicit-function-declaration]
InstallationDate: Installed on 2016-05-14 (141 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
PackageVersion: 5.0.24-dfsg-0ubuntu1.16.04.1
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.12~ubuntu16.04.1
SourcePackage: virtualbox
Title: virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
[ Test case ]
Installing virtualbox from proposed should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1629870/+subscriptions