As per VirtualBox upstream, this was a bug in it https://www.virtualbox.org/ticket/12264#comment:12 . Invalid -> linux (Ubuntu)
** No longer affects: linux (Ubuntu Precise) ** Bug watch added: Virtualbox Trac #12264 http://www.virtualbox.org/ticket/12264 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1009156 Title: linux-3.2.0-25.40: unregister netdevice change breaks VirtualBox Status in Virtualbox: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “virtualbox” package in Ubuntu: Fix Released Status in “virtualbox” source package in Precise: Fix Released Bug description: After upgrading from linux 3.2.0-24.39 to 3.2.0-25.40, my computer will no longer shut down after using a VirtualBox virtual machine. The following is printed every 10 seconds when it tries to unload the VirtualBox networking modules: unregister_netdevice: waiting for vboxnet0 to become free. Usage count = -1 To shut down, I have to hold down on the power button for 5 seconds to power off. This bug has been reported to VirtualBox. A fix for their network driver has been committed to their svn repository, but a release with the fix is not yet available: https://www.virtualbox.org/ticket/10624 https://www.virtualbox.org/changeset/41548/vbox It looks like the culprit is the kernel changes to net/dev/core.c between 3.2.16 and 3.2.18. I'm guessing this is a bug in VirtualBox that was only exposed when the kernel code changed, but it might be a bug in the kernel that the VirtualBox devs had to work around. Either way, I'm guessing lots of people will experience this issue if the new kernel hits -updates. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu9 Architecture: amd64 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=2c47e61e-2732-41d2-ad4f-ca1dafcd0062 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: System76, Inc. Gazelle Professional NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic root=/dev/mapper/hostname-root ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 RelatedPackageVersions: linux-restricted-modules-3.2.0-25-generic N/A linux-backports-modules-3.2.0-25-generic N/A linux-firmware 1.79 StagingDrivers: mei Tags: precise staging Uname: Linux 3.2.0-25-generic x86_64 [Impact] Unable to unload vbox kernel modules. Shutting down the computer no longer works. Forcing shutdown is only possible with SysRq keys. [Test Case] - Make sure you are running kernel 3.2.0-25 - Start a virtual machine with a host only networking device - Shutdown the VM and quit the main VirtualBox window - Check with "ifconfig" that a vboxnetX device is active - Run "sudo service virtualbox stop" - Command should exit normally To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1009156/+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