Hello,
I realized this strange problem with Windows 2008 R2 VMs running on Hyper-V Server 2012. My Hyper-V Server 2012 host has been running mix of VMs just fine. I've a Linux VM running, a couple of Windows 2012 R2 VMs, a Windows 8.
I created three new VMs, gave them decent hardware. 4 GB of RAM each. A fixed VHDX file of 40 GB. I left processor allocation to Hyper-V. Windows 2008 R2 ISO was mounted to all three. Installation started. The VMs were plugged into an external network to access internet for Windows activation and software updates.
Installation went smooth. I could log on and kick off windows updates installation. it took a reboot but when it came back, strange things started happening.
First, after VM won't respond to CTRL+ALT+DEL command from the VM console; saying 'VM doesn't did not respond to command'. I inserted integration start up disk from Media Menu on VM's console window. It allowed me to log on this time. I continued to download/install windows updates to update and complete that. All important updates were selected (even in first step above) and none of optional update was selected.
This round of updates download/install updates finished and VM rebooted. Again, when it became available it stopped responding to any of commands sent to VM, Reset, Stop,Shut down, Turn off and won't allow CTRL+ALT+DEL. Strangely this time it didn't like accepting mounting integration services start up disk. The message displayed; when any of these actions were performed, is "RPC service not available".
What could go wrong with Windows 2008 R2 VM created just now behaving like this?
Did someone experience issues like this with just built Windows 2008 R2 VMs? Please share and advise.
Thanks.
Regards,
Shahzad.