Displaying 4 results from an estimated 4 matches for "coperd".
Did you mean:
coped
2014 Jun 25
2
Re: data monitored by "virDomainBlockStats" API not consistent with ones reading from /proc/[pid]/io, and corrugated with /proc/diskstats
...can
that the results vary a lot, especially for the read_bytes.
Since libvirt virDomainBlockStats API reads data from qemu i should ask
the qemu folks for the answers. Great thanks, anyway.
On Jun 25, 2014, at 3:45 AM, Eric Blake <eblake@redhat.com> wrote:
> On 06/24/2014 02:24 AM, coperd wrote:
>
>>
>> It is supposed that the VM’s disk “rd_bytes" and “wr_bytes" should
> never exceed the value of the physical disk respectively, right ?
>
> That's a question for the qemu folks.
>
>> Doesn’t
>> libvirt virDomainBlockStats read d...
2014 Jun 24
2
data monitored by "virDomainBlockStats" API not consistent with ones reading from /proc/[pid]/io, and corrugated with /proc/diskstats
Hi, all.
While monitoring KVM VMs’ disk utilisation using libvirt API “virDomainBlockStats", I find that the results acquired is not consistent
with the value read from /proc/[vm_pid]/io(i only care about “rd_bytes" and “wr_bytes” fields). Since libvirt doesn’t support host level monitoring,
i have to calculate the host’s disk utilisation by reading from the /proc/diskstats file.
2014 Jun 24
0
Re: data monitored by "virDomainBlockStats" API not consistent with ones reading from /proc/[pid]/io, and corrugated with /proc/diskstats
On 06/24/2014 02:24 AM, coperd wrote:
>
> It is supposed that the VM’s disk “rd_bytes" and “wr_bytes" should
never exceed the value of the physical disk respectively, right ?
That's a question for the qemu folks.
> Doesn’t
> libvirt virDomainBlockStats read disk information from “proc” ?
No, libvirt...
2014 Jun 25
0
Re: data monitored by "virDomainBlockStats" API not consistent with ones reading from /proc/[pid]/io, and corrugated with /proc/diskstats
On 06/25/2014 05:11 AM, coperd wrote:
[please don't top-post on technical lists]
> Command line "virsh domblkstat $vmname vda” get the results below:
> vda rd_bytes 639415808
> vda wr_bytes 728186880
>
> Command line "cat /proc/4438/io” get the result below:
> read_bytes: 772415488
> wr...