That was already tried as well as several other BIOS settings. Unfortunately, disabling Intel VT-d does not fix the problem here. Its something the vendors are going to have to get fixed and hopefully that will be soon.
The eeprom on the NIC with different versions. And trust me when I say we've tried just about everything including reflashing What I do know is that the problem is specifically related to the 82574L network adapter on this supermicro X9SCM-F in regards to how it operates with Server 2012 Hyper-V. As soon as I have a solution I will post it here.īut, frankly, this has been a problem for so long that I might be forced to purchase a different board.
I was notified that there was a conference call with Intel today in regards to the issue. Like I said, I have been in close contact with SuperMicro. This confirms that it is likely isolated to this board. Its nice to see that it is the same series of motherboard. The only events generated are in regards to the improper shutdown. Its strictly a hardware level crash that causes an instant reboot of the server. and the microsoft drivers stay installed. In addition, I found that if I try the new Server 2012 R2 the intel proset drivers will not even install a driver for the Intel 82574L network adapter. There is a serious issue here that is a complete show stopper. I have been working with Supermicro for a couple of weeks to determine the problem who is also working with Intel.
In addition, it is almost impossible to uninstall or reinstall drivers without first removing the hyper-v role because the system will keep rebooting. The server is not generating a blue screen. I have tried several different versions of Proset drivers. After installing the Intel Proset drivers with advanced networking services and the Hyper-V role on Server 2012 I no longer can access the properties of the Intel 82574L network adapter or create a network team withoutĪn instant server reboot. I have been dealing with this problem for two months now. I am so glad to finally find somebody else with this problem.
0 kommentar(er)
