Al instalar Virtualbox a través de brew cask install virtualbox, obtengo el siguiente error:
==> Satisfying dependencies
==> Downloading http://download.virtualbox.org/virtualbox/5.1.28/VirtualBox-5.1.28-117968-OSX.dmg
Already downloaded: /Users/romanderlemenko/Library/Caches/Homebrew/Cask/virtualbox--5.1.28-117968.dmg
==> Verifying checksum for Cask virtualbox
==> Installing Cask virtualbox
==> Running installer for virtualbox; your password may be necessary.
==> Package installers may write to any location; options such as --appdir are ignored.
Password:
==> installer: Package name is Oracle VM VirtualBox
==> installer: Installing at base path /
==> installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
Error: Command failed to execute!
==> Failed command:
/usr/bin/sudo -E -- /usr/sbin/installer -pkg /usr/local/Caskroom/virtualbox/5.1.28-117968/VirtualBox.pkg -target /
==> Standard Output of failed command:
installer: Package name is Oracle VM VirtualBox
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
==> Standard Error of failed command:
==> Exit status of failed command:
#<Process::Status: pid 3578 exit 1>
Al instalarlo a través del .dmgpaquete, el instalador solo dice que la instalación falló
En ambas situaciones acabo teniendo Virtualbox instalado. Pero cuando comienzo mi caja Vagrant usando vagrant upesto es lo que obtengo:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "dda26a7b-cc0e-440c-b0db-9b3d3bac5925", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'rooxie-vm' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
¿Puede esto deberse al nuevo sistema de archivos de High Sierra?
