Hyper-V Images wont start since upgrade to R2 (Failed to set folder permission)
- I have just upgraded one of my Hyper-V servers to 2008 R2, no configuration changes have been made to permissions etc.
I have 5 Hyper-V images complete with snapshots that since the upgrade, 4 of the images stored on a NAS device will now not start ! however the 1 image stored on a local drive boots and works with no issues.
The Error I directly recieve from Hyper-V when I attempt to start one of the NAS images is: "failed to set folder permission"
The .VHD's themselves are storred on remote NAS, the snapshots and virtual machine images are storred on a local drive with over 300gb's of free space. the permissions on the NAS device have not changed, and nothing more has been done to the Hyper-V server since the upgrade to R2.
Server Spec:
Dell Power Edge 2950, (2x quad core xeon E5430, 16gb memory, Dell Perc 6/i Raid Controller, Broadcom 5708C twin NIC's, Intel Pro 1000 DTtwin NIC, Drive config is RAID 5 - partitioned 50gb c:\, 358gb d:\.
I can see the following errors sifting through the event logs:
The Virtual Machines configuration 60B0408B-467F-489D-BBA7-D9D89D6EAC0B at '\\nas-02\VHD-Backups\snapshots' is no longer accessible: Invalid handle (0x80070006)
'The system failed to create '\\nas-02\VHD-Backups\Live VM Images\New Virtual Machine.vhd'. Error Code: 2424869 (new image creation attempt)
'XP Test' failed to set folder permission for \\nas-02\VHD-Backups\Live VM Images\IT Testing Environment\Test-XP: General access denied error (0x80070005) (Virtual machine ID 42F114AE-C32F-4596-A634-5D3A4FD38C43) (Attempt to start an existing iamge)
Troubleshooting so Far:
Attepted to create a .VHD image on another network device, same error recieved.
Created another Image on the local server, Image boots and runs.
Image from NAS device copied to local drive, Image boots and runs.
Image copied from local drive to NAS device, Image fails to boot with same error as above.
any assistance greatly appreciated. - I suspect theres some bizarre permission issue thats come into force since the R2 upgrade.
TS GURU- Edited byMetallicabk Friday, October 16, 2009 9:40 AMspelling
Answers
Hi,
I am sorry to let you know that Network-attached storage (NAS) is not supported for Hyper-V.
For more information, you can refer to:
Planning for Disks and Storage
http://technet.microsoft.com/en-us/library/dd183729(WS.10).aspx
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorThursday, October 22, 2009 8:38 AM
All Replies
- Additional to this thread, it would appear since the upgrade the R2 server doesnt seem to want to authenticate with our server 2003 domain. as another administrator has logged on and is unable to access domain resources without first authenticating.
TS GURU Hi,
I am sorry to let you know that Network-attached storage (NAS) is not supported for Hyper-V.
For more information, you can refer to:
Planning for Disks and Storage
http://technet.microsoft.com/en-us/library/dd183729(WS.10).aspx
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorThursday, October 22, 2009 8:38 AM

