When trying to create a new virtual machine form failover clustering manager or Hyper-V manager i keep getting a message similar to the below.

The virtual disk and xml files are created but it can not seem to link iscsi controller to the virtual disk..

I tried the resolution here but it did not work: http://kazanas.com/hyper-v-account-does-not-have-sufficient-privilege-to-open-attachment/

Note the Virtual Machine ID that is listed in the "General access denied error (0x80070005)" error message.For example, consider the following error message:

In this example, the Virtual Machine ID is 5FC5C385-BD98-451F-B3F3-1E50E06EE663.

The blog you referred to is regarding errors that happen when attempting to power on a VM.  Commonly after restoring a VM folder.

The easiest way to reset permissions on the virtual disks is to remove the virtual disk from the VM, save, then add the virtual disk back to the VM and save.

This causes Hyper-V to reset the permissions on the objects.

Also, check your exclusions list if you have antivirus running on the Hyper-V Server.

The blog you referred to is regarding errors that happen when attempting to power on a VM.  Commonly after restoring a VM folder.

The easiest way to reset permissions on the virtual disks is to remove the virtual disk from the VM, save, then add the virtual disk back to the VM and save.

This causes Hyper-V to reset the permissions on the objects.

Also, check your exclusions list if you have antivirus running on the Hyper-V S

Try please to create a virtual machine without a disk and post the result ple

So..

If you keep cancelling the create process, the entire process has not had time to complete.  Not just disk creation but permissions setting.

I have to ask, why do you keep cancelling the VM creation?  (since that seems the root of the issue).

If you are creating a fixed sized virtual disk, it will take a while.  The bigger the disk the longer.

Also, since you are creating the VM on the CSV volume, you should be making it HA and thus creating it in the Failover Cluster Manager, not Hyper-V Manager. (yes, confusing).

Hi Sir,

>>When trying to create a new virtual machine form failover clustering manager or Hyper-V manager i keep getting a message similar to the below.

Within Hyper-v manager , please try to create a new VM into local disk to check the result .

In addition , if there is any antivirus software please disable it .

>>The virtual disk and xml files are created but it can not seem to link iscsi controller to the virtual disk.

Could you please explain ""can not seem to link iscsi controller to the virtual disk" for us ?

By the way , I have seen some permission issues within  CSV , I would suggest you to create a new folder under Cluster Shared Volume then create new VM in that folder  .

Best Regards,

Elton Ji