Search results

Your timeout error is between your client and PVE machine. QM command only operates on VMs that are local to the host where you execute the QM. It seems like one of the hosts in your cluster is down. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

You are trying to stop VM 220, and then status check 221 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @BigBadBlack , welcome to the forum. You do not. It would be helpful if you provided actual information that you tried to input, errors you received, etc. If you are unable to provide accurate information in text format (please use CODE tags) - screenshots will suffice. Without this...

yes, that is the correct type. Once you enable the Snapshot-as-volume-chain, the format will be QCOW on LVM. Keep in mind that this technology is in Preview mode. There is an associated performance impact to using QCOW whether on LVM or on top of a filesystem. There is additional processing...

To answer your question - NO, its not production feasible config. As @aaron pointed out, you need an odd number of servers in the cluster. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @aflocco , welcome to the forum! You may want to read this article to give you a starting point: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage Follow your vendor's guide on attaching FC LUNs to Linux. Continue with vendor specific multipath configuration, if any. Then the...

When the file is open removing it does not always release the space immediately. A fast way to empty it is to echo "" > auth.log As @Gilou mentioned, you should take your server off the internet, block access to well known ports (22 in this case) and in general beef up your security posture...

You can't start a template via user interfaces. Can you make sure that you are running the latest code? There were some issues around DBus that were fixed within the last month or so, if I recall correctly. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

You cannot add multiple SCSI controllers through the PVE UI. To do so, you will need to experiment with direct QEMU options via --args. I am not sure which UUID your SQL installation is bound to, as there are several possibilities. Most of these identifiers will change once you modify almost...

You are very welcome. Happy you found an easy explanation. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

This is exactly the impression I was getting from the discussion as well. The OP wants a “simple” small-business solution that nonetheless delivers a fully featured, reliable DR setup with many characteristics typically associated with enterprise platforms. That problem has already been solved...

That is an ESXi-dependent deployment, and it may not be something you can reproduce in PVE/QEMU. From a boot perspective, you only need a single disk. Additional disks may be required by the application itself, but the first step is to make the system boot successfully and then address the...

Hi @markosoftfl , welcome to the forum. I believe you need to switch to using Virtual SCSI Single controller. In this case a controller per disk will be created. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

It does sound very much like a duplicate IP issue. The logs are : journalctl -f You can also run tcpdump from the PVE console or SSH via "good" host to see what, if anything, happens to your "bad" connections: tcpdump -i physicalInterfaceHere -n host bad.client.ip.here Also, check ARP table...

Have you tried to login from physical console with the same password? Are you sure you don't have two PVE nodes running by accident? Since you already tried to restart pveproxy, try to stop it - did the GUI stop responding for all hosts? When you are trying to SSH - monitor the log from the...

Op's environment is two-host cluster with MSA SAN. Neither Ceph nor ZFS would be a technological fit here... Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

There appears to be work going on to address this: https://bugzilla.proxmox.com/show_bug.cgi?id=7289 https://lore.kernel.org/qemu-devel/20260105143416.737482-1-f.ebner@proxmox.com/T/ Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @katti, many people have designed their infrastructure with DR in mind. The correct solution always depends on RPO, RTO, and budget. The key questions your business decision-makers need to answer are: How much downtime can be tolerated? How far behind the primary site can the DR site lag...

This is no different than a Microsoft with MSA. They will provide standard support to the best of their abilities for their product and it's functionality. If the issue points to storage they will point you to your storage vendor. SAN is a supported configuration with PVE Cheers Blockbridge ...

https://pve.proxmox.com/pve-docs/getting-help-plain.html https://forum.proxmox.com/threads/where-should-i-report-bug.102215/ https://pve.proxmox.com/wiki/Introduction#getting_help Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox