similar to: intel nic vanished with 5.3

I am using centos 5 x86_64 AMD64 X2 4200+. I am current on yum update. My machine has two ethernet cards. e1000 (eth0) and forcedeth (eth1) [root at fsdsigns2 ~]# more /etc/modprobe.conf alias eth0 e1000 alias eth1 forcedeth sometimes on boot the forcedeth driver thinks it is eth0: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.

Hi! Maybe, I found a bug of xen. My system: - domain0 - gentoo - xen-devel-3.0, kernel 2.6.12.5-r1 - domain1 - debian - kernel 2.6.12.5-r1 (2 interface: vif1.1 = eth0 (0.0.0.0), vif1.2 = eth1 (10.0.1.1 + gw 10.0.1.2)) Bridge: xen-br0 (config as 10.0.1.2) include (vif1.2, vif0.0) xen-br1 (config as 0.0.0.0) include (vif1.1, peth0) On server domain1 I use a pppoe server. If a send a pppoe request

Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0      Link encap:Ethernet  HWaddr

Hello all. I''ve upgraded my drives, and in doing so loaded FC8. Latest kernel-xen.x86_64 (2.6.21.7-5) and xen.x86_64 (3.1.2-5) available, using 2 Intel NICs with e1000 driver. All worked fine on FC5 with custom domU FC5 with pcifront and NIC drivers in kernel. Now, I''m unable to get the NICs to function inside my domU. The are visible in lspci, and ipconfig. DomU dmesg

I recently noticed that after starting xend ethtool no longer work for my e1000 card. In my 2.X box which is a P4, ethtool is working after xend start. Same version of e1000 on both boxes. The unstable box is a Tyan 2462 SMP, FC4 dom0 The 2.X box is Dell P330 UP, Centos 4.1 domO Until xend start ethtool is fine, in both setups I am using the e1000 as eth0. Regards, Ted

I''m trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I''ve built three machines, installed XCP 1.0.0 beta on them and they all three have the same problem - the Realtek network cards don''t work. The following is the output from lspci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI

> > Attempting to install CentOS on a new MSI MB (MS 9618), which > uses the subject controllers. > There are two controllers on the board, seems as though only > one can be used. > I have to manually init, using ifconfig eth0, to use it. > > I understand that the Ethernet controller drivers are not available. > Is there any news on this or a possible date when

Hi all, I'm facing a serious problem with the e100e kernel module for Intel 82574L gigabit nics on Centos 6. The device eth0 suddenly stops working i.e. no more networking. When I do ifconfig from console I get eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:EA inet6 addr: fe80::225:90ff:fe50:8fea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

I am trying to connect two workstations (CentOS 3&4) directly using a straight through cat 5e cable with a crossover adapter on one of the ends. Both hosts have gigabit-capable ethernet card. According to lspci host 1 has: 03:0e.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01) and host 2 has: 05:00.0 Ethernet controller: Marvell Technology Group

Package: xen-utils-3.4 Version: 3.4.0-0~ct Severity: important After installation of linux 2.6.26-2-xen-686 and xen-utils-3.4 the 2 onboard NICs 82574L (driver e1000e) are not working. ping results always in unreachable hostname ethtool seems fine for the eth's mii-tool has no transceiver for the eth's ip link show shows an UNKNOWN state for the eth's With linux 2.6.26-2-xen-686 and

My system configuration: ASUS M2A-VM motherboard AMD Athlon 64 X2 4200+ 2.2 GHz 4x A-DATA 1GB DDR2 800 memory 2x Intel 10/100/1000 Pro/1000 GT Desktop Network Adapter 2x Seagate Barracuda 250GB HD (RAID 1, software RAID) CentOS 5 x86_64; Kernel 2.6.23 (custom built); Version 7.6.9.2 e1000 driver The symptoms of this problem are outlined at: http://e1000.sourceforge.net/wiki/index.php/Issues[1]

Greetings Laine, > Sent: Wednesday, May 02, 2018 at 5:56 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 05/01/2018 12:12 PM, daggs wrote: > > > > I want to see if I understood you correctly, I add: >

Hello, I have been using Xen on a Debian Lenny server for quite some time. I decided to build a new Dom0 using identical hardware, but newest version of Xen from repositories with Debian Squeeze. I attempting to create a new DomU on the new host which is similar to an existing DomU running on the older Lenny host. The DomU is a three NIC firewall. Two of the NICs are virtualized. One NIC is a

File Server OS: CentOS 5.3 (x86_64) Kernel: CentOS Plus kernel (need XFS fs drivers) The file server has a Chelsio T310 10GBASE-CX4 RNIC (rev 3) PCI Express x8 MSI-X (eth0), driver and firmware is stock from the CentOS Plus kernel. Using ethtool I have verified driver association with the 3 NICs on the system (eth1 and eth2 are not connected to any switch) Driver for eth0 driver: cxgb3

Hi Everyone, The following request was received from a Debian user; could you comment on it? I think this seems reasonable, although the cron output can be fixed by writing to a temporary file and using grep -v. (The temporary file is necessary to avoid discarding the exit code, although that may not be needed in the case of rsync, since it writes that to stderr). On Mon, Feb 20, 2006 at

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was

https://bugzilla.samba.org/show_bug.cgi?id=13147 Bug ID: 13147 Summary: inconsistent behaviour regaring vanished files information Product: rsync Version: 3.0.9 Hardware: x64 OS: Mac OS X Status: NEW Severity: minor Priority: P5 Component: core Assignee:

I run an rsync to backup my mail server ever 4 hours. Sometimes, I get these sorts of warnings: Rsyncing... file has vanished: "/usr/local/virtual/*munged1*/new/ 1210876129.43402_0.mail.server.tld" file has vanished: "/usr/local/virtual/*munged2*/courierimapkeywords/. 4036254.1210876052.43312_0.mail.server.tld" file has vanished: "/usr/local/virtual/*munged3*/cur/

https://bugzilla.samba.org/show_bug.cgi?id=4168 Summary: Random file has vanished when syncing clock with ntpdate/hwclock ? Product: rsync Version: 2.6.4 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi Rsync/Samba team, First of all, cudos on rsync 2.6.6! It is running exceptionally well. I'm using a script executed by cron to keep warm-backup servers in sync with the primary server. The execution is set to run every 5 minutes. Like any good programmer, this process is *very* paranoid and uses 'wall' to notify the users if any error occurs during the transmissions. This is