[Xen-users] domu's time is frozen after change dom0's time backward

["Hongming Xiao" <xiaohm@xxxxxxxxx>]

All,

Hope this is the right list to post my question.

I noticed that once I changed dom0's time backward, domU's time will
be frozen. Here is the step to reproduce the problem.

a) sync domU's time with dom0 by running following command in domU

# echo 0 > /proc/sys/xen/independent_wallclock

b) Verify domU's time is synced to dom0's

In dom0:
# date
Thu Sep 25 12:10:03 EDT 2008

In domU:
# date
Thu Sep 25 12:10:04 EDT 2008

c) Change dom0's time backward for 1 hour

In dom0:
# date 0925110000

In dom0:
# daten
Thu Sep 25 11:00:02 EDT 2008

d) Then, domU's time is frozen at the time we made change to dom0's time.

In domU:
# date
Thu Sep 25 12:11:00 EDT 2008
# date
Thu Sep 25 12:11:00 EDT 2008
# date
Thu Sep 25 12:11:00 EDT 2008
....

domU's time can be unfrozen by making domU's time older than dom0's,
no matter by changing dom0 or domU's time.

In domU: (change domU's time backward)
# date 0925100000

In domU:
# date
Thu Sep 25 11:01:00 EDT 2008


Question:

Appearently, Xen will stop syncing domU's time if dom0's time is older
than domU's.  Is it possible to configure Xen to let it sync domU's
time to dom0's (not matter what dom0's time is)?

Thanks in advance,
Bill Wei

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