similar to: Asterisk home on VMWare time sync issues

Displaying 20 results from an estimated 10000 matches similar to: "Asterisk home on VMWare time sync issues"

2008 May 03
9
tick divider bugs
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
2008 Sep 17
1
Status of kernel divider option in 2.6.9-78.0.1
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
2006 Jul 15
4
Vmware server help
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
2008 Aug 20
1
VMware Server clock woes (running too fast)
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
2006 Oct 16
3
CentOS guest for VMware, any similar setup?
Hi, I'm about to setup a CentOS4 server to install VmWare Server on it. Then I'll run 2 main guest OS, Microsoft SBS 2003, and a CentOS development LAMP server. Except from the clock settings, is there any problems/comments? Regards, Ugo
2007 Feb 07
2
Slow clock on CentOS 4.4 in a VMware VM
I'm running a CentOS 4.4 VM on a Windows XP host with VMware Server, and have the problem that my clock runs too slow (it happens in VMware Workstation as well). It loses between 30 and 45 seconds every minute! This is a known problem and can be fixed by adding "nosmp noapic nolapic" to the boot command according to VMware tech note ID 1420. However, despite adding these
2008 May 27
1
Centosplus vmware kernels....???
OK, so I need to bring up a new vm and was wondering what the state of vm kernels for centos. I have read this http://bugs.centos.org/view.php?id=2189about the tick divider but it wasn't clear what the best step forward is for centos 5.1 was, i usually ran with the clocksource=pit option and it looked like that and the divider option caused a problem. I have in the past compiled my own but
2014 Dec 05
4
[LLVMdev] Memset/memcpy: user control of loop-idiom recognizer
On 5 December 2014 at 06:49, Sean Silva <chisophugis at gmail.com> wrote: > > > On Wed, Dec 3, 2014 at 4:23 AM, Robert Lougher <rob.lougher at gmail.com> > wrote: >> >> Hi, >> >> In feedback from game studios a common issue is the replacement of >> loops with calls to memcpy/memset. These loops are often >> hand-optimised, and
2014 May 23
2
[LLVMdev] GVN incorrectly handling readnone parameter attribute?
Confirmed, this is a bug. This define i32* @get_pntr(i32* %p) nounwind uwtable { entry: ret i32* %p } define void @store(i32* %p) noinline nounwind uwtable { entry: %call = call i32* @get_pntr(i32* %p) store i32 10, i32* %call, align 4 ret void } run through opt -functionattrs gets a 'readnone' on @store's %p. That's wrong, it clearly stores to it. The bug is due to
2014 May 23
2
[LLVMdev] GVN incorrectly handling readnone parameter attribute?
On 23 May 2014 09:42, Robert Lougher <rob.lougher at gmail.com> wrote: > Hi Nick, > > Thanks for replying. Bug filed: > http://llvm.org/bugs/show_bug.cgi?id=19842 Thank you! Strangely enough, my first conclusion was that %p was being marked > readnone incorrectly as it wasn't handling the copy via @get_addr. > Sorry -- saying %p alone is ambiguous because
2014 May 22
2
[LLVMdev] GVN incorrectly handling readnone parameter attribute?
On 05/21/2014 02:52 PM, Robert Lougher wrote: > On 21 May 2014 21:40, Robert Lougher <rob.lougher at gmail.com> wrote: >> define i32* @get_pntr(i32* readnone %p) { >> entry: >> ret i32* %p >> } >> >> define void @store(i32* nocapture readnone %p) { >> entry: >> store i32 10, i32* %p, align 4, !tbaa !1 >> ret void >> }
2014 May 21
4
[LLVMdev] GVN incorrectly handling readnone parameter attribute?
Hi, I'm investigating a bug which I have so far been able to narrow down to the following small testcase: ======== test.c =========== int *get_pntr(int *p) { return p; } __attribute__((noinline)) void store(int *p) { int *p2 = get_pntr(p); *p2 = 10; } int test() { int i; store(&i); return i; } ----------------------------- If this is compiled in two steps as
2014 Dec 02
7
[LLVMdev] Memset/memcpy: user control of loop-idiom recognizer
Hi, In feedback from game studios a common issue is the replacement of loops with calls to memcpy/memset. These loops are often hand-optimised, and highly-efficient and the developers strongly want a way to control the compiler (i.e. leave my loop alone). The culprit is of course the loop-idiom recognizer. This replaces any loop that looks like a memset/memcpy with calls. This affects loops
2014 Dec 02
2
[LLVMdev] Memset/memcpy: user control of loop-idiom recognizer
On 2 December 2014 at 19:57, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > On Tue, Dec 02, 2014 at 07:23:01PM +0000, Robert Lougher wrote: >> In feedback from game studios a common issue is the replacement of >> loops with calls to memcpy/memset. These loops are often >> hand-optimised, and highly-efficient and the developers strongly want >> a way to
2014 Sep 05
3
[LLVMdev] Please benchmark new x86 vector shuffle lowering, planning to make it the default very soon!
On Fri, Sep 5, 2014 at 9:32 AM, Robert Lougher <rob.lougher at gmail.com> wrote: > Unfortunately, another team, while doing internal testing has seen the > new path generating illegal insertps masks. A sample here: > > vinsertps $256, %xmm0, %xmm13, %xmm4 # xmm4 = xmm0[0],xmm13[1,2,3] > vinsertps $256, %xmm1, %xmm0, %xmm6 # xmm6 = xmm1[0],xmm0[1,2,3] >
2006 Oct 17
2
Warning of protential probs with 2.6.9-42.0.3.EL upd ate
I just finished going through the time sync problem, and here's the info I used: To configure ESX 2.5.x Server: http://tinyurl.com/ycpcfv <http://tinyurl.com/ycpcfv> To configure Windows Guest OS: http://tinyurl.com/yctxrr <http://tinyurl.com/yctxrr> To configure CentOS w/o X installed, you still need to install the vmware tools. Edit the vmx file for your guest,
2014 Dec 05
2
[LLVMdev] Memset/memcpy: user control of loop-idiom recognizer
There are a large number of ways to lose information in translating loops into memset/memcpy calls, alignment is one of them. As previously mentioned, loop-trip-count is another. Another is size of accesses. For example, the loop may have originally been using int64_t sized copies. This has definite impact on what the best memset/memcpy expansion is, because effectively, the loop knows that it
2011 May 14
9
DomU clock out of sync
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
2002 Jul 25
1
/home several times not mounted on startup
Hi, on my Debian GNU/Linux (sid) i have (among others) a partition which is mounted (normally at startup via /etc/fstab) on /home. But in a few cases (say six in the last months) /home silently isn't mounted. Since then I have "debug" as option in /etc/fstab. In this cases I log in as root and do a mount -a which works with a few diagnostic messages (see below). Today it
2014 Apr 14
2
[LLVMdev] PR17975 and trunk
Hi, PR17975 was caused by r191059 which was reverted on the 3.4 branch in r196521. However, the problem still occurs with trunk (confirmed as of r206186). >From a thread on cfe-commits I see that Kai Nacke (the author of r191059) was working on a patch to fix PR17975, but the conversation ends: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20131202/197968.html So my question