[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 678
  • Last Modified:

Hyper-V VMs won't initialise

I have a new server 2012 DataCenter Hyper-V host, and I had created a Win7Pro VM (which was off) and had moved our SBS2003 to a second VM. I got the SBS VM running and it needed a re-start. After the re-start neither of the VMs will start.
I get the following error on both VMs; only the VM name is different:

Virtual Machine Connection

The application encountered an error while attempting to change the state of "VM-SBS2003"

"VM-SBS2003" could not initialize.


An attempt to initialize VM saved state failed.

"VM-SBS2003" could not initialize.(Virtual machineID
C501B627-CCD6-4654-8FDC-3A3b6AF9B3F1)

"VM-SBS2003" could not create or access saved state file
F:\Hyper-V\VMs\Virtual
Machines\C5...\C501B627-CCD6-4654-8FDC-3A3b6AF9B3F1.vsv.
Virtual machineID
C501B627-CCD6-4654-8FDC-3A3b6AF9B3F1
0
gregmiller4it
Asked:
gregmiller4it
1 Solution
 
gregmiller4itAuthor Commented:
I have searched for answers to this problem and tried a few things:
Re-started host: one person had seen the same problem and re-starting the host would fix it temporarily...it made no difference in my case.
Deleted both VMs and created new ones and still having no success

I am SOOOO stuck here and I don't know what to do!
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Create a new VM using the Hyper-V defaults. Bind an OS ISO to the new VM and run through the OS load steps to make sure everything is as it should be.

You can shut off the VM once the OS starts loading.

Replace the VHDX file for the above VM with the VHD(x) files for the VMs giving you a tough time. Start it up.

Note that you should have 1 vCPU assigned for both to start with and only 4GB of vRAM. You may need to not have a vNIC assigned until after you have installed Integration Services. Note: 2003 may not be a go on 2012 R2.
0
 
arnoldCommented:
it is peculiar that everything was running until you shutdown the two VMs and then they will not boot.
Have you looked at the referenced .vsv file to see what it is. Check the disk? Rename the .vsv to see whether on the next bootup a new file would be created?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
arnoldCommented:
Was anything installed on the hyper-v host prior to that: anti-virus etc?
0
 
gregmiller4itAuthor Commented:
Problem solved...
I started trying to work out why I might have problems accessing files and figured it could be a rights issue.
At some point in the whole exercise, I changed the default file locations for Hyper-V. I thought I had restarted one or both the VMs since then, but maybe not. Anyway, I deleted both the VMs, removed the Hyper-V role and changed the default file locations as I re-added the Hyper-V role. Then I re-created the two VMs using the same hdd files...and it works again.
So, I must have broken something without realising it and it didn't affect anything until I restarted the VM.
Thanks for your suggestions.
Note to self: don't play with Hyper-V default file locations once I have created VMs!!!
0
 
gregmiller4itAuthor Commented:
Solved it myself...see my last post
0
 
Martyn ElvyCommented:
I had a similar issue after storage migrating my Hyper-V VM's from on storage location to another.

The fix for me was based on the above, all I needed to do was delete the VM from the Hyper-V management console and then create a new VM and attach the drives.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now