Mark Brown's Blog

TFS, Visual Studio, SQL Server, BizTalk, SharePoint, .Net, and more ...

Trouble with Virtual Server 2005 (R2) Standard Edition and Network Cards

I was having trouble with Virtual Server 2005 recognizing my host network cards.  After many tries of uninstall/reinstall, add/remove virtual network machines from NIC cards, and other various config changes I finally figured out my situation.

Symptom

  • Goto Virtual Server Admin website
  • Goto Server Properties
  • Goto Physical Computer Properties
  • I could not see any network cards

You may also have problem seeing new network cards or if you reconfigured your network card order.

Resolution

Unfortunately the only resolution I found was to completely remove Virtual Server.   Removing Virtual Server required more than just uninstall through add/remove programs.

Here is the steps to perform

  • Backup all your VMC and VHD files (be safe rather than sorry!)
  • Stop the Virtual Helper and Virtual Server services
  • Goto add/remove programs and uninstall Virtual Server
  • Delete the directory and all files in the direcotry
    • C:\Document and Settings\All Users\Application Data\Microsoft\Virtual Machine Helper
    • C:\Document and Settings\All Users\Application Data\Microsoft\Virtual Server
    • C:\Document and Settings\All Users\Application Data\Microsoft\Virtual Server Webapp
    • C:\Document and Settings\All Users\Shared Virtual Machines
    • C:\Document and Settings\All Users\Shared Virtual Networks
    • C:\Document and Settings\<your user name>\Application Data\Microsoft\Virtual Server
  • Reinstall Virtual Server 2005
Published Tuesday, April 18, 2006 10:31 PM by mab
Filed under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Nick said:

The symptoms that I was experiencing were very similar - NICs that were added after I installed VS2005R2 were not being detected by guest OS's or by the VS2005R2 interface.  I found that the "internal" NIC which no physical driver assoicated with it could be changed to the new physical adapter, where as the new physcial adapter was not present in the New Network configuration wizard.  So what I ended up doing was chaning the configuration of the internal network, to use the new physical adapter, and then re-adding a new Internal network...  More details are available here if you're interested: http://addicted-to-it.blogspot.com/2006/07/virtual-server-vs2005r2-is-not.html
July 16, 2006 12:36 AM
 

SilkRoad said:

I had the same problem when installing a loop back nic after Virtual Server was installed. I was able to just stop and restart the Virtual Server service to get the Virtual Server Admin web-app to recognize the new nic.
August 28, 2006 12:25 PM
 

Eric said:

Thanks for the tip! I had a related issue resolved by following your procedure. Situation was that I'd setup virtual server on a dual NIC host before bridging the connections. For the life of me.. I couldn't get the newly created bridged adaptor to appear in the available list of network connections untill after the reinstall. Thanks again.
October 9, 2006 1:54 PM
 

John Green said:

I'm having issues along in the same vein.  Bottom line is that the system's single physical ethernet adapter doesn't show up within VS Administration (Virtual Networks, Physical Network adapter), so I can't configure virtual machines with a connection to the external network.  

I'm running VS2005R2x64 under XP Pro x64.  After changing domain membership for this system, I had authenticationi issues which I was unable to resolve.  So I've uninstalled VS, deleted the directories in "user" and "All Users" noted above, altered the path for all virtual machine configuration files (.vmc, .vsv and .vhd files), verified that the Program Files\Virtual Server was gone, and even deleted the Local area connection for the Ethernet adapter, allowing XP to recreate it after the next reboot.  

After I reinstalled VS, it starts with the error message:

Virtual Server could not open its emulated Ethernet switch driver. To fix this problem, re-enable the Virtual Server Emulated Ethernet Switch service on one or more Ethernet adapters or reinstall Virtual Server.

Local Area connection properties show "Virtual Machine Network Services" is installed and enabled.  An "Emulated Ethernet Switch service" is not present, and not available.  

I've tried uninstalling / reinstalling the "VM Network Services", with no impact.  

VS has worked on this system in the past.  It seems there must be some "tracks" left from previous installations that are impacting the reinstallation.  

Anyone have any ideas?  

October 25, 2006 3:51 PM
 

Trevor Brawn said:

I'm having a slightly different problem in that the Virtual Server (x64bit)host's network is fully functional until a virtual (32bit) client is started. The virtual client's network seems to take over the host's NIC entirely. It has full network connectivity, can access the internet, LAN, etc. I can load another virtual client and it's network is also fully operational. Only after shutting down the virtual clients, does the host's network become available again.

I have updated the Broadcom 5708c NIC with the x64 bit driver and re-installed Virtual Server R5 Enterprise a number of times, all with the same result.

I have the same virtual clients on an XP Pro SP2 host also with a Broadcom NetXtrem 57xx 32-bit driver, which functions as expected - the host and the virtual clients all utilise the single physical NIC.

Any ideas on how to resolve the issue?

January 24, 2007 10:45 PM
 

Lance said:

A MUCH simpler fix...

Look at the properties for the problem NIC or any NIC if none are working.  Look for the 'Virtual Machines Network Service'.  If you don't see it then click install, choose service, have disk, then browse to the folder where you installed virtual server Example: C:\Program Files\Microsoft Virtual Server\Drivers\VMNetSv  do to the drivers\VMnetSv folder and choose one of the inf files.  Install it and restart your virtual server service.  Your problem should be solved.  

It solved mine.

February 25, 2007 10:59 AM
 

Fernando said:

I had a similar issue with my host server being an IBM Blade,  I solved the problem by updating to the latest driver version in my case BCM5708S from Dec 2006.  Thanks for the hints

March 14, 2007 7:38 PM
 

eric@osterholm.org said:

We have problems similar to a number of these posts; we have a Dell PowerEdge 2950 with:

*Broadcom BCM5708C NetXtreme II GigE (NDIS) dual NIC (not teamed),

*PERC 5/i RAID with a RAID 10 subsystem (SAS drives),

*ATI ES1000 video,

*Windows Server 2003 R2 (32 bit for now),

*Virtual Server Enterprise 2005 R2 with a single VM at this point, running Exchange 2003 SP2.  

The physical server's network connection will lose connectivity to several hosts on the office subnet (including the default gateway), but it still has connectivity to some hosts.  

The odd thing is that the virtual machine's network connection (using the flaky physical connection) is stable! The route table looks fine.  Moving the virtual server to an older SuperMicro (X6DHR-8G) with Intel NIC's has solved the problem for now, but I really need to get the new Dell working!

I'm going to try adding a non-Broadcom NIC to the Dell and test again.

April 4, 2007 11:12 AM
 

Trev said:

Had the same problem on 3 dell 2950s

With virtual server 2005 R2

Lost network on both host and guest after starting guest on prod nic.

Downloaded latest drivers from broadcom.

Here is a link to broadcoms article.

Fixed

April 18, 2007 4:26 PM
 

Julia said:

I have a Dell 2950 2003 sp2 with two Nic's same problem one Nic loses connection will reestablish after repair for an unspeciifed amount of time. Tried other TCP/Ip parameter fixes no luck.

Thanks for the Broadcom tip, will look there.

May 10, 2007 2:20 PM
 

Nash said:

Have the same problem with clustered DELL 1950.

I lost connection to Host when dedicating a physical NIC to Virtual Machine.

I already have the latest driver version for BCM5708C.

It seems to be a problem between these NIC's and virtual server emulated switch service, when I deactivate this service on concerned NIC, I did not lose the connection but guest can't get through neither ...

May 11, 2007 5:03 AM
 

Nash said:

I fixed that issue using this link:

http://groups.google.com/group/microsoft.public.virtualserver/browse_thread/thread/1ca64224b97dc250/457d83a734bee708?lnk=st&q=broadcom+virtual+server+issues&rnum=7#457d83a734bee708

installed DELL's Drivers pack for Broadcom's NIC.

and Windows2k3 patch (if you're not using a 32bit version, browse : ftp://ftp.us.dell.com/network/ )

May 14, 2007 5:43 AM
 

nettellect.com » Virtual Server could not open its emulated Ethernet switch driver said:

PingBack from http://nettellect.com/blog/?p=40

June 4, 2007 1:22 AM
 

BK said:

Had the same with Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller on VS 2005 R2, the NIC was not on the list when trying to create new virtual network, followed the procedure and it helped! thanks for the tip.

June 19, 2007 2:21 AM
 

AKa said:

This solution resolved my problems. Thanks!

August 21, 2007 6:48 AM
 

Tukaz said:

thaks man your post was so helpful !

liceo221@hotmail.com

February 15, 2008 9:30 AM
 

James said:

Are we supposed to load the Broadcom nic driver inside the Virtual server?  It show up as an intel nic inside the virtual server.  I can't get connectivity at ALL.  Can someone educate me.  I have 16 Dell 2950 server that need virtual servers in them.  PLEASE Help!!!

February 29, 2008 10:36 AM
 

Mark Brown s Blog Trouble with Virtual Server 2005 R2 Standard | Menopause Relief said:

PingBack from http://menopausereliefsite.info/story.php?id=1859

June 13, 2009 4:14 AM

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Submit

This Blog

Syndication

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker