VictorSTS's latest activity
-
VictorSTS reacted to t.lamprecht's post in the thread New Debug Symbol (dbgsym) Package Repository with
Like.
Today we're introducing a dedicated repository for debug symbol packages, reachable at https://dbgsym.proxmox.com/. Debug symbol packages (named <package>-dbgsym) contain the detached debug information for their matching binary package. They are... -
VictorSTS replied to the thread Proxmox + CEPH - using same NICs but different VLANs for public/cluster networks.That's what I usually do: using 2 vlans over the same bond add the benefit that if you ever need to separate the cluster network to a different bond, no Ceph configuration changes will have to be made (i.e. add the cluster network and restart...
-
VictorSTS reacted to Neobin's post in the thread Call for Feature: Native LINSTOR Support with Like.
https://forum.proxmox.com/threads/supported-way-to-extend-the-pve-web-ui-for-a-third-party-package.185017/post-861469
-
VictorSTS replied to the thread DHCP in Proxmox.During PVE install, the ISO installer will try to get an IP from DHCP. If that succeeds, it will configure that IP as static for vmbr0. As you are not very experienced, I suggest that you create a DHCP reservation assigned to the MAC of your PVE...
-
VictorSTS replied to the thread DHCP in Proxmox.Wouldn't it be more precise to say that PVE on DHCP isn't supported without other tweaks even on single node setups? Some services require to resolve the host name to an IP that is currently assigned to the host to work properly.
-
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...