Greatly depends on your usage case.
Originally Posted by spiritofreason
A couple of things:
1. Better headless / remote access support.
2. Better networking support (modes, performance, etc)
3. Better SMP support when ncpu >= 4. (Might not be a desktop issue, unless you're doing heavy compilation / calculation inside the VM).
4. IMHO, qemu-kvm snapshot is better suited for install/update-test-drop cycle (no need to store a copy of the VM disk image. In qemu's snapshot mode, changes simply do not get written to the image, unless you manually commit them).
5. Personal preference: I find it easier to manage/modify/etc qemu-kvm from scripts compared to VBOX's somewhat complex command line tools. (Again, might not be a desktop issue.)
6. Better support for RHEL clients. (VBOX has a ---major--- issue with idle detection on RHEL and CentOS.)
7. Better support for non-mainstream OS. (*BSD, ReactOS, Solaris, etc)
8. Better support for development releases. (Running VBOX on rawhide and/or Fedora beta release is... challenging...)
In general, I do agree that normal desktop users might find VBOX easier to handle as long as you stick to the old Windows-on-Linux template.
However, I doubt that Joe-six-pack is the average Fedora, which usually comes with a different usage case.
DEV-NG: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB, GTX680, F20/x86_64, Dell U2711.
DEV: Intel S5520SC, 2xX5680, 36GB, 5x320GB, GTX550, F20/x86_64, Dell U2711 (^).
SRV: Tyan Tempest i5400XT, 2xE5335, 8GB, 4x2TB, 9800GTX, F20/x86-64, Dell U2412.
LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F20/x86_64.