Recent content by CodeMonkeyBill

Thanks, I also just ran into this issue and was able to find this post quickly to resolve my problem.

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...

I actually re-enabled ballooning on all VMs, I think I must have installed the wrong version of the ballooning driver/mgmt service the first time around. But I started getting crashes again as soon as I re-enabled KSM. So presently I am using ballooning but not using KSM. What storage...

Awesome, thanks for the confirmation on netconsole, and using them both together, and the tips on setting it all up. -AvE

Thanks for the suggestion! I just had a friend recommend netconsole to remotely record kernel logs. Will try and setup both to try and cover all the bases, get all the info I can.

Any assistance identifying the likely cause of this kernel panic would be greatly appreciated. (The server is headless, and this final page of console text is all I can get from the IPMI server) And if anyone has any suggestions as to the relevant logs, and how to access them, that may...

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...

Long time lurker on this forum, first time poster. I have read many many threads that are a close variation to, but not exactly similar to my issue. And I have already resolved my issue to my satisfaction, but have some questions about how Proxmox's deeper features work and if I should really be...