Clock drift has been an issue w/ VMWare since v1.0. Using a drift
correction file in ntpd.conf helps, but the nature of the clock
algorithm they use makes ntp updates problemmatical.
gerry
Dan Brown wrote:
On Wed, 8 Nov 2006, Amateur Radio WB8NUT wrote:
Eric,
You are correct. However, I was trying to get people up on VMware Player
which is a tad bit easier than VMware Server which I have also used.
Another limiting factor with VMware Server, is that IF you have multiple
virtual appliances running, you better have some decent memory like 1GB
and above.
VMware really doesn't like trying to run more guest memory than you have
physical memory in your host machine. Tuning the amount of memory to "just
enough what you need" inside the guest helps, especially if you have
multiple guests (parasites?) on the same host.
The only issue I've seen -- and I need to upgrade my software and such, is
that the clock inside the guest os can drift from reality. AND, worse,
that attempting to use ntpd can make things drift even more! A drifting
clock makes make (which is used in compiling Xastir) behave badly. Xastir
itself too. This may be fixed in later versions of VMware, I was using the
4.5.2 "Workstation" version at the time I saw these issues.
73,
N8YSZ.
--
Dan Brown
[EMAIL PROTECTED]
_______________________________________________
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
--
Gerry Creager -- [EMAIL PROTECTED]
Texas Mesonet -- AATLT, Texas A&M University
Cell: 979.229.5301 Office: 979.458.4020 FAX 979.862.3983
MAIL: AATLT, 3139 TAMU
Physical: 1700 Research Parkway, Suite 160,
College Station, TX 77843-3139
_______________________________________________
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
