Adding support for --parallel into VirtualBox provider

323 views
Skip to first unread message

Tero Saarni

unread,
Nov 16, 2014, 3:14:17 AM11/16/14
to vagra...@googlegroups.com
I'm studying what capabilities are missing from VirtualBox provider to make `vagrant up --parallel` work.  Just as a simple test, adding `parallel: true` into virtualbox/plugin.rb kind of works on Linux.  

I assume there must be many changes that are needed beyond that.  Can someone give an overview what are the missing parts to enable --parallel support for VirtualBox provider?

-- 
Tero

Umair Chagani

unread,
Nov 16, 2014, 12:34:00 PM11/16/14
to vagra...@googlegroups.com

I think the quickest test for this is to open up two terminal sessions and vagrant up both of them. I remember reading a guy trying this and VB throwing up.

VirtualBox also has a huge problem with user sessions which needs to be solved.

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tero Saarni

unread,
Nov 17, 2014, 10:43:52 PM11/17/14
to vagra...@googlegroups.com, umair....@gmail.com
On Sunday, November 16, 2014 7:34:00 PM UTC+2, Umair Chagani wrote:

I think the quickest test for this is to open up two terminal sessions and vagrant up both of them. I remember reading a guy trying this and VB throwing up.

VirtualBox also has a huge problem with user sessions which needs to be solved.

 
I already tested this before just by adding 'parallel: true' into the provider function call in virtualbox/plugin.rb file in Vagrant code.  That seemed to activate parallel support and I have not seen any big problems, besides progress printouts being a bit misleading when starting two VMs at once.  But since VirtualBox provider is not registered with 'parallel: true' by default I assume I'm not seeing the whole picture.  

I wonder if anyone got more insight into this?

-- 
Tero

Simon Gooch

unread,
Mar 26, 2019, 5:18:20 AM3/26/19
to Vagrant
Hi,

Has there been any progress on this, as I'm also interested in getting this to work.

Many thanks

Jeff Welling

unread,
Oct 18, 2019, 6:16:17 PM10/18/19
to Vagrant
I think this is worth revisiting.

I used to be able to reproduce this problem a number of years and several versions of VirtualBox ago, but with Vagrant 2.2.4 and Version 6.0.12 r133076, and monkeypatching a "parallel: true"
into this line https://github.com/hashicorp/vagrant/blob/master/plugins/providers/virtualbox/plugin.rb#L12 and the following Vagrantfile with repeated test over the course of an hour on Mac OS 10.15, I'm no longer able to reproduce the session problems with VirtualBox.

Vagrant.configure("2") do |config|
 
(1..10).each do |i|
    config
.vm.provider "virtualbox" do |v|
      v
.linked_clone = true
   
end
    config
.vm.define "test-#{i}" do |node|
      node
.vm.box = "debian/jessie64"
   
end
 
end
end

Is anyone able to reproduce the session problem? Because if not, I would argue it's time to update the provider :D
I'm not aware of the problem being OS specific, but I do recall that my previous tests were run when Debian or Ubuntu were my desktop of choice.

Thank you to everyone who's work continues to make Vagrant an awesome tool to use!
Jeff.
Reply all
Reply to author
Forward
0 new messages