-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
vfkit exited unexpectedly (invalid virtual machine configuration) #22226
Comments
@baude PTAL |
@cfergeau is this coming out of the hypervisor? im not seeing the error message in vfkit or otherwise? |
Yes, this would be coming out of Apple Virtualization Framework ( |
This can be reproduced with this |
I am also experiencing this issue. Here is what I think is the relevant debug text from CLI (I added newlines to help finding the
When can we expect #22288 to be merged and fixed in brew? |
I also need this fix. The only reason I use different machines is to separate code paths, so all of them are going to be longer than 36 characters... |
same error |
1 similar comment
same error |
same error here, my logs: arting machine "podman-machine-default"
Error: vfkit exited unexpectedly with exit code 1
Starting machine "podman-machine-default"25
Error: vfkit exited unexpectedly with exit code 1
Command execution failed with exit code 125 |
Issue Description
podman machine init fails with "vfkit exited unexpectedly with exit code 1"
Steps to reproduce the issue
Steps to reproduce the issue
podman machine init --cpus 6 -m 3072 -v $(pwd):$(pwd) --now
Based on the error below, I'm assuming this requires the working directory to be a long path (mine is
/Users/ahenning/Code/alechenninger.com/macro-server/ps4disasm
).Describe the results you received
podman machine init fails with "vfkit exited unexpectedly with exit code 1"
I tried to run gvproxy and vfkit directly using debug output as another contributor had done to see the error and work around the issue. It appears this may be related to the mount. When running vfkit directly, using the command from podman's debug output, I get:
The command I ran was:
Describe the results you expected
I expected the VM to start.
podman info output
I just downgraded podman to 4.9.4 so I don't have this. But I had just upgraded to 5, and am running macOS 14.4
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: