Recent content by bbgeek17

Do not deploy production PVE installation with either 2 or 4 nodes. Either go with 3, or implement a QDevice for quorum. As for storage, it will depend on your budget and availability requirements. At least the later seems to be very lax. Good luck Blockbridge : Ultra low latency all-NVME...

My apologies, the hostname above gave me the wrong impression that you are running inside fritz.box hosting provider. If you are sure that the IPs and subnet are correct, it still continues to be local networking issue. With properly reachable gateway you should see at least one more hop, ie...

This is not a PVE issue. It is a basic Linux networking misconfiguration problem. As you are running inside a hosting provider, you should reach out to them to confirm that you programmed your Debian Linux (which PVE is under the covers) with proper networking configuration. Check that you are...

Can you ping it? Do you have DNS set? Can you ping 8.8.8.8? Can you traceroute? Is your router working? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Do you have default route set? ip route Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @muekno, You need to provide vastly more information about your bridge configuration, your VM OS, your VM configuration. You can try to capture DHCP packets on the vmbr and physical interface of the hypervisor to see if the VM sends any, and if any replies come in but don't make it to the...

I would recommend confirming that the interface is set to manual, reboot, check the state of the network "ip a". If it still is not working - try to restart the service: systemctl restart networking. Provide updated screenshots of : ip a, /etc/networking/interfaces, journalctl -n 100 Another...

The GUI opens a Console window that connects to a Serial interface, not SSH. Your TF template has no mention of the serial console. Perhaps your VM Template does, we don't know since you have not posted what you are actually cloning. Now that you created a template - clone it manually via PVE...

Generally, cluster stability troubleshooting requires correlation of log entries from all nodes leading up to and during the event. Networking is often the cause or major part of the type of instability you described. The best route, of course, is to open a ticket with Proxmox GmbH. Short of...

In most cases the need is hardware related. Users had to use vanilla Debian to bootstrap some exotic hardware they had, i.e. network device or a particular RAID card. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @nozomi, welcome to the forum. Tools like Terraform, Ansible, etc., that manipulate VMs externally are developed and maintained by third parties. Their configuration options don’t always translate directly to native PVE configurations. Some entries can trigger multiple API calls under the...

Hi @carsb , if "sudo" works for you - you should install that package. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

In many cases, the PVE CLI simply wraps existing tools rather than reimplementing functionality from scratch. For example, LVM management can be performed using the native LVM CLI suite, and when you run a single PVE command, it often just triggers a series of those native CLI operations behind...

@dortiz Although the article uses iSCSI as an example, it is completely interchangeable with FC, as @guruevi said. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @dortiz777 , welcome to the forum. As PVE uses Ubuntu derived Kernel and Debian Userbase for underlying OS functionality, the FC connected storage is well supported. The primary option is to layer LVM on top of your FC LUN. You can find some guidance in this article...