From: Mark Adams <mark@campbell-lange.net>
To: wei song <james.songwei@gmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: Clock jumped 50 minutes in dom0 caused incorrect 2008 R2 domU time
Date: Mon, 11 Oct 2010 11:10:15 +0100 [thread overview]
Message-ID: <20101011101015.GA17511@campbell-lange.net> (raw)
In-Reply-To: <AANLkTinJvr3L9jceFvO_4jrRPCR1BV11szDxar1yv6SN@mail.gmail.com>
Hi,
I can try this, but can you please confirm what these options do?
Regards,
Mark
On Sat, Oct 09, 2010 at 10:15:20AM +0800, wei song wrote:
> added timer_mode =2 and tsc_mode = 1 and viridian=1 into your configure
> file.
>
> thanks,
> James Song
> 2010/10/8 Mark Adams <mark@campbell-lange.net>
>
> > Hi,
> >
> > My hardware is stable otherwise. I haven't had any issues for months
> > before, and ever since, and another server with IDENTICAL setup and
> > hardware did not have the issue at the same time.
> >
> > Where should those settings be added?
> >
> > Regards,
> > Mark
> >
> > On Fri, Oct 08, 2010 at 10:15:59AM +0800, wei song wrote:
> > > What's your setting of timer_mode and tsc_mode? If your hardware is not
> > > stable, pls try timer_mode =2 and tsc_mode = 1 and viridian=1.
> > >
> > > -James Song
> > > 2010/10/6 Mark Adams <mark@campbell-lange.net>
> > >
> > > > Hi Xen-Devel's
> > > >
> > > > Please see my note below regarding a serious issue where my clock
> > jumped
> > > > in dom0. I'm sending this through to the devel list as I haven't
> > managed
> > > > to glean any clear help from xen-users and the debian bug team are
> > > > unsure what could have caused this.
> > > >
> > > > Can you confirm if the kernel or xen controls the clock in dom0? I also
> > > > understand that this could be an underlying hardware issue but I have
> > > > another system on exactly the same hardware which hasn't had this
> > occur.
> > > >
> > > > Any advice on how to investigate further or ensure better clock
> > > > stability across dom0 and domU would be appreciated.
> > > >
> > > > Also is it correct behaviour for Xen to reboot an 2008 R2 HVM domU if
> > > > the time moves this much? My guess is that the domU crashed when the
> > > > time changed, and was thus rebooted automatically. Strangely the
> > Windows
> > > > 2003 server didn't get rebooted.
> > > >
> > > > If you need any more info to help please let me know.
> > > >
> > > > Thanks,
> > > > Mark
> > > >
> > > >
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@lists.xensource.com
> > > > http://lists.xensource.com/xen-devel
> > > >
> >
> > --
> > Mark Adams
> > Technical Manager
> > mark@campbell-lange.net
> > .
> > Campbell-Lange Workshop
> > www.campbell-lange.net
> > 0207 6311 555
> > 3 Tottenham Street London W1T 2AF
> > Registered in England No. 04551928
> >
next prev parent reply other threads:[~2010-10-11 10:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 11:16 Clock jumped 50 minutes in dom0 caused incorrect 2008 R2 domU time Mark Adams
2010-10-06 12:20 ` Clock jumped 50 minutes in dom0 caused incorrect 2008R2 " James Harper
2010-10-06 12:24 ` James Harper
2010-10-06 13:04 ` Mark Adams
2010-10-06 15:41 ` Clock jumped 50 minutes in dom0 caused incorrect 2008 R2 " Jeremy Fitzhardinge
2010-10-06 16:15 ` Mark Adams
2010-10-06 16:23 ` Jeremy Fitzhardinge
2010-10-07 14:04 ` Dan Magenheimer
2010-10-26 9:22 ` Mark Adams
2010-10-26 17:03 ` Jeremy Fitzhardinge
2010-10-26 21:54 ` Dan Magenheimer
2010-10-27 20:29 ` Dan Magenheimer
2011-01-04 17:00 ` Mark Adams
[not found] ` <AANLkTinDMfrR5u2k3kPJfJ9Z+op53v6ziEYnLEO03FkG@mail.gmail.com>
[not found] ` <20101008100907.GH30044@campbell-lange.net>
2010-10-09 2:15 ` wei song
2010-10-11 10:10 ` Mark Adams [this message]
2011-01-04 17:09 ` Ian Campbell
2011-01-04 17:22 ` Tim Deegan
2011-01-04 17:27 ` Ian Campbell
2011-01-04 17:28 ` Gianni Tedesco
2011-01-05 12:03 ` Mark Adams
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=20101011101015.GA17511@campbell-lange.net \
--to=mark@campbell-lange.net \
--cc=james.songwei@gmail.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).