From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 15:16:40 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17CDD6A7 for ; Wed, 14 Jan 2015 15:16:40 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id D867FE66 for ; Wed, 14 Jan 2015 15:16:39 +0000 (UTC) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t0EFGbDf079861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 14 Jan 2015 15:16:38 GMT Date: Wed, 14 Jan 2015 15:16:36 +0000 From: Karl Pielorz To: freebsd-xen@freebsd.org Subject: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Message-ID: <70A0A91F47C63040B165812D@[10.12.30.106]> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 15:16:40 -0000 Hi, This has been seen before e.g. see We're now seeing this now we've started using 10.x boxes under XenServer 6.5 Is there any work around for it? The 'hit' rate for us seems to be quite high (+70%?) i.e. the clock resets most of the time we do even just a storage migration. The guests are running NTP - and that continues running after the event, but is obviously unwilling to make such a big clock adjustment to drag the guests time from 1970 to present day. Unfortunately - this also causes various other things on the box to break as well :( Is there no 'after migration' hook or script I can lodge some code to shutdown NTP, do an ntpdate - then restart NTP again? Cheers, -Karl From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 20:42:10 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 24D67414 for ; Wed, 14 Jan 2015 20:42:10 +0000 (UTC) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9DE28A8 for ; Wed, 14 Jan 2015 20:42:09 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 82565206C7 for ; Wed, 14 Jan 2015 15:42:07 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Wed, 14 Jan 2015 15:42:07 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=l7/y0YJ0FE1RGtKDsHfG 05oS3+8=; b=HQ8m+5ILLuQl1bujbKBKyF7iKSAggJlPyEmcyfVhIIPBarlFESm4 TwHK63h1w7jFEK2izpPuTEz5c7Y6MvUrjv/F62Bz2Pa63ApfXbfLN8+Mq1fVoHTL Hiup5PQJHWxBPXeWmnYqfd3iTvi4uuu3iNNLxGVrqCn5nX2cYZeADlk= Received: by web3.nyi.internal (Postfix, from userid 99) id 5D5CF10F80C; Wed, 14 Jan 2015 15:42:07 -0500 (EST) Message-Id: <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> X-Sasl-Enc: C1dkI3VmG7sxxva6kAm7CxvSlDEKS+7k0fjK/1btzPS8 1421268127 From: Mark Felder To: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-46f3f2c7 Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Date: Wed, 14 Jan 2015 14:42:07 -0600 In-Reply-To: <70A0A91F47C63040B165812D@[10.12.30.106]> References: <70A0A91F47C63040B165812D@[10.12.30.106]> X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 20:42:10 -0000 On Wed, Jan 14, 2015, at 09:16, Karl Pielorz wrote: > > Hi, > > This has been seen before e.g. see > > > > We're now seeing this now we've started using 10.x boxes under XenServer > 6.5 > > Is there any work around for it? > > The 'hit' rate for us seems to be quite high (+70%?) i.e. the clock > resets > most of the time we do even just a storage migration. > > The guests are running NTP - and that continues running after the event, > but is obviously unwilling to make such a big clock adjustment to drag > the > guests time from 1970 to present day. > > Unfortunately - this also causes various other things on the box to break > as well :( > > Is there no 'after migration' hook or script I can lodge some code to > shutdown NTP, do an ntpdate - then restart NTP again? > When I ran into this I manually stopped NTP, migrated, ran ntpdate, started NTP again. It was painful. The problem as I recall is in the PVHVM code and is fixed upstream in Xen but wasn't pulled into XenServer. Roger will know more details, but if you have a Citrix support contract you should pressure them to open a bug / regression on this. Unfortunately I'm no longer in a position to do so... From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 20:57:03 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04210747 for ; Wed, 14 Jan 2015 20:57:03 +0000 (UTC) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id D03869D6 for ; Wed, 14 Jan 2015 20:57:02 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 8E63D30862 for ; Wed, 14 Jan 2015 15:48:47 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nEHS45T76q1s for ; Wed, 14 Jan 2015 15:48:47 -0500 (EST) Received: from EGR authenticated sender Message-ID: <54B6D62F.9090002@egr.msu.edu> Date: Wed, 14 Jan 2015 15:48:47 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> In-Reply-To: <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 20:57:03 -0000 On 01/14/2015 15:42, Mark Felder wrote: > > > On Wed, Jan 14, 2015, at 09:16, Karl Pielorz wrote: >> >> Hi, >> >> This has been seen before e.g. see >> >> >> >> We're now seeing this now we've started using 10.x boxes under XenServer >> 6.5 >> >> Is there any work around for it? >> >> The 'hit' rate for us seems to be quite high (+70%?) i.e. the clock >> resets >> most of the time we do even just a storage migration. >> >> The guests are running NTP - and that continues running after the event, >> but is obviously unwilling to make such a big clock adjustment to drag >> the >> guests time from 1970 to present day. >> >> Unfortunately - this also causes various other things on the box to break >> as well :( >> >> Is there no 'after migration' hook or script I can lodge some code to >> shutdown NTP, do an ntpdate - then restart NTP again? >> > > When I ran into this I manually stopped NTP, migrated, ran ntpdate, > started NTP again. It was painful. > > The problem as I recall is in the PVHVM code and is fixed upstream in > Xen but wasn't pulled into XenServer. Roger will know more details, but > if you have a Citrix support contract you should pressure them to open a > bug / regression on this. Unfortunately I'm no longer in a position to > do so... > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > I really thought this was fixed in Creedence alphas that I tested... I still have those test systems up but I need to make a test environment for 6.5. Are you using AMD or Intel? I don't know if it makes a difference but I've only seen the problem on AMD so far. From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 22:46:39 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50259A34 for ; Wed, 14 Jan 2015 22:46:39 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 191BDAEB for ; Wed, 14 Jan 2015 22:46:38 +0000 (UTC) Received: from [10.12.30.100] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t0EMkShf020245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jan 2015 22:46:29 GMT Date: Wed, 14 Jan 2015 22:46:28 +0000 From: Karl Pielorz To: Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Message-ID: <979140BCE806D10DE127B63B@Karls-Mac-mini.local> In-Reply-To: <54B6D62F.9090002@egr.msu.edu> References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> <54B6D62F.9090002@egr.msu.edu> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 22:46:39 -0000 --On 14 January 2015 15:48:47 -0500 Adam McDougall wrote: > I really thought this was fixed in Creedence alphas that I tested... I > still have those test systems up but I need to make a test environment > for 6.5. Are you using AMD or Intel? I don't know if it makes a > difference but I've only seen the problem on AMD so far. We're looking at getting a Creedence test setup soon, so I can re-test then - at the moment our platform is XenServer 6.5 - with HP Proliant DL320e's (all Intel / Haswell based). I'll check tomorrow to see how far off having a Creedence test setup will be. -Karl From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 23:11:59 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7784A18C for ; Wed, 14 Jan 2015 23:11:59 +0000 (UTC) Received: from mail.egr.msu.edu (gribble.egr.msu.edu [35.9.37.169]) by mx1.freebsd.org (Postfix) with ESMTP id 4D9A9DE0 for ; Wed, 14 Jan 2015 23:11:58 +0000 (UTC) Received: from gribble (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 2407F49FCC; Wed, 14 Jan 2015 18:06:52 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by gribble (gribble.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlH2e3xcipWJ; Wed, 14 Jan 2015 18:06:52 -0500 (EST) Received: from EGR authenticated sender Message-ID: <54B6F68B.3040403@egr.msu.edu> Date: Wed, 14 Jan 2015 18:06:51 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Karl Pielorz , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> <54B6D62F.9090002@egr.msu.edu> <979140BCE806D10DE127B63B@Karls-Mac-mini.local> In-Reply-To: <979140BCE806D10DE127B63B@Karls-Mac-mini.local> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 23:11:59 -0000 On 01/14/2015 17:46, Karl Pielorz wrote: > > --On 14 January 2015 15:48:47 -0500 Adam McDougall > wrote: > >> I really thought this was fixed in Creedence alphas that I tested... I >> still have those test systems up but I need to make a test environment >> for 6.5. Are you using AMD or Intel? I don't know if it makes a >> difference but I've only seen the problem on AMD so far. > > We're looking at getting a Creedence test setup soon, so I can re-test > then - at the moment our platform is XenServer 6.5 - with HP Proliant > DL320e's (all Intel / Haswell based). > > I'll check tomorrow to see how far off having a Creedence test setup > will be. > > -Karl Are you sure you are running 6.5 and not 6.2? The guest's kernel should detect Xen 4.4 instead of 4.1. 6.5 is Creedence but it was called Creedence during the long alpha stage before it became 6.5. From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 23:58:52 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88D5EF74 for ; Wed, 14 Jan 2015 23:58:52 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5093E5F3 for ; Wed, 14 Jan 2015 23:58:51 +0000 (UTC) Received: from [10.12.30.100] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t0ENwm6L026170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jan 2015 23:58:49 GMT Date: Wed, 14 Jan 2015 23:58:48 +0000 From: Karl Pielorz To: Adam McDougall , freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Message-ID: <582A8DBAC6CBEE430519DBD0@Karls-Mac-mini.local> In-Reply-To: <54B6F68B.3040403@egr.msu.edu> References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> <54B6D62F.9090002@egr.msu.edu> <979140BCE806D10DE127B63B@Karls-Mac-mini.local> <54B6F68B.3040403@egr.msu.edu> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 23:58:52 -0000 --On 14 January 2015 18:06:51 -0500 Adam McDougall wrote: > Are you sure you are running 6.5 and not 6.2? The guest's kernel should > detect Xen 4.4 instead of 4.1. 6.5 is Creedence but it was called > Creedence during the long alpha stage before it became 6.5. Sorry - my mistake (Coffee is wearing off this time of night) - doesn't help I've seen 'next' XenServer called 7 at some point :) We're running 6.2 - *not* 6.5... -Karl From owner-freebsd-xen@FreeBSD.ORG Thu Jan 15 06:38:46 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A3DCF34 for ; Thu, 15 Jan 2015 06:38:46 +0000 (UTC) Received: from mail-pa0-x245.google.com (mail-pa0-x245.google.com [IPv6:2607:f8b0:400e:c03::245]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C855F13 for ; Thu, 15 Jan 2015 06:38:46 +0000 (UTC) Received: by mail-pa0-f69.google.com with SMTP id et14so86755114pad.0 for ; Wed, 14 Jan 2015 22:38:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:message-id:date:subject:from:to:content-type; bh=tzcg9M22X03AD9Ydl9PWUP+52IJQIh+RHiWmN7f/M+I=; b=KhCTNc2IcrHGLMP5BtRVBtvXezIKF8oWkWLqIXMI1PXgLGfOuB3HMBc8yut0uMpBR7 MWWetLnDxAcx4FKFaw3FAyZHdSD7/eyonkx1KRSRpp5VrX8b5eUZ5cCzdxP3Z9OSCAwA G5iMJj2MkoB6kkBgCZDI9SLzwG/2qafsc+1AX2h4t4XdwWVo40lqTlqczOAphVwdLMmG PDslOLesB3EnDfOHflUzN+fyGoUbhVjbTxocMjDqufidBBsQ8fM1gEhL7yQpCs1F8vAK zlXQ4Bg2ZQBe1lkB5cyh5yGb4qEkFpcWE0TmAXyLp0KzOLoDOMn14zNBZgPk+A/26j08 DS0Q== MIME-Version: 1.0 X-Received: by 10.66.224.73 with SMTP id ra9mr6740230pac.0.1421303925937; Wed, 14 Jan 2015 22:38:45 -0800 (PST) Message-ID: Date: Thu, 15 Jan 2015 06:38:45 +0000 Subject: Higher Targeted Traffic: Lukemarsden.Net From: gerry.walker210@gmail.com To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 06:38:46 -0000 Hi Lukemarsden.Neta Hope you are doing well. I thought you might like to know some of the reasons why you are not getting enough Organic search engine and Social Media traffic for your website. Running and maintaining a website is not easy! With continuously changing digital market and its dynamics, it has become pretty much necessary to follow the right strategy in order to counter recent penguin 3.0 updates from Google and drive in relevant traffic. Well, you might consider this irrelevant but there are various tactics behind on-line marketing strategy and you should be well aware of the main drawbacks. Some of the major factors we keep in mind while promoting your website: 1. Fixing errors that prevents your website from being indexed properly by search engine. 2. Selecting right keywords with our SEO services to promote website. 3. Providing relevant content to create theme based back links. 4. Active and regular updates and posts on social media portals to increase the popularity and brand awareness. 5. Gaining more authority by writing articles and blogs through our SMM & SEM services We offer several services for your website such as Online Reputation Management, Social Media Optimization, SEO activities among others. We have excelled along with our customers because of some key propositions as delivering solution by competent Google Analytics certified professionals and we don't bind our customers with any set up fee or contract, i.e. *(NO CONTRACT or NO SET UP FEE)*. This e-mail provides you with a glimpse of some of the services which we offered from our company. If you have any queries about our services then kindly contact us back for a *free website audit report*. Should you be interested, get in touch with us on the mentioned email address or contact number. Wish you Luck & Happy New Year. Best Regards, Gerry Walker |DM Consultant PH. No: +1 605-277-9747 Skype: digital.marketinghm ------------------------------ ------------------------------ ------------------------------ 1: This is a onetime email and you may ask us to "UNSUBSCRIBE". 2: If you are interested we will send more details on our "corporate identity", "company profile", "why you should choose us?", "Price list", "money back" etc. in our next mail. P.S: - This is our marketing strategy that we use the Gmail account. Once you reply us back, the next communication will be done from our corporate email ID. From owner-freebsd-xen@FreeBSD.ORG Thu Jan 15 08:09:01 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3927425F; Thu, 15 Jan 2015 08:09:01 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 442D0A49; Thu, 15 Jan 2015 08:08:59 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.09,402,1418083200"; d="scan'208";a="216390254" Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.3.210.2; Thu, 15 Jan 2015 03:07:44 -0500 Message-ID: <54B7754F.2090308@citrix.com> Date: Thu, 15 Jan 2015 09:07:43 +0100 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Mark Felder Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> In-Reply-To: <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA2 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 08:09:01 -0000 El 14/01/15 a les 21.42, Mark Felder ha escrit: > > > On Wed, Jan 14, 2015, at 09:16, Karl Pielorz wrote: >> >> Hi, >> >> This has been seen before e.g. see >> >> >> >> We're now seeing this now we've started using 10.x boxes under XenServer >> 6.5 >> >> Is there any work around for it? >> >> The 'hit' rate for us seems to be quite high (+70%?) i.e. the clock >> resets >> most of the time we do even just a storage migration. >> >> The guests are running NTP - and that continues running after the event, >> but is obviously unwilling to make such a big clock adjustment to drag >> the >> guests time from 1970 to present day. >> >> Unfortunately - this also causes various other things on the box to break >> as well :( >> >> Is there no 'after migration' hook or script I can lodge some code to >> shutdown NTP, do an ntpdate - then restart NTP again? >> > > When I ran into this I manually stopped NTP, migrated, ran ntpdate, > started NTP again. It was painful. > > The problem as I recall is in the PVHVM code and is fixed upstream in > Xen but wasn't pulled into XenServer. Roger will know more details, but > if you have a Citrix support contract you should pressure them to open a > bug / regression on this. Unfortunately I'm no longer in a position to > do so... As Mark says this has already been fixed in Xen upstream, and the fix should be present at least in Xen 4.4 and the upcoming Xen 4.5. The Xen continuous test system also tests each Xen commit against FreeBSD 10.1, which includes performing x10 migrations in a row: http://www.chiark.greenend.org.uk/~xensrcts/logs/33395/test-amd64-i386-freebsd10-amd64/14.ts-guest-localmigrate.log After each migration the date inside of the guest is printed in order to make sure no skew happens. Roger. From owner-freebsd-xen@FreeBSD.ORG Fri Jan 16 15:31:53 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF9636EF for ; Fri, 16 Jan 2015 15:31:53 +0000 (UTC) Received: from srv2.directadmindns.com (srv2.directadmindns.com [65.98.99.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A9C55C4 for ; Fri, 16 Jan 2015 15:31:53 +0000 (UTC) Received: from [65.98.6.46] (helo=[10.255.255.9]) by srv2.directadmindns.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.83) (envelope-from ) id 1YC8Lj-0003hE-Ro for freebsd-xen@freebsd.org; Fri, 16 Jan 2015 09:58:11 -0500 Message-ID: <54B926FE.7040909@gardenstatecomputing.com> Date: Fri, 16 Jan 2015 09:58:06 -0500 From: Douglas Haber User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Subject: Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD? References: <45B62F4EC5BB836857AF0763@Mail-PC.tdx.co.uk> In-Reply-To: <45B62F4EC5BB836857AF0763@Mail-PC.tdx.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Seems clean. You should still use an Antivirus Scanner X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 15:31:53 -0000 I am running into similar issues "routing" traffic through a pfSense VM running FreeBSD 10.1. There has to be something with the xn driver or related causing it, as re worked flawlessly. Put together a thread here.. https://forum.pfsense.org/index.php?topic=86827.0;all -- Douglas Haber Managing Member Garden State Computing, LLC Tel: (973) 636-7350 www.gardenstatecomputing.com support@gardenstatecomputing.com