Cloning fails when source has multiple partitions or disks using the BlockClone method to ESX host
search cancel

Cloning fails when source has multiple partitions or disks using the BlockClone method to ESX host

book

Article ID: 344091

calendar_today

Updated On:

Products

VMware

Issue/Introduction

  • Converter fails during the cloning phase
  • The source is a virtual machine, VMware Consolidated Backup (VCB) image, or physical server with multiple disks or partitions
  • The destination is an ESX host
  • The cloning method is disk-based (block) clone
  • Error on logout (ignored): vim.fault.NoPermission
    CloneTask::task{8} step "cloning target disks" destroyed
    Cloning failed!
  • Image processing task has failed with MethodFault::Exception: vim.fault.NoPermission
  • ERROR: Unknown error returned by VMware Converter Agent


Environment

VMware vCenter Converter 4.1.x
VMware Converter 3.0.x
VMware vCenter Converter 4.0.x
VMware vCenter Converter Standalone 4.0.x

Resolution

To resolve this issue upgrade to VMware vCenter Converter Standalone.

This has been corrected in VMware vCenter Converter Standalone 5.x.
In previous versions of Converter, the issue occurred when a partition or disk from the source took longer than 30 or 60 minutes (depending on version) to clone onto the ESX host, and the disk-based (BlockClone) cloning method was used. The disk-based cloning method could not keep the control connection alive with the ESX host beyond the default timeout value because it did not continuously send data over the control connection. This caused the control connection to close prematurely which lead to the clone failure and error message.
To resolve the problem:
  1. Upgrade to VMware vCenter Converter Standalone which is located here. This is the recommended solution.

    Note
    : This link was correct as of April 17, 2008. If you find the link is broken, please provide feedback and a VMware employee will update the link.

  2. If upgrading your version of Converter is not possible, do one of the following:

    • When setting up the conversion, resize the failing disk by 1MB. This forces Converter to clone the volume using volume based (file level) cloning rather than disk-based (block) cloning. This method keeps the control connection alive by continuously sending data across the connection.

    • Edit the vpxd.cfg or config.xml file to increase the default timeout value.

      Notes:

      • The vpxd.cfg file is located on the VirtualCenter in the C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter directory and can be used if the conversion target is VirtualCenter.
      • The config.xml file is located on the ESX host in the /etc/vmware/hostd directory and can be used if the conversion target is ESX.
      • If you are converting using the command line tool, you can also edit the custom .xml file you have specified.

      Include a section similar to:

      <vmacore>
      <soap>
      <sessionTimeout>%TimeoutValue%</sessionTimeout>
      </soap>
      </vmacore>

      where %TimeoutValue% is a numeric value in minutes. Set this value to 60 or greater to allow Converter to hold the control connection open longer with the with the ESX host.