SBC Scheduling Problem - ProSBC on VMWare

[Guest]

I would like to work with someone to isolate the issue I currently have running the ProSBC on VMWare.

We tried increasing the CPU and Memory allocation on the VM, but it didn’t help. Currently, have both active and secondary SBC’s allocated with 8 CPU’s and 16Gbtyes of RAM and still getting the alarm in the ProSBC.

Currently running version 3.1.117 on ProSBC.





Thanks

[Guest]

Hello,

Most VMs have some scheduling problems. It means your high-priority packet processing thread that should be all ours was given to another process for more than 2ms. With a low packet rate, it should not cause problems.


Status containing “scheduling” problem may point to:
• Non-dedicated (or not ‘pinned’) CPU [Open-stack]
• Not enough CPU reservation [Vmware]
• Memory is not dedicated to the Virtual Machine (VM)
• Too many active virtual machines fighting for resources on the host


Best regards