Joseph, I'm having problems doing that because of the VirtualBox kernel modules, which don't want to compile for the 4.16 kernel. Here's what I get why I try to re-install dkms and virtualbox-dkms:
$ sudo apt-get install dkms virtualbox-dkms Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.13.0-26 linux-headers-4.13.0-26-generic linux-image-4.13.0-26-generic linux-image-extra-4.13.0-26-generic linux-signed-image-4.13.0-26-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: dkms virtualbox-dkms 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. Need to get 690 kB of archives. After this operation, 5,319 kB of additional disk space will be used. Get:1 http://nessus.rodsbooks.com/ubuntu xenial-updates/main amd64 dkms all 2.2.0.3-2ubuntu11.5 [66.3 kB] Get:2 http://nessus.rodsbooks.com/ubuntu xenial-updates/multiverse amd64 virtualbox-dkms all 5.0.40-dfsg-0ubuntu1.16.04.2 [624 kB] Fetched 690 kB in 0s (1,499 kB/s) Selecting previously unselected package dkms. (Reading database ... 550655 files and directories currently installed.) Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.5_all.deb ... Unpacking dkms (2.2.0.3-2ubuntu11.5) ... Selecting previously unselected package virtualbox-dkms. Preparing to unpack .../virtualbox-dkms_5.0.40-dfsg-0ubuntu1.16.04.2_all.deb ... Unpacking virtualbox-dkms (5.0.40-dfsg-0ubuntu1.16.04.2) ... Processing triggers for man-db (2.7.5-1) ... Setting up dkms (2.2.0.3-2ubuntu11.5) ... Setting up virtualbox-dkms (5.0.40-dfsg-0ubuntu1.16.04.2) ... Loading new virtualbox-5.0.40 DKMS files... First Installation: checking all kernels... Building only for 4.16.0-041600rc1-generic Building initial module for 4.16.0-041600rc1-generic ERROR (dkms apport): kernel package linux-headers-4.16.0-041600rc1-generic is not supported Error! Bad return status for module build on kernel: 4.16.0-041600rc1-generic (x86_64) Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information. Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details. invoke-rc.d: initscript virtualbox, action "restart" failed. ● virtualbox.service - LSB: VirtualBox Linux kernel module Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-02-13 13:30:45 EST; 3ms ago Docs: man:systemd-sysv-generator(8) Process: 9835 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) Feb 13 13:30:45 louiswu systemd[1]: Starting LSB: VirtualBox Linux kernel m..... Feb 13 13:30:45 louiswu virtualbox[9835]: * Loading VirtualBox kernel modul.... Feb 13 13:30:45 louiswu virtualbox[9835]: * No suitable module for running ...d Feb 13 13:30:45 louiswu virtualbox[9835]: ...fail! Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Control process exi...=1 Feb 13 13:30:45 louiswu systemd[1]: Failed to start LSB: VirtualBox Linux k...e. Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Unit entered failed...e. Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Failed with result ...'. Hint: Some lines were ellipsized, use -l to show in full. Is there an updated dkms and/or virtualbox-dkms to go along with the 4.16 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F.... pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
