#Hello everyone, I am at wits end.

1 messages · Page 1 of 1 (latest)

torn hornet
#

please help if anyone had the same problem and had it worked out

true valley
#

ultra core 5 probably can't turn off uefi

#

that part of the instructions is mostly for people trying to run old stuff

torn hornet
#

thank you Tom

#

i'll look into another nuc

pseudo estuary
#

No. HAOS needs UEFI so that can't be the problem. Make sure you have disabled secure boot though.
I strongly recommend virtualizing with such a machine. It's more than overkill for just HAOS: #hardware-archived message

torn hornet
#

that's right, UEFI on, secure boot OFF.

#

yes, it is overkill, cause i'm would like to run at least 10 cameras, with the CORAL TPU duo

#

so you would suggest going the PROXMOX route with VM HAOS

pseudo estuary
#

Yes but it's your choice in the end. If you want to go bare-metal boot the ubuntu iso again like the docs explain and run sudo -i; lsblk -oLABEL,FSTYPE,MODEL in a terminal and share.
Also share sudo efibootmgr's output.

torn hornet
#

i mean docker and portainer

true valley
#

I don't think you have to virtualize it, even if you ave too much hardware

torn hornet
#

thank you for the code line. what would that code do?

pseudo estuary
torn hornet
#

and this NUC is dedicated to HA and various add-ons ONLY

#

THANKS impact

pseudo estuary
#

Some of my nodes only run a single VM. Just the snapshotting alone is good enough reason for me to recommend it.

torn hornet
#

i'm at work right now during lunch. would love to run the code and share result here when i get home

pseudo estuary
#

Threads send notifications (at least to me) so just post here and we'll probably see it.

torn hornet
#

thanks impact. snapshot vs the regular backup of the HAOS. is it that more comprehensive with the snapshot (efficient with data compression?)

#

do you have a youtube channel that i can follow what you do and perhaps imitate?

true valley
#

i do regular backup

torn hornet
#

thanks tom. i had also backup HAOS and it is quite fast and speedy

#

i just don't see myself backup the data from the cameras SO it is just a matter of backup the OS and add-ons

pseudo estuary
#

Snapshots are petty much instant. They do not replace backups. VM backups often use snapshots too to avoid having to stop the VM.
HAOS' OVA has support for this so that this works fine.

torn hornet
#

oh ok... another plus for proxmox is the ability to run 2 machines and have it your system up and running if one should failed?

#

that's what i seen on the web

pseudo estuary
#

It's an option with clusters. But that only works if you don't have local resources such as your TPU or a USB stick. Or have them duplicated.

torn hornet
#

yes, i have the zigbee2mqtt and the TPU

pseudo estuary
#

One of the main benefits is that not everything is available as addon and addons are sometimes very opinionated and limited. You can run whatever you want in a different VM.
Try to disable authentication for mosquitto for example.

torn hornet
#

ok

#

nice

pseudo estuary
#

In my case I chose to buy a SLZB-06 so Zigbee does not depend on a specific node and both can use it.

torn hornet
#

i just wonder is there something that you cannot do on proxmox-container route vs HAOS barebone?

#

as far as integration

#

and execution

pseudo estuary
#

I don't personally use HAOS but I always have a VM running to be able to help people here with it.

#

HAOS would be in a VM, not a container.

torn hornet
#

ok

pseudo estuary
#

Basically just addons and managed backups. The latter is not needed if you can backup the whole VM. Might still make sense to use both though.

torn hornet
#

yes that is the table that i had looked at when decided to go with the HAOS

#

so the solution you suggested would be SUPERVISED?

pseudo estuary
#

Now since addons are just containers you can replicate them all. Voice is a bit hard to replicate though since there's no good instructions and t's complicated.
Note that I did not say not to use HAOS.

#

NO!

#

The recommendation was to run HAOS in a VM. The real HAOS.

torn hornet
#

OK

true valley
#

oh dear god no supervised.

pseudo estuary
torn hornet
#

so that is an extra layer of complication PROXMOS as base

pseudo estuary
#

It is.

torn hornet
#

so PROXMOX as base, then VM HAOS

pseudo estuary
#

But I'm fairly certain at some point you will regret not having it.

torn hornet
#

then when do you use docker container

#

can you not add ADDONS inside the VM HAOS

pseudo estuary
#

You can run another VM with docker containers that are not available as addon in HAOS.

torn hornet
#

I SEE

pseudo estuary
#

Or if an addon is too limited for what you want to do. Or too rarely updated. Or whatever. The point is to have freedom, choice, flexibility.

torn hornet
#

so how do i get the docker container addons to talk to the VM HAOS instance to have HAOS control the addons...

pseudo estuary
#

You don't. HAOS will not control other docker containers.

torn hornet
#

nice

#

oh.

#

so they the two VMs are not integrated

#

i need to read up on proxmox more

pseudo estuary
#

The VMs are not. The software can kind of be.

#

I put related software in the sidebar of HAOS even though they are all docker containers. My docker mosquitto also integrates with my HA.
Most of the time it doesn't matter how the software is run. There are some exceptions like voice which have so many and poorly documented parts.

torn hornet
#

thank you impact. i'm seriously considering ditching the bare bone option and go with proxmox and vm HAOS

#

Any recommendation on the core numbers and the memory allotment for the proxmox and vm haos if i want to run alot of cameras?

pseudo estuary
#

My link from earlier has a quick start guide. It uses a script to build (rather import) the VM with some good defaults. I don't like such scripts because you don't learn why the options were chosen but it's a quick start.

#

2-4G of memory is usually a good start. I'm not sure how cameras change the memory usage so you have to ask in #cameras-archived or test it.
For cores you can pretty much give it all your logical cores.

torn hornet
#

can you resend just the link as a post?

pseudo estuary
torn hornet
#

ok

#

thanks

#

so if you give HAOS VM all your core, would it not be slow? because proxmox as base would be choking?

pseudo estuary
#

A VM is like a process. Linux will schedule the usage.

torn hornet
#

so "give it all your logical cores" pertain to the proxmox?

pseudo estuary
#

Everyone has different opinions about that. You can also just leave 2 to the OS but if you run multiple VMs that theory kinda goes out the window.

#

No to the VM.

torn hornet
#

this is also the my first foray into VM as you can tell

pseudo estuary
#

You can over-allocate CPU cores because, like I said, a VM is just a process. So if you have a CPU with 8 cores you can have 10 VMs and give each of them 8 cores without issues.
They obviously can't use them all at 100%.

torn hornet
#

wow thank you for explaining so clearly

pseudo estuary
#

You don't give your web browser just 4 cores of your CPU either, no?

#

It's a bit like with fast internet. You probably don't max it out all the time with all your clients either 🙂

torn hornet
#

👍

pseudo estuary
#

Here's how my HAOS VM looks like in case you want a reference: https://imgur.com/a/4dn01Ro
As you can see I'm pretty stingy with the resources for no good reason but it's enough for my testing.
Btw don't enable pre-enrolled-keys like I did when I created it (forgot to uncheck). It also enables secure boot which you then have to disable in the UEFI of the VM.

true valley
#

mine's running on an i7 8700 with 64GB of RAM and a 256gb nvme drive

#

bare metal, because I don't need that box to do other things. configured like that because it was all lying around waiting to find a purpose

pseudo estuary
#

There were way too many issues with HAOS for me to be able to trust it bare-metal. Just recently it broke grub.

true valley
#

i don't have an azerty keyboard and I haven't needed to use a keyboard with it, so i'm ok

pseudo estuary
#

I don't want to bad mouth HAOS but I've also seen way too many needs for resets in the #green-archived and other channels. I'm aware that being in a help channel causes bias because mostly people with problems come here but it just changes my opinion of it. I also note that PVE is absolutely not a good fit for everyone so I don't really have a good solution. I'm just saying running/updating it on bare-metal would scare me.

torn hornet
#

i love being able to avert future problems of OS breaking down due to updates if i can.

#

having said that, i love the simplicity of the bare bones HAOS but, came here because i simply could not install it on my NUC after 1wk of sleepless nights and spending more than my paying job each day on trying to get it to work. Of note, i recently got into HAOS and had successfully installed it on 3other machines but deemed more processor and memory power (while being low energy consumption) to future somewhat to move the operation onto a newly acquired NUC with ultra core chip

#

thank you impact for all the links. will trying to imitate your install. better than hitting my head against a wall night after night trying various method to get the HAOS to install bare bone

pseudo estuary
pseudo estuary
torn hornet
#

Hi impact. Thanks for the gracious offer. I would love to have you help me

#

Yesterday I followed you our link and installed promos and haos

#

Trying to follow more posts to have usb pass through and such

#

I do have an extra 1tb nvme drive lying around and don’t mind put haos as bare bone on that

pseudo estuary
#

USB passthrough in PVE is fortunately extremely easy. Such a waste to put only HAOS on a 1TB drive though.

torn hornet
#

i understand, it is just for a lab environment. and when i do get it running, i can obtain a smaller one for the actual installation