Re: FreeBSD not stable enough for Xen environments?
* Redd Vinylene [EMAIL PROTECTED] [2008-11-14 17:32:34+]: depends on how they do their installs, i know of a couple hosting companies doing it already Hey! Which ones? Chiming in another rec for RootBSD as well. I've been a customer of theirs for a few months now and very pleased with their service. (Apart from being a customer, I have no other affiliation with them.) To respond to what another poster said on this thread about their clock, I've not seen any problems with the clock on my RootBSD Xen system. I do run the ntpd in base and on average, my clock is usually only about 15ms away from true UTC. Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
* Maxim Khitrov [EMAIL PROTECTED] [2008-11-17 14:47:00+]: I've not seen any problems with the clock on my RootBSD Xen system. I do run the ntpd in base and on average, my clock is usually only about 15ms away from true UTC. That's interesting. Can you post your `ntpq -p` output here? Sure: $ ntpq -p remote refid st t when poll reach delay offset jitter == +clock.trit.net 192.12.19.20 2 u 529 1024 377 81.5542.870 6.477 +mail.honeycomb. 192.43.244.182 u 408 1024 377 44.091 10.986 8.250 *tuppy.intrepidh 64.142.103.194 2 u 413 1024 377 67.709 15.626 10.327 +clock3.redhat.c 66.187.233.4 2 u 445 1024 377 147.283 24.455 9.397 +204.34.198.40 .USNO. 1 u 409 1024 377 88.746 20.620 10.405 +tick.usno.navy. .USNO. 1 u 427 1024 377 20.848 18.916 8.212 +ntp-s1.cise.ufl .GPS.1 u 421 1024 377 45.709 18.067 9.222 LOCAL(0)LOCAL(0)10 l 18 64 3770.0000.000 0.004 This is what I pretty much used to eyeball my offset earlier. When ntpd is running, its polling interval stays very low (around 64 seconds) because it keeps having to reset the clock. My message log is filled with the following: Intersting, I see the same in my logs, but the frequency seems to be much less than yours, e.g. for the month of November: Nov 1 00:08:22 zaph ntpd[678]: time reset -0.129649 s Nov 3 15:33:09 zaph ntpd[678]: time reset -0.137509 s Nov 4 03:11:51 zaph ntpd[678]: time reset +0.237734 s Nov 4 03:34:23 zaph ntpd[678]: time reset -0.150326 s Nov 4 13:05:20 zaph ntpd[678]: time reset +0.317738 s Nov 4 13:32:06 zaph ntpd[678]: time reset -0.560629 s Nov 4 13:54:35 zaph ntpd[678]: time reset +0.265391 s Nov 4 15:43:55 zaph ntpd[678]: time reset -0.163660 s Nov 7 17:31:03 zaph ntpd[678]: time reset -0.130039 s Nov 10 18:29:19 zaph ntpd[678]: time reset +0.169785 s Nov 10 19:46:26 zaph ntpd[678]: time reset -0.146554 s Nov 10 20:27:08 zaph ntpd[678]: time reset +0.891811 s Nov 10 20:53:59 zaph ntpd[678]: time reset -0.774636 s Nov 10 21:35:45 zaph ntpd[678]: time reset +0.384227 s Nov 10 22:33:46 zaph ntpd[678]: time reset -0.194131 s Nov 11 12:34:25 zaph ntpd[678]: time reset +0.433002 s Nov 11 13:01:09 zaph ntpd[678]: time reset -0.335592 s Nov 11 15:17:45 zaph ntpd[678]: time reset +0.933537 s Nov 11 16:01:42 zaph ntpd[678]: time reset -0.510371 s Nov 11 17:29:41 zaph ntpd[678]: time reset -0.133244 s Nov 11 19:16:41 zaph ntpd[678]: time reset +0.191431 s Nov 11 19:42:30 zaph ntpd[678]: time reset -0.458738 s Nov 11 20:09:16 zaph ntpd[678]: time reset +0.207999 s Nov 11 20:36:06 zaph ntpd[678]: time reset +0.143897 s Nov 14 01:29:44 zaph ntpd[678]: time reset +0.134492 s Nov 15 13:13:36 zaph ntpd[678]: time reset +0.199937 s Nov 15 14:45:09 zaph ntpd[678]: time reset -0.205131 s And so on... Could it be a problem with the hardware on host machine? I use the same ntp.conf file on several FreeBSD 7.1 servers, and the VPS is the only one that has this problem. I checked on my other FreeBSD boxes (all 7.0) and none of them (VPS or otherwise) exihibit this problem. I upgraded my VPS to 7.1 a few months ago, but I don't remember if I had this problem when using 7. Mine is a 7.0. Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
On Mon, Nov 17, 2008 at 03:01:02PM -0500, N.J. Thomas wrote: * Maxim Khitrov [EMAIL PROTECTED] [2008-11-17 14:47:00+]: I've not seen any problems with the clock on my RootBSD Xen system. I do run the ntpd in base and on average, my clock is usually only about 15ms away from true UTC. That's interesting. Can you post your `ntpq -p` output here? Sure: $ ntpq -p remote refid st t when poll reach delay offset jitter == +clock.trit.net 192.12.19.20 2 u 529 1024 377 81.5542.870 6.477 +mail.honeycomb. 192.43.244.182 u 408 1024 377 44.091 10.986 8.250 *tuppy.intrepidh 64.142.103.194 2 u 413 1024 377 67.709 15.626 10.327 +clock3.redhat.c 66.187.233.4 2 u 445 1024 377 147.283 24.455 9.397 +204.34.198.40 .USNO. 1 u 409 1024 377 88.746 20.620 10.405 +tick.usno.navy. .USNO. 1 u 427 1024 377 20.848 18.916 8.212 +ntp-s1.cise.ufl .GPS.1 u 421 1024 377 45.709 18.067 9.222 LOCAL(0)LOCAL(0)10 l 18 64 3770.0000.000 0.004 This is what I pretty much used to eyeball my offset earlier. When ntpd is running, its polling interval stays very low (around 64 seconds) because it keeps having to reset the clock. My message log is filled with the following: Intersting, I see the same in my logs, but the frequency seems to be much less than yours, e.g. for the month of November: Nov 1 00:08:22 zaph ntpd[678]: time reset -0.129649 s Nov 3 15:33:09 zaph ntpd[678]: time reset -0.137509 s Nov 4 03:11:51 zaph ntpd[678]: time reset +0.237734 s Nov 4 03:34:23 zaph ntpd[678]: time reset -0.150326 s Nov 4 13:05:20 zaph ntpd[678]: time reset +0.317738 s Nov 4 13:32:06 zaph ntpd[678]: time reset -0.560629 s Nov 4 13:54:35 zaph ntpd[678]: time reset +0.265391 s Nov 4 15:43:55 zaph ntpd[678]: time reset -0.163660 s Nov 7 17:31:03 zaph ntpd[678]: time reset -0.130039 s Nov 10 18:29:19 zaph ntpd[678]: time reset +0.169785 s Nov 10 19:46:26 zaph ntpd[678]: time reset -0.146554 s Nov 10 20:27:08 zaph ntpd[678]: time reset +0.891811 s Nov 10 20:53:59 zaph ntpd[678]: time reset -0.774636 s Nov 10 21:35:45 zaph ntpd[678]: time reset +0.384227 s Nov 10 22:33:46 zaph ntpd[678]: time reset -0.194131 s Nov 11 12:34:25 zaph ntpd[678]: time reset +0.433002 s Nov 11 13:01:09 zaph ntpd[678]: time reset -0.335592 s Nov 11 15:17:45 zaph ntpd[678]: time reset +0.933537 s Nov 11 16:01:42 zaph ntpd[678]: time reset -0.510371 s Nov 11 17:29:41 zaph ntpd[678]: time reset -0.133244 s Nov 11 19:16:41 zaph ntpd[678]: time reset +0.191431 s Nov 11 19:42:30 zaph ntpd[678]: time reset -0.458738 s Nov 11 20:09:16 zaph ntpd[678]: time reset +0.207999 s Nov 11 20:36:06 zaph ntpd[678]: time reset +0.143897 s Nov 14 01:29:44 zaph ntpd[678]: time reset +0.134492 s Nov 15 13:13:36 zaph ntpd[678]: time reset +0.199937 s Nov 15 14:45:09 zaph ntpd[678]: time reset -0.205131 s What time counter source does this box have available? The following will list what's being used (hardware) and what's available (choice): sysctl kern.timecounter.choice sysctl kern.timecounter.hardware Other ideas: Look into the fudge operator of ntp.conf. Try deleting your ntp driftfile. Note that if you do this, it will take a day or two for things to level out. It tries to figure out the average skew rate your system clock has. And so on... Could it be a problem with the hardware on host machine? I use the same ntp.conf file on several FreeBSD 7.1 servers, and the VPS is the only one that has this problem. I checked on my other FreeBSD boxes (all 7.0) and none of them (VPS or otherwise) exihibit this problem. Then there's a very good possibility it's hardware-related. At my workplace, we've had two separate machines in the past couple months had clocks which went crazy -- ntpd reporting 4-5 seconds of skew every 25-30 minutes. In both cases, the problem turned out to be broken/bad hardware (crystal or TSC gone bad). Just something to keep in mind. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
On Mon, Nov 17, 2008 at 12:38 PM, N.J. Thomas [EMAIL PROTECTED] wrote: * Redd Vinylene [EMAIL PROTECTED] [2008-11-14 17:32:34+]: depends on how they do their installs, i know of a couple hosting companies doing it already Hey! Which ones? To respond to what another poster said on this thread about their clock, I've not seen any problems with the clock on my RootBSD Xen system. I do run the ntpd in base and on average, my clock is usually only about 15ms away from true UTC. Thomas That's interesting. Can you post your `ntpq -p` output here? For me the problem is not just the inaccuracy without ntpd. When ntpd is running, its polling interval stays very low (around 64 seconds) because it keeps having to reset the clock. My message log is filled with the following: Nov 17 03:59:35 ntpd[568]: time reset +1.684038 s Nov 17 04:18:44 ntpd[568]: time reset +1.840754 s Nov 17 04:37:33 ntpd[568]: time reset +1.581726 s Nov 17 04:57:28 ntpd[568]: time reset +2.078004 s Nov 17 05:16:48 ntpd[568]: time reset +1.558386 s Nov 17 05:36:41 ntpd[568]: time reset +2.245156 s Nov 17 05:56:07 ntpd[568]: time reset +1.486516 s Nov 17 06:23:25 ntpd[568]: time reset +2.386411 s Nov 17 06:59:47 ntpd[568]: time reset +3.175640 s Nov 17 07:19:02 ntpd[568]: time reset +1.134997 s Nov 17 07:38:01 ntpd[568]: time reset +1.499600 s And so on... Could it be a problem with the hardware on host machine? I use the same ntp.conf file on several FreeBSD 7.1 servers, and the VPS is the only one that has this problem. Actually, that's another thing - I upgraded my VPS to 7.1 a few months ago, but I don't remember if I had this problem when using 7.0. Anyone know if there were changes made to 7.1 that would make the OS behave differently under Xen? - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
* Jeremy Chadwick [EMAIL PROTECTED] [2008-11-17 12:08:49+]: Intersting, I see the same in my logs, but the frequency seems to be much less than yours, e.g. for the month of November: What time counter source does this box have available? kern.timecounter.choice: TSC(-100) i8254(0) dummy(-100) kern.timecounter.hardware: i8254 Other ideas: Look into the fudge operator of ntp.conf. Yeah, I'm already fudging my local clock a bit. From my ntp.conf: # local clock server 127.127.1.0 # don't trust local clock too much fudge 127.127.1.0 stratum 10 Try deleting your ntp driftfile. Note that if you do this, it will take a day or two for things to level out. It tries to figure out the average skew rate your system clock has. Hmm, my drift file looks decent enough: $ cat /var/db/ntp.drift 10.047 And it's being updated regularly enough. Then there's a very good possibility it's hardware-related. I'll ask the hosting company about it though to see if anyone has brought this up. Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
On Fri, Nov 14, 2008 at 4:11 PM, Outback Dingo [EMAIL PROTECTED] wrote: depends on how they do their installs, i know of a couple hosting companies doing it already On Fri, Nov 14, 2008 at 5:42 PM, Redd Vinylene [EMAIL PROTECTED] wrote: Hello. I want this hosting company to offer FreeBSD but they claim it's not yet stable enough for their Xen setup. Is there anything I can do to prove them wrong? Much obliged y'all. Peace. -- http://www.home.no/reddvinylene Hey! Which ones? -- http://www.home.no/reddvinylene ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On November 14, 2008 11:32:34 am Redd Vinylene wrote: Hey! Which ones? http://www.rootbsd.net I have been a happy customer of their xen system for almost 1 year. If the company you are petitioning is unco-operative, then jump :) Thomas - -- Thomas Abthorpe | FreeBSD Committer [EMAIL PROTECTED] | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkdqcgACgkQ5Gm/jNBp8qABKwCfVLlfYBF0CTMpiDO7x2OdZTuX wR8AnRw1kkZyv81PatSCm1HkAXp90YqV =zDqa -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
On Fri, Nov 14, 2008 at 11:39 AM, Thomas Abthorpe [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On November 14, 2008 11:32:34 am Redd Vinylene wrote: Hey! Which ones? http://www.rootbsd.net I have been a happy customer of their xen system for almost 1 year. If the company you are petitioning is unco-operative, then jump :) Thomas I've been with them for a few months. The only issue to keep in mind is clock drift. On my VM it was very bad - a few minutes over a 24-hour period. You have to use NTPd to keep the clock in sync. The problem is that since ntpd doesn't have access to hardware, it can only reset your kernel clock, keeping it somewhat accurate. The error will still be plus or minus a few seconds. I submitted a support ticket for this issue and that was the only solution we could come up with. I don't have any experience with Xen, so I'm not sure if there is something more that can be done on the host. - Max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD not stable enough for Xen environments?
i was going to recommend the same rootbsd.net seems to have their act together On Fri, Nov 14, 2008 at 11:39 PM, Thomas Abthorpe [EMAIL PROTECTED]wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On November 14, 2008 11:32:34 am Redd Vinylene wrote: Hey! Which ones? http://www.rootbsd.net I have been a happy customer of their xen system for almost 1 year. If the company you are petitioning is unco-operative, then jump :) Thomas - -- Thomas Abthorpe | FreeBSD Committer [EMAIL PROTECTED] | http://people.freebsd.org/~tabthorpehttp://people.freebsd.org/%7Etabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkdqcgACgkQ5Gm/jNBp8qABKwCfVLlfYBF0CTMpiDO7x2OdZTuX wR8AnRw1kkZyv81PatSCm1HkAXp90YqV =zDqa -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
