Charles Marcus wrote:
On 11/30/2009 4:36 PM, Udo Rader wrote:
Recent kernels should be able to keep the VM time synced using
kvmclock clocksource...
So I'll give clocksource=acpi_pm a chance and see how it turns out ...
So for the sake of other peoples' nerves also facing this problem, the
On 11/30/2009 4:36 PM, Udo Rader wrote:
>>> Recent kernels should be able to keep the VM time synced using
>>> kvmclock clocksource...
>> So I'll give clocksource=acpi_pm a chance and see how it turns out ...
> So for the sake of other peoples' nerves also facing this problem, the
> solution was
Udo Rader wrote:
Charles Marcus wrote:
On 11/30/2009, Udo Rader (list...@bestsolution.at) wrote:
The virtual guest is Centos 5.4 based with dovecot 1.2.8 (at first we
also tried with the original 1.0.7 (?) dovecot shipped with Centos).
I wrote "alleged time shift" because there is no timeshift
Charles Marcus wrote:
On 11/30/2009, Udo Rader (list...@bestsolution.at) wrote:
The virtual guest is Centos 5.4 based with dovecot 1.2.8 (at first we
also tried with the original 1.0.7 (?) dovecot shipped with Centos).
I wrote "alleged time shift" because there is no timeshift
whatsoever, or at
On 11/30/2009, Udo Rader (list...@bestsolution.at) wrote:
> The virtual guest is Centos 5.4 based with dovecot 1.2.8 (at first we
> also tried with the original 1.0.7 (?) dovecot shipped with Centos).
>
> I wrote "alleged time shift" because there is no timeshift
> whatsoever, or at least I don't
