How to add NFS share as a "locally" attached volume in Server 2012 Hyper-V.

I am trying to create a network storage space, where I can export both Hyper-V and VMware VMs.  For VMware you can do this over SMB but it's ultra slow.  Hyper-V you can sort of do this via powershell from the host its self (forget the Hyper-V Manager...uggh), but I cannot get the import powershell command to work.

I have been able to attach "local" storage to these Hyper-V hosts using ISCSI, and export/imports work well.  But you cannot connect more than one host to a single LUN as I was hoping.  Oh well.  Anyway.

So now I am looking at NFS which is a cluster based file system that is supposed to be able to do what I am after.  IE single location, multiple servers attaching to it and seeing it as local storage, VM platform agnostic.  This of course maybe not correct and a lapse in my researching skills. :-P

However if it is correct logic, I am running into issues using the mount command via command prompt on server 2012 hyper-v, saying that mount is not a recognized command.  I try to install the client for NFS on both my Windows 8.1 pro laptop and on the Server 2012 Hyper-v and it's not even an option for add new Windows features.  How does one attach a Windows OS to a NFS volume as local storage and not a network drive?

Thanks :-)
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robin CMSenior Security and Infrastructure EngineerCommented:
On Server you can use powershell: install-windowsfeature nfs-client
On Windows 8.1 Enterprise you can go to Windows Features, and the client is under Services for NFS, Client for NFS. You say you have the Pro edition though, which does not include Client for NFS (
However this will not give you anything more than a "mapped drive" which will only be available for the current user, and not Hyper-V.

Depending on what iSCSI target you're using, you can mount multiple hosts to one target, but think about how iSCSI works - it present as a disk - which means you have to format it. If you want to mount this to both vSphere and Hyper-V hosts then you've got no common filesystem to format it as - vSphere wants VMFS, Hyper-V wants NTFS.

You can do what you want (sort of) but need to give each system what it wants. vSphere is happy with NFS, Hyper-V is happy with SMB. Both can be created from a Windows File Server:
D:\VMs (SMB share)
D:\VMs\vSphere (NFS share)
D:\VMs\Hyper-V (SMB share)
From your Windows 8.1 machine you just connect to \\fileserver\VMs and you see two folders, each with the respective VMs in them.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CnicNVAuthor Commented:
Ok thanks for the info, it seems like Hyper-V is not an idea solution for shared storage, IE it doesn't really support a cluster based file system.  I will try to get things working the way I want using VMware.  Just have to decide if I should use NFS or VMFS.

Thanks for the feedback and sorry for the delay in my following up with points.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.