said by Anub1s:I've tried several kernels, but thanks for the feed back. I think it may just be Ubuntu. But again, I've compiled fresh kernels »
wiki.ubuntu.com/KernelTe ··· nelBuild so I'm not sure it is Ubuntu's patches to the kernel.
Following the above steps doesn't
appear to use any patches, only the config file. Which can still configure a faulty kernel. Or it could be a simple Ubuntu start up script that forces something to run that doesn't need to run.
The problem with all of the reports - on the Virtual Box forum and LaunchPad - there only one log attached. Either a syslog, Xorg log, or even a Virtual Box log would be needed for
them to diagnose the problem. If other people also attach their logs, they could find the common denominator to the problem.
Virtual Box logs are located in $HOME/.VirtualBox/Machines/$MACHINE/Logs
I'd check other virtualization products to see if this boils down to a whole Ubuntu issue, or just Ubuntu + Virtual Box. VMWare can use VT extensions. KVM doesn't use the same type of extensions, but a kernel based module. I believe Ubuntu makes it extremely easy to use KVM with Fedora/Red Hat's libvirt.
FWIW, on my system, I've found KVM a tad faster than Virtual Box. Clearly not as user friendly
KVM can also use as many cores as you tell it to, and emulate other CPUs regardless of native arch (ARM, MIPS, any x86 cpu and x86_64 cpu, PPC ......)