similar to: Xen HVM Networking in 3.10

I just kickstarted a new machine with the latest CentOS 6.2 files, including kernel 2.6.32-220.13.1.el6.x86_64. It came up without network interfaces. dmesg says: bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.1 (Dec 18, 2011) alloc irq_desc for 36 on node -1 alloc kstat_irqs on node -1 bnx2 0000:01:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 bnx2 0000:01:00.0:

Hello Mailing List I got a severe network error message at a HP DL360 Server. The kernel log says: ----------------------------------- /var/log/messages ----------------------------------------------------------------- Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector (irq -1) Mar 19 15:45:17 server kernel: bnx2 0000:02:00.1: eth1: DEBUG: intr_sem[0] PCI_CMD[00100446] Mar 19

Hi Michael: Sorry to brother. But I''ve been suffered this issue quite a long time. My test environment is 2.6.32.36 + xen 4.0.1 + bnx2, 2.3. Also cpu idle is disabled in grub. Grub info: title Red Hat Enterprise Linux Server (2.6.32.36xen) kernel /xen-4.0.1.gz iommu=off x2apic=off console=com1,vga com1=115200,8n1 noreboot cpuidle=0 cpufreq=none

Hello list, I have two differents installation Xen Hypervisor on two identical physical server, on the same switch : The problem is on my new server (Xen 4.0.1 with pvops kernel 2.6.32.24), I have bad performance on bandwidth I have test with a files copy and "iperf". Result iperf average: Transfert Bandwidth XEN-A -> Windows

Hi, i test a xen-patched kernel 2.6.31.10 (kernel from kernel.org with the suse patches) on a system with a boradcom net extreme II (5709) nic using the module bnx2. The nic does not run with this kernel. I get: bnx2 0000:01:00.0: map irq failed Any experiences? Best Regards - Michael Schmidt _______________________________________________ Xen-users mailing list

Hi all I'm trying to setup second ethernet on Dell 2950 server but there isn't any eth1 device (in the bios are ON) # dmesg |grep eth eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 169, node addr 001c23d878bb eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 169, node addr 001c23d878bd

Getting "bnx2i: iSCSI not supported, dev=eth0" for all the NIC adapters on all of my R710's running CentOS 5.5. Here is an sample of the error messages: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. bonding: bond0: setting mode to active-backup

I have a new x3655 IBM and whenever the /etc/xen/scripts/network-bridge script starts, the ethernet would no longer work. This post isn''t about the cause, but the fix. I did a lot of tcpdumps and Googling, but I''ll spare you that. All they do is prove that yes, there is an issue. :) I tried Debian 4.0 i386/amd64 and Ubuntu 7.04 Server i386/amd64 and they all exhibit the

Hoping someone else has seen this before. I have a few dozen Dell R610 systems with CentOS 5.2 that are using kernels from 5.3 and 5.4 (2.6.18-128.1.10.el5 & 2.6.18-164.6.1.el5), that at random lose layer 2 network connectivity either partially or totally. Running tcpdump on the interface reveals only ARP broadcasts, no responses. Switch reports no packets being received on the interface.

I''m experimenting with xen + iscsi, and I founded that under heavy stress domU''s can crash entire system, I''ve reproduced this many many times. My system is like this Software: - iSCSI Enterprise Target v0.4.13 - RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel 2.6.16.29 + Open iSCSI v2.0.730 (Initiator) - Bonnie++ v1.03a VM: - Debian 3.1r3 + Open iSCSI v2.0.730

Hi, I hope someone can help me, I cannot seem to get a system's ethernet interface to correctly work in promiscuous mode... I have a Centos 6.4 system with 2 bnx2 interfaces on it. I have set up eth1 in promiscuous mode and am sending traffic to it using the port mirroring configuration on a Nortel 3510-24T switch. The switch reports that it is sending a fair amount of traffic to the

Hi all, I have a problem when from domU I need to configure a network interface. My system configuration is the next: dom0: xen 3.4.3 with 2.6.18-238.9.1.el5xen kernel, making pci back from a network card. All ok. This is the result from "lspci -v -s 09:00.0" 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) Subsystem: Broadcom

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in

I am having an extremely strange issue with a BL460c1 (G1) blade on a c7000 enclosure. I could not for the life of me get the machine to ping the gateway or any other blade on the same enclosure (yes, the subnet mask was correct & quadruple-checked); although pinging to the local IP works. I was almost convinced that it was a network or hardware issue; until I asked someone to try

Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64 Version: 3.4.3-1 and 2.6.32-15 Hello all, GRUB-PC does not automatically populate Xen related parameters in /boot/grub/grub.cfg so I added them manually (see below). All the packages involved on my Dell PowerEdge R710 running Debian GNU/Linux Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB SATA HDD

Hi, I''ve run into the same issue as: http://lists.xensource.com/archives/html/xen-users/2006-07/msg00599.html In that, running the network bridge script kills networking completely, trying to ping the gateway gives me destination host unreachable. The card is: 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) Using the bnx2 module:

we have DELL R900 with CENTOS 5.3 in it. This DELL R900 come with one integrate PERC6/I and two PERC6/E card. DELL 6/I control 5 internal disks. The original disk sequence are: /dev/sda1 /boot /dev/sda2 / /dev/sdb1 swap ... after I configured PERC6/E disks and reboot, /dev/sda change to RAID disk and original /boot and / change to /dev/sde1 and /dev/sde2. My modprobe.conf is: alias

I attempted an upgrade of our production system from Asterisk/Zaptel 1.2 to 1.4 this weekend. Intially everything looked like it was working properly, but some time in the day following the upgrade, the system died to a kernel panic. I wasn't able to catch the entire kernel dump on the console unfortunately. I attempted to isolate the panic, and found that when 'service zaptel stop'

I have a number of machines that have 4 NICs, two of which are actually in use, running Centos 5. When they are rebooted, they seem to change the eth interface names, assigning them in different orders. I'm a little fuzzy on the details because they are at a remote location and I can't access them easily - especially after the network breaks. Shouldn't: alias eth0 bnx2 alias

I am having the same problem. But, I cannot access to the following link for solution http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround Can someone send me the content of this link? Thanks. Pete, This may be relevant: http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround - Mike At 8/18/2006 09:40 AM Friday, Peter McEvoy wrote: Hi, I''ve run