Come to find out it’s a bug (CentOS or Microsoft I don’t know…) that occurs when the VM is Live-Migrated - it actually hung a machine this morning which is why I found out about it - went and looked through all my running machines and it was occurring on 7 of them - the clock “De-Stabilizes” during the migration.
Simple solution - add this to /boot/grub/grub.conf and reboot when you can:
clocksource_failover=acpi_pm
Put it at the end of the kernel line as an option and then reboot.
cynjut - I don’t think they would be interested - they usually aren’t when it’s outside the scope of the actual distro. I am wondering if that setting would hurt as a default, but I guess if your machine didn’t support acpi_pm and that option was present if it would cause a problem? I don’t know.
I think LOTS of people are deploying FreePBX on Hyper-V which is why I posted it.
For what its worth, i just went through all our deployments on HyperV and i found one that is actually doing this right now. For what its worth, this one is an older PBIaf one, but exactly the same problem… I got a machine that I can at least do some triage on.
Yeah, I found 7 of my machines were doing it - Surprised the hell out of me - I looked at the machine that I first found it on this morning for hours scouring the logs - this was the ONLY thing being logged.
It’s a weird bug - I am guessing a Hyper-V bug but oh well.