VMware vSphere

 View Only

  • 1.  Failed to start the virtual machine.

    Posted Aug 19, 2019 09:20 AM

    Hi,

    I've a virtual machine copied from other places. I want to import/register this VM in another ESXi. During registering getting below error:

    ESXi Version is 6.4

    Failed to start the virtual machine.

    Module 'Disk' power on failed.

    Cannot open the disk '/vmfs/volumes/59e4c7d8-2c5b4746-3e50-a0369ff3d714/windows-server-2012/SharePoint2013-000001.vmdk' or one of the snapshot disks it depends on.

    Object type requires hosted I/O

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of Lookup[file] failed

    Please help to resolve the issue.

    Many Thanks.



  • 2.  RE: Failed to start the virtual machine.

    Posted Aug 19, 2019 09:25 AM

    Welcome to the Community,

    it looks like one, or more files are missing.

    In this case we need to be very careful, because the VM has active snapshot(s). Doing the wrong thing may cause data loss!

    As a first step, please run ls -elisa > filelist.txt in the VM's folder, and attach the filelist.txt to a reply post.

    André


  • 3.  RE: Failed to start the virtual machine.

    Posted Aug 19, 2019 09:32 AM

    Dear Andre,

    Thanks for your reply. Please check the attached output as below:

    [root@localhost:~] ls -elisa /vmfs/volumes/datastore1/windows-server-2012/

    total 50074664

    96481796      8 drwxrwxrwx    1 root     root          3500 Mon Aug 19 08:19:14 2019 .

          4   1024 drwxr-xr-t    1 root     root          4760 Mon Aug 19 03:58:07 2019 ..

    151007876      8 drwxrwxrwx    1 root     root           420 Mon Aug 19 04:28:17 2019 SharePoint2013

    146813572 41339904 -rwxr-xr-x    1 root     root     42331930624 Mon Aug 19 04:28:17 2019 SharePoint2013-000001.vmdk

    109064708 4096000 -rwxr-xr-x    1 root     root     4194304000 Mon Aug 19 04:07:52 2019 Windows Server 2012-8bad51d3.vmem

    67121796   2048 -rwxr-xr-x    1 root     root       1945681 Mon Aug 19 05:05:01 2019 Windows Server 2012-8bad51d3.vmss

    41955972 4608000 -rwxr-xr-x    1 root     root     4718592000 Mon Aug 19 04:09:56 2019 Windows Server 2012-Snapshot1.vmem

    75510404   2048 -rwxr-xr-x    1 root     root       1911847 Mon Aug 19 05:05:01 2019 Windows Server 2012-Snapshot1.vmsn

    138424836   1024 -rwxr-xr-x    1 root     root          8684 Mon Aug 19 04:07:52 2019 Windows Server 2012.nvram

    142619140      0 -rwxr-xr-x    1 root     root           489 Mon Aug 19 04:07:52 2019 Windows Server 2012.vmsd

    104870404      8 -rwxr-xr-x    1 root     root          3632 Mon Aug 19 05:21:29 2019 Windows Server 2012.vmx

    117453316      8 -rwxr-xr-x    1 root     root          4434 Mon Aug 19 04:07:52 2019 Windows Server 2012.vmxf

    163590660      8 drwxrwxrwx    1 root     root           420 Fri Aug 16 07:35:05 2019 caches

    58733188   1024 -rwxr-xr-x    1 root     root         32768 Mon Aug 19 05:05:00 2019 vmmcores-1.gz

    125841924   1024 -rwxr-xr-x    1 root     root        260029 Mon Aug 19 04:07:52 2019 vmware-1.log

    159396356   1024 -rwxr-xr-x    1 root     root        266808 Mon Aug 19 04:07:52 2019 vmware-2.log

    113259012   1024 -rwxr-xr-x    1 root     root        261409 Fri Aug 16 07:35:05 2019 vmware-3.log

    142619268   1024 -rw-r--r--    1 root     root        261409 Mon Aug 19 04:07:52 2019 vmware-4.log

    171979396   1024 -rw-r--r--    1 root     root         81811 Mon Aug 19 05:21:29 2019 vmware-5.log

    188756612   1024 -rw-r--r--    1 root     root         77429 Mon Aug 19 05:24:33 2019 vmware-6.log

    62927492   5120 -rwxr-xr-x    1 root     root       4301355 Mon Aug 19 05:05:01 2019 vmware-vmx-0.dmp

    71316100   5120 -rwxr-xr-x    1 root     root       4301673 Mon Aug 19 05:05:01 2019 vmware-vmx-1.dmp

    79704708   5120 -rwxr-xr-x    1 root     root       4329940 Mon Aug 19 05:05:01 2019 vmware-vmx.dmp

    151007748   1024 -rw-r--r--    1 root     root         76181 Mon Aug 19 08:19:14 2019 vmware.log

    134230532   1024 -rwxr-xr-x    1 root     root         83394 Mon Aug 19 04:07:52 2019 vprintproxy.log

    [root@localhost:~]

    [root@localhost:~]

    [root@localhost:~] ls -elisa /vmfs/volumes/datastore1/windows-server-2012/SharePoint2013

    total 82635792

    151007876      8 drwxrwxrwx    1 root     root           420 Mon Aug 19 04:28:17 2019 .

    96481796      8 drwxrwxrwx    1 root     root          3500 Mon Aug 19 08:19:14 2019 ..

    155202180 82635776 -rwxr-xr-x    1 root     root     84618444800 Mon Aug 19 05:05:00 2019 SharePoint2013.vmdk

    Thanks.



  • 4.  RE: Failed to start the virtual machine.

    Posted Aug 19, 2019 09:50 AM

    It looks like you've copied the files from a desktop solution like VMware Workstation!?

    The .vmdk format is not compatible with ESXi, and needs to be converted. What I'd recommend is that you use VMware's vCenter Converter  to do a V2V (Virtual-to-Virtual) from the source VM to the ESXi host. Also make sure that you shut down the source VM prior to converting it. According to the files, it has been suspended.

    André