11 October 2010

SCVMM Error (12700) Failed to start virtual machine


One of the oldest and best ways to keep track of the states of your virtual machines is to keep copies of your virtual disks.  This means multiple copies of your .vhd files.  This is NOT snapshots or checkpoints.

SCVMM gives you the option of migrating machines to your library.  This is handy but sometime you just want to grab an existing disk and replace the current one.  I recently tried that and ran into this error:


"Error (12700)
VMM cannot complete the Hyper-V operation on the hyperv01 server because of the error: 'servername' failed to start. (Virtual machine ID C4A9BFD2-848F-4F23-ACB7-608AD634AD2D)

'servername' Microsoft Emulated IDE Controller (Instance ID {83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to Power on with Error 'General access denied error' (0x80070005). (Virtual machine ID C4A9BFD2-848F-4F23-ACB7-608AD634AD2D)

'servername': IDE/ATAPI Account does not have sufficient privilege to open attachment 'C:\ProgramData\Microsoft\Windows\Hyper-V\servername\Windows 2008 x64 Standard Template_disk_1.vhd'. Error: 'General access denied error' (0x80070005). (Virtual machine ID C4A9BFD2-848F-4F23-ACB7-608AD634AD2D)

'servername':  Account does not have sufficient privilege to open attachment 'C:\ProgramData\Microsoft\Windows\Hyper-V\servername\Windows 2008 x64 Standard Template_disk_1.vhd'. Error: 'General access denied error' (0x80070005). (Virtual machine ID C4A9BFD2-848F-4F23-ACB7-608AD634AD2D) 
 (Unknown error (0x8000)) 

Recommended Action
Resolve the issue in Hyper-V and then try the operation again."

I found this rather odd since I was the creator / owner of the file and I was logged in as an administrator.  Looking at the .vhd file I noticed a padlock over the file icon.

I have not been able to track down exactly what it means but changing the NTFS file permissions got rid of the padlock.  One that was done then I could start the virtual machine again.

The problem comes in when a file is copied to or created inside the virtual machine file structure.  So when you copy or or create a file in the following directory you get the padlock.

C:\ProgramData\Microsoft\Windows\Hyper-V\servername\

This is strange since you should inherit the permissions from the parent folder when you create or copy a file.  Looking at the parent folder advance permissions shows that there are permissions that apply on to the parent folder and subfolders but not the files too.

I change the advanced permission for "Virtual Machines" to apply to  "This folder, subfolders and files" and apply it to object in the container.  Then the padlock goes away.




No comments:

Post a Comment