[SOLVED] Issue on Balloon Service

[killmasta93]

Hi,
I was wondering if someone else has had some issue installing the balloon service, whats odd is that it gets installed and the service is running but on the summary page on proxmox does not show the correct RAM, whats even more odd on the CPU of the windows server 2012r2 shows really high wmi, when i check on event viewer i see error client process ID 608 which i check on the service and its the balloon service. Any ideas?

Thank you

See pictures

 

[killmasta93]

BUMP?

 

[mbaldini]

Have you enabled ballooning in the VM configuration?

 

[killmasta93]

Thanks for the reply, as you can see from the photo it shows the service is on but whats odd out of everything it eats the CPU and then i check the Event logs and see WMI errors

 

[Oliver R]

Hi!

Which version of VirtIO driver did you use?

 

[killmasta93]

Thanks for the reply im using virtio-win-0.1.126

 

[mbaldini]

Try to upgrade to 0.1.141

In Proxmox web interface, in the memory configuration of your VM, do you have balooning enable?

 

[Oliver R]

Can you post your

pveversion -v

here

 

[killmasta93]

Thanks for the reply, the balloon service is activated see picture, i tried the ISO 0.1.141 downloaded from the fedora page using this iso
virtio-win-0.1.141.iso
but still nothing does not show the correct ram

https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.141-1/

proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-6
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

 

[Oliver R]

Can you post a screenshot of your device manager

 

[killmasta93]

Thanks for the reply, sure im attaching you the pictures

Thank you

 

[Oliver R]

Do you run the cmd script or how do you install it?

 

[killmasta93]

Thanks for the reply, I would open the iso folder find the OS in this case Ballooning 2012r2 and copy that folder called amd64 to the c drive of the windows. then i would press shift and right click to open CMD and then type

blnsvr.exe -i


then reboot the server and normally it works but this time no idea why

 

[Oliver R]

Sry I can't help you anymore. I tried to reproduce it but it works for me flawlessly.

 

[killmasta93]

Thanks again, I also forgot to mention this server was hardware and i migrated to proxmox, i followed the wiki as i installed the merg Reg before migrating it could be something with the WMI issue as it shows on the eventlog

 

[GadgetPig]

Sorry didn't mean to resurrect this old thread.

You mentioned you did a P2V conversion? Did the original machine have static network IP before P2V? What if there is still a "hidden" NIC in device manager with static IP still assigned? You could try this:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Hidden_nonpresent_devices

And go to the section "Hidden nonpresent devices", to view hidden devices and see if your old NIC is still there. Perhaps you can remove this hidden adapter. Maybe it could be causing these WMI errors?

 

[killmasta93]

Thanks for the reply, unfornatuly cant confirm if it works because that server i formatted and started from scratch again, its really good noting this because i did not know about it. But whats odd i have done around 10 P2V and never had this issue but i guess next time i need to make sure i delete the old NIC after normally never delete the hidden devices.

Thank you again