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

Provide a start VM button after successful disk image build #574

Closed
odockal opened this issue Jun 25, 2024 · 3 comments
Closed

Provide a start VM button after successful disk image build #574

odockal opened this issue Jun 25, 2024 · 3 comments
Assignees
Labels
kind/feature 💡 Issue for requesting a new feature
Milestone

Comments

@odockal
Copy link
Contributor

odockal commented Jun 25, 2024

Is your feature request related to a problem? Please describe

It would be very nice to provide user with a start VM button that would enable the user to spin up the VM from fresh disk image that was just built via the extension.

Describe the solution you'd like

Depending on the os/platform and the vm provider available, we could introduce new button that would lead to a form that would offer to start a VM based on previous step, which was image disk building (image type, etc).

I would have to detect possible vm provider or let user to pick it up or install it.

Describe alternatives you've considered

No response

Additional context

No response

@odockal odockal added the kind/feature 💡 Issue for requesting a new feature label Jun 25, 2024
@cfergeau
Copy link

https://github.com/containers/podman-bootc can be used for this.

@cdrage
Copy link
Contributor

cdrage commented Jun 26, 2024

Would love that and we actually had this feature early on in development with vfkit / qemu, but unfortunatley there are too many edge cases where people have issues with windows / linux / mac, particularly with qemu.

There are actually two issues in here..

Testing BEFORE a built image:

I would like an integration with https://github.com/containers/podman-bootc in the future like @cfergeau said, but one thing that is very common, is building AMD64 images on mac m1, and then be able to run it. With that, we would need: containers/podman-bootc#27

This would not be very viable as we would have to build it anyways (see the last comment), using bib. Which is what we do in this extension anyways..

Testing AFTER a built image:

Honestly unsure at the moment, we have this documentation: https://github.com/containers/podman-desktop-extension-bootc/blob/main/docs/vm_guide.md

However, there are so many issues with regards to everyone's particular OS, it's easier to say: "Here's the .raw file, figure it out".

We integrate one solution (launching with qemu), but it'll suddenly not work for someone with a different arch (intel vs silicon on mac), or maybe a particular version of qemu got patched incorrectly (happened alot...).

I would like a more eloquent solution and I am open for suggestions!

@cdrage
Copy link
Contributor

cdrage commented Nov 20, 2024

We now have two places for this button now that #865 is in.

The buttons are there, and the next part is support for Windows and Linux VM running: #879 and #878

Image

Image

Marking this as closed as we will be tracking this development in other issues.

@cdrage cdrage closed this as completed Nov 20, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✔️ Done in Podman Desktop Planning Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature 💡 Issue for requesting a new feature
Projects
None yet
Development

No branches or pull requests

4 participants