Recent content by bbgeek17

Hi @Tipenso , Your current L2+L3 setup refers to MAC + IP addressing. A single migration from host A to host B will use a single combination of source/destination MAC and IP, meaning only one port will be utilized. Ten concurrent migrations from host A to host B will still use the same single...

The only portion that is modified by those scripts is the web interface related files. Sounds like you are in a good place since you've rolled back and things are working for you, Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @uppsju , welcome to the forum. Out of curiosity: what do you mean "rolling back the updates"? You best way to troubleshoot the situation is by reaching out to the authors of the PVE modifications that you likely installed to remove a reminder that non-subscription repository is not...

Hello @bitlan, welcome to the forum. Starting with PVE 9, you now have the ability to preview snapshot technology that’s compatible with iSCSI-type storage: https://kb.blockbridge.com/technote/proxmox-qcow-snapshots-on-lvm/ Even if you use this option, whether your overall infrastructure will...

Hello, @pipsqueak . Welcome to the forum. What is the IP of the PVE server? What is the IP of your workstation? What is the IP of your gateway? Can you ping the PVE server? Can you ssh into PVE server? What is the output of "ip a" on PVE? What is the corresponding output from your workstation...

You could also try to run "sync" inside the VM prior to cloning. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

To answer your initial question directly: in current versions of QEMU/Proxmox, emulating an NVMe device is unlikely to deliver a dramatic performance improvement. The reason lies in understanding what "virtio" actually is. Virtio is a paravirtualized I/O framework that enables efficient...

There are always trade-offs. In general, NVMe creates multiple queues for I/O processing compared to iSCSI/SCSI. However, each queue consumes CPU. So you may get better I/O performance, but in a shared virtual environment, you may adversely affect other aspects of the infrastructure. We've done...

One other thought, so you don't experiment on your production systems - install a PVE as VM and get the process worked out there. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Curious. Perhaps try: echo "options nf_conntrack nf_conntrack_max=524288" > /etc/modprobe.d/nf_conntrack.conf You'll need to reboot, or unload/reload the module which will cause connection reset. Not sure, of the top my head, what could be causing the reversion. Blockbridge : Ultra low...

Don't forget to ensure that you make the change persistent, or you will be in for a surprise sometime after next reboot. I'd even recommend testing it by rebooting the host and checking that it was set again. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

You should ask the authors of those scripts. The information for proper repository context is here: https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo You'd need to use an editor, I recommend Emacs. Blockbridge : Ultra low latency all-NVME shared storage for...

Hi @dhenrickson , welcome to the forum. Disk naming (indexing) can and does vary across the VMs. Whether the boot disk is disk-0 or disk-1 is completely irrelevant. As @leesteken quickly pointed while I was typing - the error message is unrelated to disks and has to do with the highlighted...

Coincidentally those two files are modified by various helper scripts to disable the reminder that no-sub repo is not suitable for production. A message informing you that a package cannot be reinstalled/downloaded means that you do not have appropriate repository enabled. It could be an...

I just noticed that in your qmp_capabilities output, the block related to disk-0 contains: "io-status":"nospace" That’s a important clue. My guess is that the LV is potentially not properly sized. You have a 10 GiB LV with a 10 GiB QCOW image. Small enough that most of the clusters (≈95%) are...