Hi @dchalon , welcome to the forum.
I believe you will need to clone that new VM as full clone. There is no unlink operation.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @theuken , welcome to the forum.
You cant. Netapp is not a suitable target for ZFS/iSCSI scheme.
I am not familiar with Virtucache, so cant provide any advice there.
The out-of-the-box solution is to use LVM with iSCSI. You may find this...
Have you checked your browser console for errors? Have you disabled any password managers or other extensions that may interfere? Have you previously installed any "enhancements" that affect non-production subscription reminder...
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...
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...
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" '...
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...
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...
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 -...
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 -...
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...
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...
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...
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...
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...
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...
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...
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...