From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: HVM Migration of domU on Qemu-upstream DM causes stuck system clock with ACPI Date: Mon, 20 May 2013 15:28:52 -0400 Message-ID: <20130520192852.GB29749@phenom.dumpdata.com> References: <2068104531.8634094.1368537080014.JavaMail.root@zimbra002> <827928EC095A8D390045DA90@nimrod.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap , david.vrabel@citrix.com Cc: Anthony PERARD , Diana Crisan , Alex Bligh , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Mon, May 20, 2013 at 12:11:51PM +0100, George Dunlap wrote: > On Wed, May 15, 2013 at 2:46 PM, Alex Bligh wrote: > > Stranger and stranger. > > > > What happens after this migrate is that 'uptime' reports increasing uptime > > (as in seconds since boot), but the date/time is always the same. Setting > > date fixes this. > > > > It appears that whatever the process is that updates wall time in the kernel > > is not running, until tweaked by wall time being set manually. > > Konrad, is this related to any of the recent Linux wallclock changes > you were trying to address? It was actually David (CC-ing him here). Alex, when you boot the hosts, are the RTC times the same? (date?)