docs: Add instructions for VMware Player on Linux#39
docs: Add instructions for VMware Player on Linux#39sbrownjc wants to merge 2 commits intovmware:mainfrom
Conversation
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
|
👋 I still think that this comment is still very relevant. That said, @tenthirtyam do you have some thoughts on how we should be capture this. Is this something that you have documented within your vmware-samples repo? |
|
Hey, @nywilken - I don't have anything in that project that uses the I do use the Ryan Johnson |
|
I've added some comments to this PR for context, clarity, and correctness. Ryan Johnson |
docs/builders/index.mdx
Outdated
| Additionally you will need to have the `vmrun` command, which is part of the | ||
| VMware [Virtual Infrastructure eXtension][vix-api] [(VIX) SDK][vix-sdk]. | ||
|
|
||
| Finally, if you installed a version of VMware player newer than 7.0, you must |
There was a problem hiding this comment.
"VMware Workstation Player"
docs/builders/index.mdx
Outdated
| ## VMware (Workstation) Player on Linux | ||
|
|
||
| Unfortunately just installing VMware Player is not quite enough to be able to | ||
| use packer. You will also need the `qemu-img` command which is available in |
docs/builders/index.mdx
Outdated
|
|
||
| Unfortunately just installing VMware Player is not quite enough to be able to | ||
| use packer. You will also need the `qemu-img` command which is available in | ||
| the `qemu` package on Debian- and Fedora-like systems. |
There was a problem hiding this comment.
I would use "Red Hat Enterprise Linux and derivative" as well and "Debian and derivative".
docs/builders/index.mdx
Outdated
|
|
||
| ## VMware (Workstation) Player on Linux | ||
|
|
||
| Unfortunately just installing VMware Player is not quite enough to be able to |
There was a problem hiding this comment.
Remove "Unfortunately just..."
docs/builders/index.mdx
Outdated
|
|
||
| Finally, if you installed a version of VMware player newer than 7.0, you must | ||
| edit the file `/usr/lib/vmware-vix/vixwrapper-config.txt` and change the | ||
| version specified in the fourth column there to be the version in the third |
docs/builders/index.mdx
Outdated
| Finally, if you installed a version of VMware player newer than 7.0, you must | ||
| edit the file `/usr/lib/vmware-vix/vixwrapper-config.txt` and change the | ||
| version specified in the fourth column there to be the version in the third | ||
| column of the `vmplayer -v` command. See [this thread][so] for more details. |
There was a problem hiding this comment.
"this StackOverflow thread"
docs/builders/index.mdx
Outdated
| benefit, you can feed the artifact of this builder back into Packer to | ||
| iterate on a machine. | ||
|
|
||
| ## VMware (Workstation) Player on Linux |
There was a problem hiding this comment.
"VMware Workstation Player on Linux"
docs/builders/index.mdx
Outdated
|
|
||
| ## VMware (Workstation) Player on Linux | ||
|
|
||
| Unfortunately just installing VMware Player is not quite enough to be able to |
There was a problem hiding this comment.
"VMware Workstation Player"
docs/builders/index.mdx
Outdated
| Additionally you will need to have the `vmrun` command, which is part of the | ||
| VMware [Virtual Infrastructure eXtension][vix-api] [(VIX) SDK][vix-sdk]. | ||
|
|
||
| Finally, if you installed a version of VMware player newer than 7.0, you must |
There was a problem hiding this comment.
I would remove the versioning. Ideally the plugin should support only those versions supported by VMware per the lifecycle matrix. See project README.
|
@tenthirtyam Thanks for the review comments, I've updated the docs accordingly. |
|
Thanks! I'll review the updates tomorrow for Wilken and provide and update. Ryan Johnson |
tenthirtyam
left a comment
There was a problem hiding this comment.
LGTM! 🚀
cc @nywilken
|
@tenthirtyam thanks for the thoughts and review on this PR, and @sbrownjc thanks for updates. The changes look good me me. We just need to have you sign the CLA so that I can merge these changes in. If you have already accepted the CLA please make sure that the email used in your commits match the email you signed the CLA with and that the signing email is your primary GitHub email. The CLA bot only checks against the user's primary GitHub email. |
|
Hi @sbrownjc - could you resolve the issue with signing the HashiCorp CLA? This will help expedite your valuable updates. Ryan Johnson |
|
Hi @sbrownjc - could you resolve the issue with signing the HashiCorp CLA? This will help expedite your valuable updates. Ryan Johnson |
|
Hi @tenthirtyam, I'm sorry for the delay, I was waiting on a response from legal since I posted using my work GH account. If possible, I would like to submit this work outside of a CLA, following section 7 of the CLA:
This work is being Submitted on behalf of a third-party: Anand Kumria, the complete details of the source are in the original post. |
|
cc @nywilken for submission state review. |
|
@sbrownjc @tenthirtyam apologies for not getting back much sooner. In speaking with our legal team the author of the change must still sign the CLA in order to make the contribution on behalf of another contributor under section 7. Unfortunately that means I will not be able to merge in these changes unless the CLA is signed. I'm going to close this PR given the time I kept everyone waiting. If you wish to reopen with your personal GH and sign the CLA I would be glad to merge it right away. Thank you @tenthirtyam for your help here. |
In attempting to get packer working with VMWare Workstation Player on Linux, I had a lot of trouble until I found the information scattered about the internet, and then found this closed PR, whose instructions mirrored exactly what I'd done to get Workstation Player 16 running with Packer: hashicorp/packer#3451
This closed issue hashicorp/packer#1102 references this (lost?) commit: hashicorp/packer@c5ec92c which would have saved me much time if I could have seen it, so I'm making this PR to bring the information from hashicorp/packer#3451 in and up-to-date.