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-3A
"VM-SBS2003" could not create or access saved state file
F:\Hyper-V\VMs\Virtual
Machines\C5...\C501B627-CC
Virtual machineID
C501B627-CCD6-4654-8FDC-3A
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-3A
"VM-SBS2003" could not create or access saved state file
F:\Hyper-V\VMs\Virtual
Machines\C5...\C501B627-CC
Virtual machineID
C501B627-CCD6-4654-8FDC-3A
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.
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.
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?
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?
Was anything installed on the hyper-v host prior to that: anti-virus etc?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solved it myself...see my last post
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.
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.
ASKER
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!