[pve-devel] pve-manager : expose balloon to gui

[Alexandre DERUMIER]

>>What guest OS (windows version) and what binaries virtio drivers do you use exactly?
I have tested it with win2003 R2 SP2 X64, with virtio build48 (http://people.redhat.com/vrozenfe/build-48/)

ballon driver install:

devcon install BALLOON.inf "PCI\VEN_1AF4&DEV_1002&SUBSYS_00051AF4&REV_00"

then install the service: (as administrator)
blnsrv.exe --install

and check that the balloon service is running.


that's all




----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 18 Décembre 2012 14:47:47 
Objet: RE: [pve-devel] pve-manager : expose balloon to gui 

What guest OS (windows version) and what binaries virtio drivers do you use exactly? 

I just tested with win2008r2, and always get 

> timer hasn't been enabled or guest doesn't support 'stat-free-memory' 

I also run 'blnsrv -i' inside the guest, but still can't get usable values. Any ideas? 


> -----Original Message----- 
> From: Alexandre DERUMIER [mailto:aderumier at odiso.com] 
> Sent: Montag, 10. Dezember 2012 00:03 
> To: Dietmar Maurer 
> Cc: pve-devel at pve.proxmox.com 
> Subject: Re: [pve-devel] pve-manager : expose balloon to gui 
> 
> >>Are you sure ? because source code seem to get all balloon stats 
> >>(VIRTIO_BALLOON_S_SWAP_IN,VIRTIO_BALLOON_S_SWAP_OUT,VIRTIO_B 
> ALLOON_S_M 
> >>EMFREE...) 
> >>https://github.com/YanVugenfirer/kvm-guest-drivers- 
> windows/blob/master 
> >>/Balloon/app/memstat.cpp 
> 
> >>I'll restest it. 
> 
> 
> I have just tested it, using last ballon driver,it's working fine for me. (I check 
> values in perfmon, they are same) 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stats- 
> polling-interval 
> {u'return': 10} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stats-last- 
> update 
> {u'return': 1355091093} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stat-free- 
> memory 
> {u'return': 1263800320} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stat-total- 
> memory 
> {u'return': 2096644096} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stat-swap-in 
> {u'return': 0} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stat-swap- 
> out 
> {u'return': 0} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stat-major- 
> faults 
> {u'return': 4300} 
> (QEMU) qom-get path=/machine/peripheral/balloon0 property=stat-minor- 
> faults 
> {u'return': 19507} 
> 
> 
> >>(But It can be easily extended to get some other counters,it's just 
> >>using a wmi query to get perf counters) 
> 
> buffer cache size can be retreive with : "System Cache Resident Bytes" wmi 
> counter