Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Hyper-V VMs won't initialise

Posted on 2015-01-01
7
Medium Priority
?
587 Views
Last Modified: 2015-02-24
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
Comment
Question by:gregmiller4it
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 

Author Comment

by:gregmiller4it
ID: 40527015
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
 
LVL 39

Expert Comment

by:Philip Elder
ID: 40527035
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
 
LVL 79

Expert Comment

by:arnold
ID: 40527067
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
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 79

Expert Comment

by:arnold
ID: 40527074
Was anything installed on the hyper-v host prior to that: anti-virus etc?
0
 

Accepted Solution

by:
gregmiller4it earned 0 total points
ID: 40527108
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
 

Author Closing Comment

by:gregmiller4it
ID: 40533182
Solved it myself...see my last post
0
 

Expert Comment

by:Martyn Elvy
ID: 40627641
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

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why should I virtualize?  It’s a question that’s asked often enough.  My response is usually “Why SHOULDN’T you virtualize?”
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question