Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1,392 Views

Intel X520 SR-IOV [DMAR:[fault reason 04] Access beyond MGAW]

Hi,

i'm getting TX hang on VF with SR-IOV enable when adding a VF to KVM vm

DESCRIPTION:

i'm using intel X520 RNDc DELL card on poweredge R620,

when adding a VM and assign a new VF to it i'm getting "spoof packet detected" and TX hang floods the screen,

on another SSH session i'm getting multiple lines:

kernel: dmar: DRHD: handling fault status reg 502

kernel: dmar: DMAR:[DMA Write] Request device [01:10.4] fault addr 68c2e85400000

kernel: DMAR:[fault reason 04] Access beyond MGAW

i can run ip link set eth0 vf 0 spoofchk off but seems that only the prints is off but the spoof still occurred and packets are drooped,

SYSTEM-DETAILS

Dell PowerEdge R620

NIC: RNDc 2 ports X520, 2 ports I350

CONNECTION: DIRECT ATTACH

OS: CentOS 6.7

kernel: 2.6.32-573.8.1.el6.x86_64

Linux KVM qemu-kvm-0.12.1.2-2.479.el6_7.2.x86_64

Libvirt libvirt-0.10.2-54.el6_7.2.x86_64

no VLAN is used, only external IP address

OTHER COMMANDS OUTPUT

#

root@kvmsrv3:~# ethtool -i eth0

driver: ixgbe

version: 4.0.1-k

firmware-version: 0x80000741

bus-info: 0000:01:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

#

root@kvmsrv3:~# ethtool -S eth0

NIC statistics:

rx_packets: 1198001

tx_packets: 0

rx_bytes: 100415250

tx_bytes: 0

rx_pkts_nic: 15756978

tx_pkts_nic: 17121044

rx_bytes_nic: 3095906789

tx_bytes_nic: 9977985209

lsc_int: 1

tx_busy: 0

non_eop_descs: 0

rx_errors: 294

tx_errors: 0

rx_dropped: 0

tx_dropped: 0

multicast: 3

broadcast: 1197702

rx_no_buffer_count: 0

collisions: 0

rx_over_errors: 0

rx_crc_errors: 0

rx_frame_errors: 0

hw_rsc_aggregated: 0

hw_rsc_flushed: 0

fdir_match: 0

fdir_miss: 0

fdir_overflow: 0

rx_fifo_errors: 0

rx_missed_errors: 0

tx_aborted_errors: 0

tx_carrier_errors: 0

tx_fifo_errors: 0

tx_heartbeat_errors: 0

tx_timeout_count: 0

tx_restart_queue: 0

rx_long_length_errors: 0

rx_short_length_errors: 0

tx_flow_control_xon: 0

rx_flow_control_xon: 0

tx_flow_control_xoff: 0

rx_flow_control_xoff: 0

rx_csum_offload_errors: 0

alloc_rx_page_failed: 0

alloc_rx_buff_failed: 0

rx_no_dma_resources: 476038

.....[ REMOVING 0 LINES ]

rx_queue_0_packets: 786932

rx_queue_0_bytes: 56754214

rx_queue_0_bp_poll_yield: 0

rx_queue_0_bp_misses: 0

rx_queue_0_bp_cleaned: 0

rx_queue_1_packets: 411069

rx_queue_1_bytes: 43661036

rx_queue_1_bp_poll_yield: 0

rx_queue_1_bp_misses: 0

rx_queue_1_bp_cleaned: 0

rx_queue_2_packets: 0

...

#

attaching commands outputs that may help

thanks for your help

Chaim

0 Kudos
1 Reply
Highlighted
Valued Contributor I
25 Views

Hi Chaim,

Thank you for contacting Intel Customer Support. We are currently looking into your issue and will update you once we have any findings.

As of the moment, we suggest to also check with Dell* regarding the issue.

Sincerely,

Sandy

0 Kudos