From mboxrd@z Thu Jan  1 00:00:00 1970
From: Niall Fleming <niall.fleming@webanywhere.co.uk>
Subject: Re: Time Change Issue Xen 4.1
Date: Thu, 01 Dec 2011 08:55:25 +0000
Message-ID: <4ED740FD.4070603@webanywhere.co.uk>
References: <4EBD5AA0.3090906@webanywhere.co.uk>
	<20111111183913.GA9283@phenom.dumpdata.com>
	<4EC0F20D0200007800060B7D@nat28.tlf.novell.com>
	<20111114180045.GA14517@phenom.dumpdata.com>
	<4EC16CA7.70901@goop.org>
	<20111116142604.GA7476@phenom.dumpdata.com>
	<4ED662B0.8060105@webanywhere.co.uk>
	<20111130222628.GE16651@andromeda.dapyr.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6540729954828015765=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20111130222628.GE16651@andromeda.dapyr.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, keir.xen@gmail.com, Jan Beulich <JBeulich@suse.com>, pbonzini@redhat.com, lersek@redhat.com
List-Id: xen-devel@lists.xenproject.org

This is a multi-part message in MIME format.
--===============6540729954828015765==
Content-Type: multipart/alternative;
 boundary="------------090609040509070806080705"

This is a multi-part message in MIME format.
--------------090609040509070806080705
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Cheers, at least I know that someone is still looking at it!

If someone could give me a general timeframe, like it'll be a month, 
before we fix it, or
two weeks or whatever, I just need to give my line manager something so 
he gets off my
case about it!


*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

On 30/11/2011 22:26, Konrad Rzeszutek Wilk wrote:
> On Wed, Nov 30, 2011 at 05:06:56PM +0000, Niall Fleming wrote:
>> Another week, and no response?
> I am sooo tempted to make a time joke :-)
>> ping?
> We are just swamped.<sigh>  Wish I had a better response,
> like: Try this patch, but not yet.
>
>> Please?
>>
>> *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
>>
>> On 16/11/2011 14:26, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Nov 14, 2011 at 11:31:51AM -0800, Jeremy Fitzhardinge wrote:
>>>> On 11/14/2011 10:00 AM, Konrad Rzeszutek Wilk wrote:
>>>>> Right. With those patches too (he used the xen-settime patch set which
>>>>> has it).
>>>>> The hypercall is done (and the do_settime gets called) and the results
>>>>> are saved
>>>>> in the RTC. And the wc_sec and wc_nsec are updated and propagated.
>>>>>
>>>>> The problem is that wc_sec and wc_nsec are only propagated to the
>>>>> existing guests.
>>>>>
>>>>> If you launch a new guest after the 'hwclock', the new guests
>>>>> retains the old wallclock time.
>>>> Existing (pvops) guests shouldn't see updated wallclock time, because
>>>> they never look at the hypervisor's wallclock after boot time.
>>>>
>>>> It's surprising that new guests don't see the updated wallclock though.
>>>> That sounds like a Xen issue.
>>> <nods>   That is what I think is happening here.
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel

--------------090609040509070806080705
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Cheers, at least I know that someone is still looking at it!<br>
    <br>
    If someone could give me a general timeframe, like it'll be a month,
    before we fix it, or<br>
    two weeks or whatever, I just need to give my line manager something
    so he gets off my<br>
    case about it!<br>
    <br>
    <div class="moz-signature"><br>
      <b>Niall Fleming BSc. (Hons)</b><br>
      Systems Administrator<br>
      Webanywhere Limited<br>
      <br>
      Phone: 0800 862 0131 Ext: 203<br>
      Web: <a class="moz-txt-link-freetext" href="http://www.webanywhere.co.uk">http://www.webanywhere.co.uk</a><br>
      <br>
      Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB<br>
      Registered in England with company number 4881346</div>
    <br>
    On 30/11/2011 22:26, Konrad Rzeszutek Wilk wrote:
    <blockquote cite="mid:20111130222628.GE16651@andromeda.dapyr.net"
      type="cite">
      <pre wrap="">On Wed, Nov 30, 2011 at 05:06:56PM +0000, Niall Fleming wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Another week, and no response?
</pre>
      </blockquote>
      <pre wrap="">
I am sooo tempted to make a time joke :-)
</pre>
      <blockquote type="cite">
        <pre wrap="">
ping?
</pre>
      </blockquote>
      <pre wrap="">
We are just swamped. &lt;sigh&gt; Wish I had a better response,
like: Try this patch, but not yet.

</pre>
      <blockquote type="cite">
        <pre wrap="">
Please?

*Niall Fleming BSc. (Hons)*
Systems Administrator
Webanywhere Limited

Phone: 0800 862 0131 Ext: 203
Web: <a class="moz-txt-link-freetext" href="http://www.webanywhere.co.uk">http://www.webanywhere.co.uk</a>

Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB
Registered in England with company number 4881346

On 16/11/2011 14:26, Konrad Rzeszutek Wilk wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">On Mon, Nov 14, 2011 at 11:31:51AM -0800, Jeremy Fitzhardinge wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">On 11/14/2011 10:00 AM, Konrad Rzeszutek Wilk wrote:
</pre>
            <blockquote type="cite">
              <pre wrap="">Right. With those patches too (he used the xen-settime patch set which 
has it).
The hypercall is done (and the do_settime gets called) and the results 
are saved
in the RTC. And the wc_sec and wc_nsec are updated and propagated.

The problem is that wc_sec and wc_nsec are only propagated to the
existing guests.

If you launch a new guest after the 'hwclock', the new guests
retains the old wallclock time.
</pre>
            </blockquote>
            <pre wrap="">Existing (pvops) guests shouldn't see updated wallclock time, because
they never look at the hypervisor's wallclock after boot time.

It's surprising that new guests don't see the updated wallclock though.
That sounds like a Xen issue.
</pre>
          </blockquote>
          <pre wrap="">&lt;nods&gt;  That is what I think is happening here.

_______________________________________________
Xen-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xensource.com">Xen-devel@lists.xensource.com</a>
<a class="moz-txt-link-freetext" href="http://lists.xensource.com/xen-devel">http://lists.xensource.com/xen-devel</a>
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
</pre>
      <blockquote type="cite">
        <pre wrap="">_______________________________________________
Xen-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xensource.com">Xen-devel@lists.xensource.com</a>
<a class="moz-txt-link-freetext" href="http://lists.xensource.com/xen-devel">http://lists.xensource.com/xen-devel</a>

</pre>
      </blockquote>
      <pre wrap="">
</pre>
      <blockquote type="cite">
        <pre wrap="">_______________________________________________
Xen-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xen-devel@lists.xensource.com">Xen-devel@lists.xensource.com</a>
<a class="moz-txt-link-freetext" href="http://lists.xensource.com/xen-devel">http://lists.xensource.com/xen-devel</a>
</pre>
      </blockquote>
      <pre wrap="">
</pre>
    </blockquote>
  </body>
</html>

--------------090609040509070806080705--


--===============6540729954828015765==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============6540729954828015765==--