[Intrepid] No network using Vmware Workstation

Bug #259133 reported by Carroarmato0
0
Affects Status Importance Assigned to Milestone
vmware-server (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu Intrepid Alpha 4

For some reason networking doesn't work when you've set Vmware Workstation up to use a Bridged network.

Networking DOES work when instead you use a Nat configuration in Vmware.

In both cases, Network Manager doesn't recognize any networking device. This may be due to the proprietary nature of the virtual Vmware networking device (vmxnet).

***Workaround***

Manually set-up networking:
1. Manually add the pcnet32 kernel module ( #sudo modprobe pcnet32 )
2. Start the eth0 interface ( #sudo ifconfig eth0 up )
3. Restart networking ( #sudo /etc/init.d/networking restart )
4. Request DHCP address ( #sudo dhc_client )
5. Test connection and interrupt command with CTRL-C ( #ping google.com)

description: updated
description: updated
Revision history for this message
Willem Ligtenberg (wligtenberg) wrote :

I can confirm this bug in kernel 2.6.24-21-generic using KVM.
Also the mentioned workaround worked for me.

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

It looks like compiling vmware-tools in the new kernel 2.6.27-2 makes things work better.

Although there are many compiling errors with various vmware modules, vmxnet seems to work correctly now.

Waiting for someone to confirm that the networking part works with the new kernel.

Revision history for this message
Andreas Moog (ampelbein) wrote :

This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in vmware-server.

Revision history for this message
Willem Ligtenberg (wligtenberg) wrote :

This bug might be related to:
https://bugs.launchpad.net/ubuntu/hardy/+source/kvm/+bug/251480
As running with -no-kvm resolves the problem.

Revision history for this message
Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in vmware-server (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.