Hi,

I'm running automake in a Xen domU (virtual guest system) with a inexact
kernel time source (not matching the hardware clock). It seems that
automake gets its time from the outer dom0 (host) system which is very
strange as this may differ from the time as reported by date:

$ rm Makefile.in
$ automake
$ stat Makefile.in; date
  File: #Makefile.in#
  Size: 24463           Blocks: 0          IO Block: 32768  reguläre Datei
Device: 12h/18d Inode: 5287779     Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1001/    jens)   Gid: ( 1000/    jens)
Access: 2010-04-30 10:52:43.000000000 +0200
Modify: 2010-04-30 10:52:43.000000000 +0200
Change: 2010-04-30 10:52:43.000000000 +0200
Fr 30. Apr 10:51:50 CEST 2010

Do you see that the timestamp of Makefile.in is 10:52:43 which is newer
than the current time (10:51:50)? I'm (nearly) sure that 10:52:43 is the
dom0 time. I also verified that the time in domU increases (no jumps
backwards).

Since make complains about "has modification time xy s in the future" I
don't trust the build system.

Please use the same time source as make does.

My info:
dom0 kernel: 2.6.18.8
domU kernel: 2.6.32.7
domU boot parameter "hpet=disable clocksource=jiffies nolapic acpi=off"

I tried many other clocksource values (such as "noapic clocksource=hpet, notsc")
but these seem to be very fragile and freeze my system with this domU kernel after
approximately one day.

Jens