Bug#838999: (no subject)
On Thu, 29 Sep 2016 23:33:31 +0200 Emmanuel Kasperwrote: 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) It works here too - thanks for the quick fix. I'm still on VirtualBox 5.0.26 and Vagrant 1.8.4 because of Vagrant bug #7610 (support for VirtualBox 5.1 was first added in Vagrant 1.8.5). Best regards, Laurențiu https://github.com/mitchellh/vagrant/issues/7610
Bug#838999: (no subject)
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) @lukasz: since you were the original bug reporter, feel free to close the bug if it works for you too
Bug#838999: (no subject)
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#838999: (no subject)
after reading the virtualbox forums especially https://forums.virtualbox.org/viewtopic.php?f=7=78840#p368748 it is clear that the problem is on the virtualbox side Virtualbox 5.1 exports cannot be direclty mported in 5.0
Bug#838999: (no subject)
Ł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 ?