On Fri, Apr 13, 2007 at 01:52:46PM -0700, Curtis Doty wrote: > Am I going about this wrong? It's quite trivial to deadlock the Fedora > kernel. > > # modprobe netloop ; rmmod netloop > unregister_netdevice: waiting for veth3 to become free. Usage count = 1 > unregister_netdevice: waiting for veth3 to become free. Usage count = 1 > unregister_netdevice: waiting for veth3 to become free. Usage count = 1 > ... > > This is without doing anything else with xend or the other modules. So > why/who/what grabbed a hold of that veth? This is basically a limitation of the netloop module - its not written to allow its removal once loaded. Fortunately we don't need to worry about fixing this, because in the very near future we will be blasting netloop into oblivion :-) This will make networking in Dom0 much simpler because you won't have this crazy set of extra devices for Dom0 - just the real eth*, the bridge device & any VIFs for guest VMs. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
