similar to: Resolve "Time went backwards" problem by using jiffies as clocksource

Hi there, I''m trying to find out if theres anything wrong with using extra = "clocksource=jiffies" in domU configuration. It seems to fix some problems we''ve had with live migration. Thanks. -- Please remember that an email is just like a postcard; it is not confidential nor private nor secure and can be read by many other people than the intended recipient.

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

When booting 2.6.37 (from kernel.org) under Xen 4.1, there are apparently issues with timer interrupts being delivered to the dom0. Repeatedly causing an interrupt (for example, the ACPI power button) will allow the system to boot, as does adding "clocksource=jiffies" to the kernel command line. This is only present under Xen, not when booting the same kernel on real hardware. When boot

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

Hello xen-users ! I am coming for help concerning the just released 4.0 version. Install has worked rather well on my Debian Lenny. I have just had a few bugs for which I have found the answer looking around on this list. I have created a Debian Lenny domU which boots up just fine. The only problem is that I am unable to get a console prompt when using "xm console nameofdomU". I do see

Hi all: I am pretty new to xen, but ,thanks to you, I am learning fast :) I have a Dell Poweredge 2950 server running Debian Lenny as Dom0 named Asgard I have configured three DomU (Loki, Hermod and Thor) with DHCP support. All the machines (Dom0 and DomU''s) ask for an IP address to a DHCP server in the Office LAN. The DHCP server is configured to bind certain IP addresses to the Dom0

Hey, I''m experiencing strange problem: non-deterministic PV domain hang, only on some machines (with fast SSD drive). I''ve tried xen-4.1.0 and xen-4.1.1 with many kernels different kernels: VM: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.0.3 - vanilla 3.1 rc2 dom0: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.1 rc2 Result always the same: sometimes VM

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

I''m running Xen 3.2 on Debian 5.0 (Lenny) and am having trouble booting up a Debian Etch DomU. It hangs at the end when it says "Starting periodic command scheduler: cron." It''s just completely frozen. At one point I set it sit for a few hours and got back into the console and it said something about "time went backwards" but I used the

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

Hi All, Hope I''m not too annoying yet.. I have CentOS 5.4 running as Domain 0. I can create CentOS guest domains via network using virt-install. However that''s a bit slow, and I don''t want to repeat the download process again if I create new guest domains. So my questions: - Can I create guest CentOS domains using virt-install and specify a dvd iso image as its

Hi, I''m getting errors while live migrating a pv guest. I''m running Xen 3.4.3 on CentOS 5.5, DRBD 8.3.8.1 and OCFS2 1.4.7-1. The two servers are identical. After live migrating the Debian lenny PV guest(2.6.26-2-686-bigmem), it crashes, It prints this on console [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent printk recursion! [ 502.689357] BUG: recent

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''ve been using xen for a number of years now without issues, but now have a problem. First, the problem: I have a Windows Server 2008 Standard 64bit DomU, I''ve installed a number of applications, and it works quite well and runs stable for weeks at a time so far (ie, has never crashed yet). I tried to install QuickBooks

On 21/11/2015 00:05, Ming Lin wrote: > [ 1.752129] Freeing unused kernel memory: 420K (ffff880001b97000 - ffff880001c00000) > [ 1.986573] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x30e5c9bbf83, max_idle_ns: 440795378954 ns > [ 1.988187] clocksource: Switched to clocksource tsc > [ 3.235423] clocksource: timekeeping watchdog: Marking clocksource 'tsc'

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

On 20/11/2015 09:11, Ming Lin wrote: > On Thu, 2015-11-19 at 11:37 +0100, Paolo Bonzini wrote: >> >> On 18/11/2015 06:47, Ming Lin wrote: >>> @@ -726,7 +798,11 @@ static void nvme_process_db(NvmeCtrl *n, hwaddr addr, int val) >>> } >>> >>> start_sqs = nvme_cq_full(cq) ? 1 : 0; >>> - cq->head = new_head;

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:

Hi, I''m using Xen 3.2.1 with 2.6.26 as Dom0 and DomU in the x86_64 Versions/Builds as provided by Debian Lenny. I noticed that when using "jiffies" as clocksource, the resolution of the timers in a DomU is 4ms, e.g. ping shows only runtimes in 4ms increments [1]. When using "xen" the resolution is fine (didn''t make exact measurements) but xen is a no-go

I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now" can be