LoginSignup
2
1

More than 3 years have passed since last update.

vagrant up 時にCommand: ["startvm", "XXXXXXX”, "--type", "headless"]エラーが出たときに対処方法

Last updated at Posted at 2019-09-09

概要

先日自宅のPCのboxをpackage importしてvagrant upした際に下記のエラーが出たので、その対処方法を記録しておきます。
※注意:これは一時対処です。原因がわかっていないので、根本的な解決策でない可能性があります。
他の対処方法をご存じでしたら、コメントいただければ幸いです。

作業環境

  • Windows10 1903
  • Vagrant 2.2.5
  • VirtualBox 6.0.8

エラー内容

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "a12690a5-aec0-4dca-b9ef-53d69c872d92", "--type", "headless"]

Stderr: VBoxManage.exe: error: RawFile#0 failed to create the raw output file C:\WORK\GitHub\Vagrant\ubuntu\ubuntu-bionic-18.04-cloudimg-console.log (VERR_PATH_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

対処方法

vagrantfileに下記の情報を追記する

config.vm.provider "virtualbox" do |vb|
  vb.customize [ "modifyvm", :id, "--uartmode1", "disconnected" ]
end

参考リンク

GitHub:Vagrant up (1.9.5) not running on WSL

2
1
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
2
1