Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

cf dev start fails on windows 10 pro 64 bits: Error: failed to provision VM: Process exited with: 127. Reason was: () #256

Closed
javafreek opened this issue Aug 30, 2017 · 4 comments
Labels

Comments

@javafreek
Copy link

I'm trying to get CF-DEV to run on my local machine but it fails on the same spot:
image

I run MS Windows 10 Pro, 64 bits edition with an Intel Core i7-4720HQ and 16GB (DDR3) memory. Image files are stored on a RAID 0 drive (using 2 SSD drives). I'm connected to the internet without using a proxy on a wired connection (to prevent time-outs or slow connections)

What I've tried so far?

  • I've switched (removed) off: Hyper-V. (it was conflicting)
  • Removed native Docker support.
  • Ubuntu is still part of the install but I doubt it is causing the issue.
  • removed virtualBox and installed latest version. (to be sure)
  • downloaded CF tool and CF-dev again.
  • tried CMD and powershell
  • ran cf dev start with 8192MB memory (instead of 4GB it assigned itself)
  • tried running with no services: cf dev start -s none
  • Modified the vm NAT (shouldn't be a solution): VBoxManage modifyvm "pcfdev-v0.529.0" --natdnshostresolver1 on
  • removed all old VM, OVAs and retried the install from scratch again

and all resulted in the same error: Error: failed to provision VM: Process exited with: 127. Reason was: ()

What does work: I can start the image from virtualBox manager (GUI) but can't login on the console:
image
(admin/admin tried as I found in a different issue as a way to login?)
When dev is started in virtualBox Manager and stopped through the console (cf dev stop) It works as expected. If I try (and fail) to start the dev env from the console (cf dev start) and then try to stop it, I get a new error from VirtualBox:
image
and:
image
(instruction xxxxx is always pointing to memory on 0xFFFFFFFFFFFFFFFFFFFFFFFFFF.)

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@sclevine
Copy link
Contributor

Can you provide the full output of cf dev destroy followed by cf dev start?

Then run cf dev debug, make sure the resulting archive doesn't have an sensitive data in it, and send it to me at [email protected].

@nathan-alden-inl
Copy link

@javafreek, I think this is the same issue that I reported a few days ago. #255

@sclevine
Copy link
Contributor

I can confirm that this is the same issue. Even though you mention having a stable internet connect, the VM fails to resolve a Github domain during the provisioning stage:

curl: (6) Could not resolve host: raw.githubusercontent.com

This request shouldn't happen. We're going to cut a new release (0.28.0) that removes it.

Closing in favor of #255.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants