-
Notifications
You must be signed in to change notification settings - Fork 972
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
Adjust ova to support VMware ESXi (#826) #1674
Merged
agners
merged 3 commits into
home-assistant:dev
from
agners:use-openssl-to-generate-ova-manifest-file
Dec 15, 2021
Merged
Adjust ova to support VMware ESXi (#826) #1674
agners
merged 3 commits into
home-assistant:dev
from
agners:use-openssl-to-generate-ova-manifest-file
Dec 15, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It seems that sha256sum adds a space after the hash algorithm which causes "Invalid OVF checksum algorithm" on certain VMware virtualization products. Using OpenSSL avoids the space and makes the manifest file compatible wiht VMware products.
jens-maus
added a commit
to jens-maus/RaspberryMatic
that referenced
this pull request
Dec 14, 2021
manifest file for the ova so that we are compatible to other VMware products which cannot deal with spaces after the hash algorithm obviously. (This refs home-assistant/operating-system#1674)
jens-maus
reviewed
Dec 14, 2021
agners
changed the title
Use OpenSSL to generate OVA manifest file (#826)
Adjust ova to support VMware ESXi (#826)
Dec 14, 2021
pvizeli
approved these changes
Dec 15, 2021
agners
added a commit
that referenced
this pull request
Dec 29, 2021
* Use OpenSSL to generate OVA manifest file (#826) It seems that sha256sum adds a space after the hash algorithm which causes "Invalid OVF checksum algorithm" on certain VMware virtualization products. Using OpenSSL avoids the space and makes the manifest file compatible wiht VMware products. * Use Buildroot provided OpenSSL binary * Use SCSI controller by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
board/ova
Open Virtual Appliance (Virtual Machine)
cla-signed
REL-7
run-dev-build
Execute development build on a PR
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use OpenSSL to generate OVA manifest file. It seems that sha256sum adds a
space after the hash algorithm which causes "Invalid OVF checksum algorithm"
on certain VMware virtualization products.
Using OpenSSL avoids the space and makes the manifest file compatible
with VMware products.
Use the common LSI Logic SCSI controller for disks. This is supported by Virtual Box
as well as VMware.