This didn't work for me, but when I explicitly open VMWare Fusion, quit, and then vagrant up again, the "'vmnet1' can't be started because its routes collide" problem goes away.
On Thursday, April 18, 2013 5:29:16 PM UTC-4, Mitchell Hashimoto wrote: > > Curtis, > > Yep, vmnet1 and vmnet13 definitely do collide. Do you have Fusion pro or > Fusion regular? If you have Fusion pro, please open the network editor and > remove all the networks to start over. If you have Fusion regular, you'll > need to edit some files... > > Get rid of all the lines in that file _except_ the ones that start with > "answer VNET_1_" or "answer VNET_8_". We want to keep those, as they're the > default networks that ship with Fusion. After that, open VMware Fusion.app, > then run these commands in a separate terminal: > > sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop > sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli > --configure > sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start > > Then run > > sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --status > > And tell me the output. Should only have the vmnet1/vmnet8 devices. After > THAT you shoudl be good to go again. > > VMware networking is an absolute nightmare. > > Best, > Mitchell > > > On Thu, Apr 18, 2013 at 2:25 PM, Curtis <[email protected] <javascript:> > > wrote: > >> On Thu, Apr 18, 2013 at 3:23 PM, Mitchell Hashimoto < >> [email protected] <javascript:>> wrote: >> >>> Curtis, >>> >>> Hm, it might be easy to just clear out all the existing vmnet devices >>> and start over. Maybe I should add a hidden command to do that. >>> >>> Anyways, can you get me the file contents of >>> "/Library/Preferences/VMware\ Fusion/networking" >>> >> >> Here you go: >> >> $ cat /Library/Preferences/VMware\ Fusion/networking >> VERSION=1,0 >> answer VNET_10_DHCP yes >> answer VNET_10_DHCP_CFG_HASH 1A21E888A905E39B922CB6D92FA4E8AFD6DAA26B >> answer VNET_10_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_10_HOSTONLY_SUBNET 192.0.0.0 >> answer VNET_10_VIRTUAL_ADAPTER yes >> answer VNET_11_DHCP yes >> answer VNET_11_DHCP_CFG_HASH 68A99E8C498C8197835EB78E015DC1DD3CB9BC50 >> answer VNET_11_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_11_HOSTONLY_SUBNET 10.20.0.0 >> answer VNET_11_VIRTUAL_ADAPTER yes >> answer VNET_12_DHCP yes >> answer VNET_12_DHCP_CFG_HASH 7FABD62FCA75FD73362CECFA74AD902376B068CC >> answer VNET_12_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_12_HOSTONLY_SUBNET 10.200.0.0 >> answer VNET_12_VIRTUAL_ADAPTER yes >> answer VNET_13_DHCP yes >> answer VNET_13_DHCP_CFG_HASH 5F0E2E7BDCF8E15408E0E84217CC047AE57903ED >> answer VNET_13_HOSTONLY_NETMASK 255.255.0.0 >> answer VNET_13_HOSTONLY_SUBNET 172.16.0.0 >> answer VNET_13_VIRTUAL_ADAPTER yes >> answer VNET_1_DHCP yes >> answer VNET_1_DHCP_CFG_HASH 2DDDBBAE34AC633BB00FE0ED303D12A5F6CE2B9B >> answer VNET_1_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_1_HOSTONLY_SUBNET 172.16.93.0 >> answer VNET_1_VIRTUAL_ADAPTER yes >> answer VNET_2_DHCP yes >> answer VNET_2_DHCP_CFG_HASH 02906B6214A172DBC3CA0225D1F2EBAD5EB98E4E >> answer VNET_2_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_2_HOSTONLY_SUBNET 192.168.33.0 >> answer VNET_2_VIRTUAL_ADAPTER yes >> answer VNET_3_DHCP yes >> answer VNET_3_DHCP_CFG_HASH ECA49BB5A25F4677584FDFC0A0110DF6B22442EB >> answer VNET_3_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_3_HOSTONLY_SUBNET 192.168.135.0 >> answer VNET_3_VIRTUAL_ADAPTER yes >> answer VNET_4_DHCP yes >> answer VNET_4_DHCP_CFG_HASH 6B729EFB930C7422BC5748334917444B65225F79 >> answer VNET_4_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_4_HOSTONLY_SUBNET 192.168.206.0 >> answer VNET_4_VIRTUAL_ADAPTER yes >> answer VNET_5_DHCP yes >> answer VNET_5_DHCP_CFG_HASH A6F051BDBEAA8D86F02F93B34D46C97D1CF2EB1B >> answer VNET_5_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_5_HOSTONLY_SUBNET 10.0.5.0 >> answer VNET_5_VIRTUAL_ADAPTER yes >> answer VNET_6_DHCP yes >> answer VNET_6_DHCP_CFG_HASH BF60F3D7FDBB3D3FC4D26317D8E7E18C625939DB >> answer VNET_6_HOSTONLY_NETMASK 255.255.0.0 >> answer VNET_6_HOSTONLY_SUBNET 172.10.0.0 >> answer VNET_6_VIRTUAL_ADAPTER yes >> answer VNET_7_DHCP yes >> answer VNET_7_DHCP_CFG_HASH C547F9624FAF1EE63FEF9C2BE3C6767919EB5CF2 >> answer VNET_7_HOSTONLY_NETMASK 255.255.0.0 >> answer VNET_7_HOSTONLY_SUBNET 10.10.0.0 >> answer VNET_7_VIRTUAL_ADAPTER yes >> answer VNET_8_DHCP yes >> answer VNET_8_DHCP_CFG_HASH D2C805562AA7834E92A09AC99FFDD5F5C2A6BB4A >> answer VNET_8_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_8_HOSTONLY_SUBNET 192.168.134.0 >> answer VNET_8_NAT yes >> answer VNET_8_VIRTUAL_ADAPTER yes >> answer VNET_9_DHCP yes >> answer VNET_9_DHCP_CFG_HASH 0267A54D69B8F9DFFA0D75861E6B18099074274A >> answer VNET_9_HOSTONLY_NETMASK 255.255.255.0 >> answer VNET_9_HOSTONLY_SUBNET 10.0.0.0 >> answer VNET_9_VIRTUAL_ADAPTER yes >> >> == >> >> Thanks, >> Curtis. >> >> >>> >>> Best, >>> Mitchell >>> >>> >>> On Thu, Apr 18, 2013 at 1:47 PM, Curtis <[email protected]<javascript:> >>> > wrote: >>> >>>> How about this? It's not a virtualbox device now... >>>> >>>> $ vagrant up --provider=vmware_fusion >>>> Bringing machine 'percona0' up with 'vmware_fusion' provider... >>>> Bringing machine 'percona1' up with 'vmware_fusion' provider... >>>> Bringing machine 'percona2' up with 'vmware_fusion' provider... >>>> Bringing machine 'haproxy0' up with 'vmware_fusion' provider... >>>> Bringing machine 'haproxy1' up with 'vmware_fusion' provider... >>>> [percona0] Cloning Fusion VM: 'precise64'. This can take some time... >>>> [percona0] Verifying vmnet devices are healthy... >>>> The VMware network device 'vmnet1' can't be started because >>>> its routes collide with another device: 'vmnet13'. Please >>>> either fix the settings of the VMware network device or stop the >>>> colliding device. Your machine can't be started while VMware >>>> networking is broken. >>>> >>>> == >>>> >>>> And this was right after a reboot... >>>> >>>> Thanks, >>>> Curtis. >>>> >>>> >>>> On Tue, Apr 9, 2013 at 3:26 PM, Mitchell Hashimoto < >>>> [email protected] <javascript:>> wrote: >>>> >>>>> Curtis, >>>>> >>>>> I'm sorry! But please don't blame the provider, the issue is that the >>>>> two hypervisors don't play nice together with their networking. It is a >>>>> standard issue that would happen with any sort of combination of >>>>> hypervisors. You must use distinct network interfaces otherwise they >>>>> can't >>>>> route to their own VMs. :) >>>>> >>>>> >>>>> >>>>> On Tue, Apr 9, 2013 at 2:24 PM, Curtis <[email protected]<javascript:> >>>>> > wrote: >>>>> >>>>>> On Tue, Apr 9, 2013 at 7:29 AM, Trevor Roberts >>>>>> <[email protected]<javascript:> >>>>>> > wrote: >>>>>> >>>>>>> I tried changing the Subnets that my existing vmnets were using, and >>>>>>> that worked for me... >>>>>>> >>>>>> >>>>>> Hmm, Ok, I had changed the subnet in the vagrant file I was using >>>>>> with vmware_fusion. >>>>>> >>>>>> vmware_fusion is not working out like I'd hoped... >>>>>> >>>>>> Thanks, >>>>>> Curtis >>>>>> >>>>>> >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Vagrant" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected] <javascript:>. >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Twitter: @serverascode >>>>>> Blog: serverascode.com >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Vagrant" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected] <javascript:>. >>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Vagrant" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected] <javascript:>. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Twitter: @serverascode >>>> Blog: serverascode.com >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Vagrant" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected] <javascript:>. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> Twitter: @serverascode >> Blog: serverascode.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
