Forum Discussion

Matt Simms's avatar
Matt Simms
Copper Contributor
Mar 25, 2018

Windows Server 2019 Preview Build 17623 Hyper-V Issue

Hello Everyone, just downloaded the Windows Server 2019 Preview Build 17623 and commenced to build an environment using Hyper-V. The Hyper-V role installed successfully after a restart and I created ...
Hyper-V
MarcoMangiante's avatar
MarcoMangiante
Iron Contributor
Mar 28, 2018

Hello,

 

I installed Server Core on an HP ProLiant DL380 G6, enabled the Hyper-V role, created a vm with Windows 10 and started it without any issue; the only problem found is on the network in the guest vm: infact I created an external virtual switch bound to the nic used on the host but it doesn't connect to internet and doesn't ping the network gateway.

 

Marco

Matt Simms's avatar
Matt Simms
Copper Contributor
Mar 30, 2018

Hey Marco,

 

Are there IP Address settings on the virtual switch adapter on the Hyper-V Host?

 

By default the adapter may be called something like "vEthernet (Microsoft Network Adapter Multiplexor Driver - Virtual Switch)". Log into your Server Core, then once you have logged in launch PowerShell within the command prompt. Then run this command to display what adapters you have Get-NetAdapter

 

Note the ifIndex of the vEthernet (Microsoft Network Adapter Multiplexor Driver - Virtual Switch) adapter, for example 22, and then check your IP settings with this command using the ifIndex.

Get-NetIPConfiguration -InterfaceIndex 22

 

Let me know how you go

 

Cheers,

Matt

 

  • MarcoMangiante's avatar
    MarcoMangiante
    Iron Contributor
    Mar 30, 2018

    Hello Matt,

     

    the strange thing is that the nic has the address that usually a network takes when there is an unidentified network, 169.253.12.63.

     

    The Get-NetAdapter gives this:

     

    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
    ----                      --------------------                    ------- ------       ----------             ---------
    vEthernet (External)      Hyper-V Virtual Ethernet Adapter             16 Up           00-25-B3-E3-69-E8        10 Gbps
    Ethernet                  QLogic BCM5709C Gigabit Ethernet ...#49       8 Disconnected 00-25-B3-E3-69-E8          0 bps
    Ethernet 3                QLogic BCM5709C Gigabit Ethernet ...#50       6 Disconnected 00-25-B3-E3-69-EA          0 bps
    Ethernet 4                QLogic BCM5709C Gigabit Ethernet ...#48       5 Up           00-25-B3-E3-69-E6         1 Gbps
    vEthernet (InternalVne... Hyper-V Virtual Ethernet Adapter #2          28 Up           00-15-5D-00-28-01        10 Gbps
    Ethernet 2                QLogic BCM5709C Gigabit Ethernet ...#51       4 Up           00-25-B3-E3-69-EC         1 Gbps

     

    and if I apply the command to see the ip this is the result:

     

    InterfaceAlias       : vEthernet (External)
    InterfaceIndex       : 16
    InterfaceDescription : Hyper-V Virtual Ethernet Adapter
    NetProfile.Name      : Unidentified network
    IPv4Address          : 169.254.12.63
    IPv6DefaultGateway   :
    IPv4DefaultGateway   :
    DNSServer            : fec0:0:0:ffff::1
                           fec0:0:0:ffff::2
                           fec0:0:0:ffff::3

     

    I also seen this with Get-VMNetworkAdapter -All (but I never used previously this command so I don't know if it is so that the ip address doesn't appear for External switch):

     

    InternalVnet40  True                        InternalVnet40 00155D002801 {Ok}
    External        True                        External       0025B3E369E8 {Ok}
    Scheda di rete  False          vm-w10-mgt   External       00155D002805 {Ok}   {169.254.202.201, fe80::5012:480e:323...
    Scheda di rete  False          vm-w10-n1    InternalVnet40 00155D002802 {Ok}   {192.168.40.200}
    Scheda di rete  False          vm-w10-n2    InternalVnet40 00155D002803 {Ok}   {192.168.40.201}
    Network Adapter False          vm-w2k19-pre External       00155D002806        {}

     

    Seems like that the virtual nic that Hyper-V creates was not bound to the physical nic.

     

    Any suggestion?

     

    I'm also trying if there is the same behavior with the 17623 Semi-Annual build. I'll let you know.

     

    Marco

     

     

     

      • Matt Simms's avatar
        Matt Simms
        Copper Contributor
        Mar 31, 2018

        Hi Marco,

         

        Good to hear that you might have found a solution.

         

        I am curious about your previous post though, you have both a vEthernet (External) adapter and a vEthernet (Internal) adapter on your VM Host. Are you using the vEthernet (Internal) adapter?

         

        In my environment if my VM Host has more than one physical NIC I tend to Team them for redundancy and performance. I do this before I install the Hyper-V role.

         

        I can post the PowerShell commands that I use to create a teamed NIC. Then after installing Hyper-V role I disable DHCP and tcpip6, set a static IP Address and DNS on the  Hyper-V Virtual Ethernet Adapter.

         

        Also Project Honolulu is a good way to manage Server core versions in conjunction with PowerShell and RSAT.  Below is the link.

         

        https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewserver

         

        Regards,

        Matt

Resources