bbgeek17's latest activity
-
bbgeek17 reacted to soufiyan's post in the thread [SOLVED] API agent/get-fsinfo missing VM ID in response with
Like.
I went ahead and filed an official bug report with Proxmox and even built a fix that works. Here's the bug ticket: https://bugzilla.proxmox.com/show_bug.cgi?id=6922 Where things stand: I've submitted a working patch that adds VMID to agent... -
bbgeek17 replied to the thread [SOLVED] API agent/get-fsinfo missing VM ID in response.Again, I dont disagree with the premise. Not having to run multiple API calls, or stitch data for basic things, is good. This does not seem to track with the actual output. A quick check shows there is no VMID in: /nodes/pve-2/qemu/3000/snapshot...
-
bbgeek17 replied to the thread [SOLVED] API agent/get-fsinfo missing VM ID in response.Hi @soufiyan , welcome to the forum. I think the expectation is that you already know the $vmid. You can always do something like this: pvesh get /nodes/pve-2/qemu/$vmid/agent/get-fsinfo --output-format json | jq --argjson vmid "$vmid" '...
-
bbgeek17 replied to the thread Best practice and recommendations for building VM templates.Hi @Veidit, Packer is a great tool to continue building your templates - there’s plenty of documentation available, so no need to reinvent the wheel. I’m not entirely clear on what issue you’re facing with expanding the root disk. Packer...
-
bbgeek17 replied to the thread [SOLVED] disc is not imported.Looks good, keep in mind that the img needs to be in your current directory the way the command is written. If this worked and you are all set, dont forget to mark the thread solved by editing the first post and selecting appropriate drop down...
-
bbgeek17 replied to the thread [SOLVED] disc is not imported.Running "pvesm status" might be helpful Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread After upgrade from 8.4 to 9.0 pveproxy.service & pvedaemon.service not running.8 to 9 involves an OS upgrade of Deb12 to Deb13. I would not recommend attempting to rollback. You will likely end up in a bigger trouble than you are now. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
-
bbgeek17 replied to the thread After upgrade from 8.4 to 9.0 pveproxy.service & pvedaemon.service not running.It seems like your upgrade was not successful. Do you still have output from upgrade process? What do these show: pveversion -v debsums -s dmesg Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
-
bbgeek17 replied to the thread After upgrade from 8.4 to 9.0 pveproxy.service & pvedaemon.service not running.Hi @kazi, Can you please provide information regarding how you determined that those services are not running, commands, outputs, log snippets, full version output of the system, etc. Blockbridge : Ultra low latency all-NVME shared storage for...
-
bbgeek17 replied to the thread open-iscsi-service failed to start after update to Proxmox 9.0.10 (6.14.11-3-pve).PVE runs the iscsiadm discovery, similar to what is mentioned here: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/#understand-multipath-reporting-for-your-device You can manually run the discovery against the mgmt IP. However...
-
bbgeek17 replied to the thread open-iscsi-service failed to start after update to Proxmox 9.0.10 (6.14.11-3-pve).You can modify /etc/pve/storage.cfg at any time - it will not affect already established iSCSI sessions (or any other storage that’s already active). New sessions will take the updated configuration. On reboot, all session will be adjusted. That...
-
bbgeek17 replied to the thread Server Compatibility.Hi @Albionfbird , welcome to the forum. Please note that an odd number of cluster nodes is recommended for production deployment. As for hardware compatibility - PVE does not maintain its own matrix. However, PVE is based on Debian userland with...
-
bbgeek17 replied to the thread open-iscsi-service failed to start after update to Proxmox 9.0.10 (6.14.11-3-pve).Hi @AndreasS , you may find this article helpful as you work on a solution: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/#understand-multipath-reporting-for-your-device Blockbridge : Ultra low latency all-NVME shared storage...
-
bbgeek17 replied to the thread HyperV to PVE migration - Windows VM boot issues - local-lvm disk vs shared disk.Sounds good! Let us know what you find. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread Proxmox VE 9 with SAS Shared Storage.Hi @michael.v , welcome to the forum. yes it will be. Yes No. LVM-Thin is not compatible with shared-storage application. Veeam for PVE does not use storage level snapshots. You will be able to use Veeam. Yes, it should work. PVE relies on...
-
bbgeek17 replied to the thread HyperV to PVE migration - Windows VM boot issues - local-lvm disk vs shared disk.Hi @ikalafat, welcome to the forum. My suspicion is that in the failure cases, the underlying disk was not properly erased, allowing the VM’s OS to read residual or invalid data. After a few conversions, the VM disk was likely...
-
bbgeek17 replied to the thread Web portal issue after updates.Looks like the authors did put the warnings: https://github.com/MacRimi/ProxMenux?tab=readme-ov-file#:~:text=%E2%9A%A0%EF%B8%8F,check%20the%20source...
-
bbgeek17 replied to the thread Web portal issue after updates.Hi @ds010123 , glad these steps helped you. The best way to understand what this script does is to research the website or repository where you originally found it. If that source doesn’t provide a clear explanation, that alone is a good reason...
-
bbgeek17 replied to the thread Web portal issue after updates.https://forum.proxmox.com/threads/proxmox-ve-web-gui-is-a-blank-page.172804/page-2#post-806736 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread shared storage with Dell MD3200i (iSCSI multipath) for VM and file server use with Live Migration.There are some drawbacks, i.e. instead of using block oriented Virtio architecture you are now relying on network Virtio. However, given that you were planning to pass-through the LUN (bypassing Virtio) - you probably will not see a difference...