none
Windows 8 Hyper-v External Switch

    Question

  • HI ALL

    I have been running windows 8 for about 3 months without hyper-v and its been perfect. However i need to create some test machines and run some VM's so  have enabled the feature etc. etc..

    Created my external V-Switch and added that to my VM's everything is fine, except over the last 2/3 days every time i reboot my machine the External switch status changes to unidentified network and the only way i have found of fixing the issue is to completely removed the external switch and re-create. which in turn sometimes messes with the physical NIC settings on the host machine and i loose connectivity completely. 

    This is really getting frustrating but i want to persist with hyper-v and not go back to VMware. 

    Can someone help 

    Chris

    Tuesday, September 10, 2013 9:13 AM

Answers

All replies

  • Hi,

    First, I would like to know whether there is any change on your computer before this issue, like installing updates or other program.

    Please be aware that this issue can be caused if the VM Network Adapter doesn't setup correctly.

    Please check following articles and try solutions there and let me know what’s going on:

    FIX WINDOWS 8 AND HYPER-V VIRTUAL SWITCH PROBLEMS

    http://blog.siliconvalve.com/2012/09/26/fix-windows-8-and-hyper-v-virtual-switch-problems/

    Windows Hyper-V "Unidentified Network"

    http://www.howtonetworking.com/virtualization/hyper-vnet1.htm

    Also, I would like share following articles with you to see the detailed information about creating external switch in hyper-v:

    Hyper-V Virtual Switch 101: How to create and use Virtual Switches to connect Virtual Machines to Network

    http://www.eightforums.com/tutorials/19359-hyper-v-virtual-switch-manager.html

    Hope these could be helpful and keep post.


    Kate Li

    TechNet Community Support

    Wednesday, September 11, 2013 10:00 AM
    Moderator
  • HI All

    I have been rather busy so did not get a chance to say what the fix was. Basically as I did not have a WSUS set up in my environment windows update was downloading a new drivers for the NIC on the HyperV host,

    This meant that after every reboot I guess the new driver was applied and the Virtual Extension then failed to work.

    I downloaded the latest driver packs from the manufactories installed then re-created the switches and fingers crossed no issues.

    The strange thing is although windows thought the drivers where newer they were actually a version older than the drivers which already installed.

    Very strange issue.

    Chris

    Tuesday, October 08, 2013 8:16 AM