Quote:
Originally Posted by fwaggle
Code:
# [XEN] hypervisor wallclock nudged; nudging TOD.
I actually get that closer to every 30 seconds - so annoying I actually commented out the line that generates it in case it blew away something more pertinent in dmesg (in my notes, the notice is generated at sys/i386/xen/clock.c:344). As you said, the clock seems to be working fine, and I don't feel like tracking down the actual cause (I'm not near familiar enough with Xen/FreeBSD). 
|
Instead of commenting this line to halt these messages
Code:
# [XEN] hypervisor wallclock nudged; nudging TOD.
I decided to turn on the
independent_wallclock in the dom0 side.
For my Centos dom0 I did the following actions (no need to restart):
Code:
# DOMO(CENTOS)
echo '/bin/echo 1 > /proc/sys/xen/independent_wallclock' >> /etc/rc.local
echo 1 > /proc/sys/xen/independent_wallclock
I also turned on the relative mibs on my domU:
Code:
#add the following lines to /etc/sysctl.conf
machdep.disable_rtc_set = 1
machdep.indipendent_wallclock = 1
and voila' the messages stopped appearing in my terminal.
I run ntp to synchronize my domU clock. Perfect
This is a greatly working FreeBSD paravirtualized guest (I use the
tap:aio driver) in XEN and it consumes less memory than all other linux distros!