search

philhagen / sof-elk

Configuration files for the SOF-ELK VM
GNU General Public License v3.0
1.47k stars 276 forks source link

v20221025 VMDK boots fine. v20230329 does not #273

Closed Drookoo closed 1 year ago

Drookoo commented 1 year ago

Hey team,

I am very excited to utilize v20230329 but the VMDK doesn't boot. I did a sanity check and tried a clean boot of v20221025 and that worked without an issue.

Thank you

philhagen commented 1 year ago

Could you provide some more detail? MD5 of the VMDK as extracted from the 7z archive, specific error message, version of VMware and product family, etc. Did you use a non-OS archive extraction tool to extract the distributed 7z file?

I can confirm it works here, and we've had no reports of this with quite a few downloads, so I am pretty sure it's not the distributed content but maybe some odd edge case

Drookoo commented 1 year ago 
MD5 (Public+SOF-ELK+v20230329.7z) = ba74b78fbbfb9217d6c17658741eaa7e
MD5 (SOF-ELK.vmdk) = 85dff75314425e0cb9d37a0c12397777
MD5 (SOF-ELK.vmx) = 7082e98be6f017997dd0f2efd7a6efe5

VMware Fusion Professional Version 13.0.1 (21139760)

I used Macos Ventura 13.3.1 default archive utility to unzip

Screenshot 2023-04-11 at 4 43 03 PM

philhagen commented 1 year ago

Your screenshot shows CentOS 8, which is not what we distribute. Please do not attach the VMDK to any other VM - just boot the supplied VMX directly. If opening the existing VMX as supplied still causes an error, this ticket can be re-opened.

Also, I'd definitely use Keka to extract it. Not a prime cause of this kind of thing, but we've seen native OS decompression utilities fail on large files like VMDKs.

Drookoo commented 1 year ago 
Your screenshot shows CentOS 8, which is not what we distribute.

Well aware, that's just an alias from Fusion

Please do not attach the VMDK to any other VM

right, I'm creating a custom virtual machine. and only attaching the extracted VMDK to the virtual controller Screenshot 2023-04-11 at 4 59 03 PM

I can run my exact steps with a fresh extracted Public+SOF-ELK+v20221025.7z and get my vm to boot without an issue.

I'm just here to test the new changes introduced from the inclusion of /logstash/microsoft365/

philhagen commented 1 year ago

Not sure how that would ever work - you should use "File | Open" and navigate to the VMX file in Fusion. That is pre-configured to boot properly. The workflow you're using creates a new VMX that points to the existing VMDK, which is probably causing a mismatch due to BIOS/UEFI or related settings.

File | Open will work and has been the only supported method to boot the VM.