search for: efffe

Hi. there is a way to MARK udp VOIP (SIP) traffic, in order to put in a highest prio class ? Traffic flow seems start on udp 5060 port, but next both server and client seems jump to a random(?) port. I can''t use CONNMARK because is udp traffic. I only see a pattern for L7 patch in order to SIP traffic identification , but I run 2.4 kernel series . When you patch 2.4 kernel with

I've been working on an asterisk box at work for a few weeks now, things were finally starting to sail smoothly until I hit this head scratcher this morning. It's a rather intricate problem, so bear with me. Heres the scenario. What works: If I call from my sip phone -> sip phone everythings ok If I call from sip phone -> external pots number ok as well If I map one of our

...g error in the qemu-dm log: domid: 3 qemu: the number of cpus is 3 config qemu network with xen bridge for tap3.0 br0 Watching /local/domain/0/device-model/3/logdirty/next-active Watching /local/domain/0/device-model/3/command qemu_map_cache_init nr_buckets = 10000 size 3145728 shared page at pfn efffe buffered io page at pfn efffc Time offset set 0 Register xen platform. Done register platform. medium change watch on `hdc'' (index: 1): /mnt/images/2003SrvCD1.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count...

Hello We are seeing the following lines in our /var/log/kern file. and I am wondering why IO window is disabled for those pci bridges and if it is necessary to enable them. Nov 1 15:19:18 Song kernel: IO window: disabled. Nov 1 15:19:18 Song kernel: MEM window: f4000000-f7ffffff Nov 1 15:19:18 Song kernel: PREFETCH window: disabled. Nov 1 15:19:18 Song kernel: PCI: Bridge: 0000:07:00.0 Nov

http://bugzilla.netfilter.org/show_bug.cgi?id=742 Summary: ip6tables "-m iprange" ipv6 range detection Product: netfilter/iptables Version: linux-2.6.x Platform: x86_64 OS/Version: SuSE Linux Status: NEW Severity: critical Priority: P5 Component: ip6_tables (kernel) AssignedTo:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I followed the instructions here: http://nixcraft.com/file-servers/14803-how-centos-5-pxe-linux-installation-server.html, along with a few other sources that were less successful, and I finally got a pxe boot going. I'm using CentOS 5.3 x86_64 media as the source. The server boots, but keeps hanging. Here is my boot line:

FreeBSD 4.1.1-RELEASE #1: Tue Oct 10 18:09:51 CDT 2000 root@test-drive.tamu.edu:/usr/src/sys/compile/TEST-DRIVE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM

Hi, we are currently working on getting windows working on your xen servers. but we are facing a severe problem where dom0 and all domus hang for 1-5 seconds from time to time. we think it is probably because of disk i/o, because top sometimes says 100% wa (waiting on io) during the hang. dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. should we give dom0 more than once

Hi, I'm geting this message from virt-manager. Server: SuperMicro X8SIL with INTEL X3440 Here is my logs /var/log/dmesg: Bootdata ok (command line is ro root=/dev/md2) Linux version 2.6.18-194.3.1.el5xen (mockbuild at builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:49:53 EDT 2010 BIOS-provided physical RAM map: Xen: 0000000000000000 -

Hello, every few hours I get the following message in /var/log/message: Jul 5 20:23:28 hXXX kernel: Machine check events logged Jul 5 20:53:28 hXXX kernel: Machine check events logged Jul 5 22:13:28 hXXX kernel: Machine check events logged Jul 5 23:53:28 hXXX kernel: Machine check events logged Jul 5 23:58:27 hXXX kernel: Machine check events logged Jul 6 01:38:27 hXXX kernel: Machine

Hello, yesterday night I had a problem with my server located at a hoster (strato.de). I couldn't ssh to it and over the remote serial console I saw "out of memory" errors (sorry, don't have the text). Then I had reinstall CentOS 5.5/64 bit + all my setup (2h work), because I have a contract with a social network and they will shut down my little card game if it is not

OK, so after several weeks of trying to get various versions of Xen running of various distributions, I''m starting to wonder if I''ve got a hardware compatibility problem and as the system never really boots with the Xen kernel I''ve got no log files to tell me where the problem is. I was wondering if there''s a way to compile from source with debug turned on,

Hi, I have a problem booting the Xen hypervisor on my brand new Lenovo Thinkpad T400 2765D2G (Core2 Duo P8600 CPU, 2.40GHz. 4GB RAM). I''m running Debian 5.0 (Lenny) and I use the Debian-provided xen-hypervisor-3.2-1-amd64 package. The Dom0 kernel seems to be the Xen patches ported to a 2.6.26 kernel: linux-image-2.6.26-1-xen-amd64 I can boot the hypervisor only very unrealiably: Out of

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important The Xen hypervisor very unreliably boots on my 4GB Lenovo Thinkpad T400 2765D2G. Right after installation it booted the DomO kernel from linux-image-2.6.26-1-xen-amd64 without any problems, but every subsequent restart failed completely. Once I had a XEN "early fatal page fault" error message, on every other of