Und was soll der geneigte Leser antworten? Du hast nicht einmal eine Frage formuliert. ;-)
Beschreibe mal dein Setup: was für einen (mehrere?) Rechner verwendest du für PVE? Wie hast du installiert? Ist die Installation nagelneu, oder lief sie...
Und was soll der geneigte Leser antworten? Du hast nicht einmal eine Frage formuliert. ;-)
Beschreibe mal dein Setup: was für einen (mehrere?) Rechner verwendest du für PVE? Wie hast du installiert? Ist die Installation nagelneu, oder lief sie...
Wenn es im Bios erkannt wurde, sollte auch Proxmox keine Problene haben. 256GB RAM sind überhaupt kein Limit für Proxmox. Ist eher noch im unteren Bereich. Daher wie schon darauf hingrwiesen: Was zeigt und erkennt das Bios?
Great! :-)
Please tell us shortly what you did, as it may be helpful for future readers. And please tag this thread "Solved" via the "Edith thread" Button at the top right.
Oh..., and welcome in this forum!
Same here on my Proxmox with Ryzen 5700G. Seems to be a little bit more efficient. I can observe it also on my 4 LMDE7 (debian 13 based) desktops with Ryzen CPU with backport kernel 7.0.4. For the Debian VM's itself I can't say more, because...
Jup, for stuff like that I usually boot a live linux from the virtual CD drive.
Something like an Ubuntu or one of the many system rescue Linux distributions that come with all the needed tools preinstalled.
I finally managed to get some time to spin up a new instance.
Exact same hardware setup as original post, but with a different SSD. Previous storage drives have been disconnected.
PVE: 9.0.3
Kernel: 6.17.9-1-pve
Repeated prior steps and...
I always assumed that you could get support from any other company but the enterprise repository access does indeed look a lot like a license (regardless of location).
Maybe one could keep the packages from the ISO releases (which is a public...
I sent an e-mail to Bjorn at the address listed on the linked page from celemine and that got the ball rolling. I believe they referenced this thread to get the required changes into the kernel. Not sure what else you'd have to do or how...
I see that 7.0.2-4 is the latest available via the Updates section of the node. Can one safely assume that since it's a later/higher version that it should also work?
Some more info that might be useful:
ip -d link show tailscale0
3: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none promiscuity 0 allmulti 0 minmtu...
I have just done a test with pure WireGuard, and it does not show the issue:
10:58 user@samba:~ > iperf3 -c 192.168.99.2 -t 10
iperf3 -c 192.168.99.2 -t 10 -R
Connecting to host 192.168.99.2, port 5201
[ 5] local 192.168.99.1 port 60466...