similar to: module-info vs pci.ids

Kevin Stange, It can be either kernel or update the NIC driver or firmware of the NIC card. Hope that helps! Xlord -----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Kevin Stange Sent: Tuesday, January 24, 2017 1:04 AM To: centos-virt at centos.org Subject: [CentOS-virt] NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18 I have three

On 01/23/2017 11:04 AM, Kevin Stange wrote: > I have three different types of CentOS 6 Xen 4.4 based hypervisors (by > hardware) that are experiencing stability issues which I haven't been > able to track down. All three types seem to be having issues with NIC > and/or PCIe. In most cases, the issues are unrecoverable and require a > hard boot to resolve. All have Intel NICs.

On 02/21/2017 11:47 AM, Johnny Hughes wrote: > On 01/23/2017 11:04 AM, Kevin Stange wrote: >> I have three different types of CentOS 6 Xen 4.4 based hypervisors (by >> hardware) that are experiencing stability issues which I haven't been >> able to track down. All three types seem to be having issues with NIC >> and/or PCIe. In most cases, the issues are

I have three different types of CentOS 6 Xen 4.4 based hypervisors (by hardware) that are experiencing stability issues which I haven't been able to track down. All three types seem to be having issues with NIC and/or PCIe. In most cases, the issues are unrecoverable and require a hard boot to resolve. All have Intel NICs. Often the systems will remain stable for days or weeks, then

On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: > Kevin Stange, > It can be either kernel or update the NIC driver or firmware of the NIC > card. Hope that helps! > > Xlord > -----Original Message----- > From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Kevin > Stange > Sent: Tuesday, January 24, 2017 1:04 AM > To: centos-virt

On 09/19/2014 10:35 AM, lejeczek wrote: > hi everybody > > a windows kvm guest would not start, process gets killed with: > > Out of memory: Kill process 21984 (qemu-kvm) score 44 or sacrifice child > > I really don't know where/what I might be missing, config seems fine, > everything looks ok - I only am not sure, do I need to first stub a > SR-IOV device like

hi everybody a windows kvm guest would not start, process gets killed with: Out of memory: Kill process 21984 (qemu-kvm) score 44 or sacrifice child I really don't know where/what I might be missing, config seems fine, everything looks ok - I only am not sure, do I need to first stub a SR-IOV device like regular passthrough? I'm trying sr-iov, having one NIC left to the host and the

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.4 Severity: important When using the the intel igb driver from the 3.2.0-0.bpo.4-amd64 kernel and debian squeeze hypervisor with a Intel 82576 quad port nic the first nic fails to get an IRQ mapping: relevant lines from dmesg ----8<---- [ 24.264857] Intel(R) Gigabit Ethernet Network Driver - version 3.2.10-k [ 24.264929] Copyright (c)

Hi! we have two Intel Quad Nic 82576, PCI ID 8086:10E8 and use the igb driver 1.3.19.3 on Debian 5.0.1. I used the pciback.hide XEN kernel parameter and made on of the NIC''s interfaces available in a DomU. Now, when I am starting the VM, the system crashes (log attached) I also tried to boot with the irqpoll option - the Interrupt Disabled message still appears when I try to start the

Hi, I got a problem when prepared to pass-thru 82576 ethernet card with SR-IOV support. The 82576 card is build-in on the board. When loading igb driver for the card, dmesg show some errors like: pci 0000:05:00.0: BAR 10: can''t allocate mem resource [0xfbf00000-0xfbefffff] . igb 0000:05:00.0: not enough MMIO resources for SR-IOV igb 0000:05:00.0: Failed to initialize

On 01/30/2017 06:12 PM, Adi Pircalabu wrote: > On 31/01/17 10:49, Kevin Stange wrote: >> You said 3.x kernels specifically. The kernel on Xen Made Easy now is a >> 4.4 kernel. Any chance you have tested with that one? > > Not yet, however the future Xen nodes we'll deploy will run CentOS 7 and > Xen with kernel 4.4. I'll keep you (and others here) posted on my

On 31/01/17 10:49, Kevin Stange wrote: > You said 3.x kernels specifically. The kernel on Xen Made Easy now is a > 4.4 kernel. Any chance you have tested with that one? Not yet, however the future Xen nodes we'll deploy will run CentOS 7 and Xen with kernel 4.4. > Did you ever try without MTU=9000 (default 1500 instead)? Yes, also with all sorts of configuration combinations like

Hi, I am working with a westemere based server. I need to find out if the NIC installed there supports SR-IOV - what would be the best way to determine that? Regards, Kashyap hwconfig ------------- Summary: HP DL160 G6, 2 x Xeon E5620 2.40GHz, 15.7GB / 16GB 1333MHz, 1 x 500GB SATA System: HP ProLiant DL160 G6, C-2N/16/500, ySPEC 25.0 Processors: 2 x Xeon E5620 2.40GHz (HT

# lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) 00:05.0 PCI bridge [0604]: Intel Corporation 5520/X58 I/O Hub PCI

Hi all, I've setup a ethernet bond on my centos 5.6 server , when i do a reboot the bond does come up but cleared all the slaves and i've to manually re-add them with ifenslave. does anyone know a solution to this? am i missing something? offcourse i can add it to my rc.local but there must be a more elegant way. please see my configs below Thanks, Wessel ifcfg-bond0: DEVICE=bond0

On 7/30/2016 6:56 AM, Fawzy Ibrhim wrote: > # lspci -nn > 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) > 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) > 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) >

On 7/28/2016 3:41 PM, Fawzy Ibrahim wrote: > LSI SATA MEGARAID 95Q9 afaik, the megaraid cards are mostly all SAS, which support SATA drives, except very old ones were SCSI. Ok, I do see they had a series of MegaRAID SATA 150-xx and 300-xx cards, these were 64 bit PCI or PCI-X cards. 95Q9 does not appear to be a valid card number, 9240, 9260, 9280 are some pci-express SAS MegaRaid

On 01/30/2017 04:17 PM, Adi Pircalabu wrote: > On 28/01/17 05:21, Kevin Stange wrote: >> On 01/27/2017 06:08 AM, Karel Hendrych wrote: >>> Have you tried to eliminate all power management features all over? >> >> I've been trying to find and disable all power management features but >> having relatively little luck with that solving the problems. Stabbing

Hi, I have been trying to get NIC PCI Passthrough to work on Xen 4.3.0 and have hit a wall. On attaching the NIC the domU network driver (igb) crashes. I followed the Xen PCI Passthrough wiki http://wiki.xen.org/wiki/Xen_PCI_Passthrough and am using dynamic device assignment with xl. Trying to passthrough this device: root@dom0:~# lspci|grep 82575EB 05:00.1 Ethernet controller: Intel

Hi all, I've got a Centos 5.1 kickstart that I must continue to use. How can I update the kick start image so that it recognizes Intel gigabit 82576 nic? BTW, I compiled the driver I need and have this igb.ko file. How do I incorporate that into my initrd.img file that I see on the kickstart CD that is probably my kickstart boot OS. Thank you very much in advance. aurf -