[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#838936: marked as done (Vagrant + VirtualBox "Cable connected: off" + debian/jessie64 8.6.0)

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 + VirtualBox "Cable connected: off" + debian/jessie64 8.6.0
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
When installing "debian/jessie64" via Vagrant and using VirtualBox as a provider it seems that networking is not working (1). 

VM is created with "Cable connected: off" status and Vagrant fails to boot.

Steps to reproduce (make sure to use box version 8.6.0):
$ mkdir test
$ cd test
$ vagrant init debian/jessie64
$ vagrant up

Last working box version is 8.5.2.
I've tested other boxes: centos/7 and ubuntu/trusty64 and they are working properly. 

It is possible to workaround this issue by modifying Vagrantfile (2):

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

  config.vm.box = "debian/jessie64"

  # Bugfix for "Cable connected: off"
  config.vm.provider :virtualbox do |vm|
    vm.customize [
      "modifyvm", :id,
      "--cableconnected1", "on",
    ]
  end

end

and now VM boots properly.
I'm using Vagrant 1.8.5, VirtualBox 5.0.26 r108824 and OS X El Capitan 10.11.3.
I should mention that I'm finding it hard to reproduce this problem reliably on different computers (it either works in 100% out of the box and every time or the opposite - depending on the computer used). 

I've tested it on 4 computers and only on 2 of them problem is occurring.
(1) Big thanks to Stuart Spencer for finding the reason of this issue and Emmanuel Kasper for providing the help. 

(2) Source: http://stackoverflow.com/questions/20910716/#answer-20911136

--- 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: