xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Niall Fleming <niall.fleming@webanywhere.co.uk>,
	lersek@redhat.com, pbonzini@redhat.com, JBeulich@suse.com
Cc: xen-devel@lists.xensource.com, keir.xen@gmail.com
Subject: Re: Time Change Issue Xen 4.1
Date: Fri, 11 Nov 2011 13:39:13 -0500	[thread overview]
Message-ID: <20111111183913.GA9283@phenom.dumpdata.com> (raw)
In-Reply-To: <4EBD5AA0.3090906@webanywhere.co.uk>

On Fri, Nov 11, 2011 at 05:25:52PM +0000, Niall Fleming wrote:
> Hi all,
> 
> Already posted this over in xen-users and Konrad confirms it as a
> bug and suggested to repost
> it over here!

Laszlo, Paolo, Jan, you guys haven't seen domething like this? It looks
like a hypervisor issue where the wallclock time is not really dispursed
in the shared_info.

> 
> Issue is that changing the time in dom0 doesn't take effect on the
> VMs until a reboot of dom0.
> The testing example below illustrates what I mean....
> 
> Synopsis of testing:
> 
> 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!
> 
> 
> Kernel: I git cloned tag v3.1 from the kernel.org linux.git, and
> applied xen-settime patches
> Also tested with jeremy-git-xen-next-2.6.32 (.41/.46) without patch,
> they wouldn't apply.
> Xen: 4.1.1/4.1.2
> Distribution: Gentoo
> 
> It still doesn't work.
> 
> I've tested that the issue also exists in Debian Squeeze (with
> linux-image-3.0.0 from testing as 2.6.32-5 is broken
> on my hardware).
> -- 
> 
> *Niall Fleming BSc. (Hons)*
> Systems Administrator
> Webanywhere Limited
> 
> Phone: 0800 862 0131 Ext: 203
> Web: http://www.webanywhere.co.uk
> 
> Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB
> Registered in England with company number 4881346

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-11-11 18:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 17:25 Time Change Issue Xen 4.1 Niall Fleming
2011-11-11 18:39 ` Konrad Rzeszutek Wilk [this message]
2011-11-14  9:48   ` Jan Beulich
2011-11-14 18:00     ` Konrad Rzeszutek Wilk
2011-11-14 19:31       ` Jeremy Fitzhardinge
2011-11-16 14:26         ` Konrad Rzeszutek Wilk
2011-11-17 12:47           ` Niall Fleming
2011-11-22 10:23           ` Niall Fleming
2011-11-30 17:06           ` Niall Fleming
2011-11-30 22:26             ` Konrad Rzeszutek Wilk
2011-12-01  8:55               ` Niall Fleming
2011-12-01  9:53                 ` Ian Campbell
2011-12-01 10:28                   ` Laszlo Ersek
2011-12-01 18:16                     ` Niall Fleming
2011-11-14 10:15   ` Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111111183913.GA9283@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=keir.xen@gmail.com \
    --cc=lersek@redhat.com \
    --cc=niall.fleming@webanywhere.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).