Date: Fri, 6 Dec 2013 13:09:39 -0500 From: Adam McDougall <mcdouga9@egr.msu.edu> To: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com> Cc: freebsd-xen@freebsd.org Subject: Re: FreeBSD 10-BETA4 r258899 PVHVM Xen clock -> 1970 on VM migration Message-ID: <20131206180939.GE5386@egr.msu.edu> 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 Fri, Dec 06, 2013 at 12:14:07PM -0500, 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. 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. The same happens with PVH it seems: FreeBSD pvhvm 11.0-CURRENT FreeBSD 11.0-CURRENT #0 2740cfb(master) Maybe as the VM is resuming after migration it can sync clock with the Dom0? Some of my servers run daemons that are sensitive to abrupt time changes (dovecot) which will purposely stop running if the time is altered by more than 60 seconds. Even on 9 I've seen the time jump by a few minutes or more after a migration.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131206180939.GE5386>