On Fri, 13.03.15 12:25, Michael Marineau (michael.marin...@coreos.com) wrote:
> Greetings,
>
> Currently systemd-timesyncd.service includes
> ConditionVirtualization=no, disabling it in both containers and
> virtual machines. Each VM platform tends to deal with or ignore the
> time problem in the
This was suposed to go to the list.
2015-03-13 21:25 GMT+01:00 Michael Biebl :
> 2015-03-13 20:25 GMT+01:00 Michael Marineau :
>> I don't know of a robust way to know if a platform needs a little
>> extra help from userspace to keep the clock sane or not but it seems
>> generally safer to try than
On Sun, Mar 15, 2015 at 7:50 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Mar 15, 2015 at 07:47:46PM +0100, Kay Sievers wrote:
>> On Fri, Mar 13, 2015 at 8:25 PM, Michael Marineau
>> wrote:
>> > Greetings,
>> >
>> > Currently systemd-timesyncd.service includes
>> > ConditionVirtualization=no,
On Sun, Mar 15, 2015 at 07:47:46PM +0100, Kay Sievers wrote:
> On Fri, Mar 13, 2015 at 8:25 PM, Michael Marineau
> wrote:
> > Greetings,
> >
> > Currently systemd-timesyncd.service includes
> > ConditionVirtualization=no, disabling it in both containers and
> > virtual machines. Each VM platform t
On Fri, Mar 13, 2015 at 8:25 PM, Michael Marineau
wrote:
> Greetings,
>
> Currently systemd-timesyncd.service includes
> ConditionVirtualization=no, disabling it in both containers and
> virtual machines. Each VM platform tends to deal with or ignore the
> time problem in their own special ways, K
Greetings,
Currently systemd-timesyncd.service includes
ConditionVirtualization=no, disabling it in both containers and
virtual machines. Each VM platform tends to deal with or ignore the
time problem in their own special ways, KVM/QEMU has the kernel time
source kvm-clock, Xen has had different s
