Re: [Xen-devel] Clock jumped 50 minutes in dom0 caused incorrect 2008 R2 domU time

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

Which ever one of you started it: Please don't top post.

> 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.

On Mon, 2010-10-11 at 11:10 +0100, Mark Adams wrote:
> I can try this, but can you please confirm what these options do?

viridian=1 turns off support for the Hyper-V virtualisation
compatibility layer. Not many of these are actually supported but AFAIK
one or two are and can affect the behaviour of Win2008 (although you
would hope it was for the better!)

According to xmexample.hvm: tsc_mode : TSC mode (0=default, 1=native
TSC, 2=never emulate, 3=pvrdtscp).

Timer mode is apparently "0=delay virtual time when ticks are missed;
1=virtual time is always wallclock time".

To be honest I'm not entirely sure that those last two actually mean in
practice. Hopefully someone who understands this stuff will weigh in.

Ian.



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