similar to: [PATCH] [HVM] Fix virtual apic irq distribution

Hi It seems that the Xen4.1''s HVM LAPIC clock for HVM fails to function normally, the guest OS cannot receive interrupts and Linux chooses to use PIT based TSC timer. Is there any change from Xen3.x with respect of this? Thanks - Zhefu _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Hey all, I was watching some logs on a domU today and i suddenly noticed that the timestamps were off by something on the order of 47 seconds. I was surprised because *I don''t* run independent wall clocks. I checked some other domUs and the "drift" was also very close to that of the first domU. I also checked another dom0, Here the domUs were "only" out of sync by

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

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

Hi, Sometimes, seemingly randomly, long-running Xen domains, using clocksource xen, have their clock shift by ~3000 or ~36000 seconds, often with the dom0 complaining about clocksource tsc. The number changes if the hypervisor is explicitly told to use clocksource=pit, but it still happens. It doesn''t seem to be particularly hardware-specific. See also http://bugs.debian.org/599161 I

It seems that VCPU system time isn''t monotonic (using 3.0.4). It seems it might be correlated to when a VCPU is switched across real CPUs but I haven''t conclusively proved that. But e.g.: { old = { time = { version = 0x4ec pad0 = 0xe8e0 tsc_timestamp = 0x22cc8398b7194 system_time =

Hi, I have a dual core athlon server and it is gaining 1 day every 2 days w/o time sync. Even with ntpd running, the time is not under control. I must put a very frequent cronjob of 'ntpdate' to keep the time under control. This creates big problems since winbind eventually stops working so my users can't access their data. Any ideas? -- Ugo -> Please don't send a copy of

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections

Hi, I have two installs of Xen 4.0.1 on Debian squeeze dom0s that occasionally skew the time by 3000 seconds. It is always 3000 seconds and it always affects all guests. Depending on the kernels in the guests they will say: tp0 kernel: [9339489.266542] Clocksource tsc unstable (delta = -2999660317697 ns) or perhaps the kernel doesn''t notice but ntpd does: ls0 ntpd[15009]:

I have a lot of this errors in my Centos stock 4.3 version in an Intel D945gnt motherboard with a Pentium D (dual core) If I disable apic in the grub.conf (apic=off) will I get a performance hit? Im running Asterisk on that machine. 40 is Received Illegal Vector 20 is Send Illegal Vector 60 means you're getting both errors at the same time. Basically it means that the APIC bus messages are

Hi All, I am trying to run guestfish inside an Ubuntu instance running in VirtualBox. I'm running into problems, and my first question, is this setup even possible? I compiled and installed libguestfs-1.8.4. Running libguestfs-test-tool fails with the following output. Would appreciate any advice, Chris new guestfs handle 0x8b77958 ===== Test starts here ===== LIBGUESTFS_DEBUG=1 library

Hello all, I thought I'd ask you guys about this one since I've had no luck from vmware forums/kb or google ... I have a centos 4.3 x86-64 (athlon64 with cool-n quiet enabled) with vmware server 1.0 installed and working beautifully with the annoying exception of my guest machines clocks (centos, ubuntu etc) run very fast. I've read the vmware white paper on guest clocks, tried

>I''ve been seeing these pretty regularly on a single-socket dual-core Athlon >system for the last couple of months, and only on Friday finally found time >to start looking into these. Besides the messages above, I also see hangs >in about every other boot attempt but only if I do *not* use serial output >(which makes debugging a little harder), and never once initial boot

Local APIC timer may stop at deep C state (C3/C4...) entry/exit. Initial HPET broadcast working in legacy replacing mode, broke RTC intr, so was bypassed. This patch add the logic that use platform timer (PIT) to reenable local APIC timer at C state entry/exit. Currently, only keep PIT enabled with 100Hz freq. The next step is trying to dynamically enable/disable PIT while needed, and give it

Maybe that is https://reviews.llvm.org/D30171. On Mon, Feb 20, 2017 at 11:16 PM, Dmitry Golovin <dima at golovin.in> wrote: > Hi, > > I can't build the Linux kernel anymore. With the latest kernel source and > latest LLVM and LLD (with D30163) I can only get this error message when > linking vmlinux: > > ld.lld: error: unable to move location counter backward >

Hi, I set "quota: fs:INBOX:noenforcing:mount=/var/spool/mail", but receive: "fs quota add storage dir = /home/pit/mail"... Why ? In fstab: /dev/mapper/mpath1p1 /var/spool/mail ext2 usrquota 0 0 In dovecot.log: Sep 06 15:02:00 pop3-login: Info: Login: user=<pit>, method=PLAIN, rip=192.168.3.10, lip=192.168.6.3, TLS Sep 06 15:02:00 POP3(pit): Info: Loading modules

Hi, # doveadm -Dv quota get -u pit doveadm(pit): Debug: auth input: pit system_groups_user=pit uid=500 gid=500 home=/home/pit doveadm(pit): Debug: Effective uid=500, gid=500, home=/home/pit doveadm(pit): Debug: Quota root: name=INBOX backend=fs args=mount=/var/spool/mail doveadm(pit): Debug: Quota rule: root=INBOX mailbox=* bytes=19922944 messages=0 doveadm(pit): Debug: Quota warning:

The custom_sched_clock hook is broken. The result from sched_clock needs to be in nanoseconds, not in CPU cycles. The TSC is insufficient for this purpose, because TSC is poorly defined in a virtual environment, and mostly represents real world time instead of scheduled process time (which can be interrupted without notice when a virtual machine is descheduled). To make the scheduler

The custom_sched_clock hook is broken. The result from sched_clock needs to be in nanoseconds, not in CPU cycles. The TSC is insufficient for this purpose, because TSC is poorly defined in a virtual environment, and mostly represents real world time instead of scheduled process time (which can be interrupted without notice when a virtual machine is descheduled). To make the scheduler

This is a note to let you know that I've just added the patch titled x86/hyper-v: Enable PIT shutdown quirk to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: x86-hyper-v-enable-pit-shutdown-quirk.patch and it can be found in the queue-4.19 subdirectory. If you, or anyone