Piranha clusters and VMware clock synch -- SOLUTION
"Kit Gerrits" <[email protected]> Mon, 22 Dec 2008 13:09:11 +0100
| Newsgroups | gmane.linux.redhat.piranha,gmane.comp.linux.lvs.user |
|---|---|
| Message-ID | <[email protected]> |
--===============0439060295== Content-Type: multipart/alternative; boundary="----=_Part_34577_11860886.1229947751774" ------=_Part_34577_11860886.1229947751774 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello all, A few notes w.r.t. section 48.4 of the LVS HOWTO (VMware problems with NTP/time) It -IS- possible to keep several hosts in sync time-wise in VMware, even on a simple laptop. I am currently running an LVS cluster and 2 webservers on my laptop with VMWare Server 1.0.7 and 1GB RAM. There have been no spontaneous cluster failovers (yet) today. For GSX / VMware Server: Pass the following options to the kernel via grub.conf: clock=pit nosmp noapic nolapic For RHEL5/CentOS5, you should use the following: clocksource=pit nosmp noapic nolapic Because this will disable all of Linux' intelligent clock tricks, you'll need to run NTPd to keep your clock in sync. More info at: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1420 For ESX servers, the solution is 'simpler': You need to lower the minimum time between clok requests: Configuration --> Software --> Advanced Settings --> Misc --> Misc.TimerMinHardPeriod Lower this value (it is in microseconds) More info at: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2219 ------=_Part_34577_11860886.1229947751774 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <br>Hello all,<br><br>A few notes w.r.t. section 48.4 of the LVS HOWTO (VMware problems with NTP/time)<br>It -IS- possible to keep several hosts in sync time-wise in VMware, even on a simple laptop.<br><br>I am currently running an LVS cluster and 2 webservers on my laptop with VMWare Server 1.0.7 and 1GB RAM.<br> There have been no spontaneous cluster failovers (yet) today.<br><br><br>For GSX / VMware Server:<br>Pass the following options to the kernel via grub.conf:<br> clock=pit nosmp noapic nolapic<br><br>For RHEL5/CentOS5, you should use the following:<br> clocksource=pit nosmp noapic nolapic<br><br>Because this will disable all of Linux' intelligent clock tricks, you'll need to run NTPd to keep your clock in sync.<br>More info at:<br><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1420" target="_blank">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1420</a><br> <br><br>For ESX servers, the solution is 'simpler':<br>You need to lower the minimum time between clok requests:<br> Configuration --> Software --> Advanced Settings --> Misc --> Misc.TimerMinHardPeriod <br> Lower this value (it is in microseconds)<br>More info at:<br> <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2219" target="_blank">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2219</a><br> <br><br> ------=_Part_34577_11860886.1229947751774-- --===============0439060295== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Piranha-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/piranha-list --===============0439060295==--