[clug-talk] vmware bridged network woes clug-talk Digest, Vol 65, Issue 4

Mon Apr 5 23:20:02 PDT 2010

This does not directly address you issue but might be an alternative ---
I have tried a few of the Virtual Machine apps including VMWare and  
have settled out on VirtualBox on Ubuntu. Works very well and includes  
3D acceleration (if thats important to your).
I have not noticed it changing any setting after an update.
Install and Update directly from the Vbox site and insure that you  
have DKMD (dynamic kernel module support) installed.
Also it is strongly suggested to use (install) the additions.
OK for Win7-Pro, XP-Pro, Window Servers. Ubuntu, etc.
Can run a VMWare image as well, but probably need tweaks in the settings.
Supports import export .OVF (Open Visualization Format) as does VMWare.
http://www.virtualbox.org/wiki/Guest_OSes
TTFN

Quoting clug-talk-request at clug.ca:

> Send clug-talk mailing list submissions to
> 	clug-talk at clug.ca
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> or, via email, send a message with subject or body 'help' to
> 	clug-talk-request at clug.ca
>
> You can reach the person managing the list at
> 	clug-talk-owner at clug.ca
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of clug-talk digest..."
>
>
> Today's Topics:
>
>    1. Re: vmware bridged network woes (resend) (Gustin Johnson)
>    2. Re: COSSFEST Volunteers (GJM)
>    3. Re: vmware bridged network woes (resend) (John Clarke)
>    4. Re: vmware bridged network woes (resend) (Greg King)
>    5. Re: vmware bridged network woes (resend) (Greg King)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 05 Apr 2010 04:16:25 -0600
> From: Gustin Johnson <gustin at echostar.ca>
> Subject: Re: [clug-talk] vmware bridged network woes (resend)
> To: wgking at cips.ca, CLUG General <clug-talk at clug.ca>
> Message-ID: <4BB9B879.40108 at echostar.ca>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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).
>
> 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.
>
>>
>> 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 capable
> enough 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>
>
> Hth,
> __
> G
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 261 bytes
> Desc: OpenPGP digital signature
> URL:  
> <http://clug.ca/pipermail/clug-talk_clug.ca/attachments/20100405/df67d3c8/attachment-0001.bin>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 5 Apr 2010 10:54:58 -0600
> From: "GJM" <gjm at hotmail.com>
> Subject: Re: [clug-talk] COSSFEST Volunteers
> To: "'CLUG General'" <clug-talk at clug.ca>
> Message-ID: <BLU0-SMTP29AA2CE4DC8FCBA46CED2BAF190 at phx.gbl>
> Content-Type: text/plain;	charset="us-ascii"
>
>
> If you need another body to help out.... I can be available on either day
>
> Cheers
> Gary
>
> -----Original Message-----
> From: clug-talk-bounces at clug.ca [mailto:clug-talk-bounces at clug.ca] On Behalf
> Of Shawn
> Sent: March 31, 2010 6:17 PM
> To: CLUG General
> Subject: [clug-talk] COSSFEST Volunteers
>
> COSSFEST (http://www.cossfest.ca) is just over a week away.  It is time
> for volunteers.  So we are calling on CLUG members first.
>
> We have a need for 5 volunteers on each day.  We need a couple of
> volunteers for the registration desk, a couple for the rooms, and
> someone to make sure the speakers get where they need to go.  Email me
> off list if you are interested in helping out.  There ARE some perks to
> being a volunteer.
>
> ALSO, we have a time slot available at 2:00 on Friday that needs a
> presentation (and we've shuffled everyone we can...).  I'd also like to
> have a "backup" presentation ready to go "just in case".  If you are
> interested in doing a presentation, message me off list.  Any topic
> touching on open source in some way is fair game.  Take a look at the
> schedule (http://www.cossfest.ca/schedule) and the speaker list
> (http://www.cossfest.ca/speakers) for an idea of what is being covered.
>
> Finally, consider this message a general invitation to ALL CLUG members
> to come out to COSSFEST.  We have some interesting topics lined up, an
> audio production workshop, a social party (starting at 7:00) with a live
> DJ and a bar.  Oh, and don't forget the contests!  Hope to see you all
> there!
>
> Shawn
>
> _______________________________________________
> clug-talk mailing list
> clug-talk at clug.ca
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.791 / Virus Database: 271.1.1/2783 - Release Date: 04/01/10
> 00:35:00
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 05 Apr 2010 11:17:24 -0600
> From: John Clarke <clarkej at cuug.ab.ca>
> Subject: Re: [clug-talk] vmware bridged network woes (resend)
> To: CLUG General <clug-talk at clug.ca>
> Message-ID: <4BBA1B24.2060608 at cuug.ab.ca>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Gustin Johnson wrote:
>> 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).
>>
>> 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.
>>
>>> 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 capable
>> enough or somehow the laws of the Universe reverse and VMWare chooses to
>> play nice with the kernel developers... I am not holding my breath.
>
> I wonder whether in time as os's offer a built-in vm, vmware may evolve
> into a niche product. For eg. RHEL now offers kvm (about a year ago
> Redhat replaced support for xen with kvm, possibly because Citrix
> acquired zensource and is apparently close with MS - say in the same way
> Novell with SuSE is playing nice with MS)
>
> BTW for hands-on learning kvm I found this
> http://www.telecom-lille1.eu/people/landru/viminal/index-en.html#vodka-lab.
> The lab explains with clear hands on lessons COW (copy on write) file
> images, network bridging and other mysteries.
>
> These folks offer liveDVD 'learning lab environment' for ipv6,
> networking, kerberos authentication, with ldap and snmp labs in the works.
>
> It seems Telecom Lille is a French technical university. But these labs
> include superb English documentation for us not so bilingual types.
>
> John
>
>>
>> <snip>
>>
>> Hth,
>> __
>> G
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> clug-talk mailing list
>> clug-talk at clug.ca
>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>> **Please remove these lines when replying
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 05 Apr 2010 11:30:36 -0600
> From: Greg King <wgking at shaw.ca>
> Subject: Re: [clug-talk] vmware bridged network woes (resend)
> To: Gustin Johnson <gustin at echostar.ca>
> Cc: CLUG General <clug-talk at clug.ca>
> Message-ID: <f317f43e5c0b.4bb9c9dc at shaw.ca>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
> ----- Original Message -----
> From: Gustin?Johnson <gustin at echostar.ca>
> Date: Monday, April 5, 2010 4:16 am
> Subject: Re: [clug-talk] vmware?bridged network woes?(resend)
> To: wgking at cips.ca, CLUG?General <clug-talk at clug.ca>
>
>> 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
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:  
> <http://clug.ca/pipermail/clug-talk_clug.ca/attachments/20100405/66a381a3/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 05 Apr 2010 12:08:12 -0600
> From: Greg King <wgking at shaw.ca>
> Subject: Re: [clug-talk] vmware bridged network woes (resend)
> To: Gustin Johnson <gustin at echostar.ca>
> Cc: CLUG General <clug-talk at clug.ca>
> Message-ID: <f310d91149c8.4bb9d2ac at shaw.ca>
> Content-Type: text/plain; charset="iso-8859-1"
>
> FYI - upgrading to VMware 2.0.2 fixed the problem. The  
> install/upgrade script removes v2.0.1 and installs v2.0.2 and reruns  
> the config script. The config script found a problem with the  
> bridged config and generated a "Bridged (2)"? config which now  
> works.? Looks like the v2.0.2 config script has some improved error  
> checking.
>
> Greg
>
> ----- Original Message -----
> From: Gustin Johnson <gustin at echostar.ca>
> Date: Monday, April 5, 2010 4:16 am
> Subject: Re: [clug-talk] vmware bridged network woes (resend)
> To: wgking at cips.ca, CLUG General <clug-talk at clug.ca>
>
>> 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).
>>
>> 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.
>>
>> >
>> > 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>
>>
>> Hth,
>> __
>> G
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:  
> <http://clug.ca/pipermail/clug-talk_clug.ca/attachments/20100405/a1226542/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> clug-talk mailing list
> clug-talk at clug.ca
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>
>
> End of clug-talk Digest, Vol 65, Issue 4
> ****************************************
>

Bill Rayment
Applitec Systems Inc
403 630 4848