Recent content by talos

Proxmox VE 9 may help with the new snapshot feature for thick LVM, but its tech preview for now.

I see this on Proxmox with 2025 and 11. I have some instances at NetCup (Hoster using KVM), same issues but with the disadvantge that i cant play with host/cpu settings. All on AMD Epyc 96xx

I solved it by launching the build in uefi shell of my server and startet grubx64.efi by hand, it looks like the boot entry tries to boot bootx64.efi which does not work for some reason. I did a grub reinstall and hope the next boot works without interruption.

Same issue with Proxmox Enterprise.

You can get a almost working image from https://fra1lxdmirror01.do.letsbuildthe.cloud/images/ubuntu/noble/amd64/default/ (rootfs.tar.xz), but you have to remove the yml file from /etc/netplan directory.

Hi Fiona, good to know. I ran 24.04. from linuxcontainers.org before i pulled pve-containers from pvetest and using the official template. The templates from linuxcontainers.org almost work out of the box including console except network, i had to remove netplan yml config from /etc/netplan if...

pve-container 5.1.10 alone is not enough, network and console does not work with 24.04. containers.

PBS maintanance does lots of reorganization and disk writes, that is the reason for SSDs in PBS. Cheap / non enterprise SSDs will wear out quiete fast.

I know your pain, same happend to me and not just ones.

We are on 7.4-3 here, no issues with Azure AD or Keycloak (two different installations). If it never worked, check your client id and key again.

Normaly acme likes environment variables like: AZUREDNS_SUBSCRIPTIONID="..." AZUREDNS_TENANTID="..." AZUREDNS_APPID="..." AZUREDNS_CLIENTSECRET="..." But i never used the acme Azure Plugin in Proxmox so give it a try, maybe line by line or delimited with ; or ,

Auf deinem System ist bestimmt cfdisk installiert und ich glaube auf CentOS 7 unterstützt cfdisk es auch schon extend/erweitern, das ist deutlich einfacher als sich mit fdisk rumzuschlagen.

Es sind drei Schritte erforderlich: * Virtuelle Platte vergrößern * Partition oder LVM vergrößern * Dateisystem vergrößern Ich glaube bei dir fehlt der zweite Punkt.

Installier dir mal die inotify tools mit "apt install inotify-tools" und dann schau mir "inotifywait -mr /zPool/postgres" was da so passiert. Inotify zeigt dir alle Dateisystem actions an.

And today this issue is back, i took a quick look into pveproxy/access.log. I can see there is a callback which starts with ?code=... and a long string which is about 1066 bytes long, followed by some more stuff like state=, session_state= and so on. Maybe the issue is that code= is over 1024...