Please confirm whether Hyper-V VLAN issues in driver 2.1.3.15 are under investigation.

[Elu]

This is relating to the forum post https://community.intel.com/t5/Ethernet-Products/Hyper-V-vSwitches-do-not-work-with-2-x-drivers-on-a-I225-V/m-p/1529688.

In the last message from Intel, it was claimed that an issue was fixed in driver version 2.1.3.15, which is also the same version that the bug was initially reported against. That same message included references to an "Energy Efficient Ethernet", which appears to be a different issue entirely. I suspect this message may have been posted to the wrong forum accidentally.

The Intel agent has not responded at all to any requests for clarification. This is pretty concerning given it's what I would have thought to be a simple question to answer.

As per my last message in that thread, I need to know whether the Hyper-V VLAN issue in all 2.x drivers is under active investigation by Intel or not, so I can make purchase decisions accordingly. Namely, if the bug is somehow considered closed or not to be fixed, I will obviously need to acquire other hardware fit for purpose.

[B_Y]

Hello @Elu,

Thank you for posting in Intel Ethernet Communities.

We apologies for the delay in response and also please disregard the Energy Efficient Ethernet (EEE).

Based on the current active thread <https://community.intel.com/t5/Ethernet-Products/Hyper-V-vSwitches-do-not-work-with-2-x-drivers-on-a-I225-V/m-p/1529688#M34765>, we understand that you are looking for a defined response to the following inquiries:

1. Could please confirm that the VLAN issue is still under active investigation

2. Request withdrawing the nonfunctional driver versions from Windows Update. This is something Intel should do, to stop the versions with the functionality regression from further rolling out to unsuspecting users. This is not the job of the user, who has no control over specific updates.

Additionally, the advice to "temporarily" stop Windows Updates globally is an absolute non-starter unless Intel can guarantee that Intel will release a proper fixed driver to supersede the broken version within a month. Because every month, if not more often, Windows releases important security updates, and not having these updates installed can very quickly become a critical security issue.

In case not made it clear enough: it is not safe to disable Windows Updates. That is not a reasonable workaround for one vendor (Intel) releasing broken drivers.

3. Please confirm that this specific issue, of the 2.x drivers not working with Hyper-V VLANs, is now recognised as an issue by Intel and will be worked on. At this point we still don't have positive confirmation that this is even known, never mind any estimated time frame.

Given the runaround and passing of blame (to the OEM, to Microsoft, to ...) in earlier posts, I really want this to be crystal clear:

Can you/Intel answer "yes" to this specific statement? "Intel acknowledges that the Intel wired network adapter driver versions 2.x including 2.1.3.15 do not function correctly with Hyper-V virtual NICs and VLANs, and will commit to providing a fix in a future version."

I'm working closely with the team and still waiting for an accurate response from the Intel Engineering team. I'm unable to provide an answer on your inquiries at this time. As far as we know, there could be issues with the Driver version 2.1.3.15 when the Windows update took place. As a result, we've also taken your input seriously.

Please be informed that we will now close this request and further communicate from the original thread. Just feel free to post a new question if you may have any other inquiry in the future as this thread will no longer be monitored.

Best regards,

BY_Intel

Intel Customer Support 

[Elu]

Thank you for the response. It is good to know especially that the EEE post was not intended, and that this is still being looked into. I will await further updates in the other thread.

[B_Y]

Hello @Elu,

Thank you for your understanding.

We will follow up and further communicate on the original thread. At the same time, close the request of this thread from monitoring and the web post.

Best regards,

BY_Intel

Intel Customer Support