----- Original Message ----- From: Gustin Johnson <[email protected]> Date: Monday, April 5, 2010 4:16 am Subject: Re: [clug-talk] vmware bridged network woes (resend) To: [email protected], CLUG General <[email protected]>
> Greg King wrote: > > I recently applied updates to my Ubuntu 9.04 system and as > usual had > > to reconfigure VMware. The /usr/bin/vmware-config.pl script > completed> normally (after some dicking around), and I can log > into the vmware > > console and start VMs, but they all have difficulty > using the > > bridged network (which worked before the updates). There are > all set > > to "connect at power on" but the guest OS says no link, and vmware > > console has this event "Message from HAL: The network bridge on > > device vmnet0 is not running. The virtual machine will not be > able to > > communicate with the host or with other machines on your network. > > Failed to connect virtual device Ethernet1. " This message is in > > contradiction to the diagnostic message below that "Bridged > > networking on /dev/vmnet0 is running". > > > I did not see what version of VMWare this is, but in the past on > some of > their products I have had to delete and then recreate some of the > network interfaces in the VM hardware setup (usually the VM has > to be in > a powered off state). Its VMware Server 2.0.1. I see 2.02 is available so maybe I'll upgrade if I can't resolve this. I just deleted and readded the network interface - same result... > > You may be able to get away with "sudo /etc/init.d/vmware > restart" or > you may need to reboot if the Ubuntu updates installed a new > kernel (you > will likely have to run the vmware-config.pl script again). > > > I've googled around and don't see an obvious solution. Everything > > appears to be working normally as the following diagnostics show: > > The vmnet module is a good start. Try removing the kernel > module (sudo > rmmod vmnet) and then modprobing it, see if there are any interesting > details in syslog. I ran sudo rmmod vmnet and sudo modprobe -v vmnet and there were no errors in console or in syslog. > > > > > If anyone has seen this before or better yet has a resolution, > I'd be > > very thankful. > > Over the past 10 years I have seen a wide variety of issues with > VMWare. What is worrying is that I have more problems now > than 5 years ago, and > many of their products that I have in production (vmware server) only > run reliably on older distros, like Ubuntu 8.04. I can > only hope that > by the time 8.04 is out of support that alternatives have become > capableenough or somehow the laws of the Universe reverse and > VMWare chooses to > play nice with the kernel developers... I am not holding my breath. > > <snip> > Thanks Gustin. I'm sorry I missed your last talk re this subject at CLUG. I am becoming somewhat disillusioned about VMware too. I've started playing with Virtualbox but may consider ESXi down the road. So far Virtualbox looks pretty good, but it is early times for me. > Hth, > __ > G > >
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
