" None of this makes much sense. It's certainly worth instrumenting
" SETTIME.
I added a printk in do_dom0ops. I saw the same 70 minute jump ahead in
the system clock in domain 0 when I shutdown domain 1. I did not get any
new SETTIME printk from xm dmesg. The only settime calls occured when
dom0 booted and ntp started. 
The client domains do not have CONFIG_XEN_PRIVILEGED_GUEST set and
nothing unusual is running on dom0. I start up xen0, then xenU, then
kill xenU and the xen0 date immediately jumps.
" No -- SETTIME effectively sets the dom0 system time, that Xen
" also exports to other domains.
So does that mean from the dom0 perspective that system time and hwclock
time should always be identical?
What hwclock says on dom0 did not change. Just what date says changed.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel