Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I restarted my Host server after shutting down three guest VMs. After I restarted the machine I tried to start the VMs and got an error stating the the VM failed to start.

SERVERNAME failed to start.

Attachment 'avhd file path' is read only. Please provide read/write access to the attachment. Error: 'General access denied error'

SERVENAME failed to start. (virtual machine ID 17292200-wd22-dd22-d23-dddddd2222)

The issue seems to be with the disk space. The VHD file for this VM is 128 GB and there are two AVHD files of 58 and 75 GB. Whereas the total disk space on this drive (E) is 280 GB - the free space is only around 23 GB. I understand that the error is caused by the unavailability of the required disk space.

Unfortunately, I cannot increase the disk space on this drive. However I have another drive (D) that has 400 GB of free space. I exported this VM to D drive and then tried to add the copied AVHD files but it gives me a similar error.

I am running Windows Server 2008 R2 Datacenter.

Any help is appreciated.

share|improve this question
    
Are you sure the file permissions are correct? –  Chris S Oct 2 '12 at 19:28
    
How did you export the files? Via the UI? Or did you just copy them? –  Steven Murawski Oct 2 '12 at 19:35
    
Chris - The file permissions are correct. I have used this method to assign permissions to the avhd files. support.microsoft.com/kb/2249906 Steven - I exported the files through the Hyper-V Manager. –  ahmedz Oct 2 '12 at 19:39
    
And the snapshots did not export with the VM image? They should have exported to a Snapshots folder in the export process. –  Steven Murawski Oct 2 '12 at 20:08
    
The snapshots did export and an AVHD file of the same size was created on the other drive. However the snapshots folder is empty, the AVHD file is in the same folder as the VHD file. –  ahmedz Oct 2 '12 at 20:33
show 2 more comments

1 Answer

Based on the scenario and the discussion in the comments, I would attempt to import the exported VM as Hyper-V exported it. You may need to adjust the location of files in the .exp file.

You will want to delete the previous machine's configuration from Hyper-V before importing the VM, if you want to keep the same VM ID. If you don't care, you can re-import the VM with a new ID.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.