hasselholz
Cadet
- Joined
- Feb 16, 2014
- Messages
- 4
Hi folks,
I've built my first FreeNAS server last week, which is successfully running the current version 9.2.1. The NAS is joined to my Active Directory and CIFS/SMB sharing works great for normal files.
As FreeNas 9.2.1 now supports SAMBA 4 and SMB 3, I was tempted to try out a SMB3 compatible file share as a VHD storage for my Hyper-V hosts. However I have experienced a strange behavior. This is what I tried to do:
- Created a ZFS dataset named VHD01 for storing the VHDs.
- Created a CIFS share for the above dataset
- Set permission so that my user account, and my hyper-v hosts have full control to the data (I tested connectivity by mapping the CIFS from windows 2012 r2 server which was successful)
Here comes the weird part:
- I tried to create a new virtual machine from HyperV Manager von Server 2012. I configured the VM storage to be in \\mynas\vhd01\vm001. At the end of the wizard I receive an error: "Failed to create the virtual hard disk. The system failed to create \\mynas\vhd01\vm001\vm001.vhdx: Incorrect function. (0x80070001)".
Trying to accomplish the same on a remote windows 2012 file server works pretty fine.
My assumption was that running VHDs on a SMB 3 compatible CIFS share would run the same way as on a native Microsoft Windows 2012 server.
Am I missing something or is this currently not supported?
btw. I'm aware that I could create a Zvol and ISCSI target for storing VHDs, however I wanted to give SMB 3 as a VHD storage a try.
Anyone else experiencing the same strange behavior?
Thanks in advance for any help
Udo
I've built my first FreeNAS server last week, which is successfully running the current version 9.2.1. The NAS is joined to my Active Directory and CIFS/SMB sharing works great for normal files.
As FreeNas 9.2.1 now supports SAMBA 4 and SMB 3, I was tempted to try out a SMB3 compatible file share as a VHD storage for my Hyper-V hosts. However I have experienced a strange behavior. This is what I tried to do:
- Created a ZFS dataset named VHD01 for storing the VHDs.
- Created a CIFS share for the above dataset
- Set permission so that my user account, and my hyper-v hosts have full control to the data (I tested connectivity by mapping the CIFS from windows 2012 r2 server which was successful)
Here comes the weird part:
- I tried to create a new virtual machine from HyperV Manager von Server 2012. I configured the VM storage to be in \\mynas\vhd01\vm001. At the end of the wizard I receive an error: "Failed to create the virtual hard disk. The system failed to create \\mynas\vhd01\vm001\vm001.vhdx: Incorrect function. (0x80070001)".
Trying to accomplish the same on a remote windows 2012 file server works pretty fine.
My assumption was that running VHDs on a SMB 3 compatible CIFS share would run the same way as on a native Microsoft Windows 2012 server.
Am I missing something or is this currently not supported?
btw. I'm aware that I could create a Zvol and ISCSI target for storing VHDs, however I wanted to give SMB 3 as a VHD storage a try.
Anyone else experiencing the same strange behavior?
Thanks in advance for any help
Udo