![]() ![]() I've also tried copying the VMDK's at the datastore level as well as tried performing a V2V using the VMware Standalone Converter and all have failed to write to the host. For the fun of it, I built an empty VM shell and was able to vMotion the VM between both hosts with no issues. Looking at the datastore, it creates the -flat.vmdk file (as well as the VMX and swap files) but appears to fail to copy any data into it. Could not complete network copy for file /vmfs/volumes/5f9afc6f-e37203e0-59b4-2cea7f5971d4/VMNAME/VMNAME01.vmdk When I attempt to perform an offline/cold vMotion of one of the VM's from the Dell to the HP, it typically gets to about 31% and sits there for a while before the migration fails with the error below error. I built a new 6.7 vCenter Appliance and all are licensed with an Essentials Kit. The HP is using the HP customized build and the Dell is using the Dell customized build. ![]() I've upgraded the HP to ESXi 6.7 Build 17167734 and have the same build on the Dell. The HP has spinning disks while the Dell has SSD's. I am setting up a PowerEdge T440 alongside an existing a ProLiant D元80 Gen 9, each using local storage. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |