Closed cormite closed 5 years ago
@cormite Which version of ESXi and vCenter are you using exactly?
@joschi I run: VMware vCenter Server Appliance 6.5.0.14100 Build Number 7801515 And for ESXi two versions:
Best regards, Carlos.
Have you tried to directly access the ESX host and deploy the OVA file?
Dear @casellia,
Please follow the ref. specified by @jalogisch (https://community.graylog.org/t/graylog-ova-import-problems/4422/12). This case was fixed and closed.
Thanks, Carlos.
Im getting this even with your fix Issues detected with selected template. Details: - 74:7:VALUE_ILLEGAL: Value ''6'' of Parent element does not refer to a ref of type DiskControllerReference.
Hi, could you please retry with the latest 3.0 beta image? In 3.0.0-beta-4 we removed the problematic sound card and switched from an IDE disk controller to a SATA one.
https://packages.graylog2.org/releases/graylog-omnibus/ova/graylog-pre-3.0.0-9.beta.4.ova
Was there anything I was supposed to do with it first because I got this with it as is.
Thanks
On Jan 29, 2019, at 11:03 AM, Marius Sturm notifications@github.com wrote:
Hi, could you please retry with the latest 3.0 beta image? In 3.0.0-beta-4 we removed the problematic sound card and switched from an IDE disk controller to a SATA one.
https://packages.graylog2.org/releases/graylog-omnibus/ova/graylog-pre-3.0.0-9.beta.4.ova
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Hi, could you please retry with the latest 3.0 beta image? In 3.0.0-beta-4 we removed the problematic sound card and switched from an IDE disk controller to a SATA one.
https://packages.graylog2.org/releases/graylog-omnibus/ova/graylog-pre-3.0.0-9.beta.4.ova
Thank you for the help, tried the new beta OVA but encountered the following errors. Line 57: No space left for device '7' on parent controller '5'. Line 48: Unsupported virtual hardware device 'AHCI'.
@nathjnair looks like the VirtualBox SATA controller is not supported by VmWare, so last option would be to be to use a SCSI controller instead. Will try this today.
@nathjnair could you give rc.1 a try? It's using the scsi controller now and was tested successfully with Virtaulbox 5.2 and VMware Fusion 11 https://packages.graylog2.org/releases/graylog-omnibus/ova/graylog-pre-3.0.0-10.rc.1.ova
Unfortunately we dont have a vCenter installation available to fully reproduce your issues.
@nathjnair could you give rc.1 a try? It's using the scsi controller now and was tested successfully with Virtaulbox 5.2 and VMware Fusion 11 https://packages.graylog2.org/releases/graylog-omnibus/ova/graylog-pre-3.0.0-10.rc.1.ova
Unfortunately we dont have a vCenter installation available to fully reproduce your issues.
Hi mariussturn, Thank you for your help, the ova you mentioned is working.
By the way, I am not using vcenter setup, I am using the free version of ESXi 6.5
I have successfully able to bring up web gui, but the default username and password (admin/admin) is not working, tried to reset the password using graylog-ctl , but the command is not recognised by the system.
@nathjnair ok cool, thanks for the feedback. Closing the issue for now.
Just tried to import the OVA for Graylog-3.2.2-1 using Vcenter 6.7.0 Build 10244857
I received the same manifest error
"The provided manifest file is invalid: Invalid OVF manifest entry: ."
Unfortunately Editing OVF file from lines 48 to lines 65 with the above change did not fix the issue.
When importing the provided OVA file (version 2.4.3-1) into vCenter (or ESXi straight) I came across the following error:
"The provided manifest file is invalid: Invalid OVF manifest entry: ."
After a couple of investigations I realized that the problem came from the ResourceSubType PIIX4:
Finally I was able to resolve the issue by modifying lines in the OVF file from lines 48 to lines 65 as follows:
Original block:
Modified block:
I hope this helps others solve the importing of the virtual appliance into VMware environments.
Best regards, Carlos.