My VM (installed as described in the 1st post, with q35, restored my backup from RPi3 without issue, latest Proxmox, latest HA) keeps crashing after 1-2 days usage.
I wanted to try 5.19 and then noticed they also have 6.1 available.
I was wondering if you could adapt the βProxmox Edge Kernel Toolβ to allow to choose between 5.18, 5.19 and 6.1?
When I run the script it only talks about 5.18 currently:
You can use the proxmox-boot-tool to add/remove, pin/unpin, list kernels (and more, itβs what I use in the script)
just run proxmox-boot-tool in the Proxmox Shell to see all of the commands.
You are correct and I totally overlooked the difference between the edge and opt-in kernel. In my mind I was expecting something called βedgeβ to be newer then something called βopt-inβ
Maybe an idea to extend your script to support both the Edge and Opt-in kernels?
I have the impression most people who stumble on this are just trying newer kernels because they have some issue and your scripts allow to easily try a different versionβ¦ I donβt really βcareβ what kernel I land as long as it offers a stable result. I was perfectly happy with 5.18 until I had problems with the latest 5.18. I rather try a newer branch than forever pin a specific version though.
I have readed through this thread and did not find the answer.
I am migrating HA from Proxmox Debian VM + HA supervised to a VM HA OS install . as per section 3 of this guide
Actually βpreparing home assistantβ has been completed on the web UI and then I will be ready to restore the backup of the supervised VM install to the new HAOS VM.
After I discovered the option to migrate my HA from RPI to VM via Proxmox I was very happy impatient to do it. So, I bought a recommended mini PC (Dell Optiplex 3050 -i7-6700T with 8GB RAM & 256 GB SSD) and Iβm looking now to improve this hardware configuration in order to virtualise the following apps/services:
HomeAssistant
openVPN
Plex
PFSense
Torrent server
The backup disk for photos, videos, downloaded files, etc will be either SSD connected via usb or a NAS Synology.
For the RAM memory I think it is simple. I can buy, 16GB or 32GB. My concern is related to the SSD and M.2, memories. My questions are:
It is recommended to use the m.2 for root drive (-local(pve)) and the 2.5β drive for local-lvl (images, containers, VMs) or it is enough to use only one disk?
Considering the huge number of writes on SSD/M.2 disks because of virtualisation or the use of ZFS file system, it is important to consider the TBW (Terabytes Written) parameter or it is not applied for a simple homeLab configuration like it was described above? Do you recommend to buy a SH enterprise SSD instead of a new consumer SSD?
Please share with me your experience/knowledgeβ¦
Thank you !
Hello,
I started today with my Proxmox installation on my Server.
As HAOS does not support Raid-1, I decided to go for Proxmox and so I installed it with Raid-1 with ZFS.
Was this a clever idea? Or do you recommend other Filesystems?
I have 2 SSDs.
Looking for a recommendation here⦠Currently running HA Supervised from a Proxmox VM running Debian11. I have spun up another VM using the latest HA OS version installed with the script here. All good to this point.
I always change my VMβs to run with static IPβs. Currently the HA Supervised in Debian is 10.1.xx.15. The new install uses a a non-static IP. In this case 10.1.xx.224. I would like the new HA OS to use the 10.1.xx.15. (Old VM will be turned off and deleted.)
My question is: What is the correct order to changing the assigned IP to static? Stop the old VM and change HA OS to the 10.1.xx.15, then load backup? Or load backup first, then change IP after all is running?
TIA,
Cheers!
Thanks for the fast replay
Diskspace is over 1 TB free where I want to install it
How much space does it need, I have notice that there I want to save the VM is Type βdirβ
It maybe does not like it?
The other is lvmthin but only 60 GB free and Iβm not sure how much HAOS need?
/UPDATE
Did try on lvmthin but error that to, it was a error I did have before I did run a update so I did go back to my first storage and same error