VictorSTS's latest activity
-
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...
-
VictorSTS reacted to t.lamprecht's post in the thread Proxmox Backup Server 4.2 released! with Like.
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 reacted to fba's post in the thread Proxmox cluster with SDN Vvlan client isolation with Like.
I wrote a blog article covering this a while ago, maybe it helps: https://www.croit.io/blog/microsegmentation-with-proxmox-ve
-
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 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 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...
-
VictorSTS replied to the thread Subscriptions and new hardware.@niteshadow While technically you could, you are breaking two golden rules: Good practice dictate to have the same package versions on every node. Each server in your cluster needs its own subscription based on its specific socket count. All...
-
VictorSTS replied to the thread Proxmox/Ceph - Disable OSD rebalancing.Seems you are mixing concepts here: the balancer MGR module doesn't do the recovery/backfill when an OSD goes IN/OUT, that is a core feature of Ceph managed by MONs and OSDs, not a MGR module. The balancer function is to spread PGs among all...
-
VictorSTS replied to the thread Proxmox/Ceph - Disable OSD rebalancing.Correct. PVE webUI and ceph status will report that an OSD is DOWN and the Ceph status will be "WARN" as soon as any OSD is DOWN. There will be no email alerts, though. You'll have to monitor Ceph somehow or at least configure MGR alerts module...
-
VictorSTS replied to the thread Proxmox/Ceph - Disable OSD rebalancing.Because that's the minimum ratio of OSD's that will be kept IN no matter what, not the ratio that decides when to trigger a rebalance, which happens as soon as an OSD is marked OUT.
-
VictorSTS replied to the thread Proxmox/Ceph - Disable OSD rebalancing.In a 3 node cluster with size=3, min_size=2 and the default replica rule, Ceph won't rebalance anything if one node fails. To comply with the default rule "three replicas en three OSD located in three different servers" you need 3 servers, if...
-
VictorSTS replied to the thread File restore and symlinks.Well, I didn't said it was solved, but checking the bug report 4995, "Improve file restore .zip format to include symlinks", seems to be solved with v4.0.19 of PBS [1]. That means that it should work when restoring from PBS. Doesn't mention it...
-
VictorSTS replied to the thread backup stop mode doesn't stop the VM.You need to understand how backup works. Specifically in stop mode: VM is running PVE tries to do a shutdown of the VM: If QEMU Agent is configured and running, shutdown signal is issued with it. Else, sends an ACPI signal which guest OS may or...
-
VictorSTS replied to the thread PBS Verify duration on large HDD-based datastore — how to tune settings?.I mean a "RAID0 of two RAIDz2 vdevs". Something like this: zpool create tank \ raidz2 disk1 disk2 disk3 disk4 disk5 disk6 disk7 \ raidz2 disk8 disk9 disk10 disk11 disk12 disk13 disk14 That's true, as I mentioned above: That happens...
-
VictorSTS replied to the thread PBS Verify duration on large HDD-based datastore — how to tune settings?.Good point!! I did assume OP had at least a mirror of NVMe for special device. Should be a mirror of 3 to give it the same redundancy as the HDD part. None of those settings will really help to increase performance on your big zpool on verify...