Corosync should be able to detect if it was not scheduled for long time, ether because the process itself was not scheduled, or VM was not scheduled.
Corosync displays "Token was lost" if not scheduled for long time. Sadly, same message can be result of real Token lost on network. It is potentially useful to be able to distinguish between these two types of Token lost.
Result (if any):
When corosync was not scheduled for long time, message is logged.