I noticed an issue where I was experiencing a lot of OOM errors within my LXC containers. After updating to Deb13/PVE9.x I found some of my LXC containers at 99% CPU and 99% MEM usage.
Debian 13 has, by default, moved /tmp to a tmpfs.
It...
https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases
Schau hier in der nächsten Zeit ob sich die Empfehlung ändert, wenn du nicht experimentierfreudig bist.
Wir beobachten die Lage und testen selber.
if you do not want to switch to the latest version, see the note here regarding the VSS writer issue: https://pve.proxmox.com/wiki/VM_Backup_Consistency
Fixed with current Stable QEMU Guest Agent v302
( available in .iso https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.302-1/ )
Which version of Proxmox VE are you on? I suspect not a recent one, as the pause and hibernate buttons have been added to the right click menu some time ago.
hi,
at the moment there is no option to weigh CPU load balancing higher than memory usage balancing.
feel free to file a feature request on bugzilla [0]
[0] https://bugzilla.proxmox.com/
https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases
Schau hier in der nächsten Zeit ob sich die Empfehlung ändert, wenn du nicht experimentierfreudig bist.
Wir beobachten die Lage und testen selber.
I wish that nobody was still running PVE 7 and I really hope they don't run it in the same way. It's not news because there are known vulnerabilities against PVE 7 (and the Linux kernel and SSH and other software that old) and it's very likely...
I've seen a similar post on another forum very recently about Proxmox 8 too (from what I understand the user was running a very early version 8 install, maybe 2-3 years old, close to launch date)..
I guess the worry always with these things is...
Gern darfst du die 302 testen. Ich werde auch ein paar VMs hochziehen, aber Produktiv warte ich mal noch etwas ab. Bisher habe ich mit der 271 noch keine Probleme gesehen und auf Reddit sind mir auch keine echten Probleme sondern nur Userfehler...
The Linux kernel has had at least 500 CVE's fixed per release (before LLMs) and your PVE 7 kernel (5.15?) is many version behind, so either one could potentially be the entry point. Whether you had a good password is irrelevant. Proxmox fixed...
PVE 7 and the Debian version it sits on went end of life over two (corrected from three) years ago. The list of vulnerabilities discovered and patched since then is going to be a mile long.
It would even be a bad idea to expose a fully patched...
I just saw an update from Proxmox on their host backup last week, which has its first patches / first implementation. It would be great if you could combine your approach into the official one.
This is rather an old thread, but here I am sharing my thought.
The presence of altname on an interface is not related to the Proxmox VE Network Interface Pinning tool [0]. It is determined by systemd-udevd hardware policy.
Based on the shared...
My sole intention in making this post is to report something that's happening to all Proxmox VE 7 systems exposed to the internet, since there's a zero-day vulnerability in the wild. I'm aware of the "danger" of exposing Proxmox to the internet...
In addition what others already said about patching, no additional security on ports and running EOL software, you should also considering monitor all internet-facing stuff in order to detect non-normal behaviour, e.g. I use on some sites mTLS...
So, you are:
Running a OS that is EOL since two years
Exposing it to the internet
Disabling the firewall
If this is not a troll, I hope the lesson was learned...