Xen users - Jun 2006 - independent_wallclock=0, domU''s date is 16 mins behind dom0''s date

If independent_wallclock is set to 0, then that means running
''date''
in the domU should provide exactly the same answer as running
''date''
on dom0, right?

But this isn''t happening for us.  The domU''s are all running
minutes
behind the dom0 - in one case 16 minutes behind!

dom0$ date
Tue Jun 27 14:23:01 BST 2006

domU-a$ date
Tue Jun 27 14:15:56 BST 2006

domU-b$ date
Tue Jun 27 14:07:10 BST 2006

Is this a known bug?  How to fix it?

xen-3.0.0-20060202 (from mercurial).
Linux *** 2.6.15-xen #1 Fri Feb 3 10:40:46 GMT 2006 x86_64 GNU/Linux

Rich.

-- 
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com

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