Op maandag 23 juni 2014 15:54:13 UTC+2 schreef David Woolley:
On 23/06/14 13:12, Miroslav Lichvar wrote:
I think it all depends on the VM implementation and what clocksource
is used in the guest. If the guest is using tsc (i.e. its frequency is
independent of the host clock), it will need
On 25/06/14 10:43, Rob Heemskerk wrote:
Not sure what it's worth and how it is implemented on other virtualisation
platforms but according to vmware docs they have a virtual tsc. It is set when
the vm is powered on but when the vm is moved to a different host (or resumed
more generally) it
William Unruh un...@invalid.ca wrote:
You canrun ntp on the machine that runs the virtual hardware, and tell
the virutal machines to get their time from the real system.
This is not possible on real virtual machine systems.
You can do it on your Linux box at home where you virtualize some
On 2014-06-24, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
You canrun ntp on the machine that runs the virtual hardware, and tell
the virutal machines to get their time from the real system.
This is not possible on real virtual machine systems.
You can do it on your
William Unruh un...@invalid.ca wrote:
On 2014-06-24, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
You canrun ntp on the machine that runs the virtual hardware, and tell
the virutal machines to get their time from the real system.
This is not possible on real virtual
Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
You canrun ntp on the machine that runs the virtual hardware, and tell
the virutal machines to get their time from the real system.
This is not possible on real virtual machine systems.
You can do it on your Linux box at home
On 2014-06-24, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
On 2014-06-24, Rob nom...@example.com wrote:
William Unruh un...@invalid.ca wrote:
You canrun ntp on the machine that runs the virtual hardware, and tell
the virutal machines to get their time from the real
On Tue, Jun 24, 2014 at 8:32 AM, Dave Holland d...@biff.org.uk wrote:
Rob nom...@example.com wrote:
This is not possible on real virtual machine systems.
VMware's documentation disagrees:
You've inverted the conceit*.
If you *define* a real virtual machine hypervisor as one that
doesn't run
On Tue, Jun 24, 2014 at 9:34 AM, William Unruh un...@invalid.ca wrote:
On 2014-06-24, Rob nom...@example.com wrote:
It is not possible to run programs on the bare hardware.
Since the whole VM is a set of programs running on the bare hardware,
this is clearly wrong
Yes but ... sometimes we
Paul tik-...@bodosom.net wrote:
On Tue, Jun 24, 2014 at 9:34 AM, William Unruh un...@invalid.ca wrote:
On 2014-06-24, Rob nom...@example.com wrote:
It is not possible to run programs on the bare hardware.
Since the whole VM is a set of programs running on the bare hardware,
this is clearly
Hi,
Why are NTP Servers running on virtualized hardware (vmware) unsuitable to
serve time to clients?
I've read this statement several times but can't find a good motivation. I've
searched the official documentation, FAQ, the NTP support wiki, this news
group, google search.
I found this in
Rob Heemskerk wrote:
Hi,
Why are NTP Servers running on virtualized hardware (vmware)
unsuitable to serve time to clients?
I've read this statement several times but can't find a good
motivation. I've searched the official documentation, FAQ, the NTP
support wiki, this news group, google
On 23/06/14 12:03, Rob Heemskerk wrote:
As kernels are tickles nowadays response times to clock interrupts and
(interrupt backlogs) do not seem to be relevant anymore.
Tickless kernels still use clock interrupts; they just schedule them
only when actually needed. In fact they can make it
On Mon, Jun 23, 2014 at 12:28:53PM +0100, David Woolley wrote:
On 23/06/14 12:03, Rob Heemskerk wrote:
Could we say it is safe to run ntp servers on a virtualized platform or do
we still need a few (4?) dedicated pieces of hardware to run our internal
NTP servers?
No.
Normal
Agree wholeheartedly. One other consideration to take into account. Despite the
promise of 6 nines uptime for general purpose servers, they get rebooted more
much frequently than dedicated NTP servers, and unless you are relying on
internet resources for upper stratum, then the optimal
On 23/06/14 13:12, Miroslav Lichvar wrote:
I think it all depends on the VM implementation and what clocksource
is used in the guest. If the guest is using tsc (i.e. its frequency is
independent of the host clock), it will need to run its own NTP
It will still be subject to potentially large
David Woolley david@ex.djwhome.demon.invalid wrote:
On 23/06/14 13:12, Miroslav Lichvar wrote:
I think it all depends on the VM implementation and what clocksource
is used in the guest. If the guest is using tsc (i.e. its frequency is
independent of the host clock), it will need to run its own
On Mon, Jun 23, 2014 at 9:54 AM, David Woolley
david@ex.djwhome.demon.invalid wrote:
On 23/06/14 13:12, Miroslav Lichvar wrote:
I think it all depends on the VM implementation
It will still be subject to potentially large scheduling delays between NTP
packet arrival and processing. Also,
On 2014-06-23, Rob Heemskerk rob.heemsk...@gmail.com wrote:
Hi,
Why are NTP Servers running on virtualized hardware (vmware) unsuitable to
serve time to clients?
Because the virtual clock does not tick regularly. The real clock does.
I've read this statement several times but can't find a
19 matches
Mail list logo
