Russ Allbery wrote: > The workaround I tested and confirmed today is to unload vmxnet in the > init script as well. In other words, right before modprobe -r pcnet32, > add modprobe -r vmxnet. This is harmless if it's not already loaded, but > if it were loaded by the initramfs image, this will remove it and the > subsequent modprobe will load it and force initialization.
going to add that, thanks for your detailed description. > Better, of course, is to remove vmxnet from the initramfs image, but it's > hard to do that while using dep. open-vm could have a initramfs-hook that just rm's the module, no? > The only problem that I can think of > is that if you run open-vm-tools start twice in a row, with this change > it would reinitialize the network whereas before it wouldn't. That isn't > a problem for us; I don't know if it would be for anyone else. i think, too, that this shouldn't be a problem. Regards, Daniel -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [email protected] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
