Hyper V VM's on SMB

Question

Hi I tried posting this on the FreeNAS forums as well but no luck.

I've got a pool setup on FreeNAS, I've not configured any ACL's or permissions for it so as default (apart from this dataset below), I've setup a SMB for a dataset which I can access on both of my Windows machines (as root) - I can edit, rename, create, remove etc so no problems there.

However, I've got my Hyper V virtual machines in this dataset, I map Hyper V to these virtual hard drives in the dataset and get an error, whatever way I try and path Hyper V to the dataset SMB it doesn't like it - F:\VMs or path shown in screenshot (\FREENAS\Network\VMs)

So I jumped on Putty to try and adjust the permissions using chmod -R 777 /directory
Soon as I try Hyper V again and gives the same error, this + appears at the end of the permissions, I did some research and used the setfacl -bn /directory command which gets rid of the ACL successfully so I can set permissions again (if I wanted to)

But I just can't get my head around if the directory has full permission for user, group and everyone - why is Hyper V still having issues? I looked to set permissions on the dataset but no 'everyone', ACL will just mess up the datasets as from previous experience. Is there a Windows ID I can create a user on FreeNAS to give owner of the dataset? How can I give Hyper V permission to this directory to edit, read etc?

Any idea's will be much appreciated

Answer 1

Hi,
I’m not sure if this could be the cause, but I noticed that the files where the errors came from are .avhdx, which are differencing disks:

I’m guessing that maybe you can try using the vhdx files instead and see what happens.

Thanks for your time.
Best regards,
Danny

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi @Anonymous ,

Thank you for your response.

Unfortunately this didn't work - please see attached screenshot.

This is purely down to permissions as even if I try and export these VM's to the network shared drive I get this error, eventhough it's created the folder, nothings in it -
Although as I mentioned, I gave the directory full permission for user, group and everyone and Windows is still struggling.
Essentially, I wanna store my VM's in this network share and have it mapped to my desktop which is running Hyper V so I won't have to worry about the local storage on my desktop.

Answer 3

Hi Jordan,
I’m not sure if this works, but maybe you can take a look:
https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/hyper-v-virtual-machine-not-start-0x80070005

Thanks for your time.
Best regards,
Danny

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.