Hi guys,
I haven't been able to create a Datastore for a ESX Server 3 in the testing environment. I have a shared folder in a Windows host with several Virtual Machines. I point to the server IP and Share name but I keep recieving "Error During the Configuration of the Host: NFS Error. Unable to Mount Filesystem: Unable to connect to NFS Server".
Is it possible to accomplish what I'm trying to do?
Thank you for your time.
is this a an NFS share formated as VMFS file system?
Don't understand very well what you are trying to do...
More details please
Is this ESX 3 vmfs datastore?
Regards
Jon
No, the folder is not partition as VMFS. I'm not sure how to do that.
I am trying create a Datastore from the ESX3 to a Windows Server Shared Folder . When I attempt to connect I get the error listed before. You asked if the NFS share was formated as a VMFS file system. The answer is no but I am also not sure how that can be accomplished or if that is absolutly required.
Thanks in advance for your attention to this matter.
Is this a standard windows share or is it a NFS share??
The reason I ask is because windows shares which use the SMB/CIFS protocol are not supported for use as datastores. NFS on Windows requires additional software such as services for Unix and additional configuration.
-
RHCE, VCP
It was a standard Shared Folder in Windows. I start downloading the Windows Services for Unix to install it on the server and create a NFS share.
Thanks!
Thanks everybody for your help.
I was able to create and connect the DataStore to the ESX server. Now the problem is, I'm not able to browse the folders inside the Share from the ESX VI Client.
At the same time of this post, I'm doing a research about this issue.
Thanks again.
I got it.
Some changes in the Services for Unix console allowed me to browse the folders (VM's) in the Windows Server.
When I browse through the New Virtual Machine Wizard, the *.vmdk file is not listed (visible); but through the Browse Datastore the files are there. I right click them and select Add to Inventory.
Now... the virtual Machines are listed as (invalid) in the Resource Pool.
Thanks again for your time and cooperation.