asked on

windows 2012 hyper v machine won't change state / start

after an incorrect restart was carried out on our single windows 2012 server, or main domain controller virtual machine showed "saved" status. the exchange hyper v server started normally.

when i tried to start the saved hyper v machine, it advised that the status could not be changed and failed to start.

i deleted the saved status files and tried to start again, but the same thing occurs - it says the status failed to change and the virtual machine fails to start.

can anyone advise what we need to do to get this operational?

many thanks

Patrick Bogers

Hi

Go to the directory where the VM files are stored and (re)move .bin and .vsv files (save them elsewhere until sure)
Now your machine should start.

Cheers

nigelbeatson

ASKER

while i was awaiting a reply, i closed down the exchange hyper v machine - so both vm's were stopped, and restarted the hyper v host.

once restarted, i started the domain controller and it started perfectly. i then tried to start the exchange server virtual machine and now this one says that the status cannot be changed and will not start???

any ideas?

thanks

nigelbeatson

ASKER

i have just let the domain controller vm fully update and settle, then closed it down, so both are stopped and the exchange server then started ok. i then cannot start the domain controller.

it would appear that i can't have both started at the same time??

any ideas?

thanks

ASKER CERTIFIED SOLUTION

Patrick Bogers

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

nigelbeatson

ASKER

could the host system volume being full cause this? i notice that 80gb of data had been saved to this, filling it up. i can only presume it's the saved vm status that created this as our data is still present on the file server.

i am in the process of securing this data just in case, but once i have will remove this freeing up some space on the hyper v host system volume.

if you don't think this would cause the other vm from starting please let me know as all other resources look good to me??

please advise

regards
nigel

Patrick Bogers

Hi

If all other resources look to be freely available it can be you have dynamically expending vhd(x) which can exceed the physical storage causing the hyper-v manager preventing you to start the second vm.

nigelbeatson

ASKER

the domain controller vm shows .98tb free of 1.21tb?? so no where near full.

the hyper v host shows as being nearly full and reporting this in the event log.

not sure about the exchange 2016 vm at this stage, as i can't open it.

will close the domain controller and then open the exchange vm to check,

thanks

Patrick Bogers

There looks to be some kind of overstrechting the hyper-v manager is aware off, sure will find it.

nigelbeatson

ASKER

You were sort of right, so here are the points, Many thanks. I found that something had taken up the system volume drive storage space, and this prevented the virtual machine from starting. Once cleared it started without problem. Many thanks,

Patrick Bogers

Nice! You made me a EE millionaire. Thank you too.

nigelbeatson

ASKER

well done!! :)