splincodewd
@splincodewd
Developer

Почему vagrant не запускает установку?

a64c70bddd5d42258b2626b1eae8591c.png
The provider 'virtualbox' that was requested to back the machine
'virtualbox' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.


Искал решение проблемы, все равно не понял, что не так делаю!

В директории есть конфигурационный файл, который сделал при помощи puphpet, распаковал и сразу из этой же папки запустил vagrant up, но пишет фигню какую-то
c9c34a57ce21472b9017f550ebf0aeb6.png

Установлено:
ubuntu 16
virtual 5.0.18
vagrant 1.8.1

splincode@splincode:~/Domains/QyPKkS$  vagrant up --debug
 INFO global: Vagrant version: 1.8.1
 INFO global: Ruby version: 2.3.0
 INFO global: RubyGems version: 2.5.1
 INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
 INFO global: VAGRANT_LOG="debug"

..

 INFO loader: Set "16447940_machine_virtualbox" = ["[\"2\", #<Proc:0x00000001a2e828@(eval):14>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00000001a2e828@(eval):14>]
 INFO loader: Loading configuration in order: [:home, :root, "16447940_machine_virtualbox"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 16447940_machine_virtualbox (evaluating)
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG provisioner: Provisioner defined: 
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
 INFO host: Autodetecting host type for [#<Vagrant::Environment: /home/splincode/Domains/QyPKkS>]
DEBUG host: Trying: darwin
DEBUG host: Trying: gentoo
DEBUG host: Trying: slackware
DEBUG host: Trying: suse
DEBUG host: Trying: redhat
DEBUG host: Trying: freebsd
DEBUG host: Trying: arch
DEBUG host: Trying: null
DEBUG host: Trying: bsd
DEBUG host: Trying: linux
 INFO host: Detected: linux!
DEBUG host: Searching for cap: provider_install_virtualbox
DEBUG host: Checking in: linux
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: ["virtualbox"]
DEBUG command:  -- options: {:provider=>nil}
DEBUG command: Finding machine that match name: virtualbox
 INFO environment: Getting machine: virtualbox (virtualbox)
 INFO environment: Uncached load of machine.
 INFO base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
 INFO subprocess: Vagrant not running in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: WARNING: The character device /dev/vboxdrv does not exist.
	 Please install the virtualbox-dkms package and the appropriate
	 headers, most likely linux-headers-generic.

	 You will not be able to start VMs until this problem is fixed.
DEBUG subprocess: stdout: 5.0.18_Ubuntur106667
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
 INFO environment: Running hook: environment_unload
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00000002ea3240>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::ProviderNotUsable: The provider 'virtualbox' that was requested to back the machine
'virtualbox' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.>
ERROR vagrant: The provider 'virtualbox' that was requested to back the machine
'virtualbox' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.
ERROR vagrant: /usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:140:in `rescue in machine_config'
/usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:137:in `machine_config'
/usr/lib/ruby/vendor_ruby/vagrant/vagrantfile.rb:45:in `machine'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:629:in `machine'
/usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:177:in `block in with_target_vms'
/usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:201:in `block in with_target_vms'
/usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:183:in `each'
/usr/lib/ruby/vendor_ruby/vagrant/plugin/v2/command.rb:183:in `with_target_vms'
/usr/share/vagrant/plugins/commands/up/command.rb:89:in `block in execute'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:249:in `block (2 levels) in batch'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:247:in `tap'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:247:in `block in batch'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:246:in `synchronize'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:246:in `batch'
/usr/share/vagrant/plugins/commands/up/command.rb:88:in `execute'
/usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/vendor_ruby/vagrant/environment.rb:268:in `cli'
/usr/bin/vagrant:173:in `<main>'
 INFO interface: error: The provider 'virtualbox' that was requested to back the machine
'virtualbox' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.
The provider 'virtualbox' that was requested to back the machine
'virtualbox' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.
 INFO interface: Machine: error-exit ["Vagrant::Errors::ProviderNotUsable", "The provider 'virtualbox' that was requested to back the machine\n'virtualbox' is reporting that it isn't usable on this system. The\nreason is shown below:\n\nVirtualBox is complaining that the installation is incomplete. Please\nrun `VBoxManage --version` to see the error message which should contain\ninstructions on how to fix this error."]


splincode@splincode:~/Domains/test$ VBoxManage --version
WARNING: The character device /dev/vboxdrv does not exist.
	 Please install the virtualbox-dkms package and the appropriate
	 headers, most likely linux-headers-generic.

	 You will not be able to start VMs until this problem is fixed.
5.0.18_Ubuntur106667


После манипуляций:
sudo dpkg-reconfigure virtualbox-dkms
sudo dpkg-reconfigure virtualbox
# vboxweb.service is a disabled or a static unit, not starting it.
# Job for virtualbox.service failed because the control process exited with error code. See "systemctl status
#virtualbox.service" and "journalctl -xe" for details.
# invoke-rc.d: initscript virtualbox, action "restart" failed.
sudo modprobe vboxdrv 
# modprobe: ERROR: could not insert 'vboxdrv': Required key not available
sudo apt-get install linux-headers-generic
sudo dpkg-reconfigure virtualbox-dkms


8f5489a206c8458a8e673e7cdc0177b2.png
  • Вопрос задан
  • 1962 просмотра
Пригласить эксперта
Ответы на вопрос 2
alsopub
@alsopub
run `VBoxManage --version` to see the error message

Не увидел у вас результата этой команды, где должна быть показана ошибка.
Ответ написан
@generalzorgan
Разработка сайтов | Дизайн | Front-end | Back-end
  1. Отключил безопасный запуск UEFI через биос
  2. Запустил команду - sudo dpkg-reconfigure virtualbox-dkms
  3. Заработало!
Ответ написан
Комментировать
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы