for fedora, before export/save the box 1. rm /etc/udev/rules.d/70-persistent-net.rules 2. chkconfig NetworkManager off 3. edit /etc/sysconfig/network-scripts/ifcfg-eth*
you can leave only ifcfg-eth0 and delete all the others, as Vagrant will recreate them remove UUID remove HWADDR ensure NM_CONTROLLED=no is in the file. and let me know how it goes. Alvaro. On Fri, Feb 14, 2014 at 11:23 AM, Peter Halliday <pghalli...@gmail.com>wrote: > I'm getting this too with a fedora 17 64bit live box that i built from > scratch and started with the gui turned on. Seems the networking isn't > working as expected. I manually switched to host only network and rebooted > then switched back to NAT (with 2222 port forwarding) and now it works. But > if I destroy the VM and start it again it stops working again. Still > confused :s > > On Friday, 2 August 2013 01:29:48 UTC+2, Stephen Figgins wrote: >> >> Not sure where to look yet, but the same thing just happened to me. I >> still have the virtual box vm I exported to created my vagrant box. It >> comes up okay. I just can't get to the vagrant box. >> >> >> >> >> -- > 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 vagrant-up+unsubscr...@googlegroups.com. > 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 vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
