[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/146924 Title: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen To manage notifications about this bug go to: https://bugs.launchpad.net/xen/+bug/146924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
** Changed in: xen Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/146924 Title: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Well, it's certainly valid and affects current production environment for us. We know the clearest solution is to use newer xen and kernels, and we are using the jiffies workaround, but it's not clear there isn't a better solution. >From what I've read, Jiffies are in fact obsolete and can be problematic, so this problem is certainly very old. $0.02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/146924 Title: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I guess this can be closed since it's so old it's probably no longer valid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/146924 Title: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
i found this searching for a similar problem on Debian with xen. in my DOMU a lot of messages like this, not usable at all. clocksource/0: Time went backwards: Then i found a solution, change the clock source form xen to jiffies. Problem started after moving DOM0 from kernel 2.6.18 to 2.6.26 in the xen config file for DOMu add "clocksource=jiffies" , and the problem was gone. extra= "xencons=tty clocksource=jiffies" -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
It's a "mis"-implementation of the Xen kernel patches which typically are not available for the most recent kernels. Use a RedHat Xen kernel, this is the only one I've found to work. 2.6.21 is the one I'm using, this is 100% reliable. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Any news on this one ? Just found a statement on the internet that this is some kind of XEN bug when using multicore or multiple CPUs. I am trying to run it on a dual P3 board... :/. And same problem on debian and CentOS! -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Not really. a. There's a whole list of problems I've come across and have posted details of on different threads b. As of 3 weeks ago on Hardy, it wasn't fixed (which was last time I tried it) -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
It sounds to me like this bug report is actually two different, but possibly related, bugs. The first bug is time arbitrarily going backwards on 2.6.22, which I think is fixed when using a 2.6.24 and later domU. The second bug is a problem with saving/restoring domUs. Does anyone agree? -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I think it could be taken as a general comment prompted by another posting on this thread. (which is heading for it's first anniversary) IMHO Xen should be taken out of the Repo's (for now) , Ubuntu's version simply does not work. People read the press and see "Xen is great, Xen is stable", then install Ubuntu Xen and see critical problems which look for all the world like the may be problems with Xen itself. [incidentally, this is *not* or certainly has not been the only serious problem with Ubuntu Xen] Xen does not need this sort of press .. and I'm sure Ubuntu can live without it too. You're going to say "how will it get fixed if it's not available for people to try?" .. normally I'd agree, however given the speed at which it's being worked on, I really do think it should be taken aside until it can be made to work. Note; I don't have any connection with Xen or Ubuntu other than being a heavy Xen / Ubuntu user. I wasted s much time trying to make Ubuntu/Xen work after thinking I must be at fault being convinced nothing so buggy would ever get released. At the *very* least it needs a big warning label saying "do not use in production environment due to known issues" !! -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
@Gareth: I'm not following you here. Is this a statement to my note that there is no Xen pre-release version of 2.6.27 for Intrepid? or a general comment? Leann requested (bulk I might add, as I got this same request for other Xen tickets I have open), that we test the new kernel for this issue - however, since there is no Xen kernel available, we can't test it yet. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
So .. yes it's a Xen issue, but it's Ubuntu specific, i.e. Ubuntu's Xen kernel "doesn't work". I'm running 30 VM's, all had the problem on various Ubuntu kernels. I've not had the problem in 8 months since switching the kernel out for the Redhat/Xen kernel. .. so if you think Xen are every going to worry about this, not least as Ubuntu chose another hypervisor as standard, I would think again. I'm finding Xen 3.2 to be pretty damn reliable, I'd be interested to hear how the Ubuntu supported hypervisor performs .. (which one did they go for, kvm ?) -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Leann; This is a Xen issue - I was unable to find a Xen version of the linux- image-2.6.27- tree in hardy or Intrepid. Regards, Jay -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
@James Blackwell: I can recreate it with a newer kernel. See my previous comment: 2.6.24-19-xen doesn't work. My domU and my dom0 are all running the same kernel. I don't use a ramdisk. To recreate the problem, just do a save-pause-restore of the domU. Ciao! -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
This bug seems to be fixed by moving the kernel and the ramdisk for domUs up to 2.6.24-17. Can anyone else verify this? -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
This is still a problem as of 2008/8/8: * Ubuntu 8.4.1 Hardy Heron * Xen 3.2.0 * Dom0 & DomU kernel: 2.6.24-19-xen #1 SMP Sat Jul 12 00:15:59 UTC 2008 x86_64 The workaround for this is to change your setup to not to save/restore, but to instead reboot. This is done by altering dom0:/etc/defaults/xendomains and changing the value of XENDOMAINS_SAVE to the empty string. Ciao! -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I just thought as to why it "just started" I had corrected a bug in the xendomains rc script that had two cuts - I'll have to do an upgrade and then file another bug report for that later. I'm assuming that my domU's are now suspending on my reboots, and over time the clock went backwards on the suspended domU. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Confirmed on 2.6.24-17-xen on domUs, no issue on dom0 as far as I can see. Whats weird, I was running fine for a long time, however, it just started today after about a month of no issues. Could it be a clock sync issue where if the clocks are out by X it causes the time to stop? -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I'm seeing this both on dom0 and domU with ...-19.34. As far as I can tell, there's no relation between seeing this on dom0 and domU. However, there seem to be no side-effects. (this is an amd64 install on both dom0 and domU and xen 3.2.1 from debian) dom0: Jun 26 14:02:06 quark kernel: [187781.880995] clocksource/0: Time went backwards: ret=ac186aa11cf0 delta=-36099370 shadow=ac183af22f78 offset=31d8212e domu: Jun 25 17:02:03 suzy2 kernel: [111734.752716] clocksource/0: Time went backwards: ret=6754298ec3ef delta=-64141945 shadow=675421edd381 offset=b7493a5 -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I'm seeing this sort of problem with 2.6.24 dom0 and 2.6.22 domU, both of which are running hardy. Sometimes, multiple domUs fail, other times, just one domU. In the most recent failure, ntp was running on both dom0 and domU, which should disprove that ntp causes the problem. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Just to let you know: still same problem after upgrading to 8.04beta and 8.04. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Gareth, me too. I just tried (on my domU to fool around with) the latest rawhide kernel-xen. Runs just fine (for the last 30 or minutes and there's a lockdep warning early in dmesg -- so there's not much trust). [EMAIL PROTECTED]:~$ uname -r 2.6.25-0.18.rc8.fc9.x86_64.xen -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
The former, Ubuntu with a RH kernel .. the only issue I see is unwanted warning messages when using rsync .. apparently there is a discrepancy between kernel features available on the Ubuntu and RH kernels that rsync doesn't handle very well .. and one unavailable sysctl entry which gives an entry on startup, which is easily corrected. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Just to be sure: you are using the Redhat kernel with ubuntu and ubuntu doesn't bother about it (this is what I think). Or are you trying to tell me to install a Redhat system ? -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I have a solution I'm employing on 26 Xen instances. It's called "use the Redhat 2.6.21 kernel which works!" The Ubuntu Xen kernel has SO MANY problems it really isn't even worth looking at. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Btw.: last entry in the xen-tools logs for the DomU while debootstrap: I: Configuring mktemp... -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Same problem here :/. I am just trying to install my first DomU (following http://www.howtoforge.com/ubuntu-7.10-server-install-xen-from-ubuntu-repositories) and when calling "xen-create-image ... blah blah" the screen is flooded with the "Time went backwards" messages while debootstrap. No usasble DomU image gets installed and so I can't start and edit anything within the DomU. Furtheremore these messages do show up (plenty of them) in the log of the Dom0 (at least when calling "dmesg -c" it always re-appears). No other workaround known yet ? -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
** Tags added: xen -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Myeah, but that clock=jiffies thing still makes me feel uneasy when running it in production.. I will stay with official xensource kernels until they update the kernel they build at ( 2.6.18 atm ), which will hopefully be soon because it would be welcome by now :) For domU kernels, i am waiting for paravirt_ops to be included in the mainline x86_64 kernel. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Hi Guys, I've been doing a LOT of work on Ubuntu XEN over the last couple of weeks and now have two live stacks which are staying up and doing a lot of work. (hopefully) I've found there are three fundamental things you need to make clocks reliable and not have the system pause under load, these are; a. in the Dom0's grub menu.lst, add "dom0_mem=xxx" (where xxx is for example 512 for 512M) b. add "xen.independent_wallclock=1" to /etc/sysctl.conf in each DomU c. add "clock=jiffies" in the DomU's .cnf file in the "extra" section This makes a huge difference to overall usability. hth Gareth. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
> Actually this isnt fixed for hardy because there is no dom0 kernel for hardy yet. Is there already some planning, when there will be a kernel available ? I would to configure some servers but hardware is to new to use an 2.6.19 kernel. Tom -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies . ** Changed in: linux-source-2.6.22 (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Actually this isnt fixed for hardy because there is no dom0 kernel for hardy yet. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Henrik, will this also work for a Dom0, or is the -generic kernel only for DomUs? If it can be used as a Dom0, I would set up a box and test it... Ciao Martin -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so): 1) edit the file /etc/apt/sources.list and add the following line: deb http://archive.ubuntu.com/ubuntu hardy main restricted 2) sudo apt-get update 3) sudo apt-get install linux-image-2.6.24-1-generic 4) reboot and select the new kernel from the grub menu After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance! ** Changed in: linux-source-2.6.22 (Ubuntu) Importance: Undecided => Low ** Tags added: hardy-kernel-candidate -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
If your hardware permits it, and opensuse still has the 2.6.18/2.6.19 xen kernel, try it. Since I went from 2.6.22.14 to 2.6.19-4 on ubuntu, all works well. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I have a similar problem on opensuse 10.3/xen3.1 (up to date) running on dell PE860 (mono xeon 3230 quad core, 8GB ram, lsilogic raid0 sas 15K), my 2.6.22.12 xen X64 dom0 kernel freeze under parallel iperf loopback heavy load (with or without eth0/1 tg3 module loaded, and with or without xend running). It takes about 15min to freeze. This bug does not appear in non xen kernel. I really don't know what to do... -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Same problem for me! :( DomU's are not affected, but Dom0 starts to loose performance: It tak a lot of time to open application (even console), later the TCP/IP connection get lost. The problem starts after I start HVM guest. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
** Changed in: xen Status: Unknown => Confirmed -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
** Also affects: xen Importance: Undecided Status: New ** Changed in: xen Importance: Undecided => Unknown Bugwatch: None => Xen Bugzilla #195 Status: New => Unknown -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I got the same Problem with Xen version 3.1.0 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) Fri Oct 12 16:26:34 GMT 2007 Ubuntu Gutsy. xm dmesg shows (XEN) System RAM: 2015MB (2063676kB) (XEN) Xen heap: 13MB (14228kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 15:3 APIC version 16 (XEN) Processor #1 15:3 APIC version 16 (XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3117.260 MHz processor. (XEN) HVM: SVM enabled (XEN) CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ stepping 03 (XEN) Mapping cpu 0 to node 255 (XEN) Booting processor 1/1 eip 9 (XEN) Mapping cpu 1 to node 255 (XEN) AMD: Disabling C1 Clock Ramping Node #0 (XEN) CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ stepping 03 (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Platform timer is 25.000MHz HPET (XEN) Brought up 2 CPUs (XEN) *** LOADING DOMAIN 0 *** -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I "fixed" :-/ this by not using the 2.6.22 but the 2.6.19-4 kernel. This is of course no solution, especially not for people having very new hardware. But I'll stay subscribed and will help testing if fixed packages are made available. Ciao Martin -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I must say i switched to my own home-grown kernels last week.. Problem solved :) -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I was also experiencing this problem. Is anyone here running gutsy as a guest as well as the host? Gutsy has been hanging on boot.. it dosnt spit out the clocksource errors but hangs on the syncing clock part. My dapper guest shows the clock source errors.. though the jiffies seem to have remedied this.. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Thanks Bart, setting clocksource to jiffies fixed "Time went backwards" error in my domU! However, domU clock still goes back if I reboot dom0 (domUs are saved and restored by /etc/init.d/xendomains script). But this time, nothing freezes, no kernel messages, just 'date' command and timestamps in the log files show the wrong time. How long the clock goes back is related to uptime of dom0 (or maybe hypervisor). When I reboot dom0 when uptime is 15 minutes , and domU restores at 30 seconds of uptime of rebooted dom0, the clock inside domU is 14m30s behind. So I tried setting independent_wallclock to 1 too. And now the clock does not goes back anymore! Instead, clock is suspended while domU is suspended. This is far better than clock going back. Running ntpd in domU fixes the clock. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Great, another bit of hope :) I changed to "jiffies", too. Let's pray this helps me, too ... Ciao Martin -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Euh, i just might have found the something interesting.. This morning, i wanted to check my mails ( which run in a domU ). I noticed i couldn't get to it, "Unable to connect", as usual.. But i had cacti open, which could read snmp from the server just fine. I logged in through SSH, and noticed that the date was set to "Fri Dec 22 22:49:54 CET 2226", and not going forward anymore. The clock had stopped. In the meantime, /var/log/messages was spewing messages like this: [134918.952935] clocksource/0: Time went backwards: delta=-6917269600674797899 shadow=134918109266738 offset=843667158 [134923.954592] printk: 1157408 messages suppressed. [134923.954606] clocksource/0: Time went backwards: delta=-6917269595673126078 shadow=134923109294656 offset=845310074 [134928.952308] printk: 1154382 messages suppressed. [134928.952323] clocksource/0: Time went backwards: delta=-6917269590675409336 shadow=134928109321066 offset=84253 I decided to change something to see if it works, so i did: cat /sys/devices/system/clocksource/clocksource0/current_clocksource, which showed "xen" as usual. I then did echo "jiffies" > /sys/devices/system/clocksource/clocksource0/current_clocksource, which instantly made my clock run again, and stalled programs revived. I saw my webmail ( which was still hanging all the time ) spring to life, along with my previously entered reboot command.. Does this narrow down the search to the solution? Kind regards, Bart -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
This morning, it happened again: Oct 11 12:44:01 beelzebot kernel: [80251.276057] printk: 4 messages suppressed. Oct 11 12:44:01 beelzebot kernel: [80251.276062] clocksource/0: Time went backwards: delta=-99319 shadow=80251276002078 offset=59391 Oct 12 15:48:10 beelzebot kernel: [177694.609813] Setting mem allocation to 4063232 kiB Oct 12 15:48:10 beelzebot kernel: [177694.626366] Setting mem allocation to 4063232 kiB Oct 13 06:16:29 beelzebot kernel: [229782.674001] clocksource/0: Time went backwards: delta=-6934879990527637305 shadow=229782673990236 offset=8063 May 8 01:39:03 beelzebot kernel: [229782.674007] clockso4605907 May 8 01:39:03 beelzebot kernel: [247527.670711] printk: 4 messages suppressed. May 8 01:39:03 beelzebot kernel: [247527.670713] clocksource/0: Time went backwards: delta=-6934862245530924326 shadow=247526746101540 offset=924610392 May 8 01:39:03 beelzebot kernel: [247527.670715] printk: 4 messages suppressed. May 8 01:39:03 beelzebot kernel: [247527.670717] clocksource/0: Time went backwards: delta=-6934862245530919819 shadow=247526746101540 offset=924614874 May 8 01:39:03 beelzebot kernel: [247527.670720] printk: 4 messages suppressed. May 8 01:39:03 beelzebot kernel: [247527.670722] clocksource/0: Time went backwards: delta=-6934862245530915364 shadow=247526746101540 offset=924619332 May 8 01:39:03 beelzebot kernel: [247527.670724] printk: 4 messages suppressed. . . shutting down on of the DomUs reliably crashes the whole box :( -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Yep, I played around with different settings, too. Enabling/disabling ACPI or HPET did not make a difference. And using "noapic" breaks the arcmsr driver for our RAID controller. The box went fine for a few days now, but there's already one of these "time went backwards" messages in the syslog, so i'm expecting the lock up soon. -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
