JM,
I think you may have hit the mark. Integration services are not installed so I'll do that and see if everything works OK.
Thanks!
Main Topics
Browse All TopicsHello,
My basic system configuration is a Windows 2008 server with SP-1 running on an Intel VT enabled CPU with 8 GBytes of RAM. The Hyper-V (the RTM version) role has been installed.
I set up an "External" virtual network (VN) connected to the host's Ethernet adapter, a Broadcom NetXtreme Gigabit Ethernet NIC. The external VN's name is "hvnet-1".
I have created two clients: One a Windows Vista Enterprise VM and the other a SuSe Enterprise Server 10U2 VM. When configuring these systems I configured their virtual network cards to connect to hvnet-1.
However, neither the SuSe Linux or the Vista virtual machines recognize their virtual network adapters, essentially informing me there there is no network hardware available.
Since this problem is common to both of the Virtual Machines, there seems to be a problem with my configuration of the Virtual Network.
Does anyone have any ideas?
Thank you!
"donpar"
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hello,
After installing the integration components, the Vista client networking worked just fine...
However, when I try to do the same thing for the SuSe Linux client, there are no components specified on the "CD" for Linux. I "Googled" around and found the Hyper-V Linux Integration Components were officially released about 3 months ago. But I'll be darned if I can find a link to download these released components.
Have you worked with the Linux components? If so, a URL to download them would be appreciated.
Thanks,
"donpar"
Hello donpar,
Unfortunately no, I have no experience in using the Linux integration components as I do not run Linux in VM. There is a workaround that you might like to try until you figure out how to install the Integration Services for Linux; add a legacy network adapter. To do this, shut down the virtual machine and go into the settings. Go to "Add Hardware" and add a Legacy Network. Linux should be able to see this network interface, according to Sean in his blog here; http://blogs.technet.com/s
The only download I could find for the Linux Integration Services was on Microsoft Connect, and it appears to be a beta version. Perhaps you could try the workaround for now and I'll try and find out more about the Linux Integration Services?
Regards,
James
Also, if you want to try the version of the Integration Services I came across, you can go to http://connect.microsoft.c
Let us know how it goes if you do decide to try it.
Regards,
James
Don,
No problem. It looks like there is quite a big time difference between us, which is why it took me so long to respond to you the first time. I had another brief look on google for a comprehensive guide to installing the Hyper-V Integration Services on Linux, but had no real luck. Sorry I cannot provide any real assistance on this side of your issue, but I wish you good luck and hope you get it working. If you do, it would be great if you could explain the process - I'm sure there are many others who would benefit from the knowledge.
Regards,
James
James,
The Legacy Network card workaround did the trick! After configuration, it obtained a valid IP address which persisted after a reboot.
Since this works fine for my purposes, will not need to pursue the Integration Components and further for now. It is strange that I saw twice that the released version of the SuSe components were available in September, but are apparently nowhere to be found.
Thanks again for you excellent help!
Best regards,
Don
James,
Per your suggestion above, wanted to add a bit to flesh out the solution.
I first shut down the SuSe Virtual Machine, then went to its "Settings" menu and removed the network adapter already in place. Then brought up the "Add" window and selected "Legacy Network Adapter" and added it to the VM configuration.
Saved the settings and brought up the client. Using the "ifconfig" command, found that there was indeed an "eth0" network adapter but it did not yet have an IP address.
Ran the "YAST2" SuSe configuration tool and selected "Network Card" under the "Network Devices" header. When the next screen came up, selected the "Traditional method using ifup" option.
On the next screen select the "DECchip" adapter (this IS Legacy!) and click on "Finish". YAST then does its thing and "ifconfig" showed that the VM now had an IP address which persisted when the system was rebooted.
Hope this info will be of some use to others...
Regards,
Don
Business Accounts
Answer for Membership
by: Jm_saundersPosted on 2008-12-02 at 15:13:43ID: 23081862
You do not mention it in your question, so I must first ask that you ensure that the Integration Services are installed on your clients. You can do this whilst connected to one of the virtual clients from Hyper-V and selecting "Action -> Insert Integration Services Setup Disk". Assuming autoplay is enabled on the client VM, the Integration Services will be installed automatically. Once the client has restarted, the driver for the network interface will be installed.
Please let us know once/if you have performed this task.