similar to: xen backwards

I''m using a NetBSD 3.1 dom0 with Xen 2.0.7 (so far as I know, the latest supported combination for the NetBSD platform). Linux domUs have their logs fill with messages like this: May 8 02:01:39 debian kernel: Timer ISR: Time went backwards: -316000 131542680000000 9684000 131542690000000 May 8 02:01:39 debian kernel: Timer ISR: Time went backwards: -277000 131542680000000 9723000

i've dovecot --version 1.2.5 hg log | grep changeset | head -n 1 changeset: 9407:a3e16df805e3 in my logs, i'm seeing ... Oct 05 16:51:40 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 05 17:07:22 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now

Hello gurus, I have two physical xen hosts and when I migrate a domU from one host to another, I get many of this error from domU kernel: clocksource/0: Time went backwards: delta=-3536123661 shadow=686019823475 offset=281887188 Sometimes domU time stalls and network stops working, but other times it gets working again. The two hosts are using different platform timer source:

Dunno, your email provider doesn't want to talk to me, heh, screw them :) They claim i'm on an rbl, no rbl checks verify this. Even tried to submit a request using their website, but it's broken and doesn't work (http://postmaster.ausics.net/pmg.php) ----- Forwarded message from patrickdk at patrickdk.com ----- Date: Tue, 06 Oct 2009 23:31:37 -0400 From: Patrick

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have

Dear fellow Xen''ers! I''m having a problem with my new Xen-enabled colocation server.. I hope ( at least ;) ) one of you guys know how to fix this problem.. For a certain amount of time ( 1-2 days ) the domU runs fine.. until the console starts spitting out messages like these: [80182.004456] clocksource/0: Time went backwards: delta=-6917292717540055641 shadow=80182004054805

Hi All, I''m new to Xen and... Happy New Year! After restarting dom-0, my dom-u prints this in console once every second, [55082.616234] __ratelimit: 1503 messages suppressed [55082.616234] clocksource/0: Time went backwards: ret=380ab26c53a I resolved this by following the instructions in "http://wiki.debian.org/Xen", which is basically changing clocksource to

I have a high end IBM system with 4 HT CPUs, am running xen-unstable with only Dom0 active, and I get lots of "Timer ISR/n: Time went backwards" messages. This is a short segment from dmesg: Timer ISR/1: Time went backwards: -259000 4465110000000 9741000 4465120000000 Timer ISR/6: Time went backwards: -224000 4465110000000 9776000 4465120000000 Timer ISR/6: Time went backwards: -159000

Changeset 6902 Sep 18 13:37:23 inyoureyes kernel: 1: 5077390000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards: delta=-34786504 cpu_delta=15257914 shadow=5076506780929 off=938478409 processed=50770Sep 18 13:37:23 inyoureyes kernel: 0: 5077480044418 Sep 18 13:37:23 inyoureyes kernel: 1: 5077430000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards:

All, Attached is a patch from Prarit Bhargava, who is not subscribed to the list (but CC''ed). His description follows: Add "Warning" to the "Time went backwards" message. Most QA groups (if not all) grep for specific messages in the syslog such as "Error", "Warning", "Oops". Time went backwards is a key error which can result in

While digging through the time code, I found something very strange in do_settime: x = (secs * 1000000000ULL) + (u64)nsecs - system_time_base; y = do_div(x, 1000000000); spin_lock(&wc_lock); wc_sec = _wc_sec = (u32)x; wc_nsec = _wc_nsec = (u32)y; spin_unlock(&wc_lock); The value "x" appears to be the number of nanoseconds, while the value

Hi, first of all, my name is Karsten and I am fairly new to xen. A former colleague of mine has set up a xen dom0 with 4 virtual machines runnig on it. A few months ago this colleague left the company. Last week our office Building has been hit by a lightning wich resulted in an power blackout. After the power went back again, the system booted and all but one of the virtual machines went

I upgraded form Xen 3.1.2 to Xen 3.2.1. it works perfectly the only BIG problem is that on the domU clock is exaclty 2 hours backward the dom0, and it starts with a hwclock 2 hours back. hwclock on dom0 is correct dom0 is CentOS 5.1 and domU is XentOS 5.1 xen 3.2.1 compiled from rpm src any hints ? thank you very much Riccardo _______________________________________________ Xen-users

I think I may have fixed my memory leaks, and it may be that it was nothing to do with xen... the machine has been up for 10 days now which is the longest it has lasted in quite a while. I changed the way the bridges and vlans worked together, previously I had it configured thus: trunk = renamed Ethernet interface br0 = bridge of trunk and any domU I wanted on vlan1 br0.2 = vlan 2 on trunk br1 =

Signed-off-by: Dor Laor <dor.laor at qumranet.com> --- hack-module.awk | 28 +++++++++++++++++++++++++++- 1 files changed, 27 insertions(+), 1 deletions(-) diff --git a/hack-module.awk b/hack-module.awk index 580090b..bd63fb9 100644 --- a/hack-module.awk +++ b/hack-module.awk @@ -45,8 +45,8 @@ print " return 1;"; print " }"; print ""; -

Hello, I have recently finally gotten xen working on a Dual Core Althlon64 4200, 4GB RAM, 3ware 9500 4x160GB SATA RAID 10, but after compiling xen with 3ware support, xen does start up but i get many (to many to even access the console) of these errors: Time ISR: Time went backwards: -xxxxxxxx xxxxxxxxxxxx xxxxx xxxxxxxxx where the x''s are replaced with different numbers each time.

I continue to see occasional ''time went backwards'' messages on 3.0-testing on larger systems. Is anyone else seeing such? Have there been any improvements to -unstable that haven''t been moved over? If so, can anyone point out the respective changesets? Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I''ve been testing Xen 4.0.1 with kernel 2.6.34.5 + http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.34-4.tar.bz2, and one of the things that I noticed immediately is there are two problems with tapdisk and this combination. First, the syntax "disk = [''tap:tapdisk:aio: ..." no longer works. When tested with HVM domU, it boots, but there was no disk

================== STATUS ================== I do the heavy load test of create/destroy. CREDIT scheduler(cshed_schedule) checks BUG_ON(!vcpu_running) at the end of code. It makes error. The reason is that atomic_inc(&v->pausecnt)@vcpu_pause() is called without lock. (spin_lock(&schedule_data[cpu].schedule_lock)) This lock-less "pausecnt" makes vcpu_running state changing

http://bderzhavets.wordpress.com/2008/10/17/install-opensuse-11-domu-at-xen-33-centos-52-dom0-via-local-http-server-all-64-bit/ --- On Sun, 9/21/08, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Attempt to create OpenSuse 10.3 PV DomU at Xen 3.3 CentOS 5.2 Dom0 via pygrub To: xen-users@lists.xensource.com Date: Sunday,