Windows Server TechCenter > Windows Server Forums > Hyper-V > Hyper V networking works on Server 2008 R2 guests, but not Server 2008
Ask a questionAsk a question
 

AnswerHyper V networking works on Server 2008 R2 guests, but not Server 2008

  • Thursday, September 17, 2009 2:23 PMKelly AZ Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Ok, I am befuddled by this. I am running Server 2008 Standard R2 with just the Hyper-V role installed.

    I create a VM and install Server 2008 R2 Standard. The external network, connecting me to the internet, works fine and the guest OS automatically has a working network device and connection. I shut down this VM and leave it off.

    I then create another VM, exactly the same, choosing the same external network as above. THis time I install Server 2008 Standard (non-R2). The serve does not find its network card, and therefore cannot connect to the internet. When I look at teh guest OS, there is a yellow splay in the device manager for the virtual network adapter.

    So, on the same hardware and host OS, a R2 guest can see the virtual network but a non-R2 guest cannot.

    Server is a new Dell T300 with embedded dual NIC (Broadcom NetExtreme gibabit), Quad Xeon, 16Gb RAM.

    I also had problems getting Server 2008 (non-R2) guests to see the network on different server (Dell T105). I could not solve the problem, so I tried using Xenserver 5.5 and it worked great.

    Trying to avoid switching to Xenserver 5.5 on this T300, but I'm about done with Hyper-V's networking weirdness.

    Any ideas? Thanks!
    Kelly

Answers

  • Friday, September 18, 2009 6:45 AMDavid Shen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hello Kelly, 

    BrianEh's suggestion makes sense. 

    The yellow splay shows in device manager within guest OS, and it indicates that the Integration Service may not be installed properly in the guest OS. 

    On Hyper-V, the guest OS should depend on the VMBUS which included in integration service to utilize its host network card. 

    Can you please refer to BrianEh's suggestion to install Integration services on that problematic guest OS (Windows Server 2008)? And then, please check to see if you can access the external network. 

    Hope this can be helpful.


    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Thursday, September 17, 2009 3:04 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Did you install the Integration Components within the VM?

    Server 2008 has the ICs built in to the OS (they are extremely similar to device drivers).
    But, versioning issues can come into play - the host and guest must match for optimum performance.

    with the release of R2 the ICs included backward compatibility - thus allowing an R2 VM to 'just work' when you install it onto a Hyper-V v1 (2008, but not 2008 R2) host.

    Now, when you have a Server 2008 VM on an R2 host - the VM built-in ICs are older than the host ICs - thus the ICs in the VM need to be updated.
    Using the Hyper-V manager Console, open the console of the VM and choose Action, Install Integration Services - then respond to any prompts.

    Brian Ehlert (hopefully you have found this useful)

All Replies

  • Thursday, September 17, 2009 3:04 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Did you install the Integration Components within the VM?

    Server 2008 has the ICs built in to the OS (they are extremely similar to device drivers).
    But, versioning issues can come into play - the host and guest must match for optimum performance.

    with the release of R2 the ICs included backward compatibility - thus allowing an R2 VM to 'just work' when you install it onto a Hyper-V v1 (2008, but not 2008 R2) host.

    Now, when you have a Server 2008 VM on an R2 host - the VM built-in ICs are older than the host ICs - thus the ICs in the VM need to be updated.
    Using the Hyper-V manager Console, open the console of the VM and choose Action, Install Integration Services - then respond to any prompts.

    Brian Ehlert (hopefully you have found this useful)
  • Friday, September 18, 2009 6:45 AMDavid Shen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hello Kelly, 

    BrianEh's suggestion makes sense. 

    The yellow splay shows in device manager within guest OS, and it indicates that the Integration Service may not be installed properly in the guest OS. 

    On Hyper-V, the guest OS should depend on the VMBUS which included in integration service to utilize its host network card. 

    Can you please refer to BrianEh's suggestion to install Integration services on that problematic guest OS (Windows Server 2008)? And then, please check to see if you can access the external network. 

    Hope this can be helpful.


    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Monday, September 21, 2009 11:30 AMDavid Shen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Kelly,

    I’d like to check how things are going. Did you have the chance to try the troubleshooting steps? If you have any other questions, please do not hesitate to let me know.


    This posting is provided "AS IS" with no warranties, and confers no rights.