StarWind Software

Ladies and Gentlemen!

So after some people claimed they have Hyper-V over NFS running "just fine" but being "not supported" we've decided to run verification sequence for:

1) Newly created VM on NFS share
2) Move VM from SMB3 / CSV to NFS share
3) Move VM manually (copy) and then try to run it from NFS share

So you can read whole story here:

http://www.starwindsoftware.com/blog/hy ... nfs-share/

Making long story short: NO GO

Anton

An interesting experiment to say the least.

I would be curious is the NFS server in question was actually running Linux instead of Windows Server.

As in my experience (with Server 2008), Server for NFS is extremely unreliable for any decent workload.

From my understanding it's more of the client then server issue:

MSFT is missing some features from NFS (resilient file handles? cached oplocks?). At some point we MAYBE use non-Windows NFS sever as "Part II" of the article.

We also prefer to spawn a FreeBSD or OpenSUSE VM with Samba to serve NFS requests rather then using native Windows NFS. Performance is better and we have more experience with UNIX

thefold wrote:An interesting experiment to say the least.

I would be curious is the NFS server in question was actually running Linux instead of Windows Server.

As in my experience (with Server 2008), Server for NFS is extremely unreliable for any decent workload.

Don't you have to install the NFS client on Hyper-v
Mount the NFS share
the tell Hyper-v what local place or directory to put its VM.

the min you put "\\" that tells hyper-v its smb.

I will try it with VMware workstation, the lab of hyper using nfs.

Thanks.

Good luck on that Please keep us updated about your progress in "Hyper-V + NFS" combination. Much appreciated!