search for: nehalem

...matching number of messages that do not have an "S" flag on the end of the file name. For example: # ls .fedora-list/ cur/ dovecot.index.log new/ dovecot.index.cache dovecot-uidlist tmp/ # ls .fedora-list/cur 1293379204.26554_1.nehalem.home.rainbowdreams.com:2,S 1293379206.26571_1.nehalem.home.rainbowdreams.com:2, 1293379207.26581_1.nehalem.home.rainbowdreams.com:2, 1293380106.26744_1.nehalem.home.rainbowdreams.com:2, 1293380106.26748_1.nehalem.home.rainbowdreams.com:2,S 1293381904.26876_1.nehalem.home.rainbowdreams.com:2,S 12933...

...es to those who are subscribed to both for the dupe. I'm having a weird problem where libvirt/qemu/kvm won't let me use the model processor I have defined in my domain's config file. Instead, I get the error message in libvirtd.log that: warning : x86Decode:1346 : Preferred CPU model Nehalem not allowed by hypervisor; closest supported model will be used If I review the qemu log for that particular domain, I see that my CPU has been changed to this: -cpu kvm64,+lahf_lm,+popcnt,+sse4.2,+sse4.1,+ssse3 (in other places, I see it set to core2duo rather than kvm64) However, it *should*...

Hallo list, i am testing a Dell M610 with two quadcore Intel Nehalem CPUs at the moment, so with Hyper-Threading 16 cores in total. As mentioned in the subject I am using Ubuntu 8.04 64Bit and Xen 3.2 from Ubuntu package. During these tests I hit on some issues, which are not clear to me. I would be thankful for any comments/hints/thoughts on the following topic...

Just putting this out there to see if anyone else has seen any issues. May cross-post to asterisk-dev if it's indeed a bug (and not my own stupidity). I've got a Digium TE220 (2xT1 interface w/Echo canceller) that in two separate Nehalem-based (Xeon E5520 "Gainestown") boxes (HP ProLiant ML350 G6; HP Z800 Workstation) has caused numerous kernel panics. This is only when the dahdi service is running with a very simple config (I've defined the first span, the bchans and the dchan, and that's about it). If da...

Hello. This is my 1st post. I have tried SSE execution domain fixup pass. But I am not able to see any improvements. I expect for the example below to use MOVDQA, PAND &c. (On nehalem, ANDPS is extremely slower than PAND) Please tell me if something would be wrong for me. Thank you. Takumi Host: i386-mingw32 Build: trunk at 103373 foo.ll: define <4 x i32> @foo(<4 x i32> %x, <4 x i32> %y, <4 x i32> %z) nounwind readnone { entry: %0 = and <4 x i32...

...KAMURA Takumi wrote: > Hello. This is my 1st post. ようこそ！ > I have tried SSE execution domain fixup pass. > But I am not able to see any improvements. Did you actually measure runtime, or did you look at assembly? > I expect for the example below to use MOVDQA, PAND &c. > (On nehalem, ANDPS is extremely slower than PAND) Are you sure? The andps and pand instructions are actually the same speed, but on Nehalem there is a latency penalty for moving data between the int and float domains. The SSE execution domain pass tries to minimize the extra latency by switching instructions...

Hello, i´ve got a new Intel Nehalem server with an i7-920 CPU. I installed a Debian Lenny OS ... Now, i cannot find any images for hypervisor or kernel that seem to be runable on that hardware. :-O All of that is AMD: apt-cache search hypervisor linux-image-2.6-xen-amd64 - Linux 2.6 image on AMD64, oldstyle Xen support linux-ima...

Hey guys, I''m trying to get a gentoo dom0 running on some new Nehalem boxes. Our dozen or so existing servers run a xenified 2.6.21, but we can''t get the new Intel network chipset working with it. So, I''m giving a pv_ops dom0 from xen-tip/master a go, and Xen 3.4.1 to go with it. rebase/master is a bit too bleeding edge for me. So far, it''...

Hi everybody, Using libvirt 1.0.0 how does one change the L2 cache size of the virtual CPU? I can change the CPU model but the cache size never changes: <cpu mode='host-passthrough'/> <model>Nehalem</model> OR <cpu match='exact' mode='custom'/> <model>Nehalem</model> Is there a qemu requirement? -- peter matulis

Hi. I would like to workaround a bug, when after live-migration of KVM guest, there is a 100% steal time shown in guest. I've read, that disabling 'kvm_steal_time' feature should workarund this bug, but i can't find a way to disable it in libvirt's domain xml file. Tried in <cpu> section: <feature policy='disable' name='kvm_steal_time'/> but

...gt; <qemu:arg value='${CPU_SPEC},-kvm_steal_time'/> > </qemu:commandline> > </domain> > > where ${CPU_SPEC} is the next parameter after the '-cpu' one from the > command line, so for qemu command line similar to this: > > qemu-kvm ... -cpu Nehalem,+feat,something ... > > the line in XML would be: > > <qemu:arg value='Nehalem,+feat,something,-kvm_steal_time'/> > > HTH, > > Martin > >> Tried in <cpu> section: >> <feature policy='disable' name='kvm_steal_time'/> &...

...ng the machine. CentOS-5.4 (2.6.18-164.15.1.el5) CentOS (2.6.18-164.9.1.el5) CentOS (2.6.18-164.el5) Would this error indicate a motherboard or CPU problem? How can I diagnose? or is there something funny with the Kernel? Hardware: Supermicro X8DTL-iF motherboard. Intel Server Xeon E5502 1.86GHz Nehalem 8GB Ram Kingston DDR3-1333 w/ Parity w/ Thermal Sensor I have read on bugzilla note about mcelog and not supporting nehalem processor during error decoding. I think this is fixed in Centos 5.5, but maybe there is still a bug? https://bugzilla.redhat.com/show_bug.cgi?id=473392

Hi list, in virt-manager ver. 2.2.1 (fully upgraded CentOS 8.1), the CPU model list only shows ancient CPU (the most recent is Nehalem-IBRS). On the other hand, in virt-manager 1.5.x (fully upgraded CentOS 7.8) we have a rich selection of CPU (as recent as Icelake). Why was the list in newer virt-manager so much trimmed? Is it possible to enlarge it? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it...

My system is a dual Xeon E5540 (Nehalem) HP Proliant DL380G6. When switching between Xen 4.0.2-rc1-pre and Xen 4.1-unstable I noticed that the NUMA info as shown by the Xen ''u'' debug-key is different. More specifically, the CPU to node mapping is alternating for 4.0.2 and grouped sequentially for 4.1. This difference af...

...quot; should be disabled in the >> BIOS of the Z800 workstation when running Linux. They are reasoning >> that Linux kernels do not support this feature and even might not boot >> if it?s enabled. > > hmm, that workstation is a dual Xeon 56xx (Westmere-EP, derived from > Nehalem), new in 2010 > >> Since it apparently was years ago since they made this statement, I?m >> wondering if I should still leave this feature disabled or not. More >> recent kernels might support it, and it?s supposed to improve >> performance. >> >> Could someo...

...ge >> clocksource is a single page for the whole VM, not a per-cpu thing. Can >> we think that all the buggy hardware is already gone? > > No, and it is not the hardware you have to worry about (mostly), it is > the frigging PoS firmware people put on it. > > Ever since Nehalem TSC is stable (unless you get to >4 socket systems, > after which it still can be, but bets are off). But even relatively > recent systems fail the TSC sync test because firmware messes it up by > writing to either MSR_TSC or MSR_TSC_ADJUST. > > But the thing is, if the TSC is no...

...ge >> clocksource is a single page for the whole VM, not a per-cpu thing. Can >> we think that all the buggy hardware is already gone? > > No, and it is not the hardware you have to worry about (mostly), it is > the frigging PoS firmware people put on it. > > Ever since Nehalem TSC is stable (unless you get to >4 socket systems, > after which it still can be, but bets are off). But even relatively > recent systems fail the TSC sync test because firmware messes it up by > writing to either MSR_TSC or MSR_TSC_ADJUST. > > But the thing is, if the TSC is no...

I've seen this consistently on three systems, with three different cards, and multiple versions of DAHDI. At first I thought the issue only occurred on newer, Nehalem-based, systems, but I reproduced it on a Core 2 Duo box as well. I've tested with dahdi-linux 2.2.0.2, dadhi- linux-complete 2.0.0+2.0.0, 2.1.0.2+2.1.0.2, and 2.2.0.2+2.2.0. The card is a Digium TE220B which uses the wct4xxp module. This does not happen, on the same systems and kernel ve...

...emu:arg value='-cpu'/> <qemu:arg value='${CPU_SPEC},-kvm_steal_time'/> </qemu:commandline> </domain> where ${CPU_SPEC} is the next parameter after the '-cpu' one from the command line, so for qemu command line similar to this: qemu-kvm ... -cpu Nehalem,+feat,something ... the line in XML would be: <qemu:arg value='Nehalem,+feat,something,-kvm_steal_time'/> HTH, Martin >Tried in <cpu> section: ><feature policy='disable' name='kvm_steal_time'/> >but that doesn't work. > >Also, coul...

...39;${CPU_SPEC},-kvm_steal_time'/> >> </qemu:commandline> >> </domain> >> >> where ${CPU_SPEC} is the next parameter after the '-cpu' one from the >> command line, so for qemu command line similar to this: >> >> qemu-kvm ... -cpu Nehalem,+feat,something ... >> >> the line in XML would be: >> >> <qemu:arg value='Nehalem,+feat,something,-kvm_steal_time'/> >> >> HTH, >> >> Martin >> >>> Tried in <cpu> section: >>> <feature policy='disab...