Regarding the eqltrace.log ability to know if a HW or SW initiator is being used by the host,  no, not that I am away of. The Broadcom driver you listed is old, the newest one is v7.2.1 (www.broadcom.com/.../netxtremeii.php) Also make sure you are not doing any type of NIC teaming, you need to configure the iSCSI initiator to use the HW (target properties>add session> advanced, select the HW instance). I have also attached a document for the Broadcom setting. -joe
I'm trying to troubleshoot performance issues on 2 of my 3 Hyper-V hosts. On these hosts, in the EQLTrace.log file, I'm receiving these errors every 4 minutes:      Line 392085: 02Aug12:13:17:04.352|SNMP|2332|8752||***ERR***:CWbemQuery::read:146:MSiSCSI_TCPIPConfig instance not processed. Error code = 8007065d    Line 393021: 02Aug12:13:21:03.673|SNMP|2332|8752||***ERR***:CWbemQuery::Get_Address:394:type is 3 (not IPV4)  I've searched for the error code, but can't find anything relating to it and MSiSCSI_TCPIPConfig. According to the Microsoft iSCSI Software Initiator Version 2.x Users Guide, this is what the MSiSCSI_TCPIPConfig is: MSiSCSI_TCPIPConfig – HBA initiator only, TCP/IP configuration class.  This describes and allows configuration of the TCP/IP parameters I'm not receiving this error message on my third Hyper-V host
Error: MSiSCSI_TCPIPConfig instance not processed. Error code = 8007065d