Skip to content
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

Installing HassOS 1.5 on VMware ESXi 6.5 - Problem and solution. #102

Closed
mihalski opened this issue Jul 14, 2018 · 19 comments
Closed

Installing HassOS 1.5 on VMware ESXi 6.5 - Problem and solution. #102

mihalski opened this issue Jul 14, 2018 · 19 comments
Labels
board/ova Open Virtual Appliance (Virtual Machine) wontfix

Comments

@mihalski
Copy link

Hi,

This is specific to the versions in the topic as I've had different experiences with HassOS 1.3 for example and not yet had the chance to try ESXi 6.7.

Problem:
Installing HassOS 1.5 directly in VMware ESXi 6.5 leads to no ip/interface on the LAN (DHCP server running on pfSense), so homeassistant cannot be installed.

Solution:
You can do the installation on an identically configured vm in VMware Fusion (or Workstation I presume) and it works fine. You can then export an OVA file and import it back into ESXi. Just make sure you've got the right compatibility settings before exporting.

In my case I chose Other Linux 3.x or greater as the OS and compatibility of vmx13.

Would be interested in hearing other people's experiences with HassOS and VMware ESXi.

Regards,
Michal

@mihalski mihalski changed the title Installing HassOS 1.5 on VMware ESXi 6.5. Problem and solution. Installing HassOS 1.5 on VMware ESXi 6.5 - Problem and solution. Jul 14, 2018
@pvizeli
Copy link
Member

pvizeli commented Jul 14, 2018

Yeah the vmdk is only a workaround and need fine tuning on the hypervisor to run it.

I hope someone can help to make a OVA/OVF. At the end they are only a tar file with a xml inside they describe how you need setup a vm.

@mihalski
Copy link
Author

mihalski commented Jul 14, 2018

The strange thing is that HassOS 1.2 installed in ESXi ok and then updated to 1.3.. After that it would fail to update to 1.4 without error. But there was no problem with ip/interface in either case.

I wonder if reverse engineering the OVA I made can be of any use?

hassos-dev.ovf.zip

hassos-dev was just the name of this VM. I'm sure only a small subset of the entries in the file are actually required, and I'd be happy to test anything that anyone is able to come up with.

@mihalski
Copy link
Author

Wanted to add that I was successfully able to update from 1.5 to 1.6 on ESXi using the update function in the Hass.io System panel.

@mihalski
Copy link
Author

For the next 14 days this HassOS 1.5 OVA should be available for download. It updates to 1.6 on ESXi 6.5 for me.

https://transfer.sh/p8sTz/hassos-1.5.ova

If anyone tried it, let me know how it went.

Regards,
Michal

@pvizeli pvizeli added the board/ova Open Virtual Appliance (Virtual Machine) label Jul 16, 2018
@shad0wca7
Copy link

I'm getting this same issue installing HassOS 1.8 on ESXI 6.7. It's not getting an IP address - pfsense internally as well. I've tried the e1000 network adaptor and that's made no difference.

@mihalski
Copy link
Author

Did you try the OVA I uploaded?

I was able to transfer that (as an updated 1.7) from ESXi 6.5 to ESXi 6.7 yesterday (just upgraded) and it updated to HassOS 1.8 just fine.

@gerard33
Copy link

@mihalski installed your HassOS 1.5 OVA successfully on ESXI 6.7 and was able to update it to HassOS 1.8.
Thanks!

@mihalski
Copy link
Author

Glad somebody got some use out of it as it took me about 5 hours to upload :P

@nugget
Copy link

nugget commented Jul 21, 2018

I also installed it successfully and appreciate the hours spent uploading. One question -- is there any way to enable ssh in to the core OS (and not just the ssh addon container)?

@mihalski
Copy link
Author

You're welcome. I don't believe there is a way to ssh into the host (unless maybe you create some sort of a loopback to the console from within a container maybe?).

But in the case of being physically at the console you can log in as root with no password. So probably not advisable to make that network accessible.

I do share the desire to be able to get at the host, purely for debugging reasons.

@nugget
Copy link

nugget commented Jul 21, 2018

Logging in to the console actually does not work. It gets you a hassio shell, but not a real shell. There is an official process for the SD card images documented here where you place your authorized_keys file in the boot partition to enable host level ssh. But I don't know how that would translate to the OVA/VMDK install.

@mihalski
Copy link
Author

Did you read what it says when you go into the hassio shell? Try typing 'login'.

That authorised_keys documentation does not apply to HassOS. There appears to be an equivalent but I'm not sure how it works. See:

https://github.com/cogneato/hassos/blob/dev/Documentation/configuration.md

Either way it works via a USB drive that you connect to the HassOS device and then import the config via the web UI.

@nugget
Copy link

nugget commented Jul 21, 2018

Did you read what it says when you go into the hassio shell? Try typing 'login'.

Dang, you're right, I completely missed that. Thanks.

@apo-mak
Copy link

apo-mak commented Jul 22, 2018

@pvizeli
i made ova Version 1 and 2 files.
also ovf (for vmware compatibility).

i am planing to add a hyper-v export .. but the current vmdk (1.8) dose not work on hyper-v.. so TBD.
(#120)

here is the link ..
https://github.com/apo-mak/hassos_VM
p.s. i am planing to update them when there is a new release of hassOS

@mihalski
Copy link
Author

OVA files do work in VMware (I provided one in this very thread).

Method I used was to create the VM with VMware Fusion (Workstation should work the same), configure it appropriately (but never start it) and then export to OVA.

@borpin
Copy link
Contributor

borpin commented Jul 24, 2018

Would be interested in hearing other people's experiences with HassOS and VMware ESXi.

Using an older ESXi 5.5 (free). Had to carefully select the OS Type so I could then force EFI boot which gets me to the boot menu. The final piece was this tip https://community.home-assistant.io/t/no-bootable-medium-found-system-halted/60783/9 to delete the CD ROM.

@stale
Copy link

stale bot commented Apr 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 16, 2019
@stale stale bot closed this as completed Apr 23, 2019
@heapxor
Copy link

heapxor commented Aug 7, 2022

les do work in VMware (I provided one in this very thread).

Method I used was to create the VM with VMware Fusion (Workstation should work the same), configure it appropriately (but never start it) and then export to OVA.

@mihalski
OVA is definitely broken and it has to be RAISED AS A BUG.
After importing OVA VM cant be snapshoted/suspended anything bc wrong /old template is used.

Using vmdk there is anothe BUG as someone didnt covert old IDE to SCSI - so it cant be extended.
After conversion from ide to scsi - issue with uefi not bootable.

i cant believe that Both options are Seriously broken - nooone raised that as a BUG and noone care.
is that kind of a game how not to be able run haas properly on Esxi , are u forcing all who wants to virtualise to buy hardware, thats insane!

completely OUT OF DATA VMX version
wrong OS/Guest OS version

@stevegore
Copy link

Yeah my Linux server had a hardware malfunction so I tried to install HA on Windows. Not of the OVA images work. The instructions are terribly out of date as well. But if the images were working I'd at least have a shot.

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) wontfix
Projects
None yet
Development

No branches or pull requests

9 participants