Network Adapter disabled, Event ID 4 Netvsc, miniport reset
- Every once in a while (maybe once a week) one of our virtual machines will lose network connectivity. It all starts with Event ID 4 with the Source being "netsvc". The Event description says "The miniport 'Microsoft Virtual Machine Bus Network Adapter' reset." When this happens the network adapter in the VM becomes disabled and the only way to enable the network adapter and regain network connectivity is to reboot the VM. I am using Synthetic Network Adapters with optimatizations not enabled. The host is Hyper-V 2008 R2 RTM 6.1.7600. Hardware is Dell R610 with Broadcom gigabit network adapters. Any suggestions would be greatly appreciated.
All Replies
Hi,
In order to isolate the issue, please help me to collect the following information:
1. What’s the system version of the problematic VM?
2. Did you upgrade the Integration Services inside the VM to the latest?(If you create the VM on Windows Server 2008 Hyper-V host, you need to upgrade the IS when you move the VM to Windows Server 2008 R2 Hyper-V host)
3. Did you get the same issue on any other VMs?
4. Have you tried to use a legacy network adapter instead of the synthetic network adapter?
By the way, you may try to upgrade the Integration Services or use a legacy network adapter to check whether you get the same issue.
Vincent Hu
- Thanks for replying,
1. So far I've had the problem with guests running Windows Server 2003 R2 Standard w/SP2 and Windows Server 2008 R2 Standard, however there is no event in the event log for the 2008 guest, just loss of network connectivity.
2. The Add/Remove programs in the 2003 guests show the Integration Services as version 6.1.7600.16385. The 2008 R2 guest doesn't show Integration Services obviously, but the driver version for the Virtual Machine Bus Network Adapter is 6.1.7600.16385. These guests were all created with Hyper-V 2008 R2 RC and were migrated to Hyper-V 2008 R2 RTM.
3. I've had the issue occur once on 4 different VMs, all on different days. Three were 2003 R2 and one was 2008 R2.
4. I haven't tried a legacy adapter yet. But I will if one of the three 2003 guests experience the issue again. I can't use a legacy adapter for the 2008 guest because it is a file server with 2 terabytes of data. We wouldn't be able to back up all that data in a timely fashion using a 100 mbps adapter.
I have disabled the Large Send Offload in all the guests, don't know if that does anything. Should I use static MAC addresses for these guests so that when I migrate them from one server to another, they keep the same MAC address? Hi,
Please try to use a legacy network adapter to check whether you get the same issue next time.
Should I use static MAC addresses for these guests so that when I migrate them from one server to another, they keep the same MAC address?
>> If you care about the IP address, you may set static MAC address to those virtual network adapters.
Vincent Hu
- Hi,
we have the same problem using HP B 460 G6 Blade Servers
today we changed power options on the HyperV-R2 host,
I will post my news tomorrow
Regards Peter - Pezdkl - I don't know if this issue has been resolved yet, but I saw something really strange yesterday and wanted to post an update.
I had task manager running on one of our hosts and I noticed that in the networking tab there were four adapters present and one of them (Local Area Connection 6) said "Disconnected". I checked the Network Properties of the host in SCVMM to find out which adapter (the host has 4 physical adapters) that was and saw that Local Area Connection 6 was the adapter that I configured to be a Virtual Network for the VMs/Guests. I had unchecked "Host Access" in SCVMM so it didn't make much sense that the host was still able to see it.
I checked the other two hosts and they only had three adapters present in Task Manager, one physical adapter for live migration, one physical adapter for remote management of the host, and one virtual adapter created by the failover cluster. It's possible that I was only having issues with virtual machines that were running on that one host, I don't know for sure because I've been moving them around alot.
So I evicted the host and deleted all the virtual networks, but even after deleting them, I still saw that fourth adapter "Local Area Connection 6 - Disconnected" in the task manager. I ran this powershell command "Get-wmiobject win32_NetworkAdapter | format-table" on the host and I saw four VMSMP - Microsoft Virtual Network Switch Adapters in the list. Apparently, when you delete a Virtual Network in SCVMM it doesn't delete the Virtual Switch associated with it so they just pile up on the host. Is there an easy way to delete Virtual Switch Adapters on a Hyper-V host?
The only way I could do it was to disable the adapters using instructions at this link:
http://rickgaribay.net/archive/2008/09/26/using-powershell-to-manage-network-interfaces-and-windows-services.aspx
and then use this script to delete the disabled adapters :
http://www.developerfusion.com/community/blog-entry/8393535/hyperv-how-to-remove-disabled-virtual-network-adapters-from-the-parent-partition/
After all that, I created the Virtual Networks for the VMs/Guests and the fourth adapter "Local Area Connection 6 - Disconnected" was gone. If I make it a week, I think it will have been fixed.
As far as why that adapter showed up in the first place, my guess would be that I created a Virtual Network, deleted it, and then created another one. I think that SCVMM and Hyper-V manager need improvements in terms of network management for the host. It would be nice to have a GUI to manage network adapters on the Hyper-V host. - I have exatly the same problem "The miniport 'Microsoft Virtual Machine Bus Network Adapter' reset". This happens from time to time on different servers and the down time varies from seconds to minutes.
- Same exact problem. Happened to me on an HP DL160G5 running 2008 R2 Hyper-V. Guest OS is SBS 2008. Network reset with Event id 4 but never came back. Had to restart the whole box to get it to come back up.
Only thing going on was a backup of the host using server backup.
Hope this doesn't become a regular issue!
Come on MS. Whats going on? - I have the same problem "The miniport 'Microsoft Virtual Machine Bus Network Adapter' reset" with different VM's W2k3 SP2, W2K SP4, XP SP3.
- got the same problem with W2K3 SP2 and Linux (Debian server x64) VMs. i have tried to change the VM LANs to Legacy network adapters, but it didn't solved the issue. i have to use the Linux server as a proxy from 2008 when i want to do anything on the net (doesn't matter if it's a single forum post or a download or anything...).
with the Legacy LAN the system does not create event log entry but the connection dropped.
i have re-created the virtual network and updated the LAN driver also.
any idea? - Hi,
We have the same issue "The miniport 'Microsoft Virtual Machine Bus Network Adapter' hung" followed by "The miniport 'Microsoft Virtual Machine Bus Network Adapter' reset."
Does anyone know how to stop this happening?
Mike Loveless - I am getting the same issue here, though my error lists it as adapter #2."The miniport 'Microsoft Virtual Machine Bus Network Adapter #2' hung."The Host OS is Standard 2008 R2, the guest is 2003 SP2.Integration services version 6.1.7600.16385Did the 'legacy network adapter' change fix this issue for anyone?
- Hi,
had the same problem, host OS Hyper-V R2 Server guest OS W2003 R2 x64, network interface used for NLB was loosing connectivity with error "The miniport 'Microsoft Virtual Machine Bus Network Adapter #2' hung.", switched the network interface to legacy network adapter and everythings seems to be working (3rd day). Second virtual adapter in guest running in default without problem (for higher traffic bandwidth).
PS. There is no supported driver for legacy network controller for W2003R2 x64 so I used drivers from W2008R2 (dc21x4vm.inf and dc21x4vm.sys). - Experiencing exactly the same issues on a range of VM's running 2000, XP and 2003, all on 2008 R2 Hyper-V Hosts. Network connectivity drops and the only way to get it back is to either reboot the virtual machine or Live Migrate it another host (which I assume re-initialises something). All hosts are identical Dell R610 servers, all hosts are 2008 R2 with all the latest patches, the networking is Intel Quad Port adapters teamed with the latest drivers.
I can find no pattern, it hasn't affected VM's on 1 host as yet, but all the other 3 have been. It has affected all the VM's to a lesser or greater degree, although some more than others (oddly those with less load seem to be greater affected).
If anyone can find a solution to this I'd really appreciate it as we have had to put a stop to our Virtualisation plans until this is resolved. - I have also been able to change to the legacy network driver and had no more issues.
I am also experiencing this error - "The miniport Microsoft Virtual Machine Bus Network Adapter hung" followed by "The miniport Microsoft Virtual Machine Bus Network Adapter reset". I have attempted to contact Microsoft but have been told "We do not provide technical support for virtual machines only physical". I find this absolutely unacceptable and cannot believe they do not provide support for a product they have developed and expect people to use.
My problem is with a single Virtual Machine running Windows Server 2003 32Bit Standard R2. The Physical Host is a Server 2008 64Bit and runs two Virtual Machines of the same build (Microsoft Windows Server 2003 Standard R2). The Virtual Machine with the problem is a Microsoft Exchange Server and the errors ONLY occur during a backup of the server. The times the failure occurs can vary, but there have now been five attempts at a backup on this server and all five have resulted in this error occurring. At this point i then need to shut down the Virtual Server within Hyper V manager to bring it back online. Initially i believed the problem to be caused by the specific backup software, but i have since attempted an NT Backup from the OS and the same problem occurred during this.
The hardware we are using is a Dell PowerEdge T610 with the latest Drivers and Firmware from the Dell Support website. I have not yet tried the Legacy Network Adapter fix posted here but would prefer to further understand the root cause of this problem instead of attempting this. I have however, swapped the Physical NIC's associated with the Virtual Machine over but, as yet, have not had chance to test further.
Any help regarding this would be greatly appreciated, and any response from Microsoft would be beneficial as clearly this problem is more widespread than just a few separate instances.- David,
Thank you for responding.
I have already installed the following hotfix: http://support.microsoft.com/kb/975530 to prevent the Hyper-V host from blue screening and I noticed that the files in your suggested hotfix are the same files. If I install your hotfix, I will overwrite the files that were installed with hotfix 975530. So it appears that I can only have one of the two problems fixed at a time.
Would the best method then be to install hotfix 974909 and then use the registry workaround suggested in kb975530 to prevent the blue screening?
I guess we'll just have a higher electric bill... - HotFixes are not mutually exclusive. When files are replaced, it is only if the new file version is higher.
At least that is the way it is supposed to be.
There can also be registry and other setting changes involved. - So which hotfix do I install to fix both problems?
- Hi David,
hotfix 974909 does not solve the issue on our virtualized servers. Still netvsc service with reset then hung appear.
Regards,
Vojta - I would try disabling network offloads inside the virtual machine, and see if that helps.
Cheers,
Benjamin Armstrong
============================
Windows Virtualization
Senior Lead Program Manager
This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.
