Latest activity
-
SStereoscope replied to the thread 9.2 ISO verification, and best practices security wise.I only looked at the "proxmox-ve_9.2-1.iso.sha256" file, saw only one hash and assumed the asc file also only had one signature. Never seen a dual signature signature before. Makes sense now! Never assume as they say. Thanks.
-
SStereoscope reacted to LnxBil's post in the thread 9.2 ISO verification, and best practices security wise with
Like.
The signature file contains two signatures, one from bookworm and one from trixie: $ gpg --list-packets proxmox-ve_9.2-1.iso.asc # off=0 ctb=89 tag=2 hlen=3 plen=563 :signature packet: algo 1, keyid A7BCD1420BFE778E version 4, created... -
LnxBil replied to the thread Qemu-Gest-Agent.It's fairly new, have you tested them well? The page in the wiki has been updated yesterday, that v302 is tested and not yet ready for production -
By using a hook script, you can automatically perform a rollback only when the VM shuts down. mkdir -p /var/lib/vz/snippets cat << 'EOF' > /var/lib/vz/snippets/shutdown_rollback.sh #!/bin/bash if [ "$2" = "post-stop" ]; then ( sleep... -
LnxBil replied to the thread DC and DR Setup.Proxmox Backup Server is the answer, if you want to use other backup software, please ask in their respective forums. It is also highly advised to use a Proxmox consultant for commercial best practices which also helps with implementation...
-
GG0ldmember reacted to fabian's post in the thread Hash Sum mismatch in no-subscription repo with Like.
this seems to be a hardware issue on the de2 CDN node, which we've just taken out of rotation. there's two packages which were corrupted - ceph-mgr as noted here, and libzfs7linux_2.4.4-pve1_arm64.deb I am not sure how the result in #6 above...
-
GGreyAreaUK posted the thread Passing a second SATA controller through to a VM in Proxmox VE: Installation and configuration.Hi - sorry, I know this has been asked before but I can't seem to find a definitive solution. Aim: to install under a Debian (probably) VM the Docker container 'Automatic Ripping Machine'. My understanding is that for this to work I have to...
-
-
UdoB reacted to LnxBil's post in the thread 9.2 ISO verification, and best practices security wise with Like.
The signature file contains two signatures, one from bookworm and one from trixie: $ gpg --list-packets proxmox-ve_9.2-1.iso.asc # off=0 ctb=89 tag=2 hlen=3 plen=563 :signature packet: algo 1, keyid A7BCD1420BFE778E version 4, created...
-
LnxBil replied to the thread 9.2 ISO verification, and best practices security wise.The signature file contains two signatures, one from bookworm and one from trixie: $ gpg --list-packets proxmox-ve_9.2-1.iso.asc # off=0 ctb=89 tag=2 hlen=3 plen=563 :signature packet: algo 1, keyid A7BCD1420BFE778E version 4, created...
-
81.7% of data requests are for metadata. I assume ZFS can do with less memory to maintain a high hit rate? Pfsense workloads don't perform heavy write IO like databases/webservers etc.. Below numbers are for a full host. We will not add...
-
Ddick_fiddler69 posted the thread Windows Server 2025 EventLog crashes with x86-64-v4 CPU after Windows Update — 0xC000001D illegal instruction in Proxmox VE: Installation and configuration.Environment: Proxmox VE (latest) Host CPU: Intel Xeon Platinum 8260 @ 2.40GHz (AVX-512 capable) Guest: Windows Server 2025 Datacenter (build 26100.33438) Machine type: pc-q35-10.1 QEMU Guest Agent: 110.0.2 Problem: After installing Windows...
-
cwt replied to the thread Bad Windows network performance - how to improve?.Your latest tests actually suggest that VirtIO itself is not the main bottleneck. The important result is that the same Windows VM reaches ~12–14 Gbit/s single stream in both directions on an otherwise idle EPYC 9175F host. Once the host gets... -
Nnetfront 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 I would definitively put a VPN before the port 8006. If your customers are annoyed remind them, that you don't want to risk another incident and that it's in their best interest to make life harder for ransomware gangs.
-
Mmutex reacted to ggoller's post in the thread Debian 13 LXC template: IPv4 DHCP + IPv6 SLAAC launches DHCPv6 and breaks backups with Like.
https://lore.proxmox.com/pve-devel/20260911095623.429947-1-g.goller@proxmox.com/ Debian doesn't have a newer ifupdown2 version than 3.0.0, nothing we can do there.
-
Mmutex replied to the thread Debian 13 LXC template: IPv4 DHCP + IPv6 SLAAC launches DHCPv6 and breaks backups.Quite alright :) Thank you!
-
Ffh4352 replied to the thread Problem firewall dropping packet.Has there ever been a solution found or published for these issues, the other threads dont seem to have reached a proper conclussion either. We are experiencing a similiar issue on PVE 9.2.4 with SFTP uploads randomly timing out on the very first...
-
ggoller replied to the thread Debian 13 LXC template: IPv4 DHCP + IPv6 SLAAC launches DHCPv6 and breaks backups.https://lore.proxmox.com/pve-devel/20260911095623.429947-1-g.goller@proxmox.com/ Debian doesn't have a newer ifupdown2 version than 3.0.0, nothing we can do there. -
UdoB reacted to Johannes S's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
Thanks for the writeup. One thing I'm missing: Did you you recreate the cluster with a non-EOL version (PVE9) or did you resetup them up with an EOL version? If you did the latter I would reconsider since although you might have closed this...
-
UdoB reacted to netfront's post in the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth with Like.
We were compromised through CVE-2023-54391 on 1–2 September and rebuilt 22 nodes from backup. A few of the post-exploitation findings cost us real time, so probably worth sharing here. Getting the obvious out of the way first: we were on 7.4...
-
UdoB reacted to Johannes S's post in the thread Proxmox in enterprice environments with shared fc storage with Like.
Or to be more blunt: Just because somebody want everything to work like vmware that doesn't mean that it makes sense. ProxmoxVE and the underlying technologies are after all a different system with it's own tradeoffs, pros and cons.
