none
vm (copied to new host) has no network connectivity RRS feed

  • Question

  • The problem:

    Yesterday we had a power outage.

    Fried the system disk (c:) on the host machine.

    I had configured all the virtual drives and virtual machines on a second, data disk (d:); thankfully this survived.

    Everything was working fine prior to the incident.

    I popped in a new c: drive, and re-installed server 2012 r2, and added hyper-v.

    created a new machine, using the old drives, and hooray, the vm booted with all the software intact.

    *however!* the vm doesn't have internet access, nor can it be pinged.

    Salient Details

    Once again everything was working prior to the power outage.

    I have two physical nics (nic1 nic2) in the box.  Nic1 is dedicated to the host, and it's ip is statically allocated (192.168.1.25). Nic2 is supposed to be dedicated to the vm, and I didn't bother assigning an IP to it. Both are connected to the network.

    When I first added the Hyper-V role though Server Manager, I noticed that the server name/ip it came up with was ServerName/[dynamically allocated IP of nic2]; that is, hyper-V seemed to be wanting to configure the server with nic2, rather than nic1.  Is this right?  There was no option to select 'ServerName/[nic1 IP]

    In HyperV after the reboot, I created a virtual switch with nic 2.  Then I created a new VM, but used the vhx file which was on the surviving physical D: drive.  I attached the virtual switch tp the new VM.

    The VM booted.  All the files were there.  However, the network icon in the system tray always indicates 'Unidentified network/limited' under 'Connections'

    What I've Tried:

    I found i had to reset the ipv4 static ip on the new virtual machine, as well as the dns host specification.

    I tried removing the HyperV role, disabling nic2, and re-adding the HyperV role.  This time the server it came up with was ServerName/[NIC1 IP].  Then re-enabled nic2, used it to create a virtual switch, and attached that to yet another created VM.

    My next try, as a diagnostic, is to create a completely new VM with a new install of the OS.  I'm doing this as a diagnostic, but forsaking the old disks has pretty unpleasant implications.

    It's got to be something simple!  Any help would be truly appreciated.

    thanks in advance



    dmc_lat47

    Tuesday, September 10, 2019 5:03 PM

All replies

  • Hi ,

    Did you mean that attaching all the VHD file in D drive will occur the same problem? 

    Did you try to export VM from other host and then import to the problematical machine to do a test? Check if this VM could have internet access.

    If possible, you could add an extra physical network adapter to the Hyper-V computer, create an External Virtual Network, connect the VMs to it to see whether you get the same issue.

    Best Regards,

    Candy



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Wednesday, September 11, 2019 6:41 AM
  • "created a new machine, using the old drives, and hooray, the vm booted with all the software intact."

    You need to configure the virtual switches on the new host in the same manner they were configured on the failed host.  Then you need to assign the virtual NIC(s) in the VM to the proper virtual switches.  When you create a new VM, even though you are using the same VHDX as a running VM, that new VM has no idea of the NIC configuration.


    tim

    Wednesday, September 11, 2019 2:02 PM
  • Hi ,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.                   

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Monday, September 16, 2019 2:10 AM