Bug#838999: (no subject)

[Łukasz Zaremba]

On 28/09/16 18:50, Emmanuel Kasper wrote:

Łukasz, I am under the impression that the bug comes from VirtualBox 5.1
from my build environment exporting its OVA under a format which is not
backwards compatible with 5.0

Can you check if updgrading to Virtualbox 5.1 allows you to use the
8.6.0 box without problems ?


Hello Emmanuel!
It works out of the box using VirtualBox 5.1! Thank you!!

I'm not sure why but I could swear that during the time I've stumbled 
onto this problem 5.0.26 was the last stable version (VirtualBox popups 
with updates from time to time).. Otherwise, I would proceed with 
upgrade right away..

Bug#838936: Vagrant + VirtualBox "Cable connected: off" + debian/jessie64 8.6.0

[Łukasz Zaremba]

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