\o/ cpu family : 15
FYI running with no-kvmclock (as suggested by Anthony in comment 2) also seems to work around the issue.
Dustin: running guests with clocksource=acpi_pm is also a valid solution for those who don't want to throw out freqscaling completely (I am one of those), so I suggest the init script check (if it is blocking and not just a warning) could be optionally disabled by a YES_I_KNOW_I_NEED_TO_ADD_CLOCKSOURCE_ACPI_PM="yes" /etc/default/kvm setting ?
\o/ cpu family : 15
FYI running with no-kvmclock (as suggested by Anthony in comment 2) also seems to work around the issue.
Dustin: running guests with clocksource=acpi_pm is also a valid solution for those who don't want to throw out freqscaling completely (I am one of those), so I suggest the init script check (if it is blocking and not just a warning) could be optionally disabled by a YES_I_KNOW_ I_NEED_ TO_ADD_ CLOCKSOURCE_ ACPI_PM= "yes" /etc/default/kvm setting ?