Nothing but problems today - now all my VM's have lost their IP config


  1. Posts : 87
    Windows 10
       #1

    Nothing but problems today - now all my VM's have lost their IP config


    Have had a Hyper-V setup going here for years without any issues - and then suddenly today - things started falling away.

    First my WDS server suddenly stopped serving up it's PXE boot to a new VM I was testing - that led me to investigate a few other things which then pointed to a Virtual Switch problem vis Hyper V

    I have confirmed that the Host Virtual Switch is now working correctly:

    Nothing but problems today - now all my VM's have lost their IP config-2021-03-17_20-43-36.png


    but two existing Guest VMs (that I have had for at least a year) will not get an IP address no way or no how. I have updated the VM setting countless times dropping the network adapter and re-adding the "new" V-Switch I created.

    But each time I boot on these VMs - they come up with 169.xxx.xxx.xxx address and of course no connectivity.

    I have attempted a battery of resets and so on in each VM and still no joy. All I get this:

    Nothing but problems today - now all my VM's have lost their IP config-2021-03-17_20-41-19.png

    What am I missing?

    Sonic.
      My Computer


  2. Posts : 1,244
    Windows 10 Pro x64 21H2 (Build: 19044.1415)
       #2

    SonicMojo said:
    But each time I boot on these VMs - they come up with 169.xxx.xxx.xxx address and of course no connectivity.
    169.254.xxx.xxx is Link-Local address that the client self assigns when there are no DHCP servers available.
    In your case DHCP server is virtual switch set up and configured in host OS.

    make sure the guest OS adapter "default gateway" field is configured according to vEthernet adapter IP address field.
    (both in IPv4 item in adapter properties)
      My Computer


  3. Posts : 87
    Windows 10
    Thread Starter
       #3

    zebal said:
    169.254.xxx.xxx is Link-Local address that the client self assigns when there are no DHCP servers available. In your case DHCP server is virtual switch set up and configured in host OS. make sure the guest OS adapter "default gateway" field is configured according to vEthernet adapter IP address field. (both in IPv4 item in adapter properties)
    SOLVED!
    Ok - so I slept on this and as usual - clarity!

    The available DHCP address pool was very narrow (I set this several years ago) - never thinking I would need more than 40 available IPs.
    I increased the pool, rebooted the router - and of course the VMs get an IP straight away.
    Cheers,
    Sonic.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:21.
Find Us




Windows 10 Forums