Search results

old stable normaly gets all security relevant Updates for at least a year or more. but thats not the main point. even if you are a very security affine sysop (and I am) there are reasons or circumstances where you cannot upgrade a virtualization stack in a timeframe given by a 3rd party eg...

I would like to suggest that on "old stable" (Bullseye, PVE7) there are not "YOU ARE EOL" messages shown on the GUI. I think it's unneccesary stress between IT and customer to force an update where it's not security relevant. imo stable and old-stable should be "warning free" just had an...

it is a good default to block cifs for home users. cifs is not meant to be a "remote" protocol

thomas-krenn.com bietet auf proxmox getestete Systeme an. Du kannst das "ausnutzen" und einfach einmal schauen, was sie verbauen. Und damit sie auch etwas davon haben: thomas-krenn ist wegen dieses services und auch sonst in allen belangen ein absolut empfehlenswerter Hardware Lieferant. wir...

and you see - no offense - that a backup would have made life so much easier :) even a small usb stick on a host and regularily cp /etc and config.db (or a scp, rsnyc, cp to nas etc...) is better than no backup cant say this often enough

imo decrease it a lot. upgrading a large hyperconverged production cluster is.... challenging :) and yes, i too think that scaling is much easier that way. depends on your situation, you need more hardware, more rackspace but we dont do hyperconverged clusters ever. we also have more than...

as we need cpu and ram for workloads anyway we dropped the concept of hyperconverged and seperate storage (ceph, nfs) from workload clusters. and we dont go further then 20 nodes/Cluster (the only disadvantage of pve imo, scalability)

wir hatten mehrmonatige Versuche mit Backups auf Hetzner Storage Boxen gemacht. System war nicht PBS aber auch ein Backup mit chunks und deplizierung. sehr viel io. bei uns kam es zu Datenverlust, vermutlich auch weil die Storages eher "unzuverlässig" sind, was connectivity betrifft. wir sind...

maybe your physical switches block vlan 1 as it is the default management vlan

I guess the "cluster" way to deal with it is * move vms from the missconfigured node * drop the node * setup new node (new name, new keys) * move vms back * goto 10

thanks. i knew. but at the moment the spam amount is overwhelming. my fingers forced me to post a "rant". thank you for your excellent work anyway!

i am sure team is aware of the problem but the mass of spam in the forum is annoying. i use rss feed and i see it all :)

pmg is not an imap server. if you are sesrching for a full featured 'mailserver' take a look for mailcow as example pmg has another purpose

ich würde dem Kunden für die Migration ein NAS (nfs) zur Verfügung stellen und danach die VMs auf ceph migrieren

as I said before, we are running quite large freeswitch installations on "default" settings. guest os is debian. we dont have latency problems.

we are running several freeswitch installations without any special configurations. normaly with "host" cpu type

I think the forum does not reflect the position of proxmox within the hypervisor market very well. you could think that many users are homelab or very small..many questions about networking e.g. are very very low profile... so. i think that pve is a player in a quite professional and wealthy...

probably, send more details plz: ioeekjlk@duck.com (one time email)

we dont use it at all. we deploy nftables with ansible

why prevent? there is probably a reason for them to start up take a look, e.g. why your CPU has high load from time to time..i guess this releates to the fans spinning up