bbgeek17's latest activity
-
The deprecation itself was not strongly influenced by that, but the decision to communicate it more actively was in fact primarily driven by it. Normally, we only mentioned it on the side once a new kernel became the default. In the past, we... -
bbgeek17 reacted to Johannes S's post in the thread Hardware sizing guidance for Proxmox production cluster with
Like.
Obligatory reminder regarding Ceph: https://forum.proxmox.com/threads/fabu-can-i-use-ceph-in-a-_very_-small-cluster.159671/ Please note, that Udos Writeup is a little extreme since he assumes, that you want to survive the outage of two nodes... -
bbgeek17 replied to the thread Kernel 6.14 - End of Support.Out of curiosity, is this decision primarily driven by the recent wave of Kernel security vulnerability disclosures, or has there been a particular subsystem or area in the 6.14/6.17 series that has proven especially difficult to stabilize...
-
bbgeek17 replied to the thread Stockage Type.Hi @CIRE, welcome to the forum. The best _supported_ option is LVM. There are multiple articles that go over the details of the configuration. We wrote one that is iSCSI oriented, however beyond actual physical connectivity the steps to bring up...
-
bbgeek17 reacted to LnxBil's post in the thread Hardware sizing guidance for Proxmox production cluster with Like.
This is not the default query you would ask just in the forums. To answer this properly, best to contact a proxmox partner for a tailored setup. Information is just not enough to answer properly. Your money bounds would also be very important...
-
bbgeek17 replied to the thread Hardware sizing guidance for Proxmox production cluster.Hi Nadee, This is a pretty common design pattern we see for production Proxmox clusters at scale for folks coming from VMware. The good news is that what you're describing is absolutely achievable. That said, before anyone can give you truly...
-
bbgeek17 replied to the thread Clustered iSCSI as LVM on LVM-Thin SAN.@d.oishi , You are correct: regardless of the layer at which thin provisioning is implemented, careful monitoring must be in place. Unexpectedly running out of space is rarely handled gracefully by operating systems or applications. Cheers...
-
bbgeek17 replied to the thread Clustered iSCSI as LVM on LVM-Thin SAN.Using thin pool inside your storage device is completely independent of client connectivity. You will be completely fine using that option. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
I can't find a better place to put this, but why are the forums so painfully slow? I don't know when this started, but traversing the forum, searching for stuff, posting a thread or comment, all of it is painfully slow. What's up with that?
-
bbgeek17 replied to the thread NVMe/U.2/U.3/etc hot-swap?.The hot-swappability of NVMe disks is not directly controlled by PVE itself. It is primarily a function of the underlying hardware (CPU, motherboard, chassis, BIOS/firmware) and software (kernel), as well as the ability of userland components...
-
bbgeek17 replied to the thread Dutch Proxmox Day 2026.Happy to hear about this! There is always a lot of good feedback from this gathering! Sincerely, Blockbridge Team. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
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...
-
bbgeek17 replied to the thread NFS Share status unknown on 2 of 5 nodes.PVE uses native Linux means of connecting NFS, i.e. Ubuntu-based Kernel and Debian-based userland. These are used in millions of nodes world-wide. There are many possibilities here, for example,a bad NIC/Cable that is affected by solar flares, a...
-
bbgeek17 replied to the thread NFS Share status unknown on 2 of 5 nodes.Can you manually mount the NFS share on the problematic nodes when the issue is present? Are you sure there is duplicate IP on the network at that time? Have you compared all package versions, including Kernel, across the nodes? Without logs and...
-
bbgeek17 replied to the thread QEMU 11.0 available on pve-test and pve-no-subscription as of now.Exciting! We will put this into our CI/CD. Thank you! Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread proxmox (VSphere VMWare to Proxmox migration).If it were me, I would use it to confirm that the hardware is broadly compatible (for example SCSI controllers, graphics adapters, and similar devices). It could also help identify which kernel modules are being loaded and potentially highlight...
-
bbgeek17 replied to the thread proxmox (VSphere VMWare to Proxmox migration).That user never came back to report on their progress or lack thereof. My recommendation to try a new OS install still stands. Using recovery boot is another option that previous reported was not quiet comfortable with. Proxmox team does not...
-
bbgeek17 replied to the thread community.proxmox.proxmox_kvm not setting VLAN Tag on update.Hi @mosespray , the Ansible modules are not maintained by PVE staff. I'd recommend reaching out to Ansible team/maintainer - perhaps via github issue. I believe these modules are using API to communicate to PVE. You could try to troubleshoot...
-
bbgeek17 replied to the thread proxmox (VSphere VMWare to Proxmox migration).Take a look at this thread, there may be some useful information there for you: https://forum.proxmox.com/threads/proxmox-9-1-4-import-suse-vm-from-esxi.179180/ Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
-
bbgeek17 replied to the thread [SOLVED] Are there any companies that extensively use PVE in daily production environments?.While these threads are storage-slanted, the feedback it the threads is from companies running successful businesses, almost exclusively on Proxmox Virtualization Environment...