bbgeek17's latest activity
-
bbgeek17 replied to the thread Proxmox in enterprice environments with shared fc storage.@rbremer, another AI-generated driver... They've been coming in droves lately. It even modifies the PVE source files! The problem with most AI-generated integrations is that they sound convincing, are thoroughly documented, and are subtly broken... -
bbgeek17 replied to the thread Proxmox in enterprice environments with shared fc storage.@rbremer discussing CSI is a big conversation of its own and deserves a separate thread, but for future readers: which CSI driver is this? Separate from the driver: this type of PVE/K8s combination works, but it isn't reliable. Proxmox tracks...
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Intriguing. Nothing in your data points to a root cause, and it doesn't look like the Dell. Our best guess is a Linux issue. That said, we run a lot of iSCSI with PVE in the field and haven't seen any issues at customer sites. This suggests...
-
bbgeek17 replied to the thread Proxmox in enterprice environments with shared fc storage.You've got it. That's exactly why SUSE put OCFS2 on corosync, kernel DLM and Pacemaker. One membership, one fencing authority. As for doing the same on PVE... someone still has to pay to develop, debug, and support it. Not my circus not my...
-
Yes. Problem solved afer reinstall.
-
bbgeek17 replied to the thread Qemu-Gest-Agent.Has it been cold started? I.e. powered off and powered on? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Proxmox in enterprice environments with shared fc storage.Fair point. Reflink with sparse raw files gets you thin provisioning and snapshots without qcow2... so qcow2 metadata is out of the picture. What's left is the stuff underneath. o2cb has its own heartbeat and fencing that doesn't know corosync...
-
bbgeek17 replied to the thread [SOLVED] Pinning vCPU causes 100% cpu pressure stall, using isolcpus.That's isolcpus doing exactly what it says. It disables the scheduler's load balancing on those cores, and PVE's affinity: option only sets a mask on the whole qemu process. So all 16 vcpu threads end up on the same one or two cores and nothing...
-
bbgeek17 replied to the thread Proxmox in enterprice environments with shared fc storage.@TheBigOne short answer: you didn't miss anything. There is no VMFS for Linux and GFS2/OCFS2 aren't it. VMFS did one job and VMware controlled everything around it. GFS2 and OCFS2 are mid-2000s designs for small database clusters on spinning...
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi @huganega, Thanks for the extra tracing. Some of it is useful, but I think the text you've put together is pointing you the wrong way. The solid parts: - The same stall shows up in two independent places: your I/O completions freeze for...
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi @huganega, You can find an update from our expert below. If you were a Blockbridge customer, we would also be able to engage directly with Proxmox as a Solutions Partner, with a direct line to their team. It is quite possible that resolving...
-
bbgeek17 replied to the thread PX Cluster GUI Storage delay.The most likely culprit is that the NAS response is somehow delayed. Local ZFS should be pretty fast. You could try to temporary disable the NAS storage to see if that returns the GUI response time to normal: pvesm set <storage> --disable...
-
bbgeek17 replied to the thread iSCSI on Proxmox itself for SQL Server Failover Cluster Instance (FCI) VMs.Manuel already noted this is outside what PVE supports. I'd go a step further: I can't recommend doing either of these in production. It's worth being clear about what WSFC actually needs from that disk. It isn't so much the block device as...
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi @huganega, FWIW, what you're describing looks familiar. We ran into something very similar a while back, and it turned out to be an awkward corner of the iSCSI protocol where neither side is obviously wrong, yet they still stall each other...
-
bbgeek17 replied to the thread Help Needed: Shared iSCSI Storage for PVE Cluster (Multi-node Access).It's been a year since Op's last post and presence, but based on the incident description (Dell/EMC backing ESXi) - it was likely iSCSI with VMFS. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
-
bbgeek17 replied to the thread Proxmox Virtual Environment now available for 64-bit ARM (arm64)!.Additional tech-note for ARM platform: https://forum.proxmox.com/threads/pve-arm64-on-asus-gx10-gb10-hard-reset-every-20-minutes-fix-is-loading-sbsa_gwdt.186164/ Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
-
bbgeek17 posted the thread [TUTORIAL] PVE arm64 on ASUS GX10 (GB10): hard reset every ~20 minutes, fix is loading sbsa_gwdt in Proxmox VE: Installation and configuration.Here’s another problem we hit bringing PVE arm64 up on the GX10. The first was the black screen after initrd (thread here). Posting this one since the symptom is a show stopper. Hardware ASUS Ascent GX10 NVIDIA GB10, 20 cores, 3.9 GHz 128 GB...
-
bbgeek17 replied to the thread From LVM storage screen, please allow binding LVM volume to VM.I would always recommend to stay within the bumpers of the system. Especially when an easy to use procedure is available. IMHO this is such a rare situation that complicating UI with handling this case is counterproductive. That said - feel free...
-
bbgeek17 replied to the thread Proxmox Virtual Environment now available for 64-bit ARM (arm64)!.This may be useful information for some: https://forum.proxmox.com/threads/pve-9-2-arm64-on-asus-gx10-gb10-black-screen-after-initrd-fix-is-console-tty0.186138/ Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
-
bbgeek17 posted the thread [TUTORIAL] PVE 9.2 arm64 on ASUS GX10 (GB10): black screen after initrd, fix is console=tty0 in Proxmox VE: Installation and configuration.If you install Proxmox VE 9.2 arm64 on an ASUS GX10 or a DGX Spark, the first boot will show a black screen, and you will think it hung. It did not. Here is why, and the fix. For context, we bought some GX10 systems (NVIDIA GB10, same board as...
