Re: VMWare Fusion 6.0.2 + Mavericks - Bridged Netw...

davisford · ‎11-08-2013

VMWare Version 6.0.2 (1398658)

Host OS: Mac OS X Version 10.9 (Mavericks), Hardware is a Mac Mini

Guest OS: Ubuntu 12.04 AMD64

VMWare Tools Installed: VMwareTools-9.6.1-1378637

Problem: when I switched to bridged networking, either autodetect or WiFi, the guest OS fails to establish a network connection. If I switch back to shared mode, it works fine. The Mac MINI is using the WiFi interface to connect to the network (not Ethernet). I don't have a port/cable close enough to try the Ethernet adapter right now.

Here's the output of ifconfig -a on the host

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
  options=3<RXCSUM,TXCSUM>
  inet6 ::1 prefixlen 128 
  inet 127.0.0.1 netmask 0xff000000 
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
  nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
  options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
  ether 68:5b:35:84:95:92 
  nd6 options=1<PERFORMNUD>
  media: autoselect (none)
  status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
  ether 28:cf:e9:0e:36:c1 
  inet6 fe80::2acf:e9ff:fe0e:36c1%en1 prefixlen 64 scopeid 0x5 
  inet 26.46.175.239 netmask 0xfffffe00 broadcast 26.46.175.255
  nd6 options=1<PERFORMNUD>
  media: autoselect
  status: active
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
  options=60<TSO4,TSO6>
  ether 32:00:1a:ae:c2:80 
  media: autoselect <full-duplex>
  status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
  lladdr 44:fb:42:ff:fe:aa:ec:28 
  nd6 options=1<PERFORMNUD>
  media: autoselect <full-duplex>
  status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
  ether 0a:cf:e9:0e:36:c1 
  media: autoselect
  status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
  options=63<RXCSUM,TXCSUM,TSO4,TSO6>
  ether 6a:5b:35:48:cb:00 
  Configuration:
  id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
  maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
  root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
  ipfilter disabled flags 0x2
  member: en3 flags=3<LEARNING,DISCOVER>
          ifmaxaddr 0 port 6 priority 0 path cost 0
  nd6 options=1<PERFORMNUD>
  media: <unknown type>
  status: inactive
vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
  ether 00:50:56:c0:00:01 
  inet 172.16.1.1 netmask 0xffffff00 broadcast 172.16.1.255
vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
  ether 00:50:56:c0:00:08 
  inet 172.16.8.1 netmask 0xffffff00 broadcast 172.16.8.255

I did notice when I enabled bridged mode with WiFi, it created a new "Thunderbolt Bridge" adapter in the Mac Networking Settings, but it doesn't appear to use it or connect to it.

I have restarted the Guest OS and the host OS a number of times, and applied all patches and updates. Here is the bottom of the guests vmware log file:

2013-11-08T10:34:58.164-05:00| vmx| I120: ToolsUpdateManifestInfoWorkerThreadDone: Updating the manifest info.

2013-11-08T10:34:58.164-05:00| vmx| I120: VMXVmdb_SetToolsVersionStatus: status value set to 'ok', 'current', install possible

2013-11-08T10:34:58.164-05:00| vmx| I120: TOOLS installed legacy version 9409, available legacy version 9409

2013-11-08T10:34:58.164-05:00| vmx| I120: TOOLS manifest update status is 3

2013-11-08T10:34:58.164-05:00| vmx| I120: TOOLS can be autoupgraded.

2013-11-08T10:34:58.164-05:00| vmx| I120: TOOLS Setting autoupgrade-checked TRUE.

2013-11-08T10:34:58.164-05:00| vmx| I120: RPT: Not ESX. Skipped.

2013-11-08T10:34:58.170-05:00| vmx| I120: VUsbUpdateVigorFieldsAndAutoconnect: New set of 3 USB devices

2013-11-08T10:34:58.170-05:00| vmx| I120: USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/1/1/8/2 speed:low family:hid arbRuntimeKey:4 quirks:needs-boot-camp,built-in version:2]

2013-11-08T10:34:58.170-05:00| vmx| I120: USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:828a path:13/1/1/8/1/3 speed:full family:vendor,other,wireless,bluetooth arbRuntimeKey:2 quirks:needs-boot-camp,built-in version:2]

2013-11-08T10:34:58.170-05:00| vmx| I120: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth virtPath:usb:2 deviceType:virtual-bluetooth version:2], connected to [Virtual Hub 1, Port 1]

2013-11-08T10:34:58.249-05:00| vcpu-1| I120: DDB: "longContentID" = "4c3943dfe92c4dc7d661c083812fefe2" (was "0c12b1d353a118664c753841a939d632")

2013-11-08T10:34:58.263-05:00| vthread-16| I120: VTHREAD start thread 16 "vthread-16" pid 345

2013-11-08T10:34:58.345-05:00| vcpu-2| I120: TOOLS state change 4 returned status 1

2013-11-08T10:34:58.345-05:00| vcpu-2| I120: Vix: [4732866560 mainDispatch.c:3905]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).

2013-11-08T10:34:58.446-05:00| mks| I120: GL-Backend: successfully started by HWinMux to do window composition.

2013-11-08T10:34:58.449-05:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2013-11-08T10:34:58.985-05:00| vmx| I120: Guest does not support change 3D hint RPC. Ignoring.

2013-11-08T10:35:00.985-05:00| mks| I120: Notify tools that 3d is available.

2013-11-08T10:35:00.985-05:00| vmx| I120: Guest does not support change 3D hint RPC. Ignoring.

2013-11-08T10:37:15.678-05:00| vmx| I120: VMXVmdbEditRemDevices: Reconnect of ethernet0 would be delayed.

2013-11-08T10:37:15.679-05:00| vmx| I120: VMXVmdbSetCfgState: reconnect delay = 5 seconds, reconnectEthVector = 0x1, poll cb status = 0.

2013-11-08T10:37:15.679-05:00| vmx| I120: TOOLS received request in VMX to set option 'synctime' -> '1'

2013-11-08T10:37:15.713-05:00| vmx| I120: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#7/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#ca/in/

2013-11-08T10:37:20.732-05:00| vmx| I120: VNET: ethernet0 enable link state propagation, lsp.state = 5

2013-11-08T10:37:20.733-05:00| vmx| I120: VNET: MACVnetConnectToNetwork ethernet0 lsp.state = 4

2013-11-08T10:37:20.733-05:00| vmx| I120: VNET: MACVNetConnectToNetwork Ethernet0: notify available

2013-11-08T10:37:20.733-05:00| vmx| I120: EthernetDevicesDelayedConnect: Delayed connect of network adapter ethernet0 succeeded.

2013-11-08T10:37:20.734-05:00| vmx| I120: VNET: MACVNetLinkStateEventHandler: event, up:1, adapter:1

2013-11-08T10:37:20.734-05:00| vmx| I120: VNET: MACVNetLinkStateEventHandler: ethernet0 state from 4 to 6

2013-11-08T10:37:20.834-05:00| vmx| I120: VNET: MACVNetLinkStateTimerHandler: ethernet0: state from 6 to 1

2013-11-08T10:37:25.906-05:00| vmx| I120: VNET: MACVNetLinkStateTimerHandler: ethernet0: state from 1 to 5

2013-11-08T10:39:01.026-05:00| vthread-17| I120: VTHREAD start thread 17 "vthread-17" pid 345

2013-11-08T10:39:01.026-05:00| vthread-18| I120: VTHREAD start thread 18 "vthread-18" pid 345

2013-11-08T10:39:01.026-05:00| vthread-19| I120: VTHREAD start thread 19 "vthread-19" pid 345

2013-11-08T10:39:01.026-05:00| vthread-20| I120: VTHREAD start thread 20 "vthread-20" pid 345

2013-11-08T10:39:01.027-05:00| vthread-21| I120: VTHREAD start thread 21 "vthread-21" pid 345

2013-11-08T10:39:01.027-05:00| vthread-22| I120: VTHREAD start thread 22 "vthread-22" pid 345

2013-11-08T10:39:01.027-05:00| vthread-23| I120: VTHREAD start thread 23 "vthread-23" pid 345

2013-11-08T10:39:01.027-05:00| vthread-24| I120: VTHREAD start thread 24 "vthread-24" pid 345

2013-11-08T10:39:01.027-05:00| vthread-25| I120: VTHREAD start thread 25 "vthread-25" pid 345

2013-11-08T10:39:01.027-05:00| vthread-26| I120: VTHREAD start thread 26 "vthread-26" pid 345

2013-11-08T10:39:01.027-05:00| vthread-27| I120: VTHREAD start thread 27 "vthread-27" pid 345

2013-11-08T10:39:01.028-05:00| vthread-28| I120: VTHREAD start thread 28 "vthread-28" pid 345

2013-11-08T10:39:01.028-05:00| vthread-29| I120: VTHREAD start thread 29 "vthread-29" pid 345

2013-11-08T10:39:01.028-05:00| vthread-30| I120: VTHREAD start thread 30 "vthread-30" pid 345

2013-11-08T10:39:01.028-05:00| vthread-31| I120: VTHREAD start thread 31 "vthread-31" pid 345

2013-11-08T10:45:54.074-05:00| vmx| I120: VMXVmdbEditRemDevices: Reconnect of ethernet0 would be delayed.

2013-11-08T10:45:54.074-05:00| vmx| I120: VMXVmdbSetCfgState: reconnect delay = 5 seconds, reconnectEthVector = 0x1, poll cb status = 0.

2013-11-08T10:45:54.074-05:00| vmx| I120: TOOLS received request in VMX to set option 'synctime' -> '1'

2013-11-08T10:45:54.108-05:00| vmx| I120: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#8/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#d7/in/

2013-11-08T10:45:59.081-05:00| vmx| I120: VNET: ethernet0 enable link state propagation, lsp.state = 5

2013-11-08T10:45:59.082-05:00| vmx| I120: VNET: MACVnetConnectToNetwork ethernet0 lsp.state = 5

2013-11-08T10:45:59.082-05:00| vmx| I120: VNET: MACVNetConnectToNetwork Ethernet0: notify available

2013-11-08T10:45:59.082-05:00| vmx| I120: EthernetDevicesDelayedConnect: Delayed connect of network adapter ethernet0 succeeded.

2013-11-08T10:45:59.082-05:00| vmx| I120: VNET: MACVNetLinkStateEventHandler: event, up:1, adapter:5

2013-11-08T10:51:55.876-05:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 2 rendering MKSWindow(s) of total 2.

2013-11-08T10:52:06.069-05:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2013-11-08T10:52:06.080-05:00| vmx| I120: TOOLS received request in VMX to set option 'synctime' -> '1'

2013-11-08T10:52:06.092-05:00| vmx| I120: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#9/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#245/in/

Above, I'm trying to use the WiFi adapter, but it fails in the Guest OS (background). If I try the Autodetect, it also fails. If I switch to "Share with my Mac", it succeeds, but I need bridged networking so I can reach the VM on the network.

Please advise

koi · ‎11-08-2013

Have you tried (successfully or not) with any other version of Fusion?

IIRC, some wireless access points just don't hand out multiple IP addresses to one adapter, so bridged mode won't work - you need to use wired networking, port forward, or pass through a USB wireless adapter to the guest.

Disclaimer: I'm out of date on recent Fusion releases, but suspect the above is still accurate.

trdickson · ‎11-09-2013

I'm going to throw in a "me too!"

Same symptoms, same hardware (Mac Mini - upgraded to Mavericks, running fusion 6.02 with a Windows 7 64bit host).

NAT works, but BRIDGE does not - and I need it to bridge!

davisford · ‎11-10-2013

FYI I filed a support request including a full VMWare debug log.

I've also discovered that bridge mode does work with the Ethernet adapter. I found a 30 ft. cable and was able to plug it into the Mac Mini, and I was able to run in bridged mode. It *may* be that the particular WiFi access point I'm trying to connect to disallows multiple DHCP requests from the same Mac address, as @koi suggested above. That's more difficult to diagnose since I don't have access to any of these access points.

trdickson · ‎11-10-2013

I can confirm that my AP DOES allow multiple IPs to a single MAC.

I'm running enterprise RUCKUS APs and a Ubiquiti EdgeRouter. I setup two bridges with WDS disabled to test the theory - and the clients work fine off those bridges (physical bridges - not vmware).

I'll have to try the ethernet adapter - is this Thunderbolt? or USB? that works...

I can use one of my physical bridges and push it through Ethernet for now - if it works.

Bummer is I was running Fusion 4 with no issues, but Mavericks killed that (settings panes etc would never show up) - so am running 6.0 trial to see if it fixed those issues (it did) - but now this one cropped up.

Parallels bridging works - but I'm having issues with USB mounting, so nothing is working great. Pains of an early adopter I guess.

koi · ‎11-10-2013

If Fusion 4 or Parallels on the exact same host in the exact same environment works, that's pretty good evidence something's wrong with Fusion 6. You should file a support request too.

In the meantime,Re: VMware Fusion 4 and Mavericks might work around your settings pane problems.

garryc1 · ‎01-09-2014

I also have the same issue, although any previously installed guests are still working with Bridged network. It is only new installations. Driving me nuts.

Same setup, OSX Mavericks 10.9.1 and Fusion 6.0.2. It was all working in Fusion v5.x but I thought I would upgrade to the latest for any new features. Really regretting that decision.

davisford · ‎01-09-2014

VMWare support did remote into my machine, and we isolated it down to the WiFi adapter. We ran a series of tests that seemed to really pinpoint the access point, and I was satisfied with the diagnosis. The access point I'm using is out of my control, but I'm convinced this particular issue that I was experiencing was a result of the AP limiting DHCP lease of IP address as one per mac address.

garryc1 · ‎01-10-2014

Well, I am embarrassed. Decided to debug dhcp requests on my router to see if the VM guest was even getting to that level and found the scope was exhausted. Add more addresses in and voila started working. Sorry to waste everyone's time, I should have looked there first.

All

VMWare Fusion 6.0.2 + Mavericks - Bridged Networking Broken