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
Bugs
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 bug
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 ac
Public bug reported:
Binary package hint: kvm
Description of problem:
Guest kernel can't read TSC frequency from the hypervisor on hardy and interpid
causing unstable TSC clocksource even if host has constant_tsc processor flag.
This causes clock drifting on high load and freezing of guests wit
this is not funny anymore. this issue should be fixed immediately.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
