From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laszlo Ersek Subject: Re: Time Change Issue Xen 4.1 Date: Mon, 14 Nov 2011 11:15:27 +0100 Message-ID: <4EC0EA3F.3070405@redhat.com> References: <4EBD5AA0.3090906@webanywhere.co.uk> <20111111183913.GA9283@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111111183913.GA9283@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: pbonzini@redhat.com, keir.xen@gmail.com, xen-devel@lists.xensource.com, JBeulich@suse.com, Niall Fleming List-Id: xen-devel@lists.xenproject.org On 11/11/11 19:39, Konrad Rzeszutek Wilk wrote: > On Fri, Nov 11, 2011 at 05:25:52PM +0000, Niall Fleming wrote: >> Booted the physical machine, date tells me it's 17:15:45. Hwclock agrees. >> Booted a VM (using xl as xm seems to be labouring under the >> impression that blockdev is missing - it isn't) >> The login prompt displays the time as 17:17, which is the expected >> behaviour. >> Changed the time in dom0 - (date +%T -s 12:00:00), synced to hwclock. >> Check that date and hwclock match - they do. >> Destroy the VM and recreate. >> The login prompt displays the time as 17:22. Unexpected! I shut the VM down (2.6.32-131.0.15.el6) before the systime/hwclock change in dom0 (2.6.18-286.el5xen), and restarted it afterwards. The guest entered an infinite loop during this boot :( Thanks Laszlo