readyspace's latest activity
-
readyspace replied to the thread [SOLVED] VLAN trunk with LACP in Proxmox (OPNsense virtualization).Hi, sounds like a tagging mismatch between Proxmox and OPNSense. You need to do bonding first — create LACP bond (mode 802.3ad) → bridge it to VLAN-aware vmbr → connect OPNSense VM NIC (no VLAN tag). Then do VLANs (10/20/30/40) inside OPNSense... -
readyspace replied to the thread network speed problems.Sounds like you’re bumping into a VM network stack bottleneck (bridge + single-queue) rather than a cable limit — have you tried enabling virtio multiqueue + jumbo frames (MTU 9000) end-to-end and pinning IRQs/queues to vCPUs?
-
readyspace replied to the thread [SOLVED] Does Ceph Public need to be on ProxMox Cluster network?.Looks like you’ve figured out part of it Ceph’s public network must be reachable by all Ceph clients and monitors — that includes: - all Ceph mon and mgr daemons, and any OSDs or VM hosts accessing RBD/CephFS. If it’s on a VLAN with no...
-
readyspace replied to the thread No webGUI after dnsmasq install.Great — now for VLANs, try enabling VLAN aware on vmbr0, don’t put your host IP on vmbr0 itself but on a VLAN sub-interface (e.g. vmbr0.10), and make sure your uplink switch is trunking those VLAN tags. See Proxmox docs & examples here...
-
readyspace replied to the thread The VPUG virtual machine of A16 cannot be started..From the screenshots we can see a few key points: All of your A16 GPU VFs (Virtual Functions) are still bound to the nvidia driver, not vfio-pci. That’s why your VM start command shows: kvm: error getting device from group 221: No such device...
-
readyspace reacted to Whatever's post in the thread Correct VM NUMA config on 2 sockets HOST with
Like.
Thank It's all clear now. Thanks. -
readyspace replied to the thread IP over USB?.I dont think it will work. The error message you saw: UDC core: g_ether: couldn’t find an available UDC is telling: it means the USB Device Controller (UDC) subsystem did not find any eligible hardware endpoint in “device / gadget” mode to...
-
readyspace replied to the thread Proxmox hangs after upgrade to v9.Hi, I usually dont do this, i will only backup all the VMs, then format the node and install latest PVE. After that import the VMs back into the PVE. This way is cleaner.
-
readyspace replied to the thread Proxmox hangs after upgrade to v9.For full-node rollback, a disk image (Clonezilla, etc.) is the quickest path.
-
readyspace replied to the thread The VPUG virtual machine of A16 cannot be started..Hi, it looks like your Virtual Function (VF) for vGPU passthrough is not properly bound to VFIO at the time the VM starts. Your VF (0000:8c:02.2) belongs to IOMMU group 221, but that group is not attached to VFIO yet. Run: lspci -nnk | grep -A...
-
readyspace replied to the thread Proxmox hangs after upgrade to v9.Hi, looks like something happened during your upgrade between 8 to 9. Usually I'll do move out the VMs, then do a totally fresh install of PVE for major upgrade due to changes to the kernel.
-
readyspace replied to the thread Full Server backup + restore solution.If i'm not wrong, it is possible to install Veeam agent in PVE and backup the whole host. Anyone tried it?
-
readyspace replied to the thread Correct VM NUMA config on 2 sockets HOST.Hi, in numa0/numa1, the cpus= list refers to guest vCPU indexes (0…vCPUs-1), not host CPU IDs. Affinity is the host cpuset for the whole VM process (all vCPU threads), not per-vCPU. Proxmox VE (QEMU) doesn’t expose per-vCPU pinning in the VM...
-
readyspace replied to the thread Ceph Pool PGs Reduced to 32 by Autoscale Despite Setting 256 – Is This Normal?.Yes—this is expected with the PG autoscaler. With a mostly empty pool, Ceph starts low (often 32 PGs) and grows PGs as data increases unless you guide it with bulk, target_size_ratio/bytes, or a pg_num_min.
-
readyspace replied to the thread Failed to prepare disks for restore.Hi @Chirath Perera , you might want to report this to Veeam. See what they say.
-
readyspace replied to the thread Failed to prepare disks for restore.Are you using PVE 9? If so, Veeam’s restore paths do not yet fully support Proxmox 9
-
readyspace replied to the thread [EDIT: Mellanox NIC not working] VMs not connecting after change to vmbr0.Good find — that explains it. If you still get a response with the fiber unplugged, the link was never actually active. Check that your SFP+ modules or DAC cables are compatible with the HP 546SFP+ (Mellanox ConnectX-3 Pro), and run ethtool...
-
readyspace replied to the thread Host connection issues with the VMs..Hi, please share more information as following if possible: Host network config: post the relevant parts of /etc/network/interfaces (or whatever file you use) showing eno1, the bridge (vmbr), and how they’re connected. VM NIC info: inside the...
-
readyspace replied to the thread How to read SFP+ module details from Mellanox ConnectX-2 MNPA19-XTR.Hi @logan893 , yes you are right. the older card doesnt have the necessary drivers for what you are looking for.
-
readyspace replied to the thread config issue with multiple VLAN and cisco device.Thanks for sharing your config — you’re almost there. A few quick points: Keep only one bridge (vmbr0) — you already made it VLAN-aware, so no need to create vmbr0.110 unless the Proxmox host itself needs an IP inside that VLAN. For your VMs...