\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 ? -- guest needs to boot with clock=acpi_pm (older AMD freq scaling issues) https://bugs.launchpad.net/bugs/361754 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
