On 06/13/2011 10:00 PM, Emmanuel Noobadmin wrote:
On 6/14/11, Avi Kivity<avi@xxxxxxxxxx> wrote: > My gut feeling is to do iscsi in the host. I guess it's best to measure > though. Please post your findings if you do that. Any suggestions or recommendations as to how/what should I be measuring with?
Whatever workload you'll be running on those guests.
So far in trying to determine how bad is the qcow2 disk bottleneck on my VMs, I've been using dd with dsync and direct options as well as hdparm which errors out (not sure if this is considered a KVM/virtio bug?) on the virtio disk after getting a buffered result. But these don't seem to be very good tools since it's all sequential only. I've tried iozone on my home machine but it takes too long per run; unfortunately this host and its VMs are live and I don't have the luxury of another full set of hardware to test on.
fio is a good tool. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
