Windows Server TechCenter >
Windows Server Forums
>
Hyper-V
>
Hyper V networking works on Server 2008 R2 guests, but not Server 2008
Hyper V networking works on Server 2008 R2 guests, but not Server 2008
- 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
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.- Marked As Answer byDavid Shen - MSFTMSFT, ModeratorMonday, October 19, 2009 8:34 AM
- 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)- Proposed As Answer byBrian Borg Friday, September 18, 2009 8:29 PM
- Marked As Answer byDavid Shen - MSFTMSFT, ModeratorWednesday, September 23, 2009 2:16 AM
All Replies
- 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)- Proposed As Answer byBrian Borg Friday, September 18, 2009 8:29 PM
- Marked As Answer byDavid Shen - MSFTMSFT, ModeratorWednesday, September 23, 2009 2:16 AM
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.- Marked As Answer byDavid Shen - MSFTMSFT, ModeratorMonday, October 19, 2009 8:34 AM
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.- BrianEh,Your fix:"Using the Hyper-V manager Console, open the console of the VM and choose Action, Install Integration Services - then respond to any prompts."Does not work. I get the prompt that there are updates needed but after it finishes up the network drivers are still nowhere to be found. I even tried uninstalling and reinstalling only from the Hyper-V manager, still no go, whatever is done from the SCVMM 2008 R2 Install virtual guest services does not allow the network drivers on the VM to be installed.I haven't found or figured out a hack yet, but I consider this to be a major bug. I was considering on using 2008 R2 Core on all my host servers and managing everything from my SCVMM 2008 R2 Server, however since you NEED a server not running 2008 R2 and you NEED a Hyper-V manager it doesn't look like this will be possible. Wasn't the whole reason for SCVMM to have a single point of management which they now just made impossible?If I'm wrong please show me the light because there isn't a whole lot of discussion on this issue which shouldn't even exist in my opinion.
- Installing the ICs performs the same action in the VM, regardless of whether SCVMM or the Hyper-V console is used.
In a nutshell an ISO is attached to the VM - the rest is carried out by whomever is building the VM.
-- a user with local administrator rights must be logged into the console of the VM. And the prompts (in the VM) must be answered.
Tip - If the "found new hardware" dialog appears (in the VM), you need to manually cancel it to allow the ICs to install.
Also, the ICs will only work with specific operating systems and patch levels - they are not universal.
If you are using an OS that is not supported by the ICs, then configure your VM with a Legacy Network Adapter instead of a Network Adapter. Most operating systems have a built in driver for the Legacy Network Adapter as it emulates an older Intel NIC.
I am really not sure what issue you are experiencing, and I am not sure of your expectations. Greater detail in your description would be necessary.
I am also not positive what is meant by this statement:
"I was considering on using 2008 R2 Core on all my host servers and managing everything from my SCVMM 2008 R2 Server, however since you NEED a server not running 2008 R2 and you NEED a Hyper-V manager it doesn't look like this will be possible."
SCVMM and Hyper-V manager are complementary to each other. Hyper-V manager allows easier configuration of certain things. Can SCVMM be used without Hyper-V manager? - yes, I know folks who do.
But you still (might) need additional (existing consoles) to do some detailed configuration of the host.
Since this is not the SCVMM forum the answer was specific to Hyper-V - as some folks run Hyper-V without SCVMM, it is not required.
Brian Ehlert (hopefully you have found this useful)
