Problem with Network Card (Dell M600)
- Hi there,
I've been beating my head against a wall trying to get Hyper-V up on our Blade Server (Dell M600's). I've tried creating a virtual machine through Hyper-V manager, aswell as the Beta version of the Virtual Machine Manager, but both fail.
The error that I receive on the Hyper-V Manager is as follows:
An error occurred while attempting to change the state of virtual machine Testing.
'Testing' failed to start.
Microsoft Syntehtic Ethernet Port (Instance ID {701F1F6C-9B2F-4393-B7DB-90A57558BC0C}}: Failed to power on with Error 'The specified network resource or device is no longer available.'
'Testing' failed to start. (Virtual machine 8FD27E76-6FBB-4026-B493-2916E80B4B89)
'Testing' Microsoft Synthetic Ethernet Port (Instance ID {701F1F6C-9B2F-4393-B7DB-90A57558BC0C}}: Failed to power on with Error 'The specified network resource or device is no longer available.' (0x80070037). (Virtual machine 8FD27E76-6FBB-4026-B493-2916E80B4B89)
I've also linked a couple of pictures of the error, aswell as Network Connections and the properties on the actual Virtual Machine.
http://www.flickr.com/photos/27159094@N05/2536720142/
http://www.flickr.com/photos/27159094@N05/2536720014/
http://www.flickr.com/photos/27159094@N05/2536719986/
Any help would be greatly appreciated!
Warren
Answers
Are there any antivirus programs running on the root paritition? They've been known to intefere with the configuration files.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byWarrenR Thursday, June 12, 2008 3:52 PM
All Replies
- It sounds like the virtual machine is set to use a virtual network that doesn't exist. Can you try creating a brand new, uniquely name virtual network to see if that resolves the problem?
This posting is provided "AS IS" with no warranties, and confers no rights.- Proposed As Answer byMike Sterling [MSFT]MSFT, OwnerFriday, May 30, 2008 10:37 PM
- Unproposed As Answer byMike Sterling [MSFT]MSFT, OwnerMonday, June 02, 2008 1:58 PM
Well, it seems to pop a different error, but the same result:
An error occurred while attempting to change the state of virtual machine MyVm.
'MyVm' failed to start.
Microsoft Synthetic Ethernet Port (Instant ID {C9487291-2545-4F14-B4BF-C522CB14F555}): Failed to power on with Error 'The specified network resource or device is no longer available.'
'MyVm' failed to start. (Virtual machien BBDF0E6E-3162-492F-B23B-A1DC9B0AAF70)
'MyVm' Microsoft Synthetic Ethernet Port (Instant ID {C9487291-2545-4F14-B4BF-C522CB14F555}): Failed to power on with Errror 'The specified network resource or deviice is no longer available.' (0x80070037). (Virtual machine BBDF0E6E-3162-492F-B23B-A1DC9B0AAF70)
Afterwords, the Virtual Machine disappears from the Hyper-V manager.
Any other thoughts? Uninstall Hyper-V and reinstall maybe?- Edited byWarrenR Monday, June 02, 2008 1:41 PMForgot to add something
- That's quite strange, and something I haven't seen before.
What version of Hyper-V are you using?
This posting is provided "AS IS" with no warranties, and confers no rights. - Are you by any chance using Broadcom BASP to team up adapters and creating hyper-v network on teamed virtual adapter? If so then don't it breaks things :).
Other than that i've noticed while setting up cluster (3 M600 Blades on Core and SAN) that if i destroy cluster (restarting 2 of 3 nodes - my quorum setup) and then bring it back on it resets Hyper-v network adapters on last remaining node. Had to delete network. evict node (not sure if it needed - did it while reconstructing cluster), restart node (after 2 came back and restarted cluster) and recreate hyper-v network with the same name as orgininal 2 nodes and rejoin node to cluster.
Hi Warren,
From the second picture that you attached in your first post, I noticed that you have two Broadcom BCM57985 NetXtreme II network adapter. May I know whether you are using network adapter teaming?
We have seen many relevant problems occurred in Hyper-V server because of the network adapter teaming. And it is usually very hard to tell the root cause as they usually change some low-level architecture. A good way is to try disabling network adapter teaming, or even try replacing the existing onboard network adapters with a different one. If this is the case, I am sorry to say that you may need to contact manufacturers for detailed information. Here is an article for some related information:
Network adapter teaming and server clustering:
http://support.microsoft.com/kb/254101
Additionally, please also take a look at the properties of all the network connections. Please note that only Microsoft Virtual Network Switch Protocol should be bound to the physical NIC, and all other protocols should be bound to the External virtual network adapter.
Thank you for your cooperation.
Best regards,
Chang Yin- Proposed As Answer byMike Sterling [MSFT]MSFT, OwnerFriday, June 06, 2008 2:00 PM
- Unmarked As Answer byWarrenR Monday, June 09, 2008 3:57 PM
- Unproposed As Answer byWarrenR Monday, June 09, 2008 4:33 PM
- Marked As Answer byChang Yin Monday, June 09, 2008 8:12 AM
- Nope, Teaming isn't enabled (atleast, it wasn't enabled by me, unless Windows 2008 enables it by default?). I'll double check to make sure this isn't the case.
I've also disabled the one network adapter, Hyper-V is binding to the proper NIC (with only the 'Microsoft Virtual Network Switch Protocol' enabled).
I'm unable to find out what version of Hyper-V I'm running. I'll assume that I'm running the new version, as our WSUS is configured to auto update all of that. Is there a spot within the Hyper-V manager that I can go to see which version of Hyper-V I'm running?
If I go through Server Manager and click on Hyper-V, in the Summary screen I get:
'This is a pre-release version of Hyper-V. Go to the Hyper-V TechCenter for more information.
Hyper-V is installed, but additional steps are required to begin running server workloads on virtual machines. Go to Hyper-V Manager to add new virtual machines.'
I've tried manually updated Hyper-V via KB950049, however when I run it, I get a message stating: 'The update does not apply to your system'. I'm guessing that it's already updated via WSUS?
We've had some problems with the Broadcom NIC's in the past (especially the ones that use the VBD) with RIS/WDS, but that's typically only in the WinPE environment. I'm curious if other people who have Broadcom VBD-based cards are having similar issues with Hyper-V.
Anyway, I'll try upgrading the drivers and reinstalling Hyper-V and see how that fairs.
Warren - Help -> About from the Hyper-V MMC should give you the version.
This posting is provided "AS IS" with no warranties, and confers no rights. - Hyper-V Manager
Microsoft Corproation
Version: 6.0.60001.18010 Are there any antivirus programs running on the root paritition? They've been known to intefere with the configuration files.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byWarrenR Thursday, June 12, 2008 3:52 PM
- Just Microsoft Forefront... Is there a directory that we can try excluding? Or just turn the service off and see if it works after that?
- - Well it appears to be working now. I had disabled Microsoft Forefront and now everything is working great. It may have been something else aswell, but i'll play now, atleast I have network support.
Thanks for all your help!
Warren - I was having the same issue and I stopped the services for my antivirus program and the Virtual Machines were able to start. Thanks for the advice. I was banging my head against the desk getting so frustrated and it turned out to be a simple fix.
Jay Phillips - Same boat here but cant disable forefront as its managed by the machine that no longer exists.
Now, being as WSUS/Forefront will install on guest hardware regardless, and that guest hardware tends to be virtual, dont you think it may just be a bit stupid having this occur to so many users in so many countries?
I.E. Better , explicit documention with FFS explaining that the server you just spent 10 days updating will no longer exist after you update it/forefront.
And perhaps a dev at microsoft can tell me the quick and non time consuming way to free up all the volume licenses that are in use on an unrecoverable machine??
This is a ghastly, ghastly bug that really should have been foreseen.
Without a avhd theres no fix then?
please and thankyou > explosives - Hi folks,
Exactly the same problem for me too. I disabled the Trend Worry Free v6 and the new VM started first time. After several hours of googling this problem, came across this post.
Thanks very much to you all. Problem solved. Well, if you are happy to run the host server without any Anti Virus services running. Hmmmmm
Dan
