Bug#838999: marked as done (Vagrant box inaccessible due to missing network cable (VirtualBox))
Your message dated Fri, 30 Sep 2016 18:13:02 +0200
with message-id <19688aea-7545-1a2b-fc84-5a092d0a7528@gmail.com>
and subject line Re: Bug#838999: (no subject)
has caused the Debian Bug report #838999,
regarding Vagrant box inaccessible due to missing network cable (VirtualBox)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
838999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838999
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cloud.debian.org
Severity: normal
Dear Debian Cloud Maintainers,
Version 8.6.0 of debian/jessie64 from Atlas produces a timeout when
creating a new box with "vagrant up", and it remains inaccessible to
Vagrant since eth0 doesn't receive a DHCP address. This is apparently
caused by the first network adapter (eth0) being disconnected in the
VirtualBox configuration. This is a regression from 8.5.2 (I didn't
test debian/wheezy64 or other Debian images).
Inserting the following line in my own Vagrantfile fixes the problem:
v.customize ["modifyvm", :id, "--cableconnected1", "on"]
Regards,
Laurențiu Păncescu
--- End Message ---
--- Begin Message ---
On 29/09/16 23:33, Emmanuel Kasper wrote:
I've pushed a new box with version 8.6.1 who should fix the bug ( I
tested it in a Virtualbox 5.0.* env and the network works properly)
Closing this bug.
Thank you Emmanuel, Stuart and Laurențiu for all of your help!
Now debian/jessie64 box is even running all the way back to VirtualBox
4.3.10 r101610 :-)
--- End Message ---
Reply to: