Importing a virtual machine with a large number of disks to a managed destination fails with NFC timeout errors
search cancel

Importing a virtual machine with a large number of disks to a managed destination fails with NFC timeout errors

book

Article ID: 328801

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • Importing a virtual machine with a large number of disks fails with NFC timeout errors
  • You experience NFC timeout errors when restoring VCB backed files of a virtual machine with large number of disks.
  • The virtual machine has up to 10 or more vmdk files
  • Converting a virtual machine fails with NFC timeout errors
  • In the Converter logs, you see entries similar to:

    [#13] [task-1] [2008-12-25 17:34:54.150 'App' 3660 verbose] [,0] Opening file [NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/mvo_nrt_sql2_10.vmdk (ha-nfc://[NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/[email protected]:902!52 d6 ff 69 26 b3 4e 59-7a c1 bb af 95 e1 fa 76)
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 verbose] [,0] NfcNetTcpRead: timed out waiting for data
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 warning] [,0] [NFC ERROR] NfcFssrvrRecv: failed with code = 9
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 warning] [,0] [NFC ERROR] NfcFssrvr_DiskOpen: failed to receive open reply
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 verbose] [,0] DISKLIB-DSCPTR: : "ha-nfc://[NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/[email protected]:902!52 d6 ff 69 26 b3 4e 59-7a c1 bb af 95 e1 fa 76" : Failed to open NBD extent.
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 verbose] [,0] DISKLIB-LINK : "ha-nfc://[NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/[email protected]:902!52 d6 ff 69 26 b3 4e 59-7a c1 bb af 95 e1 fa 76" : failed to open (NBD_ERR_GENERIC).
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 verbose] [,0] DISKLIB-CHAIN : "ha-nfc://[NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/[email protected]:902!52 d6 ff 69 26 b3 4e 59-7a c1 bb af 95 e1 fa 76" : failed to open (NBD_ERR_GENERIC).
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 verbose] [,0] DISKLIB-LIB : Failed to open 'ha-nfc://[NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/[email protected]:902!52 d6 ff 69 26 b3 4e 59-7a c1 bb af 95 e1 fa 76' with flags 0xa (NBD_ERR_GENERIC).
    [#13] [task-1] [2008-12-25 17:35:54.150 'App' 3660 info] [,0] Error 290 opening disk ha-nfc://[NRT_DEV_SAN_DATASTORE_5] mvo_nrt_sql2/[email protected]:902!52 d6 ff 69 26 b3 4e 59-7a c1 bb af 95 e1 fa 76.
    [#13] [task-1] [2008-12-25 17:35:54.259 'App' 3660 error] [cloneTask,457] MNTAPI Error 4649 occured when opening disk set
    [#13] [task-1] [2008-12-25 17:35:54.666 'App' 3660 info] [imageProcessingTaskStep,199] CloneTask::task{11} step "cloning target disks" destroyed
    [#13] [task-1] [2008-12-25 17:35:54.666 'App' 3660 error] [cloneTask,356] Cloning failed!


Environment

VMware vCenter Converter Standalone 4.0.x
VMware vCenter Converter Standalone 4.3.x
VMware Converter 3.0.x
VMware vCenter Converter Standalone 5.0.x
VMware vCenter Converter 4.0.x

Cause

The issue occurs because there are too many NFC (network file copy) sessions open to the ESX host. Due to a limit on the number of NFC sessions allowed, Converter may experience a timeout when attempting to open one of the disks. As this issue occurs during the reconfiguration stage, when Converter fails, it removes the destination virtual machine.
Note: The failure may occur on disk 9 or on a disk number higher than 10.

Resolution

To workaround this issue:
  1. Revoke the Remove privilege from the user account that is used in Converter to log in to vCenter Server:

    1. Connect to the host with a vSphere Client.
    2. Click Home > Roles.
    3. Right-click the administrator role and click Clone.
    4. Rename the role, for example as testadmin.
    5. Right-click the new role and click Edit.
    6. Click Virtual Machine > Inventory.
    7. Deselect Remove and then click OK.

  2. Create a new group:

    1. Click the Inventory tab.
    2. Click the Local Users & Groups tab.
    3. Right-click the Groups view and click Add to create new group.
    4. Enter a name for this new group, for example testadmin.
    5. Click OK.

  3. Create a new user:

    1. Right-click the Users view and click Add to add a new user.
    2. Enter a login name, for example testadmin.
    3. Enter a password for the new user.
    4. In the Group field, choose the group that you created in Step 2 and click Add.
    5. Click OK.

  4. Add the permission for the new user:

    1. Right-click the Permissions tab and click Add Permission.
    2. In the Users and Groups section. click Add and select the user testadmin.
    3. In the Assigned Role dropdown, select testadmin and click OK.

      You should now see the newly created user/group and its assigned role.

  5. Test the new user account and permissions by logging into the same ESX host and verify that you do not have the option to delete a test virtual machine.

    Note: Perform this step only on a test virtual machine.

  6. Try converting the virtual machine using this newly created user. You may see a failure at the reconfiguration stage, but a converted virtual machine is retained on the ESX host. This is because the new user does not have the permissions to delete the virtual machine.

Note: You can create the new user on vCenter Server also.