Possible data corruption after a Windows 2012 virtual machine network transfer
search cancel

Possible data corruption after a Windows 2012 virtual machine network transfer

book

Article ID: 328716

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article provides options to work around the issue when data corruption occur after a network file copy event.

Symptoms:
On a Windows 2012 virtual machine using the default e1000e network adapter and running on an ESXi 5.0/5.1 host, you experience these symptoms:
  • Data corruption occurs when copying data over the network.
  • Data corruption occurs after a network file copy event.
Note: This issue occurs occasionally, when there are large data transfers between virtual machines.

Resolution

This is a known issue affecting ESXi 5.0 and 5.1
This issue is resolved in ESXi 5.1 Patch Release ESXi510-201503001, available at VMware Patch Downloads. For more information on downloading patch, see How to download patches in Customer Connect (1021623).

If you experience this issue and VMware further diagnoses the problem, see How to File a Support Request with VMware support and provide this Knowledge Base article ID in the issue description. A VMware Support representative will work with you to gather your log in and environmental details to help you better and consequently resolve the issue.

Note: Consider the preceding request before applying the workaround.

To work around this issue, use any one of these options:
  • Disable TCP segmentation offload (TSO) in the source Windows 2012 guest operating system.
  • Use the vmxnet3 network adapter as an alternative to the e1000e.

    To change a network adapter:

    1. Connect to the host or vCenter Server using the vSphere Client.
    2. Right-click the virtual machine and click Edit Settings.
    3. Select the network adapter and click Remove.
    4. Click OK.
    5. Right-click the virtual machine and click Edit settings.
    6. Click Add > Ethernet Adapter.
    7. Click Next.
    8. In the Adapter Type drop down, select vmxnet3.
    9. If applicable for your environment, select the appropriate Network Connection.
    10. In Device Status, click Connect at power on.
    11. Click Next.
    12. Review the settings and click Finish, and then click OK.
If you use this workaround, leave feedback and include a contact email address.

Notes:


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.
Choosing a network adapter for your virtual machine
How to download patches in Customer Connect
Networking Error: IP address already assigned to another adapter
Understanding TCP Segmentation Offload (TSO) and Large Receive Offload (LRO) in a VMware environment
Windows 2012 仮想マシンのネットワーク転送後に生じる可能性のあるデータ破損
Windows 2012 虚拟机经过网络传输后数据可能会损坏