VictorSTS's latest activity

  • VictorSTS
    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
    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...
  • VictorSTS
    VictorSTS reacted to Neobin's post in the thread Time servers with Like Like.
    For reference: https://bugzilla.proxmox.com/show_bug.cgi?id=4420
  • VictorSTS
    @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...
  • VictorSTS
    VictorSTS reacted to t.lamprecht's post in the thread Kernel 6.14 - End of Support with Like Like.
    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
    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
    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
    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
    @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...
  • VictorSTS
    VictorSTS reacted to tuxis's post in the thread Dutch Proxmox Day 2026 with Like Like.
    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
    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
    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
    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
    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
    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...
  • VictorSTS
    We're pleased to announce the release of Proxmox Backup Server 4.2. This version is based on Debian 13.4 ("Trixie"), uses Linux kernel 7.0 as the new stable default for improved hardware support, and comes with ZFS 2.4 for reliable...
  • VictorSTS
    I wrote a blog article covering this a while ago, maybe it helps: https://www.croit.io/blog/microsegmentation-with-proxmox-ve
  • VictorSTS
    VictorSTS replied to the thread Subscriptions and new hardware.
    Can't see were I've been hostile in any way. I've been trying to propose you methods and alternatives that you didn't like and insist on doing things "the VMWware way". That's simply not how PVE works. PVE it's not a 1:1 replacement, but an...
  • VictorSTS
    VictorSTS replied to the thread Subscriptions and new hardware.
    You can get that very same behavior on PVE, either with or without aditional subscriptions for the new hardware. I've already shown you how to do it without any extra cost. In fact, as Enterprise repo has slightly older packages than...
  • VictorSTS
    VictorSTS replied to the thread Subscriptions and new hardware.
    The way I do it: - Src cluster has subscription. - Update the nodes to latest version. - Install new servers, configure network. - Move subscription to new nodes. - Install latest packages on new nodes. - Setup Ceph, storages, backups, users...