From: Stephen Hemminger <shemminger@osdl.org>
To: devzero@web.de
Cc: greearb@candelatech.com, jesper.juhl@gmail.com,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: unregister_netdevice: waiting for eth0 to become free
Date: Fri, 3 Nov 2006 13:04:51 -0800 [thread overview]
Message-ID: <20061103130451.47e70922@freekitty> (raw)
In-Reply-To: <1405740846@web.de>
On Fri, 03 Nov 2006 21:31:01 +0100
devzero@web.de wrote:
> >Vmware has there own pseudo ethernet device and unless you have the source for it.
> >It would be hard to tell if it correctly manages itself.
>
> VMware is able to emulate three different network card types:
>
> - AMD Am79C970A - PCnet LANCE PCI Ethernet Controller (linux pcnet32 driver)
> - Intel E1000 (e1000 driver)
> - VMXNET - VMware PCI Ethernet Adapter (vmxnet, vmware`s own driver)
>
> so there are 3 different drivers being used inside the guest OS for networking virtual machines.
>
> rumours tell, that the vmxnet driver is sort of a mess, but i have seen the unregister_netdevice problem with pcnet32 AND with vmxnet - and all of the vmware readme`s are telling:
>
> "In many Linux distributions, if IPv6 is enabled, VMware Tools cannot be configured with vmware-config-tools.pl after installation. In this case, VMware Tools is unable to set the network device correctly for the virtual machine, and displays a message similar to
> Unloading pcnet32 module
> unregister_netdevice: waiting for eth0 to become free"
>
> so - this is the native linux driver for pcnet32 which fails get unloaded _before_ the driver being replaced by the vmware specific one and the virtual nic being switched to the VMXNET adapter.....
>
> anyway - i got that problem while shutting down a VM, not while installing vmware tools.
>
> btw - just came across this posting from jesper juhl:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=115703768804826&w=2
>
> roland
You are also looking at 2.4 code which is OLD and probably broken in the
device ref counting. Lots of work went into cleaning up the shutdown and device
ref counting for 2.6, and I'm not surprised if 2.4 has problems.
next prev parent reply other threads:[~2006-11-03 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 20:31 unregister_netdevice: waiting for eth0 to become free devzero
2006-11-03 21:04 ` Stephen Hemminger [this message]
2006-11-03 21:43 ` roland
-- strict thread matches above, loose matches on Subject: below --
2006-11-03 18:18 roland
2006-11-03 18:47 ` YOSHIFUJI Hideaki / 吉藤英明
2006-11-03 19:53 ` roland
2006-11-03 19:58 ` Stephen Hemminger
2006-11-03 20:13 ` YOSHIFUJI Hideaki / 吉藤英明
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061103130451.47e70922@freekitty \
--to=shemminger@osdl.org \
--cc=devzero@web.de \
--cc=greearb@candelatech.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox