Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Intermittent network issues during vSAN/vMotion traffic with qedentv driver (68147)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 22534Language:
English

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Symptoms

In rare circumstances involving heavy vSAN or vMotion ethernet network traffic, intermittent network issues due to the qedentv driver could potentially emerge, leading to the failure of vMotion or errors transacting over vSAN. For vSAN/vMotion traffic, under certain conditions, vmkernel instantiates netqueue or netqueue RSS as appropriate. In high load conditions, due to an intermittent timing issue with the qedentv driver, receive traffic does not flow correctly through the netqueue. When this failure condition occurs, it can result in problems such as heartbeat failures to be reported by vSAN and vMotion failures due to timeout connecting to destination host or incomplete transfer of VM memory pages. When this issue occurs, it will result in the MAC filter associated with the vmknic that is used for vSAN/vMotion traffic to rapidly move back and forth between the default queue and netqueue. It should be noted that MAC filter movement between default and netqueue is in itself normal. But when the filter movement happens quickly accompanied by other associated traffic failures, then it is a likely manifestation of this problem. In the vmkernel logs, messages similar to what are shown below will be repeatedly observed. There may also be vSAN/vMotion failure messages interspersed with driver messages.

vmnic2)]Removing mac:00:50:56:62:c8:9a, vlan_id:0x0, from fp:0, op:MAC_DEL, hw_fn:0
vmnic2)]Applying 00:50:56:62:c8:9a filter, vlan_id:0xffff, fp_id:1, hw_fn:0.
vmnic3)]Feature RSS needed.
<snip>
WARNING: VMotionUtil: 4060: 1195397824256221929 S: Stream completion work failed: Timeout
WARNING: Migrate: 273: 1195397824256221929 S: Failed: Timeout (0xbad0021) @0x4180146cb675
WARNING: VMotionUtil: 850: 1195397824256221929 S: failed to read stream keepalive: Connection closed by remote host, possibly due to timeout
<snip>
vmnic2)]Removing mac:00:50:56:62:c8:9a, vlan_id:0x0, from fp:1, op:MAC_DEL, hw_fn:0
vmnic2)]Applying 00:50:56:62:c8:9a filter, vlan_id:0xffff, fp_id:0, hw_fn:0.

Cause

The problem is due to a corner case timing condition in qedentv driver during netqueue delete operation that could lead to mismatch in indices within the interrupt generation logic on the adapter and impact receive traffic.

Resolution

This issue is fixed in qedentv driver version 3.11.7.0, so update this driver to 3.11.7.0 version or higher available at VMware Download .

Workaround

Workaround would be to disable netqueues on qedentv interfaces. This can be done using driver module parameter as shown below. The example assumes there are four qedentv instances.

[root@host:~] esxcfg-module -g qedentv
qedentv enabled = 1 options = ''
[root@host:~] esxcfg-module -s "num_queues=0,0,0,0 RSS=0,0,0,0" qedentv
[root@host:~] esxcfg-module -g qedentv
qedentv enabled = 1 options = 'num_queues=0,0,0,0 RSS=0,0,0,0'

Reboot system for settings to take effect and will apply to all NICs managed by the qedentv driver.

It should be noted that disabling netqueue will result in some performance impact. The magnitude of the impact will depend on individual workloads and should be characterized before deploying the workaround in production. However, in most cases, the performance impact is not noticeable.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Hosts ESX/ESXi hospedando nós passivos MSCS com RDM LUNs podem levar muito tempo para inicializar (1016106)

KB
•
Los hosts de ESXi/ESX con visibilidad para los LUN de RDM que usan los nodos de MSCS/WSFC con RDM pueden tardar mucho tiempo en iniciarse o durante volver a examinar los LUN (1016106)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESXi

Related Versions:

Take Our Survey

Support Assistant