Re: Time Change Issue Xen 4.1

[Niall Fleming <niall.fleming@webanywhere.co.uk>]

[-- Attachment #1.1: Type: text/plain, Size: 2531 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 4356 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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