I tried on another machine with apparmor enabled where it worked until
the updates were applied (including kernel update from 3.2.0-23-generic-
pae to 23 to  253.2.0-25-generic-pae.

Then it began to happen - first once it worked, once not after changing
several virtualbox settings (including USB support, disabling
hostonlyadapters etc). But then happened again.

Finally I found the following ticket on virtualbox site:
https://www.virtualbox.org/ticket/10528

Now it works on both machines, so the reason is/was in the kernel and
not apparmor or whatever other package.

** Bug watch added: Virtualbox Trac #10528
   http://www.virtualbox.org/ticket/10528

** Description changed:

- With the update of apparmor v2.7.102 from today morning (at least that
- was when it popped up to me, beeing in GMT+2) starting (at least windows
- 2008r2) virtual machines in virtualbox locks up the system completely!
+ Starting virtual machines in virtualbox locks up the system completely!
  Hardware reset required (no CTRL+ALT+F1 etc available any more)!
  
- Issue initially noticed running VirtualBox 4.1.16 r78094 (from the
- Oracle repository).
+ Issue initially noticed running VirtualBox 4.1.16 r78094 (from the Oracle 
repository).
+ Problem tends to first appears only now and then, then more often, not always 
reproducable.
  
  Tried the following:
  a) Uninstalled VirtualBox 4.1.16, rebooted, installed 4.1.12 from the 
universe repositories - same issue - so is not related to latest Oracle release 
of VirtualBox.
  b) Tried using Ubuntu 2D desktop environment because I feared it was a kind 
of Unity lockup - same issue - so does not seem to be Unity related.
- 
- The only way I could resolve the issue was:
- sudo apt-get purge apparmor
- reboot
- 
- I was hit in a sudden by this bug after shutting down my laptop, leaving
- to office and there I could not start any virtual machine any more which
- worked until in the morning. Thinking of possible changes I remembered
- that I installed an update popping up right before shutting down.
- 
- The problem is for me reproducable as soon as I reinstall apparmor and reboot.
- Trying to start any of the Windows 2008r2 virtual machines (don't know if 
occurs also with other guests, I only have Win2008r2 VMs) - after a few seconds 
everything locks up.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Wed Jun 13 13:17:29 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Package: apparmor 2.7.102-0ubuntu3.1
  PackageArchitecture: i386
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae 
root=UUID=86a17a66-9a2f-471c-b8a7-ad960f3034e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

** Tags added: freeze

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012627

Title:
  virtualbox causes system to lockup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1012627/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to