Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Dec 2013 18:36:17 +0100
From:      =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>
To:        Adam McDougall <mcdouga9@egr.msu.edu>
Cc:        freebsd-xen@freebsd.org
Subject:   Re: FreeBSD 10-BETA4 r258899 PVHVM Xen clock -> 1970 on VM migration
Message-ID:  <52A20B11.7010101@citrix.com>
In-Reply-To: <20131206171407.GD5386@egr.msu.edu>
References:  <20131206171407.GD5386@egr.msu.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On 06/12/13 18:14, Adam McDougall wrote:
> Hello,
> 
> I noticed on recent (PVHVM) builds of FreeBSD 10 that I randomly lose the
> proper date/time when I migrate my VM from one XenServer to another in the
> pool.  I was intending to reproduce a much smaller time difference I've seen
> on 9 but this was a much bigger jump so I started concentrating on the big
> jumps.  When I migrate my VM back and forth between two servers, it will
> randomly jump to a date in 1970 or 1969.  Continued migrations often bring
> the proper date/time back, but there is not a strong pattern.  The 1970
> comes and goes.  I could not reproduce this kind of jump on 9.  This happens
> on XenServer 6.0 and 6.2.

Hello,

Thanks for testing, there were some bugs in Xen regarding the migration
of PVHVM guests, the one that comes to mind, and that could cause this
kind of time disruption is:

http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01110.html

The patch should be present in at least Xen 4.3, not sure about previous
versions. Is there anyway you could try this on a recent Xen version (4.3)?

> I will take a stab at trying PVH time permitting,
> but since 10.0 will ship with PVHVM it seems appropriate to try to fix it
> if possible.  Let me know if there is more testing or information gathering
> I should do.  Thanks.

Xen 4.4 will be the first version to support PVH, which has not yet been
released, and right now doesn't support migration. If you could try a
recent version of Xen that contains the mentioned patch it will
certainly help diagnose it (or at least make sure it's caused by this
issue).

Roger.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52A20B11.7010101>