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

Support for choosing between standalone VMs versus linked clone VMs #12

Open
phillipross opened this issue May 25, 2021 · 0 comments
Open

Comments

@phillipross
Copy link

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

When building an image with the parallels-pvm builder, packer seems to create a VM with a snapshot named "vagrant_linked_clone" and the resulting artifact with a snapshot included. I'm not sure if the builder explicitly chooses to use a linked clone or if it's the default, but it would be helpful to have some kind of control over this via a builder option. Despite the advantages of linked clones, having a VM without snapshots would be more convenient in some cases.

Use Case(s)

When chaining together multiple parallels-pvm builders, having standalone VMs without snapshots rather than linked clones can be more convenient for creating transportable vagrant boxes.

Potential configuration

Maybe a new option in the builder config to provide control over snapshot/linked-clone options?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants