VictorSTS's latest activity
-
VictorSTS replied to the thread Proxmox behind HAProxy SSL backend and frontend results in no encryption at all..You are using an http mode frontend with a tcp mode backend for pve, which doesn't make much sense: haproxy will terminate the ssl tunnel and send clear text traffic to PVE which won't work. Change the backend mode to http and use something like... -
VictorSTS replied to the thread ServiceNow discovery.In any case, the "ServiceNow" manual surely details what kind of access and privileges the user needs. In the end PVE is "just" Debian, so they should have clearly defined instructions on what's needed for ServiceNow to work properly in this...
-
More details here: https://gitlab.com/qemu-project/qemu/-/issues/3286
-
VictorSTS replied to the thread Glusterfs is still maintained. Please don't drop support!.Know little about Gluster, so can't compare features/performance, but wanted to clarify some points regarding Ceph (again): Among other tasks, Ceph MON will provide a copy of the CRUSH map to every component in the Ceph cluster, including...
-
VictorSTS reacted to t.lamprecht's post in the thread Glusterfs is still maintained. Please don't drop support! with
Like.
FWIW, forky isn't released, and it's still about half a year until the freeze period starts, and until then lots of packages can still get dropped. Debian cares a bit less about the reasoning we had here, there is no support (and thus liability)... -
VictorSTS replied to the thread Questions about the dynamic CRS.This is absolutely needed and has to be very precise. I.e. which exact metric is used for both CPU and Memory "loads": CPU load vs CPU usage vs CPU pressure, Mem usage vs Mem pressure. Currently testing CRS in lab and it seems to allow a node to...
-
VictorSTS replied to the thread how to set quorum 3 on 6 nodes cluster ?.Be mindful that if HA is enabled, around 2 minutes after losing quorum HA will reset the no-longer-in-quorum hosts. If you plan on using pvecm expected N, do it gradually as @UdoB explained above instead of setting it to 3 directly when the whole...
-
For reference: https://bugzilla.proxmox.com/show_bug.cgi?id=4420
-
VictorSTS reacted to fiona's post in the thread QEMU 11.0 available on pve-test and pve-no-subscription as of now with Like.
@shanreich was finally able to reproduce the issue. When the physical NIC does not support the tx-udp_tnl-segmentation: off [fixed] tx-udp_tnl-csum-segmentation: off [fixed] features, the issue can happen. When the physical NIC does support...
-
We will re-evaluate it, but cannot make any promises. What we also look into periodically is reducing the attack surface in general, like we started rolling out some simple but relatively effective approach to block autoloading of various niche...
-
VictorSTS reacted to t.lamprecht's post in the thread Proxmox Datacenter Manager 1.1 released! with Like.
We are pleased to announce the release of Proxmox Datacenter Manager 1.1! This point release focuses on expanding visibility and automation for large-scale, multi-site deployments. Our main focus for this iteration has been introducing...
-
VictorSTS reacted to t.lamprecht's post in the thread Proxmox Datacenter Manager 1.1 released! with Like.
We are pleased to announce the release of Proxmox Datacenter Manager 1.1! This point release focuses on expanding visibility and automation for large-scale, multi-site deployments. Our main focus for this iteration has been introducing...
-
VictorSTS reacted to t.lamprecht's post in the thread Proxmox Virtual Environment 9.2 available! with Like.
We are excited to announce the release of Proxmox Virtual Environment 9.2. This release focuses heavily on platform refinement, stability, and core optimization. Proxmox VE 9.2 is built on the robust Debian 13.5 "Trixie" and ships with Linux...
-
VictorSTS reacted to fiona's post in the thread QEMU 11.0 available on pve-test and pve-no-subscription as of now with Like.
@Upstairs_Cycle384 Not sure why Windows still detects it, maybe querying the CPUID leaf directly still works or something. Regarding the other question, there is a custom CPU model editor coming with the next Proxmox VE 9.2 point release. There...
-
Hi guys! As some of you might know we are organizing the Dutch Proxmox Day again. Last year we decided to reach beyond our borders and have all presentations in English. Which was a great success since almost half of the audience consisted of...
-
VictorSTS reacted to fiona's post in the thread QEMU 11.0 available on pve-test and pve-no-subscription as of now with Like.
There is a new QEMU 11.0 package available in the pve-test and pve-no-subscription repositories for Proxmox VE 9. After internally testing QEMU 11.0 for over two weeks and having this version available on the pve-test repository for over a week...
-
VictorSTS reacted to complexplaster27's post in the thread [Hint] Dell iDrac tools for PVE 8.4 / Debian 12 with Like.
Hello, I just found this thread on google. With the latest version OM-iSM-Dell-Web-LX-6100-4104.tar.gz on Proxmox 9.1.9 UBUNTU24/x86_64/dcism-6.1.0.0-4104.ubuntu24.deb I ran dpkg -i dcism-6.1.0.0-4104.ubuntu24.deb Said this: Selecting...
-
VictorSTS replied to the thread Proper way to set up a Proxmox cluster on a dedicated VLAN (separate from Management).For a fully redundant corosync, use at least two logically and physically independent links. Management. That will be populated automatically by PVE on install using the IP address you configure during setup. Yes, but you should add at least a...
-
VictorSTS replied to the thread "copy.fail" mitigations and pve-container package.It is, but: There won't be an updated kernel for PVE7 and permanently disabling the module seems the only option (which is fine for me). And that doesn't answer my question about why the official mitigation statement mentions the package...
-
VictorSTS posted the thread "copy.fail" mitigations and pve-container package in Proxmox VE: Installation and configuration.As I understand it, the "copy.fail" vulnerability is mitigated on PVE by either: Upgrading the kernel on PVE 8 or 9. Disabling module algif_aead and unloading it. The official post about this vulnerability [1] also mentions package...