[Expired for kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: kvm (Ubuntu)
Status: Incomplete = Expired
--
Guest kernel can't read TSC frequency from the hypervisor
https://bugs.launchpad.net/bugs/444531
You received this bug notification because you are a
Hi,
I was wondering if you could see if karmic is affeceted by this bug as
well?
Regards
chuck
** Changed in: kvm (Ubuntu)
Status: New = Incomplete
--
Guest kernel can't read TSC frequency from the hypervisor
https://bugs.launchpad.net/bugs/444531
You received this bug notification
in karmic TSC is marked as unstable and isn't listed in
/sys/devices/system/clocksource/clocksource0/available_clocksource
--
Guest kernel can't read TSC frequency from the hypervisor
https://bugs.launchpad.net/bugs/444531
You received this bug notification because you are a member of Ubuntu
** Changed in: kvm (Ubuntu)
Importance: Undecided = Medium
--
Guest kernel can't read TSC frequency from the hypervisor
https://bugs.launchpad.net/bugs/444531
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
i just found out another thing, when the time screw occures. time cycled in 5
second loop, that meams e.g. 18:13:04 to 18:13:09 and then jumped again to
18:13:04.
when I switched to acpi_pm clocksource on guest, screw dissapeared, and
everything works fine. this is a possible workaround, but
i've just find out that stable tsc isn't possible without constant_tsc
processor flag, so stable tsc in guest isn't possible as well, but still
with constant_tsc should work.
--
Guest kernel can't read TSC frequency from the hypervisor
https://bugs.launchpad.net/bugs/444531
You received this
