similar to: Clock jumps during live migration

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 everyone, While doing a live migration, Linux guests will frequently get stuck and become unresponsive, while the CPU utilization on the host for that guest goes to 100%. Sometimes they recover, and dmesg then shows that there's been a clock problem during the live migration: Clocksource tsc unstable (delta = 35882846234 ns) So the TSC did a jump of nearly 36 seconds. Migrations

Dear list(s), we are running a cluster of virtual machines on ganeti 2.15.2 on top of qemu-kvm 2.1.2. Hosts are Debian jessie (Kernel 3.16). We have big trouble with timekeeping on guests, no matter if these guests are lenny, squeeze, wheezy or jessie. Clock drifts heavily on some, others are fine. There is no obvious pattern on which guest this happens and on which not, but it seems the clock

Dear list(s), we are running a cluster of virtual machines on ganeti 2.15.2 on top of qemu-kvm 2.1.2. Hosts are Debian jessie (Kernel 3.16). We have big trouble with timekeeping on guests, no matter if these guests are lenny, squeeze, wheezy or jessie. Clock drifts heavily on some, others are fine. There is no obvious pattern on which guest this happens and on which not, but it seems the clock

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually exclusive with VCLOCK_HVCLOCK at run time. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 48

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support by adding hvclock_page VVAR. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 36 +++++++++++++++++++++++++++++++++++ arch/x86/entry/vdso/vdso-layout.lds.S | 3 ++-

I'm running VMware Server 1.0.6 on a CentOS 5.2 host and am having some clock difficulties. Host OS is x86_64 running on 1.9 GHz AMD Sempron, nVidia chipset. Guest OS's are 32-bit FreeBSD (clock works fine after disabling ACPI, setting the clock source to the PIT, and running the guest tools), WinXP (unknown clock status), and i686 CentOS 5.2 (here is the problem). I've tried pretty

All, There are drbd82 RPMS for CentOS-4 and CentOS-5 (i386 and x86_64) for testing here: http://people.centos.org/~hughesjr/drbd/ These are designed to be able to live in the same repository as the current STABLE versions. These RPMS are designed as CONFLICTS and not upgrades as there may be some manual actions to upgrade, especially on CentOS-4. Here is an article on the upgrade process:

Hi everyone: Just a follow up on the fast clock issue: "Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?" There is no cpufreq directory under /sys/devices/system/cpu/cpu0; all I see is "cache" (dir), "crash_notes" (a file) and

Thought this would be interesting for some people: Version 8.0.6 of DRBD comes with a nice script that adds support for a config like disk = [ ''drbd:r0,hda1,w'' ] This supports migration and live migration without having to take care of drbd yourself. Really nice feature. Read changelog on 8.0.6 on: http://svn.drbd.org/drbd/branches/drbd-8.0/ChangeLog Regards Dominik

Hi all ! Is anyone using xen kernel + drbd 8.2.4 ? I don''t know exactly if my problems come from the addition of the two packages, or from drbd 8.2.4, but I encoutered kernel panic 2 times when trying to do first sync of drbd resources :s Cheers, -- Serge Dewailly _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

I'm using KVM, libvirt and DRBD to come up with a custom mirroring and live migration setup. I have two servers, each running KVM and libvirt, and both using DRBD to mirror guests (which are stored on raw DRBD partitions). If I shut down a guest on one, I can easily get it up and running on the other without issue. I have run into some file system corruption trouble if I try to do a live

Hi all, I want to do live migration of domains using DRBD block devices for synchronisation between the two Xen hosts with Xen 2.0.7. I''ve written a script ( block-drbd ) which binds / unbinds DRBD devices for specific domains (with DRBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD

Hi, I want to combine all the above mentioned technologies. The Linbit pages warn not to use the drbd: VBD with HVM DomUs. This page however: http://publications.jbfavre.org/virtualisation/cluster-xen-corosync-pacemaker-drbd-ocfs2.en (thank you Jean), simply puts two DRBD devices in dual primary mode and starts Xen DomUs while pointing to the DRBD devices with phy: in the DomU config files.

Hi list, I have a problem with this stuff, i read many documents about it but i would like to know if anyone have got to resolve the problem. The point is that my vm has the clock unsynchronize, i tried many things and it seems that its work fine but im not sure. Now im using ntpd to synchronize the time but im not trust on it because it didnt work before. First, i tried the jiffies on

Well, to the clock being fast work around, I kind of found a way to work around it for now... 1) use a distribution that supports VMI (VMware's paravirtualization) 2) enable VMI paravirtualization support in VMware Workstation 6 VM's profile 3) use vmi-timer as the clocksource (as opposed to pit, acpi_pm, etc.) 4) CPU must be constantly at maximum frequency For 1), I use Ubuntu 7.10 For

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

Hello all, When I live migrate my centos guest from node1 to node2, I can ping the guest, but on node 2 if i do: xm console guest01 , I am not able to access it. When migrating back to node1 , I can access the console. What I noticed is, to access the console, the node ''s drbd resource/disk needs to be in primary status . Is it typical or only I am having this problem. Is there any

> From: Thomas Gleixner [mailto:tglx at linutronix.de] > Sent: Saturday, February 11, 2017 02:02 > ... > That's important if the stuff happens cross CPU. If the update happens on > the same CPU then this is a different story and as there are VMexits > involved they might provide the required ordering already. But I can't tell > as I have no idea how that host side

> From: Thomas Gleixner [mailto:tglx at linutronix.de] > Sent: Saturday, February 11, 2017 02:02 > ... > That's important if the stuff happens cross CPU. If the update happens on > the same CPU then this is a different story and as there are VMexits > involved they might provide the required ordering already. But I can't tell > as I have no idea how that host side