Deploying HassOS to ESXi

Hey guys,

I had a few issues deploying the HassOS VMDK to ESXi recently, so I decided to write a post for it here: https://blog.markdepalma.com/?p=82.

5 Likes

Many thanks for this. I may try this later. A number of people have asked how to accomplish this.

Can you expand the disk beyond the default 6 or 8 gb or is this no longer even an issue?

1 Like

Good job! I was thinking to install it on my HP microserver gen8 running ESXi after reading all the problems with RasPI and sdcards … will see if it’s working.

1 Like

I just shutdown my test instance, expanded the drive to 20GB, and turned it back on. Got into shell using console access, ran 'df", and it is showing around 19GB total. It looks like HassOS automatically takes care of it.

1 Like

Same result here.

Thanks for posting the guide. Works well.

1 Like

How did you do it? When i want to expand the disk I get an error.
Also i cant change increase the ram. When i save the new value it remains on the old one.

What version of ESXi are you doing this on?
Is it stand-alone ESXi or part of a cluster with vCenter?
Is the VM off when you attempt this?
Did you clone the disk with vmfstools per the instructions before adding it to the VM?

I think its 6.7
The server is stand-alone so its not part of a cluster. The VM is off. And I was able to change the CPU cores from 2 to 4.
I did not clone the disk with vmfstools. I dont know which instructions do you mean?

I outlined all steps here: https://blog.markdepalma.com/?p=82. Also, as I said in the article you should be fine with one vCPU. Always best to right size VMs and keep vCPU count as low as possible to avoid CPU Ready issues.

Thanks, i will take a look into at it in the evening.

1 Like

So i created a new VM with your guide and imported my snapshot. Everything is back up and with more space than before. Thank you :smiling_face_with_three_hearts:

1 Like

I followed the tut but ran into a strange state, i’m getting stuck: starting version 3.2.7 and starting eudev-3.2.7

Can anyone help me?

Run ESXI 6.5

1

Check your config logs if you have SSH enabled. It sounds like it may be a config issue.

I have just used this guide and it works perfectly. Before I was stuck running Hassio on an Ubuntu VM in ESXi. That was a pain to manage, this is much more elegant. I also feel like the interface is more responsive than before.

Thanks for this!

1 Like

Hi,

I cannot get it to work using your method and version:
VMware ESXi 6.7.0 build-10302608 and hassos_ova-3.5.vmdk. The vmkfstools works ok, but ESXI does not recognise the output. Meaning when adding an existing harddisk I cannot select the new disk.

I can select the original downloaded vmdk file.
Regards,

Sounds like something wrong is happening here…

-Can you copy/past the entire terminal output after you run the command?
-Also can you do an ls in the directory and copy that as well?

Hi mnetwork,
I’ve followed your instruction and created the vm with latest vmdk file of Hassio. Now, the vm is running fine, I can ping it from other machine but I can load the web interface on any of the browsers from any other computers within my network.

  • I am using esxi 6.7
  • tried using on Firefox, chrome, IE 11 and edge.
  • also did use the port number to browse (port 8123).
  • also have tried changing all vm nic type including E1000.

Not sure is this an issue with esxi or the vm.

To me it sounds like the VM is coming up, but hasn’t downloaded/deployed the HASSIO container. Do you have any firewalls internally that would prevent this VM from reaching out to the internet?

Freshly installed ESXi 6.7. I don’t have any firewall inside the network but on the outbound internet.
I have used the VMDK image from the original source. Some reason there are two IP addresses. Class C address is from my DHCP and it is reserved. Class B is unknown. is that soupposed to happen?

Only advice I can give is you have to wait a loooong time when you first start the VM. I have had it several times where I thought the VM was dead but in reality it was still booting. So, after you boot go for lunch and then check :slight_smile:

No, really, I’ve know the initial booting time for Hassio to take up to 20 minutes…

It is normal your Hassio has 2 IP’s: the one is on your local network the other is, I believe, the internal IP Hassio uses to communicate with its own containers (the addons). I see the same thing in my Hassio and that is running fine.

Thomas

1 Like