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
Issues with latest versions of vQFX (18.x) #221
Comments
Hi I'm having similar problems with vqfx as well. Quick hack is to simply set the version in the makefile: VERSION=19.4R1.10 It also uses vmdk images and converts them to qcow2 during startup, which is a bit silly when there is qcow images of vqfx available. |
Hi I have a branch that works with vqfx 19.4 over here: Will make pull request |
@htj I tried using your branch with vqfx 19.4 code and getting the following error. Can you please let me know whats missing here.
|
Yeah, it is missing healthcheck.py, which should have been copied from ../common into docker/ Either try and copy it in manually, or add:
to the docker-build-common target in the makefile. If it works, I'll patch it. |
Thanks @htj !! |
Thanks for the feedback. Glad that it works. I've updated the branch and pull request. @plajjan Any chance of a merge? |
I cannot make vQFX
18.x
version work with the existing code.Issues:
qcow / qcow2
. Looks like Juniper is moving away fromvmdk
qcow / qcow2
images converted tovmdk
as well. Result: booting is stuck as below:That is running on a
n1-standard-4
GCP instance on top of docker with nested virtualization enabled. It's not even remotely consuming the available instance resources.The text was updated successfully, but these errors were encountered: