none
Running Hyper-V on a Virtual Server with Windows Server 2012 R2

    Question

  • Hi, We are having an issue at work and searching in the forums and MS support we can't find an answer. 

    We have a server running Windows Server 2012 R2. This is actually a virtual server cloud assigned for our project. In order to test our tools we need to run a VM on Hyper-V. When we try to run the program we receive an error (attached screenshot) but there isn't any error codes or clue about what could be.

    The error is:  The Virtual Machine Management Service failed to start the virtual machine 'VMServer

    because one of the Hyper-V components is not running (Virtual machine ID A25071D6-A9FC-44A8-9C73-B6D1DC4D761C).


    Please, anyone could give me some advise on this matter?

    Thanks in advance!

    Tuesday, February 14, 2017 2:29 PM

Answers

  • Hi Blitz,

    If I understand right, you are trying to install and run hyper-v inside of windows server 2012 R2 virtual machine? 

    If that is the case you will not be able to do it. Nested Virtualization is working in Windows Server 2016

    • Marked as answer by Blitz55 Wednesday, February 15, 2017 1:43 PM
    Tuesday, February 14, 2017 2:43 PM
  • Agree with Nedim.  You can install Hyper-V in a VM, but you cannot run any virtual machines under.  Nested virtualization is a feature that was introduced in Windows/Hyper-V Server 2016.  So you need a physical host running Windows/Hyper-V Server 2016.

    . : | : . : | : . tim

    • Marked as answer by Blitz55 Wednesday, February 15, 2017 1:43 PM
    Tuesday, February 14, 2017 5:51 PM

All replies

  • Agree with Nedim.  You can install Hyper-V in a VM, but you cannot run any virtual machines under.  Nested virtualization is a feature that was introduced in Windows/Hyper-V Server 2016.  So you need a physical host running Windows/Hyper-V Server 2016.

    . : | : . : | : . tim

    • Marked as answer by Blitz55 Wednesday, February 15, 2017 1:43 PM
    Tuesday, February 14, 2017 5:51 PM
  • Thank you so much guys! 
    Wednesday, February 15, 2017 1:45 PM
  • Also, thank you Tim! 
    Wednesday, February 15, 2017 1:46 PM