Latest activity
-
Ggfngfn256 reacted to Neobin's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with
Like.
So, you now got your security advisory for a vulnerability, in a over three year old version of a software component, which was at the time it would have been relevant neither internally discovered nor from anyone reported and hopefully also not... -
Ggfngfn256 reacted to Johannes S's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
Then you are still vulnerable due to the known and unknown security issues in PVE8 (which is EOL) and Debian Bookworm. The fix is to upgrade to the latest supported version of PVE aka PVE9 with every updated installed. Everything else is just...
-
Aarzhost replied to the thread 2. IP - sehe den Wald vor lauter Bäumen nicht.eth0:0 kein echtes separates Interface ist, sondern nur ein Alias für eine zusätzliche IP auf eth0. Dein aktuelles Setup fügt die IP zwar korrekt hinzu, leitet aber keinen eingehenden Traffic automatisch zu einer VM oder einem anderen Ziel...
-
JJohannes S reacted to LnxBil's post in the thread Official status of support for multiple backup solutions with Like.
Do you mean with PBS using the same PVE API as PBS? I don't think that PBS and other backup solutions can send stuff to each other was your question suggests to me.
-
Yyubao reacted to quarcskter's post in the thread [SOLVED] Problems installing Windows 10 VM: No input when language setting window appears with Like.
It looks the issue is in the RAM amount. The OP assigned 8 GB of RAM to 32bit OS and it couldn't start properly. If you start the VM with 3GB the input will work.
-
Llegolas posted the thread 2. IP - sehe den Wald vor lauter Bäumen nicht in Proxmox VE (Deutsch/German).Servus, alles was mit eth0 zu tun hat funktioniert einwandfrei. Nun möchte ich allen eingehenden Traffic für die IP 152.53.175.70 auf eth0:0 umleiten. Kann mir jemand sagen was ich falsch mache? Danke auto lo iface lo inet loopback auto...
-
Wwaynej replied to the thread KVM NX huge page recovery burns a core per guest on kernel 7.0.x.That is possible, AFAIK, it should only affect systems when iTLB multihit (CVE-2018-12207) mitigation is enabled. If the CPU is not vulnerable, the mitigation has been turned off or if nx_huge_pages_recovery_ratio=0 you wouldn't any CPU time for...
-
Ttoumz replied to the thread Issues installing proxmox on Lenovo X3850 X6.It's a used pc..
-
news replied to the thread Issues installing proxmox on Lenovo X3850 X6.And the lenovo m720q is new, so as all Parts? The Bios Version and the Bios Batterie same? Is the lenovo m720q a real Server Hardware or more a tiny desktop PC? -
Mmovacialex replied to the thread Question on Signature on Spamassassin clamav.Hello @j.theisen Thank you. Best regards. Alex
-
Llhzhu reacted to t.lamprecht's post in the thread Proxmox Virtual Environment now available for 64-bit ARM (arm64)! with Like.
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only. Proxmox VE 9.2 for arm64...
-
gurubert posted the thread Purpose of pve-dbus-vmstate@VMID.service? in Proxmox VE: Installation and configuration.Hi, what is the purpose of the pve-dbus-vmstate@.service? It starts a Perl script /usr/libexec/qemu-server/dbus-vmstate but not for every VM. We have seen it running for a few VMs and sometimes it fails: Aug 31 15:17:22 pve56 systemd[1]... -
JJeanL reacted to Neobin's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
So, you now got your security advisory for a vulnerability, in a over three year old version of a software component, which was at the time it would have been relevant neither internally discovered nor from anyone reported and hopefully also not...
-
JJeanL reacted to Johannes S's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
Then you are still vulnerable due to the known and unknown security issues in PVE8 (which is EOL) and Debian Bookworm. The fix is to upgrade to the latest supported version of PVE aka PVE9 with every updated installed. Everything else is just...
-
Ttoumz replied to the thread PROXMOX 8.4 and 9 crashes during intallation..Okay!, first I will reset the bios and update it to the latest version, hopefully that might solve the problem.
-
gurubert reacted to Johannes S's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
Then you are still vulnerable due to the known and unknown security issues in PVE8 (which is EOL) and Debian Bookworm. The fix is to upgrade to the latest supported version of PVE aka PVE9 with every updated installed. Everything else is just...
-
gurubert reacted to Neobin's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
So, you now got your security advisory for a vulnerability, in a over three year old version of a software component, which was at the time it would have been relevant neither internally discovered nor from anyone reported and hopefully also not...
-
OOnslow replied to the thread PROXMOX 8.4 and 9 crashes during intallation..Welcome, @toumz Try also booting without "quiet" option - maybe some hint will be visible. And execute Memtest for a couple of hours.
-
Uurog reacted to Neobin's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
So, you now got your security advisory for a vulnerability, in a over three year old version of a software component, which was at the time it would have been relevant neither internally discovered nor from anyone reported and hopefully also not...
-
JJohannes S reacted to Neobin's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
So, you now got your security advisory for a vulnerability, in a over three year old version of a software component, which was at the time it would have been relevant neither internally discovered nor from anyone reported and hopefully also not...