similar to: Follow-up on Fast clock under VMWare

Hi everyone, I have been struggling with having the clock of Linux VM's (including CentOS 4.6 and 5.1) running very fast under VMWare, no matter what I have tried. My platform: - AMD Turion X2 TL-60 - AMD 690 chipset with integrated Radeon x1250 (probably doesn't concern in this case) - Windows Vista Ultimate x64, all Windows Update patches loaded (no SP1 yet) - 4GB RAM - VMWare

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

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

hello, a big time drift appears along time on a guest VM (time is going too slow on the guest). here the setup: ~ physical machine ~ Centos 6.0 x86_64 time set with ntpd Intel(R) Xeon(R) CPU X5650 /proc/cpuinfo shows the "constant_tsc" bit. ~ guest OS ~ Centos 6.0 x86_64 /proc/cpuinfo : processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13

I use a CentOS5.8 server with KVM. I have several virtual machines running on it. When I reboot the server (takes 10 minutes) all VMs are saved and correctly restored. The time on the clients is however of by 10 minutes. nptd is running on the clients and that is able to correct this big mismatch. But what I don't understand is that the host does not seem to help the client with it's

Hi all, If you are using the kernel divider= option in your vmware quest, you are probably aware of the bugs reported at: https://bugzilla.redhat.com/show_bug.cgi?id=315471 Someone @redhat "confirmed" the fix is in the test kernel -92. I tried it but it seems to have the same problem as before - when used with clocksource=pit, it hangs on bootup. Wonder if some of you can test this

Signed-off-by: Roy Spliet <rspliet at eclipso.eu> --- drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c | 73 +++++++++++++++--------- drivers/gpu/drm/nouveau/core/subdev/clock/nva3.h | 2 +- drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c | 2 +- 3 files changed, 48 insertions(+), 29 deletions(-) diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c

What could be the reason for /sys/devices/system/cpu/cpu0/cpufreq non-existing? The cpu supports EIST. My guess is this may not be available because of cpu power/performance settings in the BIOS, but I can't take down production machines to play with this. Any ideas? The HW is Dell PER 5xx/7xx series. # cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on

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

Last evening I updated my Cent 5 server to 5.1. All went flawlessly, and it rebooted with the new kernel just fine. How do I set the clock rate on the new kernel? According to documentation it can be done, but everything I read is rather vague. Check out section 3 at the URL below: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.1/ I'm using a 32 bit server installation (no graphical

flight 12252 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12252/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 4 xen-build fail REGR. vs. 12249 build-i386 4 xen-build fail REGR. vs. 12249 Tests which are failing intermittently

I have used samba for nearly 9 years with no problems and we have about 20 users. In the past we have had a dedicated samba server. We have recently virtualized this server to a quad core Q6600 using vmware virtual server 1.0.4 on a 64 bit host running ubuntu 7.10. As part of the virtualization I installed samba 3.0.26a in ubuntu 7.10. Since this has happened users have complained about

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

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 Is there a way i can trigger a script within a libvirt guest immediately after resume? E.g. i don't see any log message that indicates to a guest that it had been paused and was just woken up. The problem that i am trying to solve is that when i reboot the host (pausing all guests), the guests' system clocks are a few minutes late after resume. The guests RTC (current_clocksource =

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

I apologize, but it appears that I was missing one digest in my email box(issue 9). Hence I though my submission never went through to the list, thus resent my email to the list. I'll go to the list archive and check out the missing replies. M. Chan > From: Elliot Lee <elliot at vmware.com> > Subject: Re: [CentOS-virt] Fwd: Fast clock under VMWare > To: Discussion about the

Following a series of patches to improve nouveaus clock tree parsing. Reclocking these engines (all but memory) is pretty stable on the cards I've tested. Please review and merge when approved. These patches do not solve the problem that core/shader engine doesn't like to be clocked up too far without fb following, with visible corruption as a result. I suspect this problem is unrelated

Under 4.6, we recompiled the kernel with HZ=100 for improved time-keeping in VMware guests. I've read about the backporting of the divider patch into RHEL/CentOS 4.7, but it sounds like it also comes with some bugs. I have been unable to determine the current status of the divider option in the latest 4.7 kernel update. I have experimented with "divider=10" and it works with no major

Hi John, Try adding username=5702 and username=5703 to each of the configs in sip.conf. I recall I had this problem with the Grandstreams. -----Original Message----- From: John Coll [mailto:john.coll@csoft.co.uk] Sent: Saturday, January 03, 2004 11:56 AM To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] Newbie - getting two local phones tocommunicate would be a good start :)