Latest activity
-
JJohannes S reacted to _gabriel's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with
Like.
Never expose 8006 port publicly. https://forum.proxmox.com/threads/proxmox-virtual-environment-security-advisories.149331/post-867929 -
SInisterPisces replied to the thread [PDM 1.1.7] Questions re: Multiple Endpoints for the Same Node (Single-Node Remote).Thanks again. :) Just to be explicit for anyone who finds this later (and also for me, who managed to confuse myself after marking this as SOLVED), for the IP/fingerprint-based endpoints, the fingerprint is from pve-ssl.pem, correct? On my... -
Wwolframio replied to the thread Kernel 7.0.14-14-pve: immediate reset + CPU machine check when igb loads on I350 (Dell XC730xd) — 6.14 unaffected.Dell R730xd here, latest proxmox, no issues so far (never show up)
-
Wwolframio replied to the thread HPE DL380 GEN9.i have a R730XD, latest Proxmox run without issues, what is the problem with the DL380?????
-
SInisterPisces posted the thread [PDM 1.1.7] What is the recommended RAM configuration (4 GiB) based on? How does RAM usage scale? in Datacenter Manager: Installation and configuration.Ref: https://pdm.proxmox.com/docs/installation.html The above recommends "minimum 4 GiB for the OS." I installed the OS on to an ext4-formatted disk. With one (1) single-node Remote added to PDM, I'm seeing ~ 415 MiB of RAM usage. That's about...
-
SInisterPisces posted the thread [PDM 1.1.7] 2FA for Administrator Accounts on Remotes used by PDM? in Datacenter Manager: Installation and configuration.Hello, As a preamble, here's my setup: I'm currently testing PDM with a single-node PVE Remote cluster (that mostly just exists to test PDM). I've created an Administrator-privileged account on the PVE Remote cluster for PDM to use to monitor...
-
SInisterPisces replied to the thread [SOLVED] [PDM 1.1.7] Change Remote Name without Deleting Remote: Is This the Correct Procedure?.I just tried this, and it seems to have picked up the change in the GUI without me rebooting. I'm not even sure I manually reloaded the page. In any case, that worked. Even better than expected. :)
-
Ssiren4161 replied to the thread New router, PVE host can't connect to network at all.Oh gosh, I've found the error. My interface is actually eno2 but /etc/network/interfaces had eno1. It's working now. Thanks, all. I'd like to learn something here. Why would my interface name change in the process of carrying my host PC from one...
-
Ssiren4161 replied to the thread New router, PVE host can't connect to network at all.Great thread, thank you for the link and thanks @UdoB for writing it. Following this tutorial, I ran ip link and returned state DOWN for my interface eno1. I have tried several cables and the LEDs on the router and NIC are illuminated. I have...
-
Ssiren4161 replied to the thread New router, PVE host can't connect to network at all.Thanks, please see the outputs in the attached photos. Yes, I've tried several. Unfortunately I don't have a switch available, but I have tried two different routers and multiple ports on each.
-
-
PIt still works with current kernels as the io_uring bug has been fixed. According to https://www.kernel.org/doc/html/latest/process/maintainers.html OCFS2 is actively maintained.
-
Ppalladin9479 replied to the thread PVE+ISCSI.Yes random guy on forum says it's not for some random reason... According to the maintainers, the ones maintaining the code, OCFS2 is actively maintained. Oh the code base for the non-kernel tools used in Debian and RHEL distros...
-
Wwendellrodriguez replied to the thread High VM-EXIT and Host CPU usage on idle with Windows Server 2025.Please try to set CPU to native like a host and testing again.
-
SteveITS reacted to complexplaster27's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing: Boot-volume operation on vioscsi 0.1.302 Multiple reboots and device checks Five active VirtIO SCSI controllers Overnight... -
G_gabriel replied to the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth.Never expose 8006 port publicly. https://forum.proxmox.com/threads/proxmox-virtual-environment-security-advisories.149331/post-867929
-
G_gabriel reacted to complexplaster27's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing: Boot-volume operation on vioscsi 0.1.302 Multiple reboots and device checks Five active VirtIO SCSI controllers Overnight...
-
Ccomplexplaster27 replied to the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive".Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing: Boot-volume operation on vioscsi 0.1.302 Multiple reboots and device checks Five active VirtIO SCSI controllers Overnight...
-
bbgeek17 replied to the thread From LVM storage screen, please allow binding LVM volume to VM.I would always recommend to stay within the bumpers of the system. Especially when an easy to use procedure is available. IMHO this is such a rare situation that complicating UI with handling this case is counterproductive. That said - feel free... -
MMDSOperator replied to the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth.Proxmox VE 7.1 - cryptojacking rootkit + root SSH backdoor: full teardown TL;DR Two PVE 7 hosts were compromised and running an XMRig cryptominer hidden by a preload rootkit. The same "install_and_mine.sh / libhide" toolchain planted: A...
-
Ssantiagobiali replied to the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive".The TRIM issue occurs because Microsoft introduced some trim functions not yet implemented in virtio's driver. It's not related to ZFS's backend. I've added what I found in this github issue...
