I encounter a similar maybe related trim problem that is solvable by reducing the machine version to 9.2+pve1. I was able to replicate this in a fully patches W2K25 server template in CEPH and ZFS...
Hi all,
Closing the loop on this thread with good news: the issue is fixed.
After corosync and libknet1t64 were updated to 3.1.10-pve3 / 1.35-pve1 (available now in pve-no-subscription), ip_dscp works as documented. I tested on two separate...
Thank you for your feedback.
When I refer to “client,” I’m actually talking about internal users of the applications. Currently, certain (technical) staff members have the autonomy to manage snapshots, restart VMs, or perform other types of...
The thing with setups that aren't officially recommended or supported by the developers of a product is that they're unsupported for a reason: they simply aren't something the developers explicitly test or validate.
For example, when the Proxmox...
Genau darum würde es mich ernsthaft interessieren. Dank fixen IPs kannst du die Festen Regeln, bzgl Netzzonen IMHO viel eleganter und eventuell sogar sicherer umsetzen. Aber wenn du nicht willst, nehmen wir halt ein Bier zusammen :)
Here's my current thoughts/opinions about running docker/podman in CTs
- It currently works fine (at least in a debian CT)
- It might break on docker (related) or kernel updates
- Breakage is likely to be fixed soon but you'll have to be patient...
No and propably never will be since they use the same features of the kernel ( namespaces, cgroups etc) and host system ( apparmor etc ) so any update might introduce a breaking change. This is more likely with major upgrades ( like PVE8 to...
Something I forgot: ProxmoxVE9 introduced a new, still in tech-preview-feature which allows converting oci ( aka docker ) container images to lxcs. To be honest I'm not a big fan since this procedure destroys the immutability which is the biggest...
The thing with setups that aren't officially recommended or supported by the developers of a product is that they're unsupported for a reason: they simply aren't something the developers explicitly test or validate.
For example, when the Proxmox...
Thank you for your feedback.
When I refer to “client,” I’m actually talking about internal users of the applications. Currently, certain (technical) staff members have the autonomy to manage snapshots, restart VMs, or perform other types of...
Something I forgot: ProxmoxVE9 introduced a new, still in tech-preview-feature which allows converting oci ( aka docker ) container images to lxcs. To be honest I'm not a big fan since this procedure destroys the immutability which is the biggest...
A couple of comments:
1. Since you're deploying client assets in a cluster, there are two components to consider- first, what is your target overprovision/overall host load threshold and second- when deploying a new asset, you have a choice of...
I encounter a similar maybe related trim problem that is solvable by reducing the machine version to 9.2+pve1. I was able to replicate this in a fully patches W2K25 server template in CEPH and ZFS...
Thank you for bringing that to my attention and maybe I can add to that. My template is on the current patch level, so the problem may not be the same, but very similar.
Hi, a few questions:
License — there's no LICENSE file in the repo. What license do you plan to use, and can we get explicit permission to use/modify it commercially in the meantime?
Maintenance — last commit was ~3 months ago. Is this actively...
I cannot manage PMG after my admin PC ip address change. I can use SSH and Web-GUI access from a PC in the same subnet. (The routing table is equal on PMG and the second PC).
Tcpdump shows the initial packets are coming to PMG but no outgoing...
Hi,
I'm planning to upgrade pve from 8.4.x to 9.1. The reason is because version 9.2 is still not supported by Veeam. If I proceed with this upgrade I may not be able to perform agentless backup. Correct me if I'm wrong. Is there any way to pin...