|
Pavol Kycina
|
Net.e1000 in vmware ESXi 5.1
|
|
Pavol Kycina
09/28/2012 4:25 AM
post95908
|
Net.e1000 in vmware ESXi 5.1
Hello,
vmware host of our development system was upgraded to ESXi 5.1 version.
From the same time we are experiencing problems with Net.e1000 driver. Under some conditions (remote debugging, file
copy) it logs into netinfo log following information:
- rx bad pkt length
- rx some packets missed, txing NACK
We tried to slow the communication to 100Mbit (default is 1Gbit), but it didn't help. We have also tried all the
versions of the driver available (from 13.5.2011, 29.8.2011, 13.2.2012). The same holds true for Net.i82540 driver.
Is there any newer driver to try?
Regards, PKY
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Hugh Brown
10/01/2012 11:09 AM
post95949
|
Re: Net.e1000 in vmware ESXi 5.1
So did the driver work with the previous version of ESXi?
On 2012-09-28 4:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>Hello,
>
>vmware host of our development system was upgraded to ESXi 5.1 version.
>
>From the same time we are experiencing problems with Net.e1000 driver.
>Under some conditions (remote debugging, file copy) it logs into netinfo
>log following information:
>- rx bad pkt length
>- rx some packets missed, txing NACK
>
>We tried to slow the communication to 100Mbit (default is 1Gbit), but it
>didn't help. We have also tried all the versions of the driver available
>(from 13.5.2011, 29.8.2011, 13.2.2012). The same holds true for
>Net.i82540 driver.
>
>Is there any newer driver to try?
>
>Regards, PKY
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post95908
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Pavol Kycina
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Pavol Kycina
10/02/2012 4:23 AM
post95965
|
Re: Net.e1000 in vmware ESXi 5.1
Hello,
We used Net.i82540 driver in previous version of ESXi. It worked without any problem. After the upgrade the problems
started (with Net.i82540). So we tried Net.e1000 driver (which seems to be successor to Net.i82540), but the problems
remained.
version of ESXI | Net.i82540 | Net.e1000
4.x | OK | N/A
5.1 | problem | problem
Regards, PKY
> So did the driver work with the previous version of ESXi?
>
>
>
>
> On 2012-09-28 4:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>
> >Hello,
> >
> >vmware host of our development system was upgraded to ESXi 5.1 version.
> >
> >From the same time we are experiencing problems with Net.e1000 driver.
> >Under some conditions (remote debugging, file copy) it logs into netinfo
> >log following information:
> >- rx bad pkt length
> >- rx some packets missed, txing NACK
> >
> >We tried to slow the communication to 100Mbit (default is 1Gbit), but it
> >didn't help. We have also tried all the versions of the driver available
> >(from 13.5.2011, 29.8.2011, 13.2.2012). The same holds true for
> >Net.i82540 driver.
> >
> >Is there any newer driver to try?
> >
> >Regards, PKY
> >
> >
> >
> >_______________________________________________
> >
> >General
> >http://community.qnx.com/sf/go/post95908
> >To cancel your subscription to this discussion, please e-mail
> >general-qnx4-unsubscribe@community.qnx.com
>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Hugh Brown
10/02/2012 7:26 AM
post95967
|
Re: Net.e1000 in vmware ESXi 5.1
Well then I guess that the problem is with ESXi rather than with the
driver, as that is the only thing that has changed.
On 2012-10-02 4:23 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>Hello,
>
>We used Net.i82540 driver in previous version of ESXi. It worked without
>any problem. After the upgrade the problems started (with Net.i82540). So
>we tried Net.e1000 driver (which seems to be successor to Net.i82540),
>but the problems remained.
>
>version of ESXI | Net.i82540 | Net.e1000
>4.x | OK | N/A
>5.1 | problem | problem
>
>Regards, PKY
>
>> So did the driver work with the previous version of ESXi?
>>
>>
>>
>>
>> On 2012-09-28 4:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>>
>> >Hello,
>> >
>> >vmware host of our development system was upgraded to ESXi 5.1 version.
>> >
>> >From the same time we are experiencing problems with Net.e1000 driver.
>> >Under some conditions (remote debugging, file copy) it logs into
>>netinfo
>> >log following information:
>> >- rx bad pkt length
>> >- rx some packets missed, txing NACK
>> >
>> >We tried to slow the communication to 100Mbit (default is 1Gbit), but
>>it
>> >didn't help. We have also tried all the versions of the driver
>>available
>> >(from 13.5.2011, 29.8.2011, 13.2.2012). The same holds true for
>> >Net.i82540 driver.
>> >
>> >Is there any newer driver to try?
>> >
>> >Regards, PKY
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >General
>> >http://community.qnx.com/sf/go/post95908
>> >To cancel your subscription to this discussion, please e-mail
>> >general-qnx4-unsubscribe@community.qnx.com
>>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post95965
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Pavol Kycina
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Pavol Kycina
10/02/2012 8:25 AM
post95968
|
Re: Net.e1000 in vmware ESXi 5.1
Yes, that's right. But I hoped for your newer magic version of the driver would be compatible with newer ESXi (which is
imposed by our IT department).
Just for the information, there are several other people probably solving the same problem:
http://www.openqnx.com/phpbbforum/viewtopic.php?f=6&t=12535 (at the end, also suggestion to use Net.ether2100)
Regards, PKY
> Well then I guess that the problem is with ESXi rather than with
the
> driver, as that is the only thing that has changed.
>
>
>
>
> On 2012-10-02 4:23 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>
> >Hello,
> >
> >We used Net.i82540 driver in previous version of ESXi. It worked without
> >any problem. After the upgrade the problems started (with Net.i82540). So
> >we tried Net.e1000 driver (which seems to be successor to Net.i82540),
> >but the problems remained.
> >
> >version of ESXI | Net.i82540 | Net.e1000
> >4.x | OK | N/A
> >5.1 | problem | problem
> >
> >Regards, PKY
> >
> >> So did the driver work with the previous version of ESXi?
> >>
> >>
> >>
> >>
> >> On 2012-09-28 4:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
> >>
> >> >Hello,
> >> >
> >> >vmware host of our development system was upgraded to ESXi 5.1 version.
> >> >
> >> >From the same time we are experiencing problems with Net.e1000 driver.
> >> >Under some conditions (remote debugging, file copy) it logs into
> >>netinfo
> >> >log following information:
> >> >- rx bad pkt length
> >> >- rx some packets missed, txing NACK
> >> >
> >> >We tried to slow the communication to 100Mbit (default is 1Gbit), but
> >>it
> >> >didn't help. We have also tried all the versions of the driver
> >>available
> >> >(from 13.5.2011, 29.8.2011, 13.2.2012). The same holds true for
> >> >Net.i82540 driver.
> >> >
> >> >Is there any newer driver to try?
> >> >
> >> >Regards, PKY
> >> >
> >> >
> >> >
> >> >_______________________________________________
> >> >
> >> >General
> >> >http://community.qnx.com/sf/go/post95908
> >> >To cancel your subscription to this discussion, please e-mail
> >> >general-qnx4-unsubscribe@community.qnx.com
> >>
> >
> >
> >
> >
> >
> >
> >_______________________________________________
> >
> >General
> >http://community.qnx.com/sf/go/post95965
> >To cancel your subscription to this discussion, please e-mail
> >general-qnx4-unsubscribe@community.qnx.com
>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Hugh Brown
10/02/2012 8:31 AM
post95969
|
Re: Net.e1000 in vmware ESXi 5.1
Well you can try this version. It has been tested with all versions of the
Intel hardware.
On 2012-10-02 8:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>Yes, that's right. But I hoped for your newer magic version of the driver
>would be compatible with newer ESXi (which is imposed by our IT
>department).
>
>Just for the information, there are several other people probably solving
>the same problem:
>http://www.openqnx.com/phpbbforum/viewtopic.php?f=6&t=12535 (at the end,
>also suggestion to use Net.ether2100)
>
>Regards, PKY
>
>> Well then I guess that the problem is with ESXi rather than with the
>> driver, as that is the only thing that has changed.
>>
>>
>>
>>
>> On 2012-10-02 4:23 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>>
>> >Hello,
>> >
>> >We used Net.i82540 driver in previous version of ESXi. It worked
>>without
>> >any problem. After the upgrade the problems started (with Net.i82540).
>>So
>> >we tried Net.e1000 driver (which seems to be successor to Net.i82540),
>> >but the problems remained.
>> >
>> >version of ESXI | Net.i82540 | Net.e1000
>> >4.x | OK | N/A
>> >5.1 | problem | problem
>> >
>> >Regards, PKY
>> >
>> >> So did the driver work with the previous version of ESXi?
>> >>
>> >>
>> >>
>> >>
>> >> On 2012-09-28 4:25 AM, "Pavol Kycina" <community-noreply@qnx.com>
>>wrote:
>> >>
>> >> >Hello,
>> >> >
>> >> >vmware host of our development system was upgraded to ESXi 5.1
>>version.
>> >> >
>> >> >From the same time we are experiencing problems with Net.e1000
>>driver.
>> >> >Under some conditions (remote debugging, file copy) it logs into
>> >>netinfo
>> >> >log following information:
>> >> >- rx bad pkt length
>> >> >- rx some packets missed, txing NACK
>> >> >
>> >> >We tried to slow the communication to 100Mbit (default is 1Gbit),
>>but
>> >>it
>> >> >didn't help. We have also tried all the versions of the driver
>> >>available
>> >> >(from 13.5.2011, 29.8.2011, 13.2.2012). The same holds true for
>> >> >Net.i82540 driver.
>> >> >
>> >> >Is there any newer driver to try?
>> >> >
>> >> >Regards, PKY
>> >> >
>> >> >
>> >> >
>> >> >_______________________________________________
>> >> >
>> >> >General
>> >> >http://community.qnx.com/sf/go/post95908
>> >> >To cancel your subscription to this discussion, please e-mail
>> >> >general-qnx4-unsubscribe@community.qnx.com
>> >>
>> >
>> >
>> >
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >General
>> >http://community.qnx.com/sf/go/post95965
>> >To cancel your subscription to this discussion, please e-mail
>> >general-qnx4-unsubscribe@community.qnx.com
>>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post95968
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Pavol Kycina
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Pavol Kycina
10/02/2012 9:02 AM
post95971
|
Re: Net.e1000 in vmware ESXi 5.1
Thanks, but it doesn't work. Here is the log:
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 20144 (291)
14:53:32 1 Status 16258 (292)
14:53:32 1 000800 000000 (293)
14:53:32 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing NACK
14:53:32 1 Status 20144 (1099)
14:53:32 1 000800 000000 (1099)
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:33 1 Status 20144 (291)
14:53:33 1 Status 16258 (292)
14:53:33 1 000800 000000 (293)
14:53:33 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing NACK
14:53:33 1 Status 20144 (1099)
14:53:33 1 000800 000000 (1099)
14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:34 0 Status 2 ( 35) NET logical node not in node map
14:53:34 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
14:53:34 1 Status 20144 (291)
14:53:34 1 Status 16258 (292)
14:53:34 1 000800 000000 (293)
14:53:34 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing NACK
14:53:34 1 Status 20144 (1099)
14:53:34 1 000800 000000 (1099)
14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> Well you can try this version. It has been tested with all versions of the
> Intel hardware.
>
>
>
> On 2012-10-02 8:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>
> >Yes, that's right. But I hoped for your newer magic version of the driver
> >would be compatible with newer ESXi (which is imposed by our IT
> >department).
> >
> >Just for the information, there are several other people probably solving
> >the same problem:
> >http://www.openqnx.com/phpbbforum/viewtopic.php?f=6&t=12535 (at the end,
> >also suggestion to use Net.ether2100)
> >
> >Regards, PKY
> >
> >> Well then I guess that the problem is with ESXi rather than with the
> >> driver, as that is the only thing that has changed.
> >>
> >>
> >>
> >>
> >> On 2012-10-02 4:23 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
> >>
> >> >Hello,
> >> >
> >> >We used Net.i82540 driver in previous version of ESXi. It worked
> >>without
> >> >any problem. After the upgrade the problems started (with Net.i82540).
> >>So
> >> >we tried Net.e1000 driver (which seems to be successor to Net.i82540),
> >> >but the problems remained.
> >> >
> >> >version of ESXI | Net.i82540 | Net.e1000
> >> >4.x | OK | N/A
> >> >5.1 | problem | problem
> >> >
> >> >Regards, PKY
> >> >
> >> >> So did the driver work with the previous version of ESXi?
> >> >>...
View Full Message
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Hugh Brown
10/02/2012 9:04 AM
post95972
|
Re: Net.e1000 in vmware ESXi 5.1
Have you contacted VMWare to what is different with this release? As I
said, this driver has been tested with all Intel hardware and it works
without any problems.
On 2012-10-02 9:02 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>Thanks, but it doesn't work. Here is the log:
>
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 20144 (291)
>14:53:32 1 Status 16258 (292)
>14:53:32 1 000800 000000 (293)
>14:53:32 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing
>NACK
>14:53:32 1 Status 20144 (1099)
>14:53:32 1 000800 000000 (1099)
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:33 1 Status 20144 (291)
>14:53:33 1 Status 16258 (292)
>14:53:33 1 000800 000000 (293)
>14:53:33 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing
>NACK
>14:53:33 1 Status 20144 (1099)
>14:53:33 1 000800 000000 (1099)
>14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:34 0 Status 2 ( 35) NET logical node not in node map
>14:53:34 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
>14:53:34 1 Status 20144 (291)
>14:53:34 1 Status 16258 (292)
>14:53:34 1 000800 000000 (293)
>14:53:34 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing
>NACK
>14:53:34 1 Status 20144 (1099)
>14:53:34 1 000800 000000 (1099)
>14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>
>
>> Well you can try this version. It has been tested with all versions of
>>the
>> Intel hardware.
>>
>>
>>
>> On 2012-10-02 8:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>>
>> >Yes, that's right. But I hoped for your newer magic version of the
>>driver
>> >would be compatible with newer ESXi (which is imposed by our IT
>> >department).
>> >
>> >Just for the information, there are several other people probably
>>solving
>> >the same problem:
>> >http://www.openqnx.com/phpbbforum/viewtopic.php?f=6&t=12535 (at the
>>end,
>> >also suggestion to use Net.ether2100)
>> >
>> >Regards, PKY
>> >
>> >> Well then I guess that the problem is with ESXi rather than with the
>> >> driver, as that is the only thing that has changed.
>> >>
>> >>
>> >>
>> >>
>> >> On 2012-10-02 4:23 AM, "Pavol Kycina" <community-noreply@qnx.com>
>>wrote:
>> >>
>> >> >Hello,
>> >> >
>> >> >We used Net.i82540 driver in previous version of ESXi. It worked
>> >>without
>> >>...
View Full Message
|
|
|
|
|
|
Pavol Kycina
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Pavol Kycina
10/02/2012 9:11 AM
post95973
|
Re: Net.e1000 in vmware ESXi 5.1
Thanks,
I will try to follow wmvare support route as suggested.
Thanks, PKY
> Have you contacted VMWare to what is different with this release? As I
> said, this driver has been tested with all Intel hardware and it works
> without any problems.
>
>
>
> On 2012-10-02 9:02 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>
> >Thanks, but it doesn't work. Here is the log:
> >
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 20144 (291)
> >14:53:32 1 Status 16258 (292)
> >14:53:32 1 000800 000000 (293)
> >14:53:32 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing
> >NACK
> >14:53:32 1 Status 20144 (1099)
> >14:53:32 1 000800 000000 (1099)
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:33 1 Status 20144 (291)
> >14:53:33 1 Status 16258 (292)
> >14:53:33 1 000800 000000 (293)
> >14:53:33 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing
> >NACK
> >14:53:33 1 Status 20144 (1099)
> >14:53:33 1 000800 000000 (1099)
> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:34 0 Status 2 ( 35) NET logical node not in node map
> >14:53:34 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
> >14:53:34 1 Status 20144 (291)
> >14:53:34 1 Status 16258 (292)
> >14:53:34 1 000800 000000 (293)
> >14:53:34 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed, txing
> >NACK
> >14:53:34 1 Status 20144 (1099)
> >14:53:34 1 000800 000000 (1099)
> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >
> >
> >> Well you can try this version. It has been tested with all versions of
> >>the
> >> Intel hardware.
> >>
> >>
> >>
> >> On 2012-10-02 8:25 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
> >>
> >> >Yes, that's right. But I hoped for your newer magic version of the
> >>driver
> >> >would be compatible with newer ESXi (which is imposed by our IT
> >> >department).
> >> >
> >> >Just for the information, there are several other people probably
> >>solving
> >> >the same problem:
> >> >http://www.openqnx.com/phpbbforum/viewtopic.php?f=6&t=12535 (at the
> >>end,
> >> >also suggestion to use Net.ether2100)
> >> >
> >> >Regards, PKY
> >> >
> >> >> Well then I guess that the problem is with ESXi rather than...
View Full Message
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Hugh Brown
10/02/2012 11:09 AM
post95975
|
Re: Net.e1000 in vmware ESXi 5.1
Is there a difference in the network device IDs between the previous
version of ESXi and the current version? The output of show_pci from both
might help.
On 2012-10-02 9:11 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>Thanks,
>
>I will try to follow wmvare support route as suggested.
>
>Thanks, PKY
>
>
>> Have you contacted VMWare to what is different with this release? As I
>> said, this driver has been tested with all Intel hardware and it works
>> without any problems.
>>
>>
>>
>> On 2012-10-02 9:02 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>>
>> >Thanks, but it doesn't work. Here is the log:
>> >
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 20144 (291)
>> >14:53:32 1 Status 16258 (292)
>> >14:53:32 1 000800 000000 (293)
>> >14:53:32 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
>>txing
>> >NACK
>> >14:53:32 1 Status 20144 (1099)
>> >14:53:32 1 000800 000000 (1099)
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:33 1 Status 20144 (291)
>> >14:53:33 1 Status 16258 (292)
>> >14:53:33 1 000800 000000 (293)
>> >14:53:33 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
>>txing
>> >NACK
>> >14:53:33 1 Status 20144 (1099)
>> >14:53:33 1 000800 000000 (1099)
>> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:34 0 Status 2 ( 35) NET logical node not in node map
>> >14:53:34 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
>> >14:53:34 1 Status 20144 (291)
>> >14:53:34 1 Status 16258 (292)
>> >14:53:34 1 000800 000000 (293)
>> >14:53:34 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
>>txing
>> >NACK
>> >14:53:34 1 Status 20144 (1099)
>> >14:53:34 1 000800 000000 (1099)
>> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >
>> >
>> >> Well you can try this version. It has been tested with all versions
>>of
>> >>the
>> >> Intel hardware.
>> >>
>> >>
>> >>
>> >> On 2012-10-02 8:25 AM, "Pavol Kycina" <community-noreply@qnx.com>
>>wrote:
>> >>
>> >> >Yes, that's right. But I hoped for your newer magic version of the
>> >>driver
>> >>...
View Full Message
|
|
|
|
|
|
Pavol Kycina
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Pavol Kycina
10/03/2012 3:33 PM
post96003
|
Re: Net.e1000 in vmware ESXi 5.1
Hello,
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 100fh,
this is the same for both old and new ESXi.
The only difference seems to be interrupt line, which used to be 10, now it's 11.
Regards, PKY
> Is there a difference in the network device IDs between the previous
> version of ESXi and the current version? The output of show_pci from both
> might help.
>
>
>
> On 2012-10-02 9:11 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>
> >Thanks,
> >
> >I will try to follow wmvare support route as suggested.
> >
> >Thanks, PKY
> >
> >
> >> Have you contacted VMWare to what is different with this release? As I
> >> said, this driver has been tested with all Intel hardware and it works
> >> without any problems.
> >>
> >>
> >>
> >> On 2012-10-02 9:02 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
> >>
> >> >Thanks, but it doesn't work. Here is the log:
> >> >
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 20144 (291)
> >> >14:53:32 1 Status 16258 (292)
> >> >14:53:32 1 000800 000000 (293)
> >> >14:53:32 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
> >>txing
> >> >NACK
> >> >14:53:32 1 Status 20144 (1099)
> >> >14:53:32 1 000800 000000 (1099)
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:33 1 Status 20144 (291)
> >> >14:53:33 1 Status 16258 (292)
> >> >14:53:33 1 000800 000000 (293)
> >> >14:53:33 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
> >>txing
> >> >NACK
> >> >14:53:33 1 Status 20144 (1099)
> >> >14:53:33 1 000800 000000 (1099)
> >> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:34 0 Status 2 ( 35) NET logical node not in node map
> >> >14:53:34 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
> >> >14:53:34 1 Status 20144 (291)
> >> >14:53:34 1 Status 16258 (292)
> >> >14:53:34 1 000800 000000 (293)
> >> >14:53:34 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
> >>txing
> >> >NACK
> >> >14:53:34 1 Status 20144 (1099)
> >> >14:53:34 1 000800 000000 (1099)
> >> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
> >> >14:53:34 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>...
View Full Message
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 in vmware ESXi 5.1
|
|
Hugh Brown
10/03/2012 3:36 PM
post96005
|
Re: Net.e1000 in vmware ESXi 5.1
Well maybe there are other devices also on IRQ 11 that are affecting the
driver throughput. USB devices in particular can cause problems.
On 2012-10-03 3:33 PM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>Hello,
>
>Vendor ID = 8086h, INTEL CORPORATION
>Device ID = 100fh,
>
>this is the same for both old and new ESXi.
>
>The only difference seems to be interrupt line, which used to be 10, now
>it's 11.
>
>Regards, PKY
>
>> Is there a difference in the network device IDs between the previous
>> version of ESXi and the current version? The output of show_pci from
>>both
>> might help.
>>
>>
>>
>> On 2012-10-02 9:11 AM, "Pavol Kycina" <community-noreply@qnx.com> wrote:
>>
>> >Thanks,
>> >
>> >I will try to follow wmvare support route as suggested.
>> >
>> >Thanks, PKY
>> >
>> >
>> >> Have you contacted VMWare to what is different with this release? As
>>I
>> >> said, this driver has been tested with all Intel hardware and it
>>works
>> >> without any problems.
>> >>
>> >>
>> >>
>> >> On 2012-10-02 9:02 AM, "Pavol Kycina" <community-noreply@qnx.com>
>>wrote:
>> >>
>> >> >Thanks, but it doesn't work. Here is the log:
>> >> >
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 20144 (291)
>> >> >14:53:32 1 Status 16258 (292)
>> >> >14:53:32 1 000800 000000 (293)
>> >> >14:53:32 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
>> >>txing
>> >> >NACK
>> >> >14:53:32 1 Status 20144 (1099)
>> >> >14:53:32 1 000800 000000 (1099)
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:32 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:33 1 Status 20144 (291)
>> >> >14:53:33 1 Status 16258 (292)
>> >> >14:53:33 1 000800 000000 (293)
>> >> >14:53:33 1 000C29 C9F030 (4628) e1000 ( rx) some packets missed,
>> >>txing
>> >> >NACK
>> >> >14:53:33 1 Status 20144 (1099)
>> >> >14:53:33 1 000800 000000 (1099)
>> >> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:33 1 Status 1518 (4621) e1000 ( rx) Bad Pkt Lenght
>> >> >14:53:34 0 Status 2 ( 35) NET logical node not in node
>>map
>> >> >14:53:34 0 Status 2 ( 7) NET ( tx) failed (vc_attach...
View Full Message
|
|
|
|
|
|
