Markus Rehbach <markus.rehbach@gmx.de> writes:

>Unruh wrote:

>> Why in the world would you use ntp in a virtual machine. Use it in the
>> underlying operating system, and have the virtual machine get its time
>> from there. As has been pointed out the virtual machine's clock is
>> virtual, and could be stopped for arbitrarily long times, as the
>> underlying system does other things.

>Why? E.g. development of an ISO installation image in a VM with the
>requirement to have a functional ntpd after installing the ISO.

Don't expect ntp to work on the virtual machine.


>Why in the world should it be evil to have a working ntpd in a virtual
>machine? I have some with stability=0.000 and a very low offset and I'm
>happy with it.

Who said anything about evil. King Canute was not evil for ordering the
tide not to come in. Stupid perhaps, or incompetent had he then relied on
the tide not coming in in his other plans. Not evil.

That occasionally it works is great. Just do not rely on it.



>You are right, the clock could be stopped for longer times but it is not
>happening here. And you can miss interrupts on real hardware which should
>have nearly the same effect for ntpd.

Yes, and ntp will not work if you loose them too often.


>Cheers

>Markus