unable to access file {share]new virtual machine

abdulhussein · ‎09-22-2014

when i tried to cold migrate VM from localstore to sharestore or trying to create new VM in sharestore this problem appear

vThinkBeyondVM · ‎09-22-2014

As you said its cold migration. It is mean that VM is powered OFF. Can you still please confirm? I could see, you are using vCenter server version 5.0 & without shared storage vMotion is not supported on 5.0.

BUT cold migration is supported without shared storage.

----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.

dhanarajramesh · ‎09-22-2014

keep in mind that FreeNAS standard permissions as below

The Maproot and Mapall options are exclusive, meaning you can only use one or the other--the

GUI will not let you use both. The Mapall options supersede the Maproot options. If you only

wish to restrict the root user's permissions, set the Maproot option. If you wish to restrict the

permissions of all users, set the Mapall option. can you check how do you configured? change it if necessary.

abdulhussein · ‎09-23-2014

Yes Vcenter 5 And cold migration(vm switch off) but i got this error message

All

unable to access file {share]new virtual machine