f2954a64c6
Prior to this commit, the hyper-v and virtualbox system crash check existed within the initialize function of the virtualbox provider. That caused an issue when running with other providers, because the virtualbox provider still gets initialized even if not used. This commit changes that by placing the check inside of one of the virtualbox provider actions that checks if virtualbox is installed and ready to use. This action is action is used by the main vbox provider actions, and should not be called when other providers are being used with Vagrant.
32 lines
1009 B
Ruby
32 lines
1009 B
Ruby
require 'vagrant/util/platform'
|
|
|
|
module VagrantPlugins
|
|
module ProviderVirtualBox
|
|
module Action
|
|
# Checks that VirtualBox is installed and ready to be used.
|
|
class CheckVirtualbox
|
|
def initialize(app, env)
|
|
@app = app
|
|
@logger = Log4r::Logger.new("vagrant::provider::virtualbox")
|
|
end
|
|
|
|
def call(env)
|
|
# This verifies that VirtualBox is installed and the driver is
|
|
# ready to function. If not, then an exception will be raised
|
|
# which will break us out of execution of the middleware sequence.
|
|
Driver::Meta.new.verify!
|
|
|
|
if Vagrant::Util::Platform.windows? && Vagrant::Util::Platform.windows_hyperv_enabled?
|
|
@logger.error("Virtualbox and Hyper-V cannot be used together at the same time on Windows and will result in a system crash.")
|
|
|
|
raise Vagrant::Errors::HypervVirtualBoxError
|
|
end
|
|
|
|
# Carry on.
|
|
@app.call(env)
|
|
end
|
|
end
|
|
end
|
|
end
|
|
end
|