locked
Nested Visualization Not Working On TP5 But Used to Work With TP4 RRS feed

  • Question

  • Hi All,

    I'm running Windows 10 1511 build 10586 with Hyper-V.

    Before TP5 I managed to run nested Visualization VMs running Windows Server 2016 TP4 with Hyper-V successfully.

    Recently I  Installed Windows Server 2016 TP5 on a VM and enabled nested Visualization as

    same before (with TP4) but the VMs will not start.

    Does any one know If TP5 and Windows 10 Build 10586 nested Visualization work ?

    Can someone please try and tell me ?

    Error below

    Thanks,

    Simon

     

    Thursday, May 12, 2016 2:00 AM

Answers

  • Well testing the best I can installing a Server 2016 TP5 as a guest on the Windows 10 10586 it fails to run Hyper-V, so the same as you. Same error and notice Virtual Machine Bus Provider is not started in Device Manager.

    Running TP5 as a guest on 14342 Hyper-V works and the nested guests starts. So perhaps my first post is closer to mark and the change in Hyper-V to configuration 7.1 is the change and will need Windows 10 to catch up with Server TP5 before it works. So guess when the next major Windows 10 threshold is released TP5 will install as a Hyper-V guest and nested VM's will work.


    • Edited by -Mr Happy- Sunday, May 15, 2016 9:47 PM
    • Marked as answer by Simon201 Monday, May 16, 2016 11:18 AM
    Sunday, May 15, 2016 9:46 PM

All replies

  • Hi Simon,

    >>Does any one know If TP5 and Windows 10 Build 10586 nested Visualization work ?

    Based on my search, the nested Visualization could be worked.

    But I have no the environment to test this issue currently.

    Besides, I found out two links, might give us some bright-light.

    Hyper-V Nested Virtualization

    https://blogs.msdn.microsoft.com/msgulfcommunity/2015/10/14/welcome-to-hyper-v-nested-virtualization/

    https://charbelnemnom.com/2015/05/is-hyper-v-vnext-going-to-support-nested-virtualization-hyperv-containers-windowsserver/

    If this issue still persists after trying many times, I suggest you could wait for the official released version.

    Thanks again for your understanding and sharing.

    Best regards,


    Andy_Pan

    Thursday, May 12, 2016 9:09 AM
  • I noticed that on TP4 the later Windows 10 preview did not work with nested Hyper-V, This thread.

    To me this is down to the configuration version of the guests, 7.1 in TP5 and Windows 10 14291 and beyond.

    The later Windows 10 preview builds run nested Hyper-V on TP5 ok, I have run 14332 and 14342 ok.

    https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced has Insider build ISO to download if you want to try that.

    I will try 10586. EDIT tested ok, see below.


    • Edited by -Mr Happy- Thursday, May 12, 2016 9:00 PM
    Thursday, May 12, 2016 8:23 PM
  • 10586.318 nested Hyper-V works for me with TP5, so my above is wrong I would say :) Not sure if this is do with the latest update to 10586 released that took it too .318 or not, what version is your 10586?

    Thursday, May 12, 2016 9:00 PM
  • Hi There, Thanks for testing that. I'll check my version and will let you know.
    Thursday, May 12, 2016 9:04 PM
  • Just checked my version and I'm on 10586.218.

    I'll update it to 318 and will check again.

    Thursday, May 12, 2016 10:34 PM
  • I patched my Windows 10 to 318 however I'm still getting the same error.

    Any idea ?

    See screenshot below.

    Friday, May 13, 2016 1:48 AM
  • I am a little confused with you screenshots, the name Server2016TP5, so not Windows 10? or is that the name of the Windows 10 guest?

    What is running on what? My set-up, Windows Core Server 2016 TP5 Hyper-V running on a physical machine. As a guest on that WIN10HV, so that WIN10HV guest is enabled for and supports Hyper-V. The enable nested was run against the WIN10HV guest.

    Friday, May 13, 2016 7:40 PM
  • Windows 10 is the host, server2016tp5 is a vm running on the host (guest). I'm trying to start a vm inside server2015tp5 which fails.
    Friday, May 13, 2016 8:11 PM
  • Ok thanks, I have been reading this back to front then, so I have been no help to your question as I misunderstood it appears. Sorry.
    Friday, May 13, 2016 8:17 PM
  • Well testing the best I can installing a Server 2016 TP5 as a guest on the Windows 10 10586 it fails to run Hyper-V, so the same as you. Same error and notice Virtual Machine Bus Provider is not started in Device Manager.

    Running TP5 as a guest on 14342 Hyper-V works and the nested guests starts. So perhaps my first post is closer to mark and the change in Hyper-V to configuration 7.1 is the change and will need Windows 10 to catch up with Server TP5 before it works. So guess when the next major Windows 10 threshold is released TP5 will install as a Hyper-V guest and nested VM's will work.


    • Edited by -Mr Happy- Sunday, May 15, 2016 9:47 PM
    • Marked as answer by Simon201 Monday, May 16, 2016 11:18 AM
    Sunday, May 15, 2016 9:46 PM
  • Thanks for testing and confirming that you are getting the same error.

    Hope MS will release a fix soon.


    Sunday, May 15, 2016 10:57 PM
  • I hope too :(

    Same problem for me.

    Build Windows 10 : version 1511 (OS Build 10586.318)

    Build TP5 : version 1511 (OS Build 14300.1016)

    TP5 installed on Win10


    Sunday, May 15, 2016 11:15 PM
  • I couldn't wait, So I installed 14342.1000 and my nested VMs are working :)

    Monday, May 16, 2016 11:17 AM