Skip to content
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

Add documentation for qemu uri on kvm2 driver #4635

Closed
medyagh opened this issue Jun 28, 2019 · 6 comments
Closed

Add documentation for qemu uri on kvm2 driver #4635

medyagh opened this issue Jun 28, 2019 · 6 comments
Labels
co/kvm2-driver KVM2 driver related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@medyagh
Copy link
Member

medyagh commented Jun 28, 2019

it would be nice to have a doc, showing minikube running with qemu uri.

would be even better to have an example showing it working on the cloud.
Related: 9dfe660

@medyagh medyagh added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. labels Jun 28, 2019
@josedonizetti
Copy link
Member

You can assign it to me. I'll create a simple tutorial running minikube on GCE with the remote qemu uri.

@medyagh
Copy link
Member Author

medyagh commented Jun 28, 2019

Wonderful, thank you so much !

@afbjorklund
Copy link
Collaborator

Cloud ? I don't think we support running in the cloud, it was more for weird local setups...

@josedonizetti
Copy link
Member

Yeah, it seems cloud isn't supported. The --kvm-qemu-uri works fine for connecting, but unfortunately some dependencies are only available locally, so it fails to create the KVM machine, for example:

https://github.com/kubernetes/minikube/blob/master/pkg/drivers/kvm/domain.go#L56
https://github.com/kubernetes/minikube/blob/master/pkg/drivers/kvm/domain.go#L62

When the XML template is sent to the qemu remote instance those files have the local paths, and doesn't exist in the remote.

@josedonizetti
Copy link
Member

@medyagh any thoughts on this? Is this something we want to make possible?

@tstromberg tstromberg added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Jul 16, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 14, 2019
@sharifelgamal sharifelgamal added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 30, 2019
@afbjorklund afbjorklund added the co/kvm2-driver KVM2 driver related issues label Jan 12, 2020
@josedonizetti josedonizetti removed their assignment Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/kvm2-driver KVM2 driver related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

7 participants