Linked by HAL2001 on Thu 23rd Dec 2010 22:49 UTC
Permalink for comment 454788
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2006-01-19
Plus, given the relative advantage qemu/KVM has performance wise [1], VB is looking far less attractive than it used to be.
As it stands, I'll continue using qemu/kvm (using my own VM management scripts) on supported hardware (Xeons, Athon CPUs, etc) and VB (as a sole alternative) on my ASUS 1201N netbook.
- Gilboa
[1] http://www.phoronix.com/scan.php?page=article&item=linux_kvm_vi...
I am sceptical about most virtualization benchmarks because of the number of unknown factors involved. One they mentioned--by default, virtualbox caches writes that should sync to disk, inflating the results unsafely. QEMU/KVM can be configured to do this too. Another is that you can't be sure inside a VM that a measured second is really a wall clock second, since the clock ticks can get optimised out (this is why the clock slips in vmware when you don't have tools installed). If you can't reliably measure time, you can't do any xyz/second benchmarks reliably.
Anecdotally, I find QEMU/KVM to be absurdly slow on IO when using qcow2 and when the disk image is mostly unallocated. Once it gets allocated (grows), it's not as bad. An example would be compiling a kernel on a brand new guest. The first compile allocates a lot of real disk space in the qcow2, pegging the real hdd with metadata updates, etc. The next compile (after rebooting, so it's not caching) doesn't because the qcow2 doesn't really have to grow for it.
I have read that how bad this is might depend on the host FS (I use ext4), but I haven't tested this.