VirtualBox 5 NAT won't give address to guest

[chronologic]

This can easily be reproduced on an Ubuntu 14.04 host, and I think it fails on both 32 and 64 bit hosts. My current host is 64 bit, and the current image is 32 bit, not sure if that matters.

The following two images available via vagrant both exhibit the behavior: vagrant init box-cutter/ubuntu1404-i386; vagrant init sprachcaffe/php55-base;

This is the output of uname -a on my host: Linux silver 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Virtualbox 4.3.3 comes up just fine. But under Virtualbox 5 networking will fail to get an IP address. At least one image (maybe both) eventually boots without networking, after which you can do: dhclient -r eth0; dhclient -v -r eth0; and you can see that the DHCP request is never answered. With NAT enabled the virtual box system should be administering the IP address. Naturally my host networking environment is working find and never receives the DHCP request from the guest (it is not expected to).

I don't think it matters what networking hardware is on the host because I have duped it on more than one host. But anyway this is my host nic on the machine I'm using now: Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)

I have seen other reports of NAT failing to work with any version later than 4.3 but I can't find any clear answers as to why. I also tried NAT Network and that also didn't work. Other reports say that bridged networking works fine, but I did not try that as I prefer NAT and I have moved back to 4.3 to continue learning about vagrant.

The ticket seems to default to priority major which sounds about right to me if this problem is common. I'll leave it; I normally don't change defaults anyway.

[chronologic]

See: Ticket #13292 which may be a dupe ticket.

[Valery Ushakov]

Please, provide at least the VBox.log from the run that exhibits the problem.

Ideally, please provide a packet trace for the VM boot.

[Frank Mehnert]

No response, closing. Before you consider to reopen this ticket, please check VBox 5.0.4.

[Itsik_123]

The Log

[Itsik_123]

Same issue happens with Vbox 5.0.8 r 103449 attaching the log and the screenshot of ifconfig -a , netstat -rn

[Frank Mehnert]

I'm not convinced that this is a VirtualBox bug. Most likely you have a udev rule pending which is responsible for your guest nic screwup. Have a look at /etc/udev/rules.d and look for 70-persistent-net.rules (in your guest!). Delete this file and reboot your guest.

[Valery Ushakov]

Yes, please, make sure you have no stale udev rules in /etc/udev/rules.d/70-persistent-net.rules. The screenshot you posted has eth4 which is a strong indication you probably have stale rules for eth0 to eth3.

If you still have problems, please provide a packet trace as requested earlier.

Also, please, don't post screenshots of terminal output. Attach longer output as text files, or include shorted output directly using {{{ ... }}} markup.