Closed jinkunzhao closed 5 years ago
Hey there @jinkunzhao - From what I can tell in your debug log, it just looked like you interrupted the run while it was trying to boot the guest:
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO interface: warn: Waiting for cleanup before exiting...
INFO interface: warn: ==> gitlab: Waiting for cleanup before exiting...
==> gitlab: Waiting for cleanup before exiting...
ERROR warden: Error occurred: Vagrant exited after cleanup due to external interrupt.
INFO warden: Beginning recovery process...
Was there an actual error you received at all? Thanks!
Hey there @jinkunzhao - From what I can tell in your debug log, it just looked like you interrupted the run while it was trying to boot the guest:
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000 DEBUG subprocess: Exit status: 0 INFO interface: warn: Waiting for cleanup before exiting... INFO interface: warn: ==> gitlab: Waiting for cleanup before exiting... ==> gitlab: Waiting for cleanup before exiting... ERROR warden: Error occurred: Vagrant exited after cleanup due to external interrupt. INFO warden: Beginning recovery process...
Was there an actual error you received at all? Thanks!
@briancain I think the frist error is here : INFO subprocess: Starting process: ["C:\Windows\System32\WindowsPowerShell\v1.0/powershell.EXE", "-NoLogo", "-NoProfile", "-NonInteractive", "-ExecutionPolicy", "Bypass", "-Command", "Write-Output $PSVersionTable.PSVersion.Major"] INFO subprocess: Command not in installer, restoring original environment...
is that the powershell problem? i do not know how to do
Hi @jinkunzhao - That isn't an error.
When you run Vagrant without the debug, do you see an error message?
Hi @jinkunzhao - That isn't an error.
When you run Vagrant without the debug, do you see an error message?
@briancain - When i run vagrant,it hang up at "SSH auth method: password",a few minutes later,it display: $ vagrant up Bringing machine 'gitlab' up with 'virtualbox' provider... ==> gitlab: Importing base box 'centos7-template'... ==> gitlab: Matching MAC address for NAT networking... ==> gitlab: Setting the name of the VM: gitlab ==> gitlab: Clearing any previously set network interfaces... ==> gitlab: Preparing network interfaces based on configuration... gitlab: Adapter 1: nat gitlab: Adapter 2: hostonly gitlab: Adapter 3: bridged ==> gitlab: Forwarding ports... gitlab: 22 (guest) => 2222 (host) (adapter 1) ==> gitlab: Running 'pre-boot' VM customizations... ==> gitlab: Booting VM... ==> gitlab: Waiting for machine to boot. This may take a few minutes... gitlab: SSH address: 127.0.0.1:2222 gitlab: SSH username: vagrant gitlab: SSH auth method: password Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate with the guest machine within the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that Vagrant had when attempting to connect to the machine. These errors are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly working and you're able to connect to the machine. It is a common problem that networking isn't setup properly in these boxes. Verify that authentication configurations are also setup properly, as well.
If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.
and the error in virtualbox is : Kernel panic - not syncing: Fatal exception
Thanks for the image. Unfortunately, this is not a Vagrant bug. A couple of things you could into to try to resolve your issue:
Sorry we couldn't be more help!
- Hyper-V
@briancain - I have Hyper-V ,but i do not run it ,Will it have an impact?
@jinkunzhao - Disabling Hyper-V will only have an impact if you use it, or if you use Docker for Windows.
@briancain - i have disabled hyper-v,it have the same error ,but i can create virtual machine by virtualbox without vagrant.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Please note that the Vagrant issue tracker is in priority reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Tip: Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.
Vagrant version
2.2.6
Host operating system
windows10
Guest operating system
centos7
Vagrantfile
Please note, if you are using Homestead or a different Vagrantfile format, we may be unable to assist with your issue. Try to reproduce the issue using a vanilla Vagrantfile first.
Debug output
Expected behavior
What should have happened?
Actual behavior
kernel panic - not syncing: Fatal exception
Steps to reproduce
1.vagrant init 2.vagrant up
References
Are there any other GitHub issues (open or closed) that should be linked here? For example: