WARNING: No balloon device has been activated

[lynn_yudi]

hi,all

from pve-manager: 3.3-7, get a lot of this warning in /var/log/syslog

What is the problem?

......
Dec 15 13:31:52 t1 pvedaemon[22934]: WARNING: No balloon device has been activated
Dec 15 13:31:53 t1 pvedaemon[22934]: WARNING: No balloon device has been activated
Dec 15 13:31:53 t1 pvedaemon[23744]: WARNING: No balloon device has been activated
Dec 15 13:31:54 t1 pvedaemon[22934]: WARNING: No balloon device has been activated
Dec 15 13:31:54 t1 pvestatd[3033]: WARNING: No balloon device has been activated
Dec 15 13:31:54 t1 pvestatd[3033]: WARNING: No balloon device has been activated
Dec 15 13:31:54 t1 pvestatd[3033]: WARNING: No balloon device has been activated
Dec 15 13:31:55 t1 pvedaemon[22934]: WARNING: No balloon device has been activated
Dec 15 13:31:55 t1 pvedaemon[23744]: WARNING: No balloon device has been activated
Dec 15 13:31:56 t1 pvedaemon[22934]: WARNING: No balloon device has been activated
.....

# pveversion -v
proxmox-ve-2.6.32: 3.3-139 (running kernel: 3.10.0-5-pve)
pve-manager: 3.3-7 (running version: 3.3-7/bc628e80)
pve-kernel-3.10.0-5-pve: 3.10.0-20
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-34-pve: 2.6.32-139
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-15
qemu-server: 3.3-6
pve-firmware: 1.1-3
libpve-common-perl: 3.0-20
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-26
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-5
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Thanks.

 

[spirit]

Balloon driver is not installed in your vm.

if you don't need it, or your vm don't support it,

you can add "balloon: 0" in you vmid.cfg

 

[lynn_yudi]

Balloon driver is not installed in your vm.

if you don't need it, or your vm don't support it,

thanks, this feature only for Windows OS?
maybe most of the modern linux os should have ballon driver inside.

 

[CodeMonkeyBill]

I already have "balloon: 0" in all of my VMs VMID.conf and this error is still being thrown in the VE syslog almost constantly...

 

[DeeMaas]

I have the same problem. How to fix? I already have "balloon: 0" in all of my VMs VMID.conf and this error is still being thrown in the VE syslog constantly.

# pveversion -v
proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve)
pve-manager: 4.3-10 (running version: 4.3-10/7230e60f)
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-47
qemu-server: 4.0-94
pve-firmware: 1.1-10
libpve-common-perl: 4.0-80
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-68
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.3-14
pve-qemu-kvm: 2.7.0-8
pve-container: 1.0-81
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

 

[CodeMonkeyBill]

The only thing that worked for me was to verify I had installed the balloon driver and management service correctly and reactivate ballooning for all windows VMs. That got rid of the syslog messages, but I have no idea what to do if you really need to have ballooning disabled...

 

[Graftak]

Hi,

I solved this issue by removing the balloon:0 from the config files!

I think if the balloon driver is not installed, it won't understand that config setting.