|
Matthias Schmidt(deleted)
|
troubleshooting toolset for drivers
|
|
Matthias Schmidt(deleted)
09/23/2009 7:45 AM
post38530
|
troubleshooting toolset for drivers
Hi,
I'm trying to troubleshoot QNX 6.4.1 running inside a VirtualBox 3.0.6 VM. I'm using the pcnet AMD lance driver. To make
make matters worse I'm on Mac OSX 10.5.8 (x86).
But the question itself is rather general: What is the toolset for troubleshooting driver issues:
1.) tcpdump -e -i en0 -vv
2.) nicinfo
what else could i do to monitor activity, get status, etc? Since the pcnet driver doesn't seem to be part of the source
package, i couldn't build a debug version ...
cheers,
Matthias
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: troubleshooting toolset for drivers
|
|
Andrew Boyd(deleted)
09/23/2009 9:09 AM
post38542
|
RE: troubleshooting toolset for drivers
A few thoughts:
1) to increase visibility into the network driver,
start it with the "verbose" option - this will cause
it to log more diagnostic information to sloginfo.
Some drivers even support a range of verbosity - ie
"verbose=100".
2) nicinfo is always good for counters
3) look at the procotol information - any evidence
of corrupted or lost packets?
4) we have a native driver for vmware - I think it's
called devnp-vmxnet.so - which is another alternative
to pcnet.
--
aboyd
|
|
|
|
|
|
Mario Charest
|
RE: troubleshooting toolset for drivers
|
|
Mario Charest
09/23/2009 9:14 AM
post38543
|
RE: troubleshooting toolset for drivers
> -----Original Message-----
> From: Andrew Boyd [mailto:community-noreply@qnx.com]
> Sent: Wednesday, September 23, 2009 9:09 AM
> To: drivers-networking
> Subject: RE: troubleshooting toolset for drivers
>
>
> 4) we have a native driver for vmware - I think it's
> called devnp-vmxnet.so - which is another alternative
> to pcnet.
It`s not in the 6.4.1 release. Where can a binary be found?
>
> --
> aboyd
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post38542
>
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: troubleshooting toolset for drivers
|
|
Andrew Boyd(deleted)
09/23/2009 9:45 AM
post38549
|
RE: troubleshooting toolset for drivers
> Where can a binary be found?
I just found one here:
www.pittspecials.com/etc/devnp-vmxnet.so
--
aboyd
www.PoweredByQNX.com/images/gat_t6.jpg
www.PoweredByQNX.com/images/gat_t7.jpg
www.PoweredByQNX.com/images/gat_t8.jpg
www.PoweredByQNX.com/images/gat_t9.jpg
www.PoweredByQNX.com/images/gat_t10.jpg
www.PoweredByQNX.com/images/gat_t11.jpg
www.PoweredByQNX.com/images/gat_t12.jpg
www.PoweredByQNX.com/images/gat_t13.jpg
|
|
|
|
|
|
Mario Charest
|
RE: troubleshooting toolset for drivers
|
|
Mario Charest
09/23/2009 10:31 AM
post38558
|
RE: troubleshooting toolset for drivers
No go on 6.4.1. No error in sloginfo, I can see with pidin mem that it`s loaded, but nada. Nicinfo shows nothing at
all. I added verbose option to the driver and io-pkt-v4 but nothing.
> -----Original Message-----
> From: Andrew Boyd [mailto:community-noreply@qnx.com]
> Sent: Wednesday, September 23, 2009 9:45 AM
> To: drivers-networking
> Subject: RE: troubleshooting toolset for drivers
>
>
> > Where can a binary be found?
>
> I just found one here:
>
> www.pittspecials.com/etc/devnp-vmxnet.so
>
> --
> aboyd
>
> www.PoweredByQNX.com/images/gat_t6.jpg
> www.PoweredByQNX.com/images/gat_t7.jpg
> www.PoweredByQNX.com/images/gat_t8.jpg
> www.PoweredByQNX.com/images/gat_t9.jpg
> www.PoweredByQNX.com/images/gat_t10.jpg
> www.PoweredByQNX.com/images/gat_t11.jpg
> www.PoweredByQNX.com/images/gat_t12.jpg
> www.PoweredByQNX.com/images/gat_t13.jpg
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post38549
>
|
|
|
|
|
|
Xiaodan Tang(deleted)
|
Re: RE: troubleshooting toolset for drivers
|
|
Xiaodan Tang(deleted)
09/23/2009 10:45 AM
post38562
|
Re: RE: troubleshooting toolset for drivers
> No go on 6.4.1. No error in sloginfo, I can see with pidin mem that it`s
> loaded, but nada. Nicinfo shows nothing at all. I added verbose option to
> the driver and io-pkt-v4 but nothing.
You have to modify .vmx file to make the interface a "vmx" network, not a "pclan". Have you done that?
|
|
|
|
|
|
Mario Charest
|
RE: RE: troubleshooting toolset for drivers
|
|
Mario Charest
09/23/2009 11:01 AM
post38564
|
RE: RE: troubleshooting toolset for drivers
I didn`t have a pclan in the .vmx file. After a little search on the web I ended up adding
ethernet0.virtualDev = "vmxnet"
ethernet0.features = "15"
to the .vmx file and it`s working now!
I was hoping for thing like TSO to be supported but ifconfig doesn`t show anything. At anyrate thanks this is
definitely a nice improvement, I`m assuming it performs better!
> -----Original Message-----
> From: Xiaodan Tang [mailto:community-noreply@qnx.com]
> Sent: Wednesday, September 23, 2009 10:46 AM
> To: drivers-networking
> Subject: Re: RE: troubleshooting toolset for drivers
>
> > No go on 6.4.1. No error in sloginfo, I can see with pidin mem that
> it`s
> > loaded, but nada. Nicinfo shows nothing at all. I added verbose
> option to
> > the driver and io-pkt-v4 but nothing.
>
> You have to modify .vmx file to make the interface a "vmx" network, not
> a "pclan". Have you done that?
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post38562
>
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: RE: troubleshooting toolset for drivers
|
|
Andrew Boyd(deleted)
09/23/2009 11:15 AM
post38566
|
RE: RE: troubleshooting toolset for drivers
> it`s working now!
Thx to xtang! I knew there was some vmware
config that needed to be done, but I didn't
know what it was.
> hoping for thing like TSO to be supported
I added TSO support to devnp-i82544.so (which
has since been grafted into devnp-e1000.so)
and let me tell you it was a bear:
http://svn.ott.qnx.com/view/core_networking/trunk/sys/dev_qnx/mpc85xx/tr
ansmit.c?revision=1077&view=markup
I'm not quite sure how you would graft TSO support
into devnp-vmxnet.so - does the underlying emulation
support it? - but I'm not sure what the point would
be, because vmware is so hideously slow anyways.
Sort of like putting a 6-71 supercharger on a hearse.
Besides, I don't think we even officially
support devnp-vmxnet.so - it's a bit of a red-
haired stepchild.
I wanted to put the source on the Foundry but
there was *one* line in one header file with a
questionable licence, and our legal team went
ballistic, so this driver is doomed to languish
in the darkness of the nda directory forever.
--
aboyd www.pittspecials.com/images/L39_hangar.jpg
|
|
|
|
|
|
Xiaodan Tang(deleted)
|
RE: RE: troubleshooting toolset for drivers
|
|
Xiaodan Tang(deleted)
09/23/2009 11:22 AM
post38567
|
RE: RE: troubleshooting toolset for drivers
> -----Original Message-----
> From: Andrew Boyd [mailto:community-noreply@qnx.com]
> Sent: September 23, 2009 11:16 AM
> To: drivers-networking
> Subject: RE: RE: troubleshooting toolset for drivers
>
> > hoping for thing like TSO to be supported
>
> I added TSO support to devnp-i82544.so (which
> has since been grafted into devnp-e1000.so)
> and let me tell you it was a bear:
>
>
http://svn.ott.qnx.com/view/core_networking/trunk/sys/dev_qnx/mpc85xx/tr
> ansmit.c?revision=1077&view=markup
>
> I'm not quite sure how you would graft TSO support
> into devnp-vmxnet.so - does the underlying emulation
> support it? - but I'm not sure what the point would
> be, because vmware is so hideously slow anyways.
> Sort of like putting a 6-71 supercharger on a hearse.
The driver is ported like in io-net time. At that time the TSO support
is not quite fit with the stack.
Yes, the underlying vmware emulation support TSO. I guess they figure it
is faster to do it in their code, then in guest OS.
> Besides, I don't think we even officially
> support devnp-vmxnet.so - it's a bit of a red-
> haired stepchild.
>
> I wanted to put the source on the Foundry but
> there was *one* line in one header file with a
> questionable licence, and our legal team went
> ballistic, so this driver is doomed to languish
> in the darkness of the nda directory forever.
The fact we are talking about it, may also violated something Andrew. :)
-xtang
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: RE: troubleshooting toolset for drivers
|
|
Andrew Boyd(deleted)
09/23/2009 11:27 AM
post38568
|
RE: RE: troubleshooting toolset for drivers
> the underlying vmware emulation support TSO
cool
> I guess they figure it is faster to do it in
> their code, then in guest OS.
Could be - I guess it depends which stack does
the fragmenting more efficiently ... unless
they are able to pass the TSO request to the
real, underlying hardware? Naw ...
> violated something?
AFAIK QSSL has never provided the devnp-vmxnet.so
driver binary to any customer :-)
--
aboyd
|
|
|
|
|
|
Mario Charest
|
RE: RE: troubleshooting toolset for drivers
|
|
Mario Charest
09/23/2009 11:30 AM
post38569
|
RE: RE: troubleshooting toolset for drivers
VMWARE also support E1000, it`s apparently the most efficient driver to use. It works with vmware 6.5 but with ESX it
says link down although it`s not because the driver is receiving packets. I`ll keep on digging.
> -----Original Message-----
> From: Andrew Boyd [mailto:community-noreply@qnx.com]
> Sent: Wednesday, September 23, 2009 11:16 AM
> To: drivers-networking
> Subject: RE: RE: troubleshooting toolset for drivers
>
>
> > it`s working now!
>
> Thx to xtang! I knew there was some vmware
> config that needed to be done, but I didn't
> know what it was.
>
> > hoping for thing like TSO to be supported
>
> I added TSO support to devnp-i82544.so (which
> has since been grafted into devnp-e1000.so)
> and let me tell you it was a bear:
>
> http://svn.ott.qnx.com/view/core_networking/trunk/sys/dev_qnx/mpc85xx/t
> r
> ansmit.c?revision=1077&view=markup
>
> I'm not quite sure how you would graft TSO support
> into devnp-vmxnet.so - does the underlying emulation
> support it? - but I'm not sure what the point would
> be, because vmware is so hideously slow anyways.
> Sort of like putting a 6-71 supercharger on a hearse.
>
> Besides, I don't think we even officially
> support devnp-vmxnet.so - it's a bit of a red-
> haired stepchild.
>
> I wanted to put the source on the Foundry but
> there was *one* line in one header file with a
> questionable licence, and our legal team went
> ballistic, so this driver is doomed to languish
> in the darkness of the nda directory forever.
>
> --
> aboyd www.pittspecials.com/images/L39_hangar.jpg
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post38566
>
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: RE: troubleshooting toolset for drivers
|
|
Andrew Boyd(deleted)
09/23/2009 11:32 AM
post38570
|
RE: RE: troubleshooting toolset for drivers
> VMWARE also support E1000, it`s apparently
> the most efficient driver to use
yeah - if you could get devnp-e1000.so working
on vmware, you could turn on TSO and rx/tx
hardware checksums :)
--
aboyd
|
|
|
|
|
|
Mario Charest
|
RE: RE: troubleshooting toolset for drivers
|
|
Mario Charest
09/23/2009 11:36 AM
post38571
|
RE: RE: troubleshooting toolset for drivers
> -----Original Message-----
> From: Andrew Boyd [mailto:community-noreply@qnx.com]
> Sent: Wednesday, September 23, 2009 11:33 AM
> To: drivers-networking
> Subject: RE: RE: troubleshooting toolset for drivers
>
>
> > VMWARE also support E1000, it`s apparently
> > the most efficient driver to use
>
> yeah - if you could get devnp-e1000.so working
> on vmware, you could turn on TSO and rx/tx
> hardware checksums :)
It`s working with VMware 6.5, and I have these feature turned on however it will prove very difficult to figure out if
they help or not...
However it`s no go on ESX 3.5. We`ll put this on hold for now, maybe it would work with ESX 4.0, but there is no plan
to update yet.
>
> --
> aboyd
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post38570
>
|
|
|
|
|
|
Matthias Schmidt(deleted)
|
Re: RE: RE: troubleshooting toolset for drivers
|
|
Matthias Schmidt(deleted)
09/25/2009 6:10 PM
post38830
|
Re: RE: RE: troubleshooting toolset for drivers
Hi Andrew + Xiaodan,
you guys owe me some drinks for completely highjacking my topic ... ;-)
Meanwhile i managed to get the e1000 driver running ...
cheers,
Matthias
|
|
|
|
|
|
Matthias Schmidt(deleted)
|
Re: RE: RE: troubleshooting toolset for drivers
|
|
Matthias Schmidt(deleted)
11/10/2009 3:33 AM
post41680
|
Re: RE: RE: troubleshooting toolset for drivers
Hi *,
With my help, VirtualBox engineering fixt the network issues in VB 3.0.10 , see changelog:
http://www.virtualbox.org/wiki/Changelog
here's the corresponding bug:
http://www.virtualbox.org/ticket/3206
Please spread the word that QNX can now be installed and used in VirtualBox 3.0.10+.
HTH,
Matthias
|
|
|
|
|
|
Matthias Schmidt(deleted)
|
Re: RE: troubleshooting toolset for drivers
|
|
Matthias Schmidt(deleted)
09/23/2009 9:54 AM
post38553
|
Re: RE: troubleshooting toolset for drivers
Hi Andrew,
thanks a lot for your thoughts, see comments inline:
>
> A few thoughts:
>
> 1) to increase visibility into the network driver,
> start it with the "verbose" option - this will cause
> it to log more diagnostic information to sloginfo.
> Some drivers even support a range of verbosity - ie
> "verbose=100".
pcnet supports verbose=4 at a maximum. That's what I've used. It doesn't give much more information compared to nicinfo.
>
> 2) nicinfo is always good for counters
Right, but all the counters are 0, but the bytes transferred which is aprox. 200. Even the packets transmitted counter
remains zero, no matter what i do. Strange.
>
> 3) look at the procotol information - any evidence
> of corrupted or lost packets?
Packets don't travel at all. That's the trouble.
Could this be caused by the fact that the thingy is loaded through the shim wrapper?
>
> 4) we have a native driver for vmware - I think it's
> called devnp-vmxnet.so - which is another alternative
> to pcnet.
Having somehting similar would be just great. I leave this as an exercise for the future ...
>
> --
> aboyd
>
|
|
|
|
|
|
Xiaodan Tang(deleted)
|
Re: troubleshooting toolset for drivers
|
|
Xiaodan Tang(deleted)
09/23/2009 10:44 AM
post38561
|
Re: troubleshooting toolset for drivers
I take it the network is totally "not working"?
How do you set the virtual network? Try to set the network to "NAT" instead of "Bridge", see if you can come up, and qnx
could dhcp an ip address for you.
-xtang
> Hi,
>
> I'm trying to troubleshoot QNX 6.4.1 running inside a VirtualBox 3.0.6 VM. I'm
> using the pcnet AMD lance driver. To make make matters worse I'm on Mac OSX
> 10.5.8 (x86).
>
> But the question itself is rather general: What is the toolset for
> troubleshooting driver issues:
>
> 1.) tcpdump -e -i en0 -vv
> 2.) nicinfo
>
> what else could i do to monitor activity, get status, etc? Since the pcnet
> driver doesn't seem to be part of the source package, i couldn't build a debug
> version ...
>
> cheers,
>
> Matthias
|
|
|
|
|
|
Matthias Schmidt(deleted)
|
Re: troubleshooting toolset for drivers
|
|
Matthias Schmidt(deleted)
09/23/2009 10:59 AM
post38563
|
Re: troubleshooting toolset for drivers
> I take it the network is totally "not working"?
right.
>
> How do you set the virtual network? Try to set the network to "NAT" instead of
> "Bridge", see if you can come up, and qnx could dhcp an ip address for you.
It always has been NAT. The device-enumberator caused the emulation to flood the logs. I've disabled this completely to
see what's going on. Neither DHCP DISCOVERS nor ARP who-has packets get a response. I guess there's not much more i can
do on the guest-os (qnx) side of this issue. That's why i asked for additional troubleshooting options.
cheers,
Matthias
>
> -xtang
>
> > Hi,
> >
> > I'm trying to troubleshoot QNX 6.4.1 running inside a VirtualBox 3.0.6 VM.
> I'm
> > using the pcnet AMD lance driver. To make make matters worse I'm on Mac OSX
>
> > 10.5.8 (x86).
> >
> > But the question itself is rather general: What is the toolset for
> > troubleshooting driver issues:
> >
> > 1.) tcpdump -e -i en0 -vv
> > 2.) nicinfo
> >
> > what else could i do to monitor activity, get status, etc? Since the pcnet
> > driver doesn't seem to be part of the source package, i couldn't build a
> debug
> > version ...
> >
> > cheers,
> >
> > Matthias
>
>
|
|
|
|
|
|
Xiaodan Tang(deleted)
|
RE: troubleshooting toolset for drivers
|
|
Xiaodan Tang(deleted)
09/23/2009 11:12 AM
post38565
|
RE: troubleshooting toolset for drivers
I hadn't use VirtualBox myself, but ...
If you are on NAT, your dhcp request only suppose to go to VirtualBox,
and the VirtualBox need to respond to give you an IP address.
If you can't get pass this, then I'd worry something is wrong with your
VirtualBox setting.
-xtang
> -----Original Message-----
> From: Matthias Schmidt [mailto:community-noreply@qnx.com]
> Sent: September 23, 2009 10:59 AM
> To: drivers-networking
> Subject: Re: troubleshooting toolset for drivers
>
> > I take it the network is totally "not working"?
>
> right.
>
> >
> > How do you set the virtual network? Try to set the network to "NAT"
> instead of
> > "Bridge", see if you can come up, and qnx could dhcp an ip address
for
> you.
>
> It always has been NAT. The device-enumberator caused the emulation to
> flood the logs. I've disabled this completely to see what's going on.
> Neither DHCP DISCOVERS nor ARP who-has packets get a response. I guess
> there's not much more i can do on the guest-os (qnx) side of this
issue.
> That's why i asked for additional troubleshooting options.
>
> cheers,
>
> Matthias
>
>
> >
> > -xtang
> >
> > > Hi,
> > >
> > > I'm trying to troubleshoot QNX 6.4.1 running inside a VirtualBox
3.0.6
> VM.
> > I'm
> > > using the pcnet AMD lance driver. To make make matters worse I'm
on
> Mac OSX
> >
> > > 10.5.8 (x86).
> > >
> > > But the question itself is rather general: What is the toolset for
> > > troubleshooting driver issues:
> > >
> > > 1.) tcpdump -e -i en0 -vv
> > > 2.) nicinfo
> > >
> > > what else could i do to monitor activity, get status, etc? Since
the
> pcnet
> > > driver doesn't seem to be part of the source package, i couldn't
build
> a
> > debug
> > > version ...
> > >
> > > cheers,
> > >
> > > Matthias
> >
> >
>
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post38563
|
|
|
|
|
|
