DarrenNevares, 5 days ago

Finally getting MacOS setup on #Proxmox
#HomeLabServer

felis, 18 days ago German

Am gestrigen Regentag nahm ich meinen Mut zusammen wollte meinen #Heimserver von #Proxmox 6.4 auf 7.x updaten. Viel zu spät war ich dran, aber es lief seit Jahren alles so schön fehlerfrei. Leider fror das Upgrade bei 58 % ein. Ich konnte herausfinden, dass es etwas mit „memtest“ zu tun hat. Nachdem ich diesen Prozess abschoss, lief das Upgrade bis zum Ende durch jedoch nicht fehlerfrei: Ich kam nicht mehr ins Proxmox-Gui, da „pveproxy“ und „pveservice“ (oder so) nicht mehr starteten. 😞 1/3

stooovie, 22 days ago

Whew! #Proxmox host went belly up, took me seven hours to fix even with backups.

TWO SSDs failed this morning.

dustinrue, 27 days ago

Thoughts on Proxmox and Home Lab Use

This post is really a small collection of thoughts about Proxmox when used in a home lab situation and home labs in general. I was originally going to post this to Mastodon only but it didn't fit in a single post.

A lot of people (at least what I see on reddit) build Proxmox systems with shared file systems like ceph, even for home lab use.

https://dustinrue.com/2024/04/thoughts-on-proxmox-and-home-lab-use/

#ceph #proxmox #samba #truenas #zfs

stefano, 1 month ago

Proxmox VE 8.2 released!

https://forum.proxmox.com/threads/proxmox-ve-8-2-released.145723/

#Proxmox #Linux #Virtualization #SysAdmin #IT

wagesj45, 1 month ago

I totally understand men that obsess over their lawn. I do the exact same thing with my home network.

#proxmox #vm #virtualmachine #debian #network #homenetwork #server #homelab #lawncare #guystuff #justmanlythings

stefano, 1 month ago

Today I pondered something: Proxmox and others boast native ZFS integration as one of their strengths. Many Proxmox features rely on ZFS's unique capabilities, and many setups are built around them. If Oracle were to send a cease and desist tomorrow, how would the situation unfold?

#Proxmox #ZFS #Oracle #CeaseAndDesist

marud, 1 month ago

Bon, je suis complètement à court d'idées, j'ai besoin d' #aide sur du #reseau sur ce serveur... Si vous avez une idée ou si vous pouvez partager, j'en peux plus là

Le serveur qui fait tourner cette instance est sur un #proxmox. Jusqu'ici, tout allait bien.
Hier, suite à un plantage, j'ai du reboot le serveur (VPS chez Ionos). Après redémarrage, impossible d'accéder à quoi que ce soit : Interface Proxmox, services dans les conteneurs, rien.

La configuration était la suivante :

Interface externe (ens6) et 2 bridges :

• vmbr0, en bridge-port sur ens6 (avec donc son ip publique), utilisé pour l'administration
• vmbr1, avec une ip dans un réseau en 192.168.2.0/24 qui sert les conteneurs (reverse proxy pour un et docker pour l'autre)

J'ai dans mon fichier d'interfaces pour vmbr1 ceci :

        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.2.0/24 -o vmbr0 -j MASQUERADE
        post-up /script/dnat.sh
        post-down iptables -t nat -D POSTROUTING -s 192.168.2.0/24 -o vmbr0 -j MASQUERADE

Pour les ouvertures de port, j'ai dans dnat.sh des entrées comme celle ci (exemple pour le port 443)

iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to-destination 192.168.2.10:443

Après debug, j'ai vu que le trafic passait à nouveau lorsque je foutais en down VMBR0.

J'ai donc, dans l'urgence, changé mes règles pour retirer vmbr0 et le changer par ens6, qui est le nom d'interface "physique".

J'ai pu constater que tout était revenu : accès à l'interface de proxmox, accès aux conteneurs... tout sauf, un point important : impossible depuis le serveur d'utiliser sa propre ip publique.

Par exemple, impossible pour l'instance d'envoyer un mail (le conteneur de mailing est situé derrière la même ip), impossible même depuis le shell de proxmox... ou encore impossible de renouveler les certificats sur le conteneur qui fait reverse.

[1/2]

Mawoka, 1 month ago

A question for the #network-guys here:

I've got the 192.168.1.x network with HA in there. Now, I've got an #OpenWrt router with the IP 192.168.1.190 creating 2 new networks: 192.168.100.x. I now want to get the HA into the 192.168.100.x network, but I can't connect it physically, as both the OpenWrt and HomeAssistant run in containers/VMs on #proxmox. I tried experimenting with IP routes, but no success. Does anyone have a clue for me?

tomi, 1 month ago

(Link to the original blog post with a proper layout)

It’s a pity that #Proxmox doesn’t report CPU and other temperatures to #homeassistant.

I had several freezes of my old laptop that runs Proxmox due to a stuck CPU fan. I googled a bit and found an elegant solution for temperature reporting: a command_line sensor.

Nevertheless, it took several hours to configure it correctly (I forgot how to deal with ssh keys and similar).

This is the end result:

home assistant cpu temperature sensor chartThe procedure:

1. I installed the ‘Terminal & SSH’ add-on in to home assistant.
2. I created SSH keys, put them into /config/.ssh folder, and copied to my proxmox server. Read these instructions. I’ve put something like this in my HA Terminal addon:

$ mkdir /config/.ssh$ ssh-keygen <em># generated ssh keys and when asked, i enter the folder /root/config/.ssh</em> $ ssh-copy-id -i /root/config/.ssh/id_proxmox root@MY_PROXMOX_IP <em># copy keys to my prox server</em>$ ssh root@MY_PROXMOX_IP <em>#try out if I can log on without password prompt, then exit</em>

3. I had to find out where my proxmox stores temperatures. I ssh’ed to my proxmox again, browsed folders and looked into files which one store temps. My AMD laptop stores it in /sys/class/thermal/thermal_zone0/temp.

It could be also …/thermal_zone1, 2, 3 or similar.

4. Then I pulled temperature data via SSH to HA terminal:

$ ssh -i /config/.ssh/id_prox -o StrictHostKeyChecking=no -q root@YOUR_PROXMOX_IP cat /sys/class/thermal/thermal_zone0/temp

The command returned 52000.

Edited my configuration.yaml and added the sensor. This is a working #YAML code (as of Apr. 2024). I used tips from here (deprecated sensor) and here.

##################

Temperature proxmox

##################
command_line:
– sensor:
name: temperature_cpu
command: “ssh -i /config/.ssh/id_prox -o StrictHostKeyChecking=no -q root@YOUR_PROXMOX_IP cat /sys/class/thermal/thermal_zone0/temp”
value_template: “{{ value | multiply(0.001) | round(1) }}”
unit_of_measurement: “°C”

After 20 restarts of Home Assistant, it finally shows the proxmox CPU temp.

Bonus: here is a picture my homelab proxmox ‘server’ with external fans (because CPU fan is not working).

https://blog.rozman.info/wp-content/uploads/2024/04/20240415_081455-1024x576.jpgBonus #2: A hypothesis: Fediverse is causing global warming! 😉 😉

When I publish a blog post, the WordPress Activitypub plugin delivers the post to the #fediverse. This causes the CPU to heat to 75C+. I know it now, because I can track its temp. in HA.

The hypothesis is confirmed.

temperature chart of the CPU, a spike is detected at blog publish time, because of activitypub pluginhttps://blog.rozman.info/proxmox-server-temperature-tracking-in-home-assistant/

#2 #fediverse #homeassistant #Proxmox #yaml

image/jpeg
image/png

danielsreichenbach, 1 month ago

So I had a bit of a unpleasant experience with #proxmox and trying to successfully do a PCI(e) Passthrough.

In my cluster, I have a few machines running on an AMD Ryzen 7 4800U with Radeon Graphics. Following the Proxmox WIki guide, I kinda managed to pass the APU into a guest.

The unpleasant side effect was that following that, the host then lost control over the remaining PCI devices too, as in IO, network, etc. First thing to happen of course was all OSDs on that host just disappeared.

pieceofthepie, 1 month ago (edited 1 month ago)

Don't enable your #Proxmox firewall without reading the instructions, or you will have a very bad time.

Shit.

#SelfHost

mttaggart, 1 month ago

Brilliant move by #Proxmox to integrate this tool: an ESXi import wizard to make it simple to move your VMs over. forum.proxmox.com/threads/new-import-wizard-available-for-migrating-vmware-esxi-based-virtual-machines.144023/

vordenken, 1 month ago

A few weeks ago I bought a terramaster NAS (because it was the only device you could install other OSes like proxmox or truenas on it) and now UGREEN published a kickstarter with their new NASes which can do the same but are much newer in terms of hardware…

Should I buy a UGREEN and sell my terraform…?
#NAS #Proxmox #TrueNAS #UGREEN #Hardware

LeoBurr, 2 months ago

It's kinda mesmerizing watching the core speeds on one of the i7-12700Ts in the #Proxmox Cluster (the one that runs Tiggi.es presently) dynamically shift cores anywhere from 1400Mhz to 4.62GHz quickly, and on an as-needed basis. The low base speed saves energy, but it'll instantly pop cores up to speeds within its thermal/power limit envelope, so for lightly-threaded workloads, it can perform as well as beefier chips.
#homelab #servers #cpu

Screen grab of "watch -n0 "grep Hz /proc/cpuinfo" off of a Proxmox node. 20 logical CPU cores with a base of 1400MHz flickering up to as high as 4.62GHz per core as processes require it.