VMware Communities
eobet
Contributor
Contributor

The network bridge on device /dev/vmnet0 is not running

Ok, so the above message appears after I have enabled bridged mode in Fusion, and whenever I then switch off my airport and connect to the internet via FireWire instead.

First of all, that error message was written by someone used to coding Windows apps. 😛

Second, as a consumer, I'm not interested in whatever that message has to say.

All I want is for Fusion to bridge whichever network adapter is currently connected to the internet.

Is there any chance that this might get done for beta 5? Smiley Wink

Thank you!

Reply
0 Kudos
19 Replies
eobet
Contributor
Contributor

(Le bump.)

Btw, I've found no setting to switch which network adapter gets bridged...

Also, when you do connect to an airport network, you can repair the connection in XP and it works...

Reply
0 Kudos
admin
Immortal
Immortal

There's no friendly setting, currently, to set which network adapter we bridge to, but it's supposed to automatically follow what the host OS is using for connectivity.

Reply
0 Kudos
eobet
Contributor
Contributor

Oh, so I should file a bug for this?

Perhaps it really is a Firewire issue?

Reply
0 Kudos
admin
Immortal
Immortal

Yeah, please file a bug for this. I'm actually not sure we support bridging to firewire.

On the message contents, you're entirely right, but nobody's supposed to see that message. It did tell you what you needed to know -- bridged networking won't work -- though the details on why would be gobbledygook to most people, agreed.

Reply
0 Kudos
eobet
Contributor
Contributor

Done!

Thank you for the reply. Smiley Happy

Reply
0 Kudos
hhwong
Contributor
Contributor

Sorry to resurrect this old thread, but there seems to be a related issue -- if there are no network connections to the internet available when you start your VM, you're hosed -- you have to shut down and restart it again if you're in bridged mode. I guess it assumes if there are no network connections, then there never will be?

Use case -- my wireless connection sometimes takes around 30 seconds to a minute to reconnect to my wireless AP (via WPA-PSK) after I wake up my laptop. If I start my VM in this time period I never can have network connectivity unless I shut it down (not just restart it).

In Parallels, the virtual network adapter has the ability to find the network -- and I can even repair the connection once my wireless connection gets going.

The Repair Connection is greyed out in this situation in Windows XP under VMware.

BTW, i tried to submit this feedback on the support page this morning, and the page is telling my that I need the 'Account' field filled in(?)

Reply
0 Kudos
jrjX
Contributor
Contributor

I am seeing this message, and doing a quick ls of /dev doesn't show any such device. Is there supposed to be a /dev/vmnet0 device? When does it get created?

Reply
0 Kudos
headsign
Contributor
Contributor

I ran into the same problem twice now. The first time was very annoying because I was on a train and had thus no chance to work properly. It got fixed for now by (re-)installing VMWare (BETA 1.1) on top of my initial installation but it had given me quite a time of cluelessly looking through config files and trying out new settings.

I was trying to get an internal connection in order to mount a network volume and possibly, the requested device was /dev/vmnet1 while the second time, I was connected to the internet via airport and the requested device was /dev/vmnet0.

Reply
0 Kudos
cornflakes
Contributor
Contributor

I occasionally run into this error message, and it used to be the only solution was to restart my Mac. I use an Ethernet cable for my network connection, and it's always connected. For whatever reason though, Fusion will pop up with this error every so often.

Digging around I found this seems to help me with my problem:

1. Open Terminal

2.. Type the following line:

sudo "/Library/Application Support/VMWare Fusion/boot.sh" --restart

3. Type in your password when prompted

4. Close Terminal

Now I can reconnect my virtual machine to the network without having to reboot.

Reply
0 Kudos
photolee
Contributor
Contributor

I'm running windows xp in the vm and i just recently upgraded to Leopard and i'm getting that error too...i tried the terminal fix but didn't work for me =( I'm connected via ethernet cable.

Reply
0 Kudos
admin
Immortal
Immortal

I'm running windows xp in the vm and i just recently upgraded to Leopard and i'm getting that error too

Major system changes (e.g. upgrading to Leopard) may require reinstalling Fusion.

Reply
0 Kudos
gdevlugt
Contributor
Contributor

When I upgraded to Leopard I got this message using Fusion 1.0. An upgrade to 1.1RC solved it for me (although perhaps reinstalling 1.0 will also do the job).

Reply
0 Kudos
bkaupe
Contributor
Contributor

reinstalling the RC and rebooting Leopard fixed it for me

Reply
0 Kudos
photolee
Contributor
Contributor

i installed fusion 1.1 and everything is working as it should :smileygrin:

Reply
0 Kudos
Bob_Greschke
Contributor
Contributor

I can't get this bridging to work.

MacBook, Tiger, Fusion 1.1, WinXP. The laptop cannot be connected to the network (think middle of the Himalayas -- literally). A piece of equipment is connected to the laptop's Ethernet and a program is started in XP. When the equipment is "awakened" it broadcasts that it is there, then the program sees that and assigns the piece of equipment an IP address that I fill in (an address different than that of the laptop's manually set address, but on the same sub-net). What do I do with the IP settings on the Tiger side (I've got them manually set to the same sub-net)? I've manually set the IP of Windows to the sub-net. I keep getting the device not running message when starting XP.

I haven't monky'ed with anything I shouldn't have. Yet. Smiley Happy

Thanks!

Bob

Reply
0 Kudos
Maccarocks
Contributor
Contributor

I've had Fusion running an XP image on Leopard (Macbook santa rosa) for a couple of weeks now, with no problems at all.

All of a sudden this week, the bridging failed. Connectivity still worked over NAT but thats not the point, right?!

No changes to the OS or networking at all, it just stopped working on Monday.

Running "boot.sh --restart" has kicked it back into life now but I'd like to know wtf happened.

There's nothing in the logs to indicate what the problem was/is...

Reply
0 Kudos
BadTim
Contributor
Contributor

Thanks Conflakes! Worked perfectly... just make sure that your VM is powered down before executing because the command looks like it kills any processes associated with Fusion. (I could be, and probably am, wrong about that.)

Reply
0 Kudos
sandstream
Contributor
Contributor

This occurs to me when I'm connecting to work via VPN. For some reason? When I disconnect it works again.

//Peter

Reply
0 Kudos
Zardozz
Contributor
Contributor

This trick saved the day for me.

Thanks for posting it...

Reply
0 Kudos