failed to create the raw output file C:/Users/jason_06tt1g7/coding-public/newBox/ubuntu-bionic-18.04-cloudimg-console.log (VERR_PATH_NOT_FOUND)

Question

failed to create the raw output file C:/Users/jason_06tt1g7/coding-public/newBox/ubuntu-bionic-18.04-cloudimg-console.log (VERR_PATH_NOT_FOUND)

Closed this issue 4 years ago · 9 comments

Hello there,

I'm running Virtualbox 6.1.4 r136177 (Qt5.6.2) on Windows 10.

My Vagrantfile:

Vagrant.configure("2") do |config|

    config.vm.box = "reddingwebpro/cognacbox"
    config.vm.hostname = "cognacbox"
    config.vm.network "forwarded_port", guest: 80, host: 8080
    config.vm.network "private_network", ip: "192.168.33.10"
    config.vm.synced_folder ".", "/var/www", :mount_options => ["dmode=777", "fmode=777"]
    config.vm.provider "virtualbox" do |v|
        v.memory = 4096
        v.cpus = 4
    end
end

After running vagrant up I get the following result:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'reddingwebpro/cognacbox' version '2.0' is up to date...
==> 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: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 80 (guest) => 8080 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "62e7dda6-4adf-43a4-b721-0d8189daeea8", "--type", "headless"]

Stderr: VBoxManage.exe: error: RawFile#0 failed to create the raw output file C:/Users/jason_06tt1g7/coding-public/newBox/ubuntu-bionic-18.04-cloudimg-console.log (VERR_PATH_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

The machine is not starting. Is there a known solution?

I gues the path C:/Users/jason_06tt1g7/coding-public/newBox/ is causing the problem?

Answer 1 · 2020-03-26T18:30:58.000Z

Yes, looks like a bug in the build, I'll rebuild the vagrant file and post it shortly.

…

________________________________ From: Thomas Szteliga <notifications@github.com> Sent: Wednesday, March 25, 2020 1:38 PM To: reddingwebpro/cognacbox <cognacbox@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [reddingwebpro/cognacbox] failed to create the raw output file C:/Users/jason_06tt1g7/coding-public/newBox/ubuntu-bionic-18.04-cloudimg-console.log (VERR_PATH_NOT_FOUND) (#2) Hello there, I'm running Virtualbox 6.1.4 r136177 (Qt5.6.2) on Windows 10. My Vagrantfile: Vagrant.configure("2") do |config| config.vm.box = "reddingwebpro/cognacbox" config.vm.hostname = "cognacbox" config.vm.network "forwarded_port", guest: 80, host: 8080 config.vm.network "private_network", ip: "192.168.33.10" config.vm.synced_folder ".", "/var/www", :mount_options => ["dmode=777", "fmode=777"] config.vm.provider "virtualbox" do |v| v.memory = 4096 v.cpus = 4 end end After running vagrant up I get the following result: Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'reddingwebpro/cognacbox' version '2.0' is up to date... ==> 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: Adapter 2: hostonly ==> default: Forwarding ports... default: 80 (guest) => 8080 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> 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", "62e7dda6-4adf-43a4-b721-0d8189daeea8", "--type", "headless"] Stderr: VBoxManage.exe: error: RawFile#0 failed to create the raw output file C:/Users/jason_06tt1g7/coding-public/newBox/ubuntu-bionic-18.04-cloudimg-console.log (VERR_PATH_NOT_FOUND) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole The machine is not starting. Is there a known solution? I gues the path C:/Users/jason_06tt1g7/coding-public/newBox/ is causing the problem? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#2>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALGOEYPLJURAP5ZGOA7E24TRJJTTPANCNFSM4LTXTJPQ>.

Answer 2 · 2020-04-26T16:41:25.000Z

Any update? @reddingwebpro
Thank you.

Answer 3 · 2020-05-01T16:17:25.000Z

I second this issue ( i have the same issue).

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "03f83b91-97db-4680-b1f4-9332d61cecc2", "--type", "headless"]

Stderr: VBoxManage: error: RawFile#0 failed to create the raw output file C:/Users/jason_06tt1g7/coding-public/newBox/ubuntu-bionic-18.04-cloudimg-console.log (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Thank you for updating this; i await its release. :)

Answer 4 · 2020-05-11T04:11:15.000Z

same question

Answer 5 · 2020-06-11T19:01:11.000Z

same error here

Answer 6 · 2020-06-11T20:39:28.000Z

for the others maybe this helps: #3 (comment)

Answer 7 · 2020-06-11T23:46:01.000Z

Testing a fix for this now. Hoping to release it tomorrow.

Answer 8 · 2020-06-12T17:35:20.000Z

Source of the problems seems to be related to hashicorp/vagrant#10578 -- implementing a patch in the code, and should be available shortly.

Answer 9 · 2020-06-12T18:26:55.000Z

Fixed in v2.2 -- updated master.