kvm version: 71
host: rhel51 2.6.18-92.1.6.el5 64bit 16G RAM, 8CPU
guest: rhel51 2.6.18-92.1.6.el5 64bit, 3.5G ram, 2 CPU
guest run as: qemu-system-x86_64 $DEVICES -m $MEM -smp $CPUS -net nic,macaddr=$MAC,model=e1000 -net tap,script=./ifup -nographic -daemonize
in the guest executed two consecutive gettimeofday (boost::ptime in fact), the latter returned time smaller than first
(2008-Jul-22 16:34:15.477000, 2008-Jul-22 16:34:15.470000)
I'm sure no time change was made(like rdate or ntpdate) on neither host or guest. No time-releated options were passed to kernel(host or guest)
Any workaround?
Logged In: YES
user_id=2019182
Originator: NO
Is the host an AMD or an Intel system?
Logged In: YES
user_id=996150
Originator: YES
Intel quad-core xeon.
Hi
Trying to catch up on the old bugs.
Do you still experience this problem with a current version of KVM? The problem should
be resolved in upstream, in particular if you run with kvmclock.
Would you please close this bug if the problem is no longer there?
Thanks,
Jes
I've give up on this a long time ago and switched to ESXi - sorry.