We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the solution you'd like: Test with the latest version of Cloud Hypervisor.
Why do you want this feature:
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
The text was updated successfully, but these errors were encountered:
Testing with Cloud Hypervisor v41.0 and was able to create a vm doing the following:
Started Flintlock (on main) using these args:
flintlockd run --cloudhypervisor-bin /home/richard/.local/bin/cloud-hypervisor-static \ --default-provider cloudhypervisor \ --bridge-name virbr1 \ --insecure \ --containerd-socket /run/containerd-flintlock/containerd.sock"
And then created a vm using fl (from main):
fl microvm create --name test1 \ --host localhost:9090 \ --network-interface eth1:tap \ --kernel-image ghcr.io/liquidmetal-dev/cloudhypervisor-kernel:6.2 \ --kernel-filename boot/vmlinux.bin \ --root-image ghcr.io/liquidmetal-dev/ubuntu-ch:22.04 \ --metadata-ssh-key-file /home/richard/.ssh/id_rsa_personal_yubikey.pub \ --metadata-hostname node1
Sorry, something went wrong.
richardcase
Successfully merging a pull request may close this issue.
Describe the solution you'd like:
Test with the latest version of Cloud Hypervisor.
Why do you want this feature:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The text was updated successfully, but these errors were encountered: