• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Installing Ubuntu on Hyper-V

KapsZ28

2[H]4U
Joined
May 29, 2009
Messages
2,114
I was easily able to install Ubuntu 9.04 and 9.10 in Hyper-V, but for some reason the network adapter isn't showing up. From what I read, Ubuntu usually works right out of the box when installed on Hyper-V. Any ideas why it might not be detecting the network adapter?

I'm not much of a Linux guy, but I tried manually adding a network adapter through the network manager, but it doesn't seem to do anything. I think it was easier installing Ubuntu on Virtual Server 2005.
 
OK when you say you had to install a legacy adapter, do you mean you actually had to use a different network card? I recently installed Ubuntu 9.10 in a Hyper-V VM and have the same issue with no network connectivity. I shut down the VM, went to settings and removed the current network adapter. Then I went to add hardware and chose Legacy Network Adapter. I still could only choose from the same network card that I could before and I still have no connectivity. Am I doing something wrong here?
 
OK when you say you had to install a legacy adapter, do you mean you actually had to use a different network card? I recently installed Ubuntu 9.10 in a Hyper-V VM and have the same issue with no network connectivity. I shut down the VM, went to settings and removed the current network adapter. Then I went to add hardware and chose Legacy Network Adapter. I still could only choose from the same network card that I could before and I still have no connectivity. Am I doing something wrong here?

No, I didn't have to use a different network card. I did exactly what you just explained. Add Hardware>Legacy Network Adapter and then selected my network card.

Did you modify any network settings in Ubuntu prior to adding the legacy network card? I think I added mine prior to a fresh install and it worked right away.
 
No, I didn't have to use a different network card. I did exactly what you just explained. Add Hardware>Legacy Network Adapter and then selected my network card.

Did you modify any network settings in Ubuntu prior to adding the legacy network card? I think I added mine prior to a fresh install and it worked right away.

That's probably it maybe I need to fix up the network cards prior to installing. I will try that real quick. Thanks for replying.
 
OK I reinstalled the OS with just the legacy adapter there this time and it now recognizes that there is an existing network but then cannot connect to it. Any other ideas?

Thanks again for your help.
 
So Ubuntu sees a network adapter, but you have no Internet connection?

Are you sure the network adapter on the server is configured correctly? Do you have multiple network adapters? Do you have any other VMs installed with the network connection working properly?
 
So Ubuntu sees a network adapter, but you have no Internet connection?

Are you sure the network adapter on the server is configured correctly? Do you have multiple network adapters? Do you have any other VMs installed with the network connection working properly?

The host server has the network adapter configured correctly as far as I know because the internet works on the host server. I can get to anywhere from it. No other VM's are installed right now this is a brand new server and this is the first time we are trying Hyper-V.

Here is what I mean when I say Ubuntu sees the network adapter. Previously, when it was not set up as legacy, when you click the network connections icon in Ubuntu nothing would come up, no eth0 or anything. Once I reinstalled after changing the adapter to legacy, it shows that it is attempting to connect (shows the little looping circles or whatever they are) and eventually just fails and says no connection; eth0 does show up in the menu though.
 
I would say that is a configuration issue with your network adapter. Just because the server has Internet access, doesn't mean it will work on a VM. For one, make sure Microsoft Virtual Network Switch Protocol is listed and checked in the LAN properties. It is hard to say what other settings you should have since I don't know what server you are using or how it is configured. I am using 2008 and have 2 LAN adapters. Below is a screen shot of them. An additional one shows up after the installation of Hyper-V. All of them have different settings and perform different functions on the server.

LAN.jpg
 
I would say that is a configuration issue with your network adapter. Just because the server has Internet access, doesn't mean it will work on a VM. For one, make sure Microsoft Virtual Network Switch Protocol is listed and checked in the LAN properties. It is hard to say what other settings you should have since I don't know what server you are using or how it is configured. I am using 2008 and have 2 LAN adapters. Below is a screen shot of them. An additional one shows up after the installation of Hyper-V. All of them have different settings and perform different functions on the server.

LAN.jpg

The server is a Dell R610 and it is running Windows Server 2008 Standard. I checked the Microsoft Virtual Network Switch Protocol box and still getting the same problem in the VM.
 
But how many LANs do you actually have? My server has two built-in LAN cards and both are enabled. When I installed Hyper-V, there is now a third LAN called Virtual Network. If you don't have an additional LAN called Virtual Network, then something probably didn't install properly.
 
But how many LANs do you actually have? My server has two built-in LAN cards and both are enabled. When I installed Hyper-V, there is now a third LAN called Virtual Network. If you don't have an additional LAN called Virtual Network, then something probably didn't install properly.

There are four cards in the server and a 5th one shows up now, the virtual one. Is there anything special I have to do to the settings for that one?
 
There are four cards in the server and a 5th one shows up now, the virtual one. Is there anything special I have to do to the settings for that one?

My second physical LAN is setup with ONLY Virtual Network Switch Protocol checked. Then the virtual LAN has everything checked EXCEPT Virtual Network Switch Protocol.
 
My second physical LAN is setup with ONLY Virtual Network Switch Protocol checked. Then the virtual LAN has everything checked EXCEPT Virtual Network Switch Protocol.

OK so here is where I am. Out of the four LAN's, two are being used and two are currently disabled. One of them I have now designated for the virtual LAN only. I unchecked everything except for the Switch Protocol on that physical LAN. In the virtual one I checked everything (except IPv6). When I apply the changes the virtual LAN sits there with "Identifying..." where it usually just says "Enabled". I tried manually setting the IP and gateway and such (based on the subnet it is on of course) and still it just sits there with "Identifying...".

Again, thanks for taking the time to help and try to work this out.
 
Back
Top