You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: