bbgeek17's latest activity
-
bbgeek17 replied to the thread Stopped start failed: QEMU exited with code 1.Hi @skins4ever86 , the exit error is generic - anything not 0 is conventionally an error. 1 is a catch all. Some developers use other integers to describe specific problems. Your particular error is related to the PCI passthrough, and is more... -
bbgeek17 replied to the thread After Upgrading from v8 to 9.2, one node cannot resolve DNS.Its not part of our installation here that went through 7>8>9 upgrades. I don't know off hand whether it is part of any standard PVE install, I suspect not. Somehow you, or someone on your team brought it in. I'd examine the journal and dpkg logs...
-
bbgeek17 replied to the thread Proxmox VE GUI won't load after upgrade.There was a typo in the journal command - extra p at the end, did you fix it by chance in your run? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Proxmox VE GUI won't load after upgrade.You can try to run the pveproxy manualy to see the error you are getting: pveproxy start or pveproxy start --debug 1 Looking at the log, as @fabian suggested, should, of course, be the first step. Blockbridge : Ultra low latency all-NVME shared...
-
bbgeek17 replied to the thread After Upgrading from v8 to 9.2, one node cannot resolve DNS.Your /etc/resolv.conf is a symlink to systemd-resolved's generated file (as evident by the text at the start), and resolved has no DNS servers, hence "No DNS servers known." Removing the package leaves the symlink behind, pointing at a stale...
-
bbgeek17 replied to the thread [TUTORIAL] PVE 9.2 ARM64 on ASUS GX10 (GB10): 6 GB/s of NVMe/TCP out of the box, 29 GB/s after two kernel flags.Hi @Nemesiz, it's just a little console tool we wrote for this project. One Python script on top of the Rich library: https://github.com/Textualize/rich. Strictly read-only: it pulls from /sys/class/net, /proc/stat, /proc/interrupts, the CPPC...
-
bbgeek17 replied to the thread Thin Pool `vg_hdd-data-tpool` stuck with open count 1, preventing volume deactivation and reboot.LVM is not my area of expertise, but here are a few things to try and report back: 1. An open count of 1 on -tpool is normal while the pool is active. It's the internal pool device, held open by the thin LVs and by dmeventd monitoring. lvchange...
-
bbgeek17 replied to the thread Create a cloud init vm using API only.My mistake, my reading of your initial post was you are using Proxmoxer to create a PVE template VM. It appears that these are two independent flows that you are trying. The wrapper is only as good as the API request it creates. If it omits the...
-
bbgeek17 replied to the thread Does Proxmox accept external contributions/patches for projects such as PDM?.Hi @Tacioandrade , I believe most if not all of your questions about coding are covered here: https://pve.proxmox.com/wiki/Developer_Documentation As for the goal alignment, that is a more appropriate discussion for PDM list here...
-
bbgeek17 replied to the thread Proxmox PVE will crash out when Win Server 2025 and MS SQL 2025 is used..@Francois Baillargeon , the VirtIO version is mentioned in the opening post, and it appears to be the latest version. That said, a VM should not normally be able to hard-crash the hypervisor host. Even in the case of memory exhaustion, I would...
-
bbgeek17 replied to the thread Intel Xeon vs AMD Epyc.Glad it helped, @ns33. With U.2 and 100Gb, PCIe placement matters. On dual socket, keep your NVMe and the NIC carrying Ceph traffic on the same socket so I/O isn't crossing the inter-socket link. cat /sys/bus/pci/devices/<addr>/numa_node will...
-
bbgeek17 replied to the thread Create a cloud init vm using API only.Hi @Zernox, Your post is confusing because you seem to jump between the VM and Template but the connection is not there. For example, in your Proxmoxer config (btw this is a 3rd party tool and if you really have questions/issues with it - you...
-
bbgeek17 replied to the thread Intel Xeon vs AMD Epyc.Hi @ns33, It really depends on your applications. Neither vendor is a universally "better" choice, and the right answer comes from the workloads you plan to run. That said, my general preference is single-socket servers for anything network or...
-
bbgeek17 replied to the thread Lost connectivity with external storage after upgrade.@ghusson, this thread is specifically about FC connectivity with a particular QLogic card, so I don't think recommending iSCSI would be directly applicable to the posters' situation. That said, the best way to confirm hardware compatibility...
-
bbgeek17 replied to the thread Proxmox Virtual Environment now available for 64-bit ARM (arm64)!.A new article finally showing what a small ARM box running PVE is capable of: https://forum.proxmox.com/threads/pve-9-2-arm64-on-asus-gx10-gb10-6-gb-s-of-nvme-tcp-out-of-the-box-29-gb-s-after-two-kernel-flags.186770/ Blockbridge : Ultra low...
-
bbgeek17 posted the thread [TUTORIAL] PVE 9.2 ARM64 on ASUS GX10 (GB10): 6 GB/s of NVMe/TCP out of the box, 29 GB/s after two kernel flags in Proxmox VE: Installation and configuration.One more GX10 post, the last one for now. After battling the black screen, the hard resets and the power cap, we were finally able to see what this box and PVE on arm64 can do. Out of the box, the kernel initiator managed NVMe/TCP reads at 6.3...
-
-
we already have previous reports about HPE MSA (and Dell) appliances misbehaving in exactly this fashion - they advertise support for zeroing unmap, but only do it when the request matches some conditions, and simply ignore the zeroing part...
-
bbgeek17 replied to the thread losing dirty-bitmaps during Live Migration.Hi @aday , welcome to the forum. The journal line Cannot find device='z…' nor node-name='z…' on the target comes from the incoming dirty-bitmap migration: it couldn't find the block node the bitmap was attached to, so QEMU dropped the bitmap and...
-
bbgeek17 replied to the thread data corruption on shared-lvm.I'd recommend trying to reproduce this directly on the PVE host, bypassing the VM. Allocate a raw volume with pvesm alloc and test against the block device directly (or mkfs and mount it). My suspicion is that LVM doesn't clear extents on...
-
bbgeek17 reacted to PaulKo's post in the thread Windows Server 2025 + FSLogix Fileserver: sporadic vioscsi Event ID 129 ("Reset to device \Device\RaidPortX") causing inaccessible volume with
Like.
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.302-1/
