This seems to me like a permission issue on the host:
By default, the qemu/kvm process is started as a non-privileged user (libvirt-qemu in Debian Wheezy).
So only files accessible (or writable) by that user are accessible (writable) by the VM guests.
You might try setting ownership of the directory to the user qemu is run as (see user= and group= in /etc/libvirt/qemu.conf)
Maybe this helps in your case?
I will give very rough idea/explanation.
In OP situation, besides measuring within the VM, the host should be look at too.
In this case, we can assume the following are correct
- In all the test, the host I/O(disk) bandwidth is not max out. As VM(
"monitoring") I/O increases with more CPUs allocated to it. If host I/O was already max out, there should be no I/O performance gain.
"bla" is not the limiting factor As "monitoring" I/O performance improved without changes to "bla"- CPU is the main factory for performance gain(in OP case) Since I/O is not the bottle neck, and OP not mention any memory size changes. But why? Or how?
Additional factor
- Write take more time than Read This is the same for VM and for host. Put it in extremely simple terms: VM wait for host to finish read and write.
What happen when more cpu assigned to "monitoring"?
When "monitoring" is allocated more CPUs, it gain more processing power, but it also gain more processing time for I/O.
This has nothing to do with rsync as it is a single thread program.
It is the I/O layer utilizing the increased CPU power, or more precisely, the increased processing time.
If cpu monitoring program (eg. top) is used on "monitoring" during test, it will show not one, but all cpu usage go up, and also %wa. %wa is wait time spend on I/O.
This performance increase will only happen when your host I/O is not max. out.
I cannot find the cpu scheduling in KVM site, but there is this blog mentioning KVM is using CFS and cgroups, following is the quote
Within KVM, each vcpu is mapped to a Linux process which in turn utilises hardware assistance to create the necessary 'smoke and mirrors' for virtualisation. As such, a vcpu is just another process to the CFS and also importantly to cgroups which, as a resource manager, allows Linux to manage allocation of resources - typically proportionally in order to set constraint allocations. cgroups also apply to Memory, network and I/O. Groups of processes can be made part of a scheduling group to apply resource allocation requirements to hierarchical groups of processes.
In a nutshell, more cpu = more cpu time = more I/O time slot in a given period of time.
Best Answer
The qemu message protocol (QMP) supports a number of asynchronous messages, including one about restart. If you start your qemu instance with a QMP Server it will report a restart. libvirtd uses QMP to manage qemu guests, so you might try setting something like a proxy qmp server up to look for reboot messages. http://wiki.qemu.org/QMP#Asynchronous_message has a little bit more, but the QEMU-KVM source code has the best documentation of events.