similar to: "failed to setup INTx fd: Operation not permitted" error when using PCI passthrough

On 03/16/2017 04:22 PM, Kevin Stange wrote: >> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >> server has yet had a NIC issue, with some being up almost a full month. >> It looks promising! (I'm knocking on all the wood everywhere, though.) > > I'm ready to call this conclusive. The problems I was having across the > board seemed to

On 03/27/2017 04:03 PM, Kevin Stange wrote: > On 03/25/2017 02:35 PM, Sarah Newman wrote: >> On 03/16/2017 04:22 PM, Kevin Stange wrote: >> >>>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>>> server has yet had a NIC issue, with some being up almost a full month. >>>> It looks promising! (I'm knocking on all the

Hi there, I?m working on deploying our new cluster. Masters have 5?1gbps (i210 and i350, thus using igb.ko), configured with mtu 9000, 802.3ad. Works fine *but* I can?t get DCB working (pause frame, aka flow control, which is supported by and enabled on our switches). [root at master2 ~]# dcbtool gc eno1 dcb Command: Get Config Feature: DCB State Port: eno1 Status:

On 7/1/2015 2:58 AM, Gene Cumm wrote: >> I'm setting up UEFI booting and got to the point of having the system talk >> >to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and >> >then continuously request the secondary image file (ldlinux.e64). > So it appears to go deaf. > >> >I'm wondering if I'm missing something or if someone

Does anyone here know which CentOS release added support for 8086:1521, some I350 class device? We cannot get it to work under 5.4/igb driver version 1.3.16-k2. There must have been some major updates since, 5.8 driver is 3.0.6-k2-2 and current is 3.3.6.

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

Hi, I managed to get SR-IOV with an Intel I350 NIC to work.For this I followed the documentation on this page: https://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VFs_in_a_libvirt_.3Cnetwork.3E_definition But as I have more VMs then VF on the NIC I also have a bridge wich serves the other guests. As I run Debian Buster as host I followed the documentation here:

Hello, CentOS 7(1) I like to setup a new Server with SR-IOV for Networking.. I have a I350 Network Card on Board. But on my System this is, I mean, not correct working ? When I like to have Virtual Network Cards I have to unload / reload the "igb" driver? afterward I have my virtual Network Cards. Have any a way, to have the virtual Network Cards on boot time? Thanks for a

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with

Team I have a Dell PowerEdge R720xd, with the Broadcom NetXtreme bcm5720. I found the following thread: http://forums.freebsd.org/showthread.php?t=31769 I find I am unable to use the NIC's (there are 4 on the server). When we put a cable into it we get a "watchdog timeout -- resetting" error, and the machine will pause for 5 or so seconds. IP may or may not come up randomly.

> > On 7/1/2015 2:58 AM, Gene Cumm wrote: > >> I'm setting up UEFI booting and got to the point of having the system talk > >> >to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and > >> >then continuously request the secondary image file (ldlinux.e64). > > So it appears to go deaf. > > > >> >I'm wondering

On 03/25/2017 02:35 PM, Sarah Newman wrote: > On 03/16/2017 04:22 PM, Kevin Stange wrote: > >>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>> server has yet had a NIC issue, with some being up almost a full month. >>> It looks promising! (I'm knocking on all the wood everywhere, though.) >> >> I'm ready to call

On Thu, Feb 26, 2015 at 9:18 AM, Laurent Wandrebeck < l.wandrebeck at quelquesmots.fr> wrote: > Hi there, > > I?m working on deploying our new cluster. > Masters have 5?1gbps (i210 and i350, thus using igb.ko), configured with > mtu 9000, 802.3ad. Works fine *but* I can?t get DCB working (pause frame, > aka flow control, which is supported by and enabled on our switches).

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 05:32 PM, Kevin Stange wrote: > On 02/21/2017 11:50 AM, Johnny Hughes wrote: >> On 02/21/2017 11:47 AM, Johnny Hughes wrote: >>> >>> >>> Kevin, >>> >>> Please try the 4.9.11-22 kernel that I just released for CentOS-6 (along >>> with the newer linux-firmare packages and xfsprogs). >>> >>> If you enable

I'm setting up UEFI booting and got to the point of having the system talk to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and then continuously request the secondary image file (ldlinux.e64). I'm wondering if I'm missing something or if someone can point me in the right direction of trouble shooting this. The tftp root has all the files to boot a BIOS type

On 2020-07-06 10:01, Laine Stump wrote: > On 7/6/20 5:10 AM, Yalan Zhang wrote: > > > > Hi Laine, > > > > For the feature testing before, I only test the linux bridge setting as > > in 2), it works. > > Now I tried 1), to use macvtap bridge mode connected to the PF, it can > > not work as the hostdev interface can not get dhcp ip address on the >

I did not hear back on this posting so I figured I was addressing the wrong audience. Maybe someone on the host-side better understands how the 4.12 kernel is interacting with KVM. Thanks, -Philip > Begin forwarded message: > > From: Philip Prindeville <philipp_subx at redfish-solutions.com> > Subject: Network interface regression on F26 VM after 4.13/4.12 kernel update

Hello, I have a big problem with my servers. I have 4 NIC on all my KVM Servers but the most time on a start (restart) I lost one NIC? It is not always the same, but this two are virtio NICs. with ifup eth0(1) the system say,I have no configured eth0 or eth1 file ? Can any tell me what I can do? thank's for a answer NetworkManager is disabled. -- mit freundlichen Gr??en / best regards,