Closed wolfsden3 closed 5 years ago
I get the exact same error message and same symptoms.
It works in Virtual Box...I'm trying a new export, v2 (of whatever compatibility it asked for) and I left everything default. It is a different file size than the original OVF but not much. I imported it into VBox > exported it right away. Then after it got done with the export I started the original from your git download up and it worked. I'm compressing it > xfering it to my site > then will try to re-import it and see what happens.
Rafael
On Sat, Mar 30, 2019 at 10:30 AM Jm Casler notifications@github.com wrote:
I get the exact same error message and same symptoms.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/librenms/packer-builds/issues/8#issuecomment-478251047, or mute the thread https://github.com/notifications/unsubscribe-auth/ARvgcyjftKnJ8D9g1trtW66rbKARTkYGks5vb3T3gaJpZM4cTrsG .
-- Rafael
765-714-7257
Well that failed miserably. I was able to finally import it using this guide: https://www.vionblog.com/migrate-virtualbox-vmware-esxi-6-5/
You have to jump through some hoops. I think if you're creating it in VBox maybe making a SATA disk instead of IDE (assuming that's an option) might fix this issue.
Thanks! Checking out LibreNMS!
Rafael
On Sat, Mar 30, 2019 at 12:27 PM Rafael Wolf rfwolf@gmail.com wrote:
It works in Virtual Box...I'm trying a new export, v2 (of whatever compatibility it asked for) and I left everything default. It is a different file size than the original OVF but not much. I imported it into VBox > exported it right away. Then after it got done with the export I started the original from your git download up and it worked. I'm compressing it > xfering it to my site > then will try to re-import it and see what happens.
Rafael
On Sat, Mar 30, 2019 at 10:30 AM Jm Casler notifications@github.com wrote:
I get the exact same error message and same symptoms.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/librenms/packer-builds/issues/8#issuecomment-478251047, or mute the thread https://github.com/notifications/unsubscribe-auth/ARvgcyjftKnJ8D9g1trtW66rbKARTkYGks5vb3T3gaJpZM4cTrsG .
-- Rafael
765-714-7257
-- Rafael
765-714-7257
The virtual images aren't built for Vmware so that's probably why you've had issues.
Glad you got it sorted and thanks for documenting for the next person.
The idea fix for this is for someone to donate an esxi box we can build images against......
PM me and maybe I can get you access to one ;-)
I wonder if ProxMox export would import into VMWare?
Rafael
On Sun, Mar 31, 2019 at 9:31 AM Neil Lathwood notifications@github.com wrote:
The virtual images aren't built for Vmware so that's probably why you've had issues.
Glad you got it sorted and thanks for documenting for the next person.
The idea fix for this is for someone to donate an esxi box we can build images against......
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/librenms/packer-builds/issues/8#issuecomment-478342289, or mute the thread https://github.com/notifications/unsubscribe-auth/ARvgc7UnJS0OHHYbdlwYZg3Vi1cs4GVhks5vcLiUgaJpZM4cTrsG .
-- Rafael
765-714-7257
Thanks @wolfsden3 no PMs on GitHub and can't see your email address in your profile.
The access would need to be a permanent one as we build the images monthly. Is that something you can do as the last thing users would want is a vmware image for 2 months then it stops.
🤔... can you point me in the direction of documentation for that? Is this something where I can provide you with ssh access to and all you'd need is CLI?
I'd just need more information and I'd be happy to contribute a VM on VMware for you and your team for an honorable mention of my consulting business by the download link 😊.
On Tue, Apr 2, 2019, 6:00 AM Neil Lathwood notifications@github.com wrote:
Thanks @wolfsden3 https://github.com/wolfsden3 no PMs on GitHub and can't see your email address in your profile.
The access would need to be a permanent one as we build the images monthly. Is that something you can do as the last thing users would want is a vmware image for 2 months then it stops.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/librenms/packer-builds/issues/8#issuecomment-478928534, or mute the thread https://github.com/notifications/unsubscribe-auth/ARvgc2X7-J0B9WRunZyCeQO9HUL1yF9Yks5vcyojgaJpZM4cTrsG .
Sorry it's a little more complicated than that :(
We need full access to the base ESXi box so that packer can build a VM within it and it be exported for an image to use by others: https://www.packer.io/docs/builders/vmware-iso.html
I was just reading that.
I still might be able to do that. Let me fiddle with it and get back to you.
We definitely want to be automated if you do it.
On Tue, Apr 2, 2019, 6:53 AM Neil Lathwood notifications@github.com wrote:
Sorry it's a little more complicated than that :(
We need full access to the base ESXi box so that packer can build a VM within it and it be exported for an image to use by others: https://www.packer.io/docs/builders/vmware-iso.html
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/librenms/packer-builds/issues/8#issuecomment-478944889, or mute the thread https://github.com/notifications/unsubscribe-auth/ARvgcw62hmGFsfO-1wyB9BTakED7zP1oks5vczaxgaJpZM4cTrsG .
Thanks :)
We'll definitely be able to provide a big thank you and a mention for your business.
It does say you can SSH into a VMware server and set it up to upload the finished product as an iso.
https://www.packer.io/docs/builders/vmware-iso.html
...they don't mention esxi but I bet it would work.
I can put one on a public IP and give you access to it if you want so you can play around with it. Full console access.
You want to try that?
On Tue, Apr 2, 2019, 6:57 AM Neil Lathwood notifications@github.com wrote:
Thanks :)
We'll definitely be able to provide a big thank you and a mention for your business.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/librenms/packer-builds/issues/8#issuecomment-478946120, or mute the thread https://github.com/notifications/unsubscribe-auth/ARvgc0El6DAhciHBG6kJB8pK_cHpcbapks5vczeegaJpZM4cTrsG .
Yeah ssh is fine, it just can't be a VM within Vmware, has to be to the vmware server itself.
Happy to give it a try. Feel free to drop me an email to gh+n@laf.io
The virtual images aren't built for Vmware so that's probably why you've had issues.
Glad you got it sorted and thanks for documenting for the next person.
The idea fix for this is for someone to donate an esxi box we can build images against......
I work for VMware ...
You can download ESXi (vSphere 6.7) from the VMware website and run it within a virtual machine (instructions via google search). From the same site you download vSphere is a free license key generator for unlimited use at smaller installations like what you're proposing.
vSphere is a free license key generator for unlimited use at smaller installations like what you're proposing.
A non-expiring license?
Yes, non-expiring license for a single server, nearly unlimited cpu, nearly unlimited memory, no clustering, no fail over.
Thanks for that, will take a look when we can.
Did this get fixed? I get the same issue today trying to import into ESXi 6.7 Update 3.
Thanks
This is still not working, No idea why the issue was closed ...unless esxi is not catered or cared for!
@t0m5k1 LibreNMS is a community project having a ticket like this open is not helpful unless someone is willing and able to work on it. I would love to see an ESXi image, but I am unable to work on it.
I downloaded both the Ubuntu and CentOS image (Cent after Ubuntu wouldn't work) and both are getting this error when trying to import into VMWare ESXi 6.7.
It errors out then when you click "finish" it says [missing message value]. It happens every time I try the import. Is anyone else having this problem on ESXi?