kern/135008: FreeBSD-current/Xen timecounter jumps
Adrian Chadd
adrian at FreeBSD.org
Wed May 27 20:30:03 UTC 2009
>Number: 135008
>Category: kern
>Synopsis: FreeBSD-current/Xen timecounter jumps
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed May 27 20:30:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Adrian Chadd
>Release:
>Organization:
>Environment:
>Description:
The Xen DomU clock seems "off". Its not sync'ed to the value of the Dom0 clock (at least by "date" in both VMs.) "xen.independent_wallclock" is 0 in the DomU.
I triggered a weird clock drift by running ntpdate in the dom0 by running ntpdate.
>How-To-Repeat:
In the Dom0:
[root at hosting-2 adrian]# ntpdate 203.56.14.1
28 May 04:03:03 ntpdate[30489]: step time server 203.56.14.1 offset 50.619242 sec
[root at hosting-2 adrian]# date
Thu May 28 04:03:07 WST 2009
In the DomU:
freebsd1# date
Mon May 25 04:04:39 UTC 2009
freebsd1# date
Sun May 24 07:03:31 UTC 2009
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list