Re: [libvirt-users] memoryStats question

At Tue, 08 Jul 2014 18:21:54 +0300, Gleb Voronich wrote: > > > > In that case, I'd guess that Gleb just forgot to call > > virDomainSetMemoryStatsPeriod, perhaps? > I've just performed the same test with CentOS 7 at the host and CentOS > 7 at the guest. > Everything works. > > # virsh dommemstat

Re: [libvirt-users] memoryStats question

In that case, I'd guess that Gleb just forgot to call virDomainSetMemoryStatsPeriod, perhaps? I've just performed the same test with CentOS 7 at the host and CentOS 7 at the guest. Everything works. # virsh dommemstat vm1 actual 1048576 swap_in 0 swap_out 0 major_fault 751 minor_fault 3958627

Re: [libvirt-users] memoryStats question

At Fri, 04 Jul 2014 16:18:45 +0200, Ján Tomko wrote: > > [1 ] > On 07/04/2014 03:18 PM, Claudio Bley wrote: > > At Thu, 03 Jul 2014 17:46:14 +0300, > > Gleb Voronich wrote: > >> > >> > >>> virDomainMemoryStats() gets those stats, if qemu is new enough to > >>> provide them, and if the guest coope

Re: [libvirt-users] memoryStats question

On 07/04/2014 03:18 PM, Claudio Bley wrote: > At Thu, 03 Jul 2014 17:46:14 +0300, > Gleb Voronich wrote: >> >> >>> virDomainMemoryStats() gets those stats, if qemu is new enough to >>> provide them, and if the guest cooperates to provide them. >> Well I use the latest QEMU 2.0.0 >> I have the lates

Re: [libvirt-users] memoryStats question

At Thu, 03 Jul 2014 17:46:14 +0300, Gleb Voronich wrote: > > > > virDomainMemoryStats() gets those stats, if qemu is new enough to > > provide them, and if the guest cooperates to provide them. > Well I use the latest QEMU 2.0.0 > I have the latest CentOS 6.5 installed on the guest and unfortunat

Re: [libvirt-users] memoryStats question

Then your problem is your libvirt is too old. It is the combination of qemu new enough to provide stats (qemu1.4; probably not present in the qemu shipped in CentOS, but present in your self-built 2.0) and libvirt new enough to read stats (v1.1.1 or newer; which is in RHEL 7.0, but not backpor

Re: [libvirt-users] memoryStats question

> You also have to have new enough qemu that reports stats without > blocking (qemu 0.14 or newer added stat reporting via qom-get, since the > older query-balloon interface blocks) and libvirt that knows how to read > stats via qom-get (libvirt 1.1.1 or newer) As I've already mentioned I use QEM

Re: [libvirt-users] memoryStats question

On 07/03/2014 08:39 AM, Claudio Bley wrote: > At Thu, 03 Jul 2014 17:32:20 +0300, > Gleb Voronich wrote: >> >> >>> Actually, you should get more stats when using the virtio balloon >>> driver in your guests. >> I use the balloon but I can't get more stats. >> I use python binding for libvirt and as

Re: [libvirt-users] memoryStats question

On 07/03/2014 08:46 AM, Gleb Voronich wrote: > >> virDomainMemoryStats() gets those stats, if qemu is new enough to >> provide them, and if the guest cooperates to provide them. > Well I use the latest QEMU 2.0.0 > I have the latest CentOS 6.5 installed on the guest and unfortunately I > can't get

Re: [libvirt-users] memoryStats question

virDomainMemoryStats() gets those stats, if qemu is new enough to provide them, and if the guest cooperates to provide them. Well I use the latest QEMU 2.0.0 I have the latest CentOS 6.5 installed on the guest and unfortunately I can't get more stats that I have. Which OS are you using in y

Re: [libvirt-users] memoryStats question

At Thu, 03 Jul 2014 17:32:20 +0300, Gleb Voronich wrote: > > > > Actually, you should get more stats when using the virtio balloon > > driver in your guests. > I use the balloon but I can't get more stats. > I use python binding for libvirt and as far as I can see it calls > virDomainMemoryStats

Re: [libvirt-users] memoryStats question

On 07/03/2014 08:29 AM, Gleb Voronich wrote: >> Eric Blake >> > >> > In the case of the memory balloon device, libvirt CAN provide stats from >> > the guest, because of the way the balloon device works. But if you >> > aren't using a balloon, or if the guest is not cooper

Re: [libvirt-users] memoryStats question

Actually, you should get more stats when using the virtio balloon driver in your guests. I use the balloon but I can't get more stats. I use python binding for libvirt and as far as I can see it calls virDomainMemoryStats exactly. ___ libvirt-users

Re: [libvirt-users] memoryStats question

Eric Blake In the case of the memory balloon device, libvirt CAN provide stats from the guest, because of the way the balloon device works. But if you aren't using a balloon, or if the guest is not cooperative, this won't work. Better would be a guest-agent command for

Re: [libvirt-users] memoryStats question

At Thu, 3 Jul 2014 15:58:41 +0200, Martin Kletzander wrote: > > On Thu, Jul 03, 2014 at 04:31:46PM +0300, Gleb Voronich wrote: > >Hello, > > > >I'm trying to get memory usage statistic inside a guest machine using > >virDomainMemoryStats function at libvirt. > >According to > >http://libvirt.org/h

Re: [libvirt-users] memoryStats question

On 07/03/2014 07:58 AM, Martin Kletzander wrote: > On Thu, Jul 03, 2014 at 04:31:46PM +0300, Gleb Voronich wrote: >> Hello, >> >> I'm trying to get memory usage statistic inside a guest machine using >> virDomainMemoryStats function at libvirt. >> According to >> http://libvirt.org/html/libvirt-lib

Re: [libvirt-users] memoryStats question

On Thu, Jul 03, 2014 at 04:31:46PM +0300, Gleb Voronich wrote: Hello, I'm trying to get memory usage statistic inside a guest machine using virDomainMemoryStats function at libvirt. According to http://libvirt.org/html/libvirt-libvirt.html#virDomainMemoryStatTags the structure could have a lot o

[libvirt-users] memoryStats question

Hello, I'm trying to get memory usage statistic inside a guest machine using virDomainMemoryStats function at libvirt. According to http://libvirt.org/html/libvirt-libvirt.html#virDomainMemoryStatTags the structure could have a lot of useful memory statistic but the amount of parameters depen