Jump to content

Recommended Posts

Posted

Hi all, been a long time since I've had to post here.

I'm managing a network where we have 2 Server 2012 R2 host servers running a handful of VM's each, but our 2 Server 2019 VM's seem to have issues with rebooting, no other VM has issues, just the Server 2019 ones.

It doesn't matter if it's a manually triggered reboot, or one for updates, they won't boot, they'll just sit at the spinning dots until you turn it off and back on.

Turning the server off through Hyper-V manager, and then back on doesn't have the same issue, thankfully.

Has anyone come across this before, of have any ideas?

I've already checked host resources and VM resources, there's ample CPU, Memory and storage, so it's not a resource issue, there's nothing to explain it in the logs and we're Microsoft -30 for updates on both hosts and VM's.

Posted
Hi,

 

Server 2019 isn't supported as a guest operating system on Server 2012R2.

 

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn792027(v=ws.11)

 

Doesn't mean it wont work but it's going to make troubleshooting difficult. What do you see in the event logs?

 

Do you have another host running Server 2016 or above that you could test the vm on?

 

 

Hi Ronnoco thanks for that, unfortunately our only hosts are 2012 R2, and I don't see approval coming through to upgrade them any time soon, they joys of inheriting someone else's mess.

Unfortunately there's nothing in the event logs other than the shutdown event, after that the next entry is the cold boot after I turn the power off through Hyper-V because it's hung.

It runs like a dog too, so I'm guessing there are also resource things going on in the background of 2016 and 2019 hosts.

Posted

I feel your pain my friend. I inherited an incredibly complex school network and on my second day, I came in to find nothing working, just solid green lights on the SAN. I could have cried!

 

On your 2019 VM, have you got secure boot turned on? If so, is it possible to try turning this off?

 

You could use this incompatibility as a business case to upgrade one of your hosts. Do you have an old sever kicking around you could install a newer version of server os on and then tests the server 2019 vm?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...