Host instable after update 5.0.21-5

[DANILO MONTAGNA]

Hi,

I'm using Proxmox 6.0-12..

After updating the kernel to 5.0.21-5 the /var/log/syslog start to ouput these erros below:

VM 106 qmp command failed - VM 106 qmp command 'balloon' failed - Invalid parameter type for 'value', expected: integer
VM 103 qmp command failed - VM 103 qmp command 'balloon' failed - Invalid parameter type for 'value', expected: integer
VM 120 qmp command failed - VM 120 qmp command 'balloon' failed - Invalid parameter type for 'value', expected: integer

etc...

After some time, the proxmox host becomes very unstable and I have to reboot the node in order to the virtual environment become online again..

 

[DrPhlux]

Hi.
I'm seeing the same error message after upgrading to 6.0-12 .
Turning "balloon" off in the hardware memory settings for the kvm guest seems to be a quick workaround.
Updating the guest with the latest virtio-win drivers did not help.

 

[DANILO MONTAGNA]

I'm seeing the same error message after upgrading to 6.0-12

are your nodes unstable also?

 

[DrPhlux]

are your nodes unstable also?

No, but I upgraded to 6.0-12 just an hour or two before I saw the error messages.
Maybe I didn't run the kvm guest long enough.

Did you try turning off memory ballooning?

 

[DANILO MONTAGNA]

Did you try turning off memory ballooning?

Yep, I turned off, and the errors disappeared, but in this case, I loose the dynamic memory feature!!!

 

[DrPhlux]

Yep, I turned off, and the errors disappeared, but in this case, I loose the dynamic memory feature!!!

Yes, you do unfortunately.
I'm only running one kvm guest, so it's not that big a problem for me yet.

I'm sure there will be a fix for this pretty soon.

 

[DANILO MONTAGNA]

Yes, you do unfortunately

At least my nodes is not experiencing crashes after this!!! hope they correct the problem soon!! Cause we area a cloud company running hundred of VMs.. and not having the possibility to regain unused memory from guest is a waste of resources!!!

 

[psionic]

I"m also seeing the balooning error since updating for VMs...
pvestatd[2339]: VM 200 qmp command failed - VM 200 qmp command 'balloon' failed - Invalid parameter type for 'value', expected: integer
pvestatd[2339]: VM 200 qmp command 'balloon' failed - Invalid parameter type for 'value', expected: integer

 

[Stefan_R]

I can confirm the issue happening for me as well. Looking into it, meanwhile I have opened a bug report with a few more details: https://bugzilla.proxmox.com/show_bug.cgi?id=2476

 

[mircsicz]

THX @Stefan_R for bringing my thread and this together...

And sorry for not posting here right away, as the thread starter mentioned instability I wasn't sure we're having the same issue

 

[Stefan_R]

FYI: This should be fixed in pve-manager 6.0-15, currently available from pve-no-subscription. Testing/Feedback always appreciated!