search for: ixgbevf

...[ 1.703044] BUG: unable to handle kernel paging request at ffffc90000c0a00c [ 1.703061] IP: [<ffffffff8121be22>] __msix_mask_irq+0x21/0x24 [ 1.703078] PGD 1b7c43067 PUD 1b7c44067 PMD 1ac44d067 PTE 80100000d510c465 [ 1.703098] Oops: 0003 [#1] SMP [ 1.703108] Modules linked in: ixgbevf(+) This works with kernel 3.8 with iommu=soft, but 3.10 and 3.11-rc4 does not work. Dom0 memory is less than 4G and I tried with e820_host=1 but still get the error. Not sure if the following has anything to do with it: These are in dom0 on all kernels: [ 24.445555] pci 0000:01:00.1: address...

...ual interfaces correspond to eth2, i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0 on my dom0 machine, i can ping other machine using eth2, (implying PF on eth2 is active) on my domU machine, when i attach the virtual function, i get the following messages [ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mapped GSI0 to IRQ28 [ 2282.688470] ixgbevf 0000:00:00.0: setting latency timer to 64 [ 2282.690187] ixgbevf 0000:00:00.0: PF still in reset state, assigning new address while PF on eth2 is there and active, since i can ping other machine. Now, when I try to bring up the VF...

...ual interfaces correspond to eth2, i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0 on my dom0 machine, i can ping other machine using eth2, (implying PF on eth2 is active) on my domU machine, when i attach the virtual function, i get the following messages [ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mapped GSI0 to IRQ28 [ 2282.688470] ixgbevf 0000:00:00.0: setting latency timer to 64 [ 2282.690187] ixgbevf 0000:00:00.0: PF still in reset state, assigning new address while PF on eth2 is there and active, since i can ping other machine. Now, when I try to bring up the VF...

...ment Advisory 2017:1194 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1194.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ead8dfcb3828518aed74380b77d990bb193ee63417354c20c4b91b2ef95a720f kmod-redhat-ixgbevf-3.2.2_k_rh7.4_z-1.el7_3.x86_64.rpm Source: dccc0b49f0cdf5751526307d6572aec90d0b28cad6c0137898affeb6ed6cdf2b kmod-redhat-ixgbevf-3.2.2_k_rh7.4_z-1.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos at irc.freenode.net Twitter: @JohnnyCentOS

...-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbevf Enhancement Update (Johnny Hughes) 2. CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbe Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 4 May 2017 15:23:48 +0000 From: Johnny Hughes <johnny at centos.org&gt...

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of

...see with these implementations is that the network configuration requirements that are passed on to the owner of the VM are quite complicated. You have to set up bonding, you have to configure it to enslave two interfaces, those interfaces (one is virtio-net, the other is SR-IOV device/driver like ixgbevf) must support MAC address changes requested in the VM, and on and on... So, on to the proposal: Modify virtio-net driver to be a single VM network device that enslaves an SR-IOV network device (inside the VM) with the same MAC address. This would cause the virtio-net driver to appear and work like...

...see with these implementations is that the network configuration requirements that are passed on to the owner of the VM are quite complicated. You have to set up bonding, you have to configure it to enslave two interfaces, those interfaces (one is virtio-net, the other is SR-IOV device/driver like ixgbevf) must support MAC address changes requested in the VM, and on and on... So, on to the proposal: Modify virtio-net driver to be a single VM network device that enslaves an SR-IOV network device (inside the VM) with the same MAC address. This would cause the virtio-net driver to appear and work like...

...he network configuration > > requirements that are passed on to the owner of the VM are quite > > complicated. You have to set up bonding, you have to configure it to > > enslave two interfaces, those interfaces (one is virtio-net, the other > > is SR-IOV device/driver like ixgbevf) must support MAC address changes > > requested in the VM, and on and on... > > > > So, on to the proposal: > > Modify virtio-net driver to be a single VM network device that > > enslaves an SR-IOV network device (inside the VM) with the same MAC > > address. Thi...

...he network configuration > > requirements that are passed on to the owner of the VM are quite > > complicated. You have to set up bonding, you have to configure it to > > enslave two interfaces, those interfaces (one is virtio-net, the other > > is SR-IOV device/driver like ixgbevf) must support MAC address changes > > requested in the VM, and on and on... > > > > So, on to the proposal: > > Modify virtio-net driver to be a single VM network device that > > enslaves an SR-IOV network device (inside the VM) with the same MAC > > address. Thi...

Guest needs the ability to enable and disable MSI-X interrupts by setting the MSI-X control bit, for a passed-through device. Guest is allowed to write MSI-X mask bit only if Xen *thinks* that mask is clear (interrupts enabled). If the mask is set by Xen (interrupts disabled), writes to mask bit by the guest is ignored. Currently, a write to MSI-X mask bit by the guest is silently ignored. A

...mentations is that the network configuration > requirements that are passed on to the owner of the VM are quite > complicated. You have to set up bonding, you have to configure it to > enslave two interfaces, those interfaces (one is virtio-net, the other > is SR-IOV device/driver like ixgbevf) must support MAC address changes > requested in the VM, and on and on... > > So, on to the proposal: > Modify virtio-net driver to be a single VM network device that > enslaves an SR-IOV network device (inside the VM) with the same MAC > address. This would cause the virtio-net d...

...> requirements that are passed on to the owner of the VM are quite > > > > complicated. You have to set up bonding, you have to configure it to > > > > enslave two interfaces, those interfaces (one is virtio-net, the other > > > > is SR-IOV device/driver like ixgbevf) must support MAC address changes > > > > requested in the VM, and on and on... > > > > > > > > So, on to the proposal: > > > > Modify virtio-net driver to be a single VM network device that > > > > enslaves an SR-IOV network device (insid...

...> requirements that are passed on to the owner of the VM are quite > > > > complicated. You have to set up bonding, you have to configure it to > > > > enslave two interfaces, those interfaces (one is virtio-net, the other > > > > is SR-IOV device/driver like ixgbevf) must support MAC address changes > > > > requested in the VM, and on and on... > > > > > > > > So, on to the proposal: > > > > Modify virtio-net driver to be a single VM network device that > > > > enslaves an SR-IOV network device (insid...

...tion requirements that are passed on > > > to the owner of the VM are quite complicated. You have to set up > > > bonding, you have to configure it to enslave two interfaces, > > > those interfaces (one is virtio-net, the other is SR-IOV > > > device/driver like ixgbevf) must support MAC address changes > > > requested in the VM, and on and on... > > > > > > So, on to the proposal: > > > Modify virtio-net driver to be a single VM network device that > > > enslaves an SR-IOV network device (inside the VM) with the same &...

...tion > > > requirements that are passed on to the owner of the VM are quite > > > complicated. You have to set up bonding, you have to configure it to > > > enslave two interfaces, those interfaces (one is virtio-net, the other > > > is SR-IOV device/driver like ixgbevf) must support MAC address changes > > > requested in the VM, and on and on... > > > > > > So, on to the proposal: > > > Modify virtio-net driver to be a single VM network device that > > > enslaves an SR-IOV network device (inside the VM) with the same M...

...+- drivers/net/ethernet/intel/igb/e1000_phy.c | 2 +- drivers/net/ethernet/intel/ixgbe/ixgbe_82599.c | 2 +- drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 2 +- drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c | 2 +- drivers/net/ethernet/intel/ixgbevf/vf.c | 2 +- drivers/net/ethernet/netronome/nfp/nfpcore/nfp6000_pcie.c | 2 +- drivers/net/ethernet/qlogic/qed/qed_mcp.c | 2 +- drivers/net/ethernet/sfc/falcon/farch.c | 2 +- drivers/net/ethernet/sfc/farch.c | 2 +-...

...at the network configuration >> requirements that are passed on to the owner of the VM are quite >> complicated. You have to set up bonding, you have to configure it to >> enslave two interfaces, those interfaces (one is virtio-net, the other >> is SR-IOV device/driver like ixgbevf) must support MAC address changes >> requested in the VM, and on and on... >> >> So, on to the proposal: >> Modify virtio-net driver to be a single VM network device that >> enslaves an SR-IOV network device (inside the VM) with the same MAC >> address. This woul...

...at the network configuration >> requirements that are passed on to the owner of the VM are quite >> complicated. You have to set up bonding, you have to configure it to >> enslave two interfaces, those interfaces (one is virtio-net, the other >> is SR-IOV device/driver like ixgbevf) must support MAC address changes >> requested in the VM, and on and on... >> >> So, on to the proposal: >> Modify virtio-net driver to be a single VM network device that >> enslaves an SR-IOV network device (inside the VM) with the same MAC >> address. This woul...

Hi, the updated Amazon Web Service AMI (ami-4ac6653d) has a serious bug. It is not possible to resize a disk after creating a new volume with a size greater than 8GB. resize2fs does nothing. The previous AMI worked perfectly but is no longer available. This bug is a show stopper for using CentOS on AWS. Regards, Thorsten PS: It would also be great to have a CentOS 6 AMI with HVM