-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While reload --provisioning I get an error #1685
Comments
This is a hard virtual box error. Does destroy and then up successfully complete?
…--
- Joe Ferguson
JoeFerguson.me
osmihelp.org
On Aug 25, 2021, 06:49 -0500, timruis ***@***.***>, wrote:
Please note that the Homestead issue tracker is reserved for bug reports and enhancements. We are not always able to debug Vagrant, Provider or Operating System issues, but will do our best to help. Thank you!
Versions
• Vagrant: Run vagrant -v to show the version.
• Provider: Virtualbox, VMWare, Hyper-V, or Parallels and its version.
• Homestead: You should be on the most recent release branch.
A lot of issues can be resolved by simply updating vagrant, provider or homestead.
> Note: Virtualbox users, please upgrade to 6.x. You'll need to download a newer version of Virtualbox.
Host operating system
This is the operating system that you run locally.
Homestead.yaml
# Copy-paste your Homestead.yaml here
Vagrant destroy & up output
Provide a link to a GitHub Gist containing the complete output of vagrant destroy && vagrant up.
Do NOT paste the debug output in the issue, just paste the link to the Gist.
Expected behavior
Restarting the Homestead vm with other YAML properties.
Actual behavior
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "9766dd64-1845-433c-bbb8-6a188b867fa9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession
Steps to reproduce
1. Using windows type "vagrant reload --provision"
2. wait until error (i dont know what i do else but i include my yaml file)
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
- ~/.ssh/id_rsa
folders:
- map: C:\Projects
to: /home/vagrant/code
php: "7.2"
sites:
- map: homestead.test
to: /home/vagrant/code/laravel/public
databases:
- homestead
features:
- mysql: true
- mariadb: false
- postgresql: false
- ohmyzsh: false
- webdriver: false
#services:
- enabled:
- ***@***.***"
- disabled:
- ***@***.***"
#ports:
- send: 3306 # MySQL/MariaDB
to: 33060
- send: 4040
to: 4040
- send: 5432 # PostgreSQL
to: 54320
- send: 8025 # Mailhog
to: 8025
- send: 9600
to: 9600
- send: 27017
to: 27017
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
• GH-1234
• ...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I figured out if you use Remove homestead folder in the location. |
Reload --provision tells the VM to reboot then run provision. Sometimes
it's what you want. Sometimes it's not. Glad you got it sorted out.
…On Wed, Aug 25, 2021 at 8:16 AM timruis ***@***.***> wrote:
I figured out if you use "vagrant provision" it works.
Maybe reload is an older command.
hope people with the same struggle find this.
So first try vagrant reload --provision if it doesn't work, destroy your
vagrant box.
and when you do up and it won't work anymore go to task manager turn off
all virtualbox apps.
Go to C:\users**username**\VirtualBox VMs
Remove homestead folder.
Go again to your command line type up.
and use from now on "vagrant provision"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1685 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHMFQVVSTSBMT3HZZHSQILT6TUKLANCNFSM5CY4LT5A>
.
--
- Joe Ferguson
JoeFerguson.me
osmihelp.org
|
Please note that the Homestead issue tracker is reserved for bug reports and enhancements. We are not always able to debug Vagrant, Provider or Operating System issues, but will do our best to help. Thank you!
Versions
vagrant -v
to show the version.release
branch.A lot of issues can be resolved by simply updating vagrant, provider or homestead.
Host operating system
This is my windows 10 development laptop
Homestead.yaml
Vagrant destroy & up output
Provide a link to a GitHub Gist containing the complete output of
vagrant destroy && vagrant up
.Do NOT paste the debug output in the issue, just paste the link to the Gist.
Expected behavior
Restarting the Homestead vm with other YAML properties.
Actual behavior
There was an error while executing
VBoxManage
, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "9766dd64-1845-433c-bbb8-6a188b867fa9", "--type", "headless"]
Stderr: VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession
Steps to reproduce
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
The text was updated successfully, but these errors were encountered: