Cloned vm is pionting to original vm disks, and you get error when powering on cloned vm, File system specific implementation of LookupAndOpen[file] failed.

(We are using old version of VCenter Server 6.5 Update 1e), Yes, we are about to upgrade!

When you clone a machine in HTML5 it failes to powered on the cloned machine, this works when you are using Flash client.

In HTML5 the cloned machine still points to the original vmdk files.
In Flash it works.

Must be a bugg, but not verified.

Error message:

File system specific implementation of LookupAndOpen[file] failed An error was received from the ESX host while powering on CLONED-VM. Failed to start the virtual machine. Module ‘Disk’ power on failed. Cannot open the disk ‘/vmfs/volumes/59f0495a-9d458693-70d5-38eaa733215c/ORGINAL-VM/ORGINAL.vmdk’ or one of the snapshot disks it depends on. Failed to lock the file File system specific implementation of OpenFile[file] failed File system specific implementation of OpenFile[file] failed File system specific implementation of OpenFile[file] failed File system specific implementation of OpenFile[file] failed File system specific implementation of OpenFile[file] failed File system specific implementation of OpenFile[file] failed

7 thoughts on “Cloned vm is pionting to original vm disks, and you get error when powering on cloned vm, File system specific implementation of LookupAndOpen[file] failed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.