What's new

Solved Can not install Virtual Switch external in Hyper-V

Martin7

New Member
I am running Windows 8.1 Pro with Hyper-V enabled. When I had Windows 8 I could install a Virtual switch with out any problems, since upgrading I can not install a Virtual Switch with External or Internal settings.

Not sure if this is relevant or not but when I look at the Ethernet properties never "Hyper-V Extensible Virtual Switch" or "Microsoft Network Adapter Multiplexor Protocol" are ticked. I have tried ticking them but get the error message "Could not add the requested feature. The error is: The data is invalid". I have checked that I am using the latest and correct driver for the card.

Any help gratefully received.
 

Attachments

  • Capture.JPG
    Capture.JPG
    46.5 KB · Views: 8,100

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Martin7

New Member
I think it is a hardware problem - when I switch on the computer today there was no internet connection. Looking in the Device Manager there is a yellow exclamation mark next to the Broadcom Netlink and the message says "this device cannot start (code 10).

I will get a network card and see what happens!
 

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Hey,

Have your tried updating your network drivers?

It would be good to see how your network adapter setup looks an easy way or us to do this work is going to be in PowerShell.

Open PowerShell:

On the Start screen, type PowerShell, right-click the Windows PowerShell app tile, and then, in the app bar, click Run as administrator.

Once PowerShell is loaded you can run a command to get your Network adapters. Enter the cmdlet:

Get-NetAdapter

This will show in a table a list of your network adapters and under the column “InterfaceDescription

From here you will be able to see if you have any VEthernet networks created in your network.

I suggest you try and create a new virtual switch from PowerShell. The command will be shown below (Note you may want to delete previous Vethernet switches bound to the Network adapter before hand). The one thing you will need to change is the “-NetAdapterName”; input the name from the “Name” field from the “Get-NetAdapter” table.

The command below will create an external network with OS management enabled.

New-VMSwitch "VM Network" -NetAdapterName "Ethernet 2" -AllowManagementOS $True

Screen Shot 2014-02-05 at 22.43.43.png


Hope this helps.

Cheers,
Harry
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
Thank you - still have same problem

Thank you for your reply and help.

I followed your instructions and the Virtual Switch showed up in the PowerShell. I then removed it and then made a new one in the PowerShell - checked it with the Get-NameAdapter and all appeared to be ok.

But still when I run my Virtual machine it says there is no connection. The annoying thing is it all work in Windows 8 and it is only since I have upgraded to 8.1 that the problem has occurred. I have checked that I have the latest drivers and I have even done a Windows restore in case something had gone a miss.
 

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Hello Martin,

Ok, I am going to need to know a bit more about your setup.

Just get a few of the easy questions done :)

has Your hyper-v host machine currently got network?
Is the network from your machine using the Same network interface card as you have bound to the Vswitch?
Have you made sure in the Hyper-v Switch manager you have got the Virtual machine attached to the correct Vswitch?
Within the Virtual machine have you got the Network properties set to DHCP or static?
If static are your settings correct ? (please double check)

Are you able to ping google for example.
ping 8.8.8.8

are you able to ping the hyper-v host machine from the VM?
Can the Virtual machine be pinged from the Hyper-V host?

Also on the Virtual machine please try and run a troubleshoot problem - right click the connection icon in the bottom right and click "Troubleshoot Problem"

It is very hard to troubleshoot network problems with out knowing you setup.

for example from both machines seeing IPConfig /all and then seeing your network adapters might be useful and the rest of the topology


Cheers,
Harry
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
Hi Harry,
Going through your questions:
Yes - the host machine has network.
Yes - the Vswitch is bound to the only network card I have.
Yes - I only have one Vswitch
I believe the virtual machine is to DHCP it is running Windows XP - if I do an IPconfig it gives the following:
Connection-specific DNS Suffix . :
Autoconfiguration IP Address . . : 169.254.47.203
Subnet Mask . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . :

The only thing I can ping from the virtual machine is 127.0.0.7 and the 169.254.47.203 anything else returns "destination host unreachable".

No - I can't ping the host machine from the virtual machine.
No - I can't ping the virtual machine from the host.

If I run the network trouble shooter from within the virtual machine it ends with "Windows could not finish repairing the problem because the following action cannot be completed Renewing your IP address"

I have attached screen shoots of the IPconfig /all of the Host and the virtual machine.

Thanks again for your help.
Martin
 

Attachments

  • Host.PNG
    Host.PNG
    44.9 KB · Views: 84
  • Virtual.PNG
    Virtual.PNG
    18.1 KB · Views: 72

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Martin,

Currently your virtual machine is seeing what is called an APIPA address. If you want a little more information I will attach a link with a little synopsis:

What is Automatic Private IP Addressing (APIPA)? - Definition from WhatIs.com

Right we need your Virtual Machine not to be looking at this address so lets go in and set the Virtual Machines IP Address to static:

For this you are go in to the Virtual machines networking Settings:

Windows key
Type "Network and Sharing Center"
Click "Change Adapter settings"
Right click the ethernet adapter
click "properties"
Click "Internet Protocol Version 4(TCP/IPv4)

Now to set the static address (note you might want to log in to your router just to find an address that is not being to make sure you do not attempt to assign two machines the same IP address)

for example:
Ip Address: 192.168.0.20
subnet mask: 255.255.255.0
Default Gateway: 192.168.0.1

Primary DNS Server: 192.168.0.1

After setting your IP address correctly as static, restart your virtual machine and then come back to me with your findings and we will go from there.

Cheers,
Harry
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
Hi Harry,

Thanks again for your input.
I made the changes you suggested and there appeared to be some improvement.
The virtual machine now "thinks" it is connected, however there is no received data and it is not going on line or showing up in my router as an attached item and the Hyper-V shows that it doesn't have an IP address.

I have taken a few screen shots.

Martin
 

Attachments

  • Hyper-V.PNG
    Hyper-V.PNG
    4.2 KB · Views: 7,946
  • Virtual Local Area .PNG
    Virtual Local Area .PNG
    26.6 KB · Views: 7,961
  • VirtualXP.PNG
    VirtualXP.PNG
    18.8 KB · Views: 71

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Right as you are on XP you will need to use a legacy adapter in hyper-v it will not recognize a normal hyper-v switch
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Harrylowt

New Member
Pro User
To do this you will need to power down your virtual machine:

Bring up the virtual machine settings (right click vm settings)

Locate the Network Adapter > click "Remove", click "Ok"

Then click "Add Hardware" select "legacy Network Adapter", Click Add

Then bind the Vswitch to the new legacy adapter and boot that VM backup :)
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
Thanks Harry,

It is already set to "Legacy Network Adapter" and bound to the Virtual Switch!
 

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Have you installing the Integration Services?

Cheers,
Harry
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
More information:

I have three virtual machines and only ever run one at a time, they all connect via the same Virtual switch.
The Virtual XP is connected via a Legacy adapter - doesn't connect
The Virtual Windows 7 is connected via a Network adapter - doesn't connect
The Virtual Ubuntu connects via a Network Adapter and does connect and works fine.

Looking at the Hyper-V Networking Status all three say "Degraded (Intergration services upgrade required)" and does not show an IP address even though the Ubuntu machine is clearly connected and is shown in the router with an IP address.

Why the Ubuntu machine should decide to work now is beyond me as I haven't changed anything that would have affected that other than re-install the Virtual Switch.
 

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Martin7

New Member
Yes - integration Services are installed.
 

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
ok please can you try update the integration service with the following:

1 - Upgrade Hyper-V Host with latest code - RTM, Hotfix etc...
2 - Launch the Hyper-V Manager MMC
3 - Connect to the Hyper-V Guest System (1 at a time)
4 - Click Action - Insert Integration Services Setup
5 - Run through the prompts

After the VM should restart.

 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
Right, I have followed your instructions, things have changed but still no connection to the outside world.

Virtual machines running Windows 7 and Windows XP now both show an IP address in Hyper-V now which they didn't previously; but I still cannot connect to the internet and neither show as being connected to my router.

Thank you again for your input.
 

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Well let us hope we are going in the right direction!

Right lets try troubleshoot that windows 7 one first please can you right click network and troubleshoot problem and post the results.

Cheers,
Harry
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
This is what the Virtual Windows 7 says:
 

Attachments

  • Connections 7.PNG
    Connections 7.PNG
    36.3 KB · Views: 58
  • Virtual 7.PNG
    Virtual 7.PNG
    65.5 KB · Views: 59

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Harrylowt

New Member
Pro User
Martin,

Thanks for that I was hoping to see the graphical version.
If you click troubleshoot problem at the bottom of your second screenshot and send that would be most appreciated.
Cheers,
Harry
 

My Computer

System One

  • OS
    Windows Server 2012 R2 / 8.1
    Name
    Harry
    Occupation
    IT Consultant
    Country Flag
    UK
    State/Region Flag
    uk city of london

Martin7

New Member
Harry,

This is what I get if I click on the troubleshooting and the text in the previous screen shoot is what I am given when I click on "View detailed information".

Thanks again for you interest.
Martin
 

Attachments

  • Trouble shooting 01.PNG
    Trouble shooting 01.PNG
    12.2 KB · Views: 896

My Computer

System One

  • OS
    Windows 8
    System Manufacturer/Model
    Dell Studio XPS
    CPU
    Intel Core i3-530
    Motherboard
    dh57m01
    Memory
    4Gb
    Country Flag
    UK

Users Who Are Viewing This Thread (Users: 0, Guests: 2)

Top