Comment 5 for bug 347487

I am not sure whether this really is related to virtualbox or might be a kernel issue: In my environment, I managed to boot up any VM reliably after, in the VM configuration, disabling "VT-x/AMD-V" support (which is not really what one wants on a Core2 Duo that actually supports VT). However:

- Switching VT-x/AMD-V on and trying to boot the VM reliably ends up in a complete system lockup (frozen UI, SysRq keys not working anymore, machine not ping'able via LAN anymore).

- Switching off VT-x/AMD-V, the virtual machine comes up and seems to work as expected.

So, overally, this is a workaround to at least get VMs in virtualbox-ose running again.

- System: up-to-date jaunty build
- Kernel: Linux n428 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 09:00:52 UTC 2009 i686 GNU/Linux