unregister_netdevice: waiting for eth0 to become free
hi list,
I have come across a problem on a SLES8 (2.4 kernel based) system today.
getting "unregister_netdevice: waiting for eth0 to become free" on shutdown and the shutdown got stuck at this point. needed to do a hard reset to continue.
by some search via google/vmware-forum i found a hint very soon (this was for RedHat, but also worked with SLES)
------------------------------------------------
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 moduleunregister_netdevice: waiting for eth0 to become free
This message repeats continuously until you reboot the virtual machine. To prevent this problem in virtual machines running Linux, disable IPv6 before installing VMware Tools. To disable IPv6 in a virtual machine running Linux:
1 If the file /etc/sysconfig/network contains the line NETWORKING_IPV6=yes, change the line to NETWORKING_IPV6=no.
2 In the file /etc/modules.conf, add the following lines:
alias ipv6 off
alias net-pf-10 off
After you disable IPv6, you should be able to install and configure VMware Tools successfully.
------------------------------------------------
this solved my shutdown problem. (network driver wasn`t pcnet32 but vmxnet , which is a vmware specific network device)
anyway - i wondered about this "waiting to become free". this is just a workaround, not a solution.
what if i needed to use ipv6 ?
before i disabled ipv6 (as it is being recommended) , i tried some manual steps to disable ipv6, but failed.
don`t have the sles8 here at home, but trying to disable ipv6 "manually" on a newer system gives a similar error:
vserver1:~ # rmmod ipv6
ERROR: Module ipv6 is in use by ip6t_REJECT
vserver1:~ # rmmod ip6t_REJECT
ERROR: Module ip6t_REJECT is in use
ok - rmmod telling me, that ip6t_REJECT is in use.
but - what/who is using it ?
i disabled all network services for which lsof had shown that they had an ipv6 socket open, i also did "ifconfig sit0 down", which seems to be a ipv6 related network device, but still having ip6t_REJECT in use.
now my questions:
- how can i determine what "component" (i.e. one of userspace app, device, kernel-thread....whatever) is using a module, so i`m able to unload that module ?
- is there sort of "lsof" for kernel modules ?
- what is causing the unregister_netdevice to fail ? is it an older bug which has been resolved in later kernels ?
im quite sure, that i have seen this issue in the past, more then once and not related to vmware. so, this is why im reporting it here and asking for help
regards
roland
In article <01a501c6ff74$6fc52c80$962e8d52@aldipc> (at Fri, 3 Nov 2006 19:18:17 +0100), "roland" <[email protected]> says:
Quoted 4 lines
vserver1:~ # rmmod ipv6
ERROR: Module ipv6 is in use byip6t_REJECT
vserver1:~ # rmmodip6t_REJECT
ERROR: Moduleip6t_REJECTis in use
The ipv6 module cannot be unloaded once it has been loaded.
I'm not sure what is happened with vmware.
--yoshfuji
Quoted 2 lines
The ipv6 module cannot be unloaded once it has been loaded.
sorry, i thought i could rmmod evey module which was insmod/modprobe'd before and i didn`t know that there are exceptions
Quoted 1 line
I'm not sure what is happened with vmware.
i think this is not completely related to vmware - but maybe this is being triggered more often by vmware ?
http://www.google.de/search?hl=de&q=%22unregister_netdevice%3A+waiting+for+eth0+to+become+free
it`s really strange, but after taking a look, vmware seems to recommend disabling ipv6 for _every_ linux based guest OS in general:
http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/common/html/wwhelp.htm?context=gos_ww5_output&file=choose_install_guest_os.html
since there are already running millions of linux based VMs in this world, i think this isn`t very good "promotion" for ipv6, if vmware recommending disabling it. ok, there are not that much people already needing ipv6 NOW, but the later they are running it and the later outstanding bugs being fixed, the harder it will be to convert from ipv4 to ipv6....
roland
----- Original Message ----- From: "YOSHIFUJI Hideaki / ????" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>; <[email protected]>; <[email protected]>
Sent: Friday, November 03, 2006 7:47 PM
Subject: Re: unregister_netdevice: waiting for eth0 to become free
Quoted 13 lines
In article <01a501c6ff74$6fc52c80$962e8d52@aldipc> (at Fri, 3 Nov 2006 19:18:17 +0100), "roland" <[email protected]> says:
Quoted 4 lines
vserver1:~ # rmmod ipv6
ERROR: Module ipv6 is in use byip6t_REJECT
vserver1:~ # rmmodip6t_REJECT
ERROR: Moduleip6t_REJECTis in useThe ipv6 module cannot be unloaded once it has been loaded.
I'm not sure what is happened with vmware.
--yoshfuji
Quoted 16 lines · On Fri, 3 Nov 2006 20:53:09 +0100 "roland" <[email protected]> wrote:
Quoted 2 lines
The ipv6 module cannot be unloaded once it has been loaded.
sorry, i thought i could rmmod evey module which was insmod/modprobe'd before and i didn`t know that there are exceptions
Quoted 1 line
I'm not sure what is happened with vmware.
i think this is not completely related to vmware - but maybe this is being triggered more often by vmware ?
http://www.google.de/search?hl=de&q=%22unregister_netdevice%3A+waiting+for+eth0+to+become+freeit`s really strange, but after taking a look, vmware seems to recommend disabling ipv6 for _every_ linux based guest OS in general:
http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/common/html/wwhelp.htm?context=gos_ww5_output&file=choose_install_guest_os.html
Quoted 10 lines
since there are already running millions of linux based VMs in this world, i think this isn`t very good "promotion" for ipv6, if vmware recommending disabling it.
ok, there are not that much people already needing ipv6 NOW, but the later they are running it and the later outstanding bugs being fixed, the harder it will be to convert from ipv4 to ipv6....roland
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.
Signature · 1 line
Stephen Hemminger <[email protected]>
In article <01d001c6ff81$b4bb5dc0$962e8d52@aldipc> (at Fri, 3 Nov 2006 20:53:09 +0100), "roland" <[email protected]> says:
Quoted 5 lines
Quoted 1 line
I'm not sure what is happened with vmware.
i think this is not completely related to vmware - but maybe this is being triggered more often by vmware ?
http://www.google.de/search?hl=de&q=%22unregister_netdevice%3A+waiting+for+eth0+to+become+free
I think all except for vmware related ones seem ancient reports and I believe we have fixed them.
--yoshfuji