none
Hyper-V server 2016 - Nested on Nas [solved]

    General discussion

  • Hi All,

    I installed a Hyper-V server 2016 on Qnap Nas with no problem : It runs fine !

    The problem : i create a VM on the Hyper-V, but it doesn't work... I have the error (picture 1)... The picture 2 is the same but in English (for the forum)...

    When i run the script for Hyper-V to see if the device is ok with the virtualization, no problem (it's fine : see the picture 3)...

    don't understand ???

    Thanks for an idea or a solution please !!!

    InterRupteur




    Tuesday, February 28, 2017 6:00 PM

All replies

  • There are no pictures.

    What script are you running?  Not all hypervisors pass through the necessary components for virtualization, or require additional changes to be made.  

    Hyper-V isn't supported in a nested configuration, but it does work under VMware's hypervisors with the correct settings.  

    Are you sure your NAS's hypervisor passes through whats needed?

    See: https://www.tenforums.com/virtualization/47749-kvm-host-w10-vm-hyper-v-running-another-vm-nesting.html

    Tuesday, February 28, 2017 7:34 PM
  • Hi,
    Could this help you what comes to the qnap NAS?
    https://forum.qnap.com/viewtopic.php?t=118544

    Regards,
    -Tomi

    Tomi Pietilä

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Blog
    Twitter
    LinkedIn

    Tuesday, February 28, 2017 9:44 PM
  • Hi Smjain,

    i can't put pictures, it tells that the forum must verify my username ???

    I run these scripts :

    .\Enable-SRV-HPR-01.ps1 -vmname WIN2016-LAB

    Result :

    This script will set the following for WIN2016-LAB in order to enable nesting:
        None, vm is already setup for nesting

    ---------------------------------------------------

     .\Get-NestedVirtStatus.ps1

    Result :

    Getting system information...done.
    Getting build information...done.
    Validating host information....done.

    The virtualization host SRV-HPR-01 supports nested virtualization: YES


    Computer                     : SRV-HPR-01
    Manufacturer                 : QEMU
    Model                        : Standard PC (i440FX + PIIX, 1996)
    ProccessorManufacturer       : GenuineIntel
    Product Name                 : Hyper-V Server 2016
    Installation Type            : Server Core
    Edition ID                   : ServerHyper
    Build Lab                    : 14393.447.amd64fre.rs1_release_inmarket.161102-0100
    HypervisorRunning            : True
    FullHyperVRole               : True
    HostNestedSupport            : True
    HypervisorLoadOptionsPresent : False
    HypervisorLoadOptionsValue   :
    IumInstalled                 : False
    VbsRunning                   : False
    VbsRegEnabled                : False
    BuildSupported               : True
    VbsPresent                   : False

    Looking for VMs...found 1 VMs.
    Validating virtual machines...done.

    The virtual machine WIN2016-LAB supports nested virtualization: YES

    Name                           : WIN2016-LAB
    SupportsNesting                : True
    ExposeVirtualizationExtensions : True
    DynamicMemoryEnabled           : False
    SnapshotEnabled                : False
    State                          : Off

    ------------------------------------------------------------------

    So i don't understand, why i can start the vm for installation of Windows 2016 server ???

    Thanks for your help !

    InterRupteur


    • Edited by InterRupteur Tuesday, February 28, 2017 10:45 PM
    Tuesday, February 28, 2017 10:16 PM
  • Hi Tommy,

    thank you for your return !

    The Hyper-v was installed with success, it runs fine ! It's just the Vm on the Hyper-V that causes to me a problem... If you watch before the result of the scripts, you will see that it's ok... So i don't understand, why the vm won't start...

    The error : An error occured while attemping to start the selected virtual machine(s). Failed to start the virtual machine 'WIN2016-LAB' because one of the Hyper-V components is not running.

    Thanks

    InterRupteur

    Tuesday, February 28, 2017 10:23 PM
  • anyone to help me.... :-(
    Wednesday, March 1, 2017 8:47 AM
  • Hi,

    are you sure that your QNAP model is supported for running of MS Hyper-V server?

    Check here https://www.qnap.com/cs-cz/business_solutions/con_show.php?op=showone&cid=7

    You should also check if MS Hyper-V Server 2016 is supported on QNAPs.

    As for nested virtualization:

    You need to have dynamic memory turned off on your VM - so use static Memory assignement and 

    Set-VMProcessor -ExposeVirtualizationExtensions $true

    Than you can install and run Hyper-V server 2016 on your VM running on Hyper-V 2016.

    Radek

    Wednesday, March 1, 2017 9:47 AM
  • Hi Radek,

    yes because at the moment, Hyper-V server 2016 is running fine on my Qnap... It's not the problem with the first Hyper-V... The problem become with the VM (Hyper-v or Windows 2016 server or other system) on the Hyper-V...

    Checking :

    - Set-VMProcessor -ExposeVirtualizationExtensions $true ==> OK
    - .\Enable-SRV-HPR-01.ps1 -vmname WIN2016-LAB ==> OK

    Result :

    This script will set the following for WIN2016-LAB in order to enable nesting:
         None, vm is already setup for nesting

    - \Get-NestedVirtStatus.ps1 ===> OK

    Result :

    Getting system information...done.
     Getting build information...done.
     Validating host information....done.

    The virtualization host SRV-HPR-01 supports nested virtualization: YES


     Computer                     : SRV-HPR-01
     Manufacturer                 : QEMU
     Model                        : Standard PC (i440FX + PIIX, 1996)
     ProccessorManufacturer       : GenuineIntel
     Product Name                 : Hyper-V Server 2016
     Installation Type            : Server Core
     Edition ID                   : ServerHyper
     Build Lab                    : 14393.447.amd64fre.rs1_release_inmarket.161102-0100
     HypervisorRunning            : True
     FullHyperVRole               : True
     HostNestedSupport            : True
     HypervisorLoadOptionsPresent : False
     HypervisorLoadOptionsValue   :
     IumInstalled                 : False
     VbsRunning                   : False
     VbsRegEnabled                : False
     BuildSupported               : True
     VbsPresent                   : False

    Looking for VMs...found 1 VMs.
     Validating virtual machines...done.

    The virtual machine WIN2016-LAB supports nested virtualization: YES

    Name                           : WIN2016-LAB
     SupportsNesting                : True
     ExposeVirtualizationExtensions : True
     DynamicMemoryEnabled           : False
     SnapshotEnabled                : False
     State                          : Off


    - Dynamic memory turned off on the VM ===> OK


    Despite all this, it does not work or it doesn't start. The same error like before (5th post)...

    I don't know what can i do now...

    InterRupteur

    Wednesday, March 1, 2017 3:26 PM
  • Hi,

    let's proceed step by step:

    1) SRV-HPR-01 is Win2016 Core with Hyper-V on physical Host ..this one is running OK

    2) Any VM running on that host is running OK with no problems (For example another Win server 2016 core without Hyper-V, or some testing Win7 gen 1 virtual machine)?

    3) In this step you are trying to Install Hyper-V role on WIN2016-LAB Virtual Machine and enable Nested virtualizuation, this one suceeded with no error. WIN2016-LAB is gen 2 Virtual machine with VM version 8.0.

    4) Now you run any VM on WIN2016-LAB Hypervisor and it fails...

    Is this your procedure? Have you checked running VM in step 2 ??

    Radek

    Thursday, March 2, 2017 7:34 AM
  • Hi,

    no no it's not this :

    1) NAS Qnap with virtualization Inside (physical Host)

    2) On the Qnap virtualization, i installed an Hypervisor Hyper-V : SRV-HPR-01 (is running fine)

    3) On the SRV-HPR-01, i created a VM : WIN2016-LAB

    4) Win2016-LAB (gen 2 Virtual machine ) : doesn't start...

    5) I created another VM : WIN2017-LAB (gen 1 Virtual machine ) : the same probleme...

    InterRupteur

    Thursday, March 2, 2017 8:50 AM
  • Hi all,

    so i beat it because it's not possible on the config i made...

    Thanks to all

    InterRupteur

    Sunday, March 5, 2017 3:46 PM
  • Hi InterRupteur

    as you use a let's call it appliance type of hardware you need to check with the vendor what they support.

    Cheers

    Udo

    Sunday, March 5, 2017 6:11 PM