Search results

Running a VM as NFS server is your best option. Keep in mind that the host that owns the disks is your single point of failure in that case. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

At least once in your life, you’ll reboot the wrong system or run rm -rf /. It’s a rite of passage. Usually, you won’t make that mistake again. Since only root can reboot the system, this package won’t prevent malicious reboots - root can always override or remove the barrier. The package also...

Officially, there is no such thing as ZFS-over-FC. You may be thinking that it is similar to ZFS-over-iSCSI, however it is not. The built-in PVE ZFS-over-iSCSI plugin not only internally provisions ZFS volumes inside the backend storage, but also exports them via iSCSI. I am not aware of any...

Hi @PHPMaroc , We just finished working on an article that is related to your initial inquiry : https://forum.proxmox.com/threads/understanding-qcow2-risks-with-qemu-cache-none-in-proxmox.175933/ Hope it helps! Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

Hey everyone, A few recent developments prompted us to examine QCOW2’s behavior and reliability characteristics more closely: 1. Community feedback There are various community discussions questioning the reliability of QCOW2. We have customers (predating our native integration) interested in...

The primary, migration oriented, document is https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE All the best best practices references in multiple official documents are applicable. There is not a single official "XCPg to PVE" guide. If you are running critical production, then you should...

Hi @wesleysilva01 , welcome to the forum. Both LVM/iSCSI and NFS are valid choices. NFS is generally more suitable for file operations and cross-host concurrent access. LVM/iSCSI is block storage, where concurrent access means different thing than the one in NFS. There has always been snapshot...

That depends on how you are tagging. If its a native port VLAN - no, otherwise yes. https://www.youtube.com/watch?v=stQzK0p59Fc https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_network_vlan https://pve.proxmox.com/pve-docs/chapter-pvesdn.html Blockbridge : Ultra low latency...

A QCOW/VMDK/etc can be imported from any location. The "import disk" requires absolute path at this time. These are stored in "VM images". For historic reasons "VM Image" is a VM disk in PVE-speak. There is no GUI qcow import at this time. Blockbridge : Ultra low latency all-NVME shared...

What is the IP of your workstation? Can you ping the gateway? Can you ping the PVE server? Can you ssh into PVE server? What is the corresponding output from your workstation? (ipconfig /all ; ip a) What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or...

Hi @arielcace , welcome to the forum. What does "ip a" show? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Most of the hardware complaints reported in the forum are by homelab users. A single-packet AMD server from any of the major vendors will do the job just fine. You will likely need at least two Compute servers with additional node for quorum. Or, getting 3 identical ones may be an easiest route...

Hi @fanton , The server task suitability is not measured by who produced it. Any Enterprise server is generally suitable to run Linux. What you need to ask yourself: - how many virtual machines will I need? - how many virtual cores? - how much RAM? - how much disk space? - how critical is part...

This is not something I'd recommend implementing in production/business environment. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

https://forum.proxmox.com/threads/proxmox-with-48-nodes.174684/#post-812003 Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

@gtrovato , The short answer is "yes" - the fact that you are merging nodes into a single cluster that have different local-lvm definitions is what is causing the question marks. When you add a node to the cluster, there is a warning that any existing configuration on the new node will be...

@PwrBank , you are correct. This is why Backup Fleecing Storage was created. Prior to it, a write to a non-backed up segment was blocked until that segment could be backed up. If the backup link/storage/cpu are inadequate - it creates bottleneck. Fleecing Storage should alleviate this issue...

Since you are already maintaining an external map of category=lower-upper, I'd try to avoid frequent cluster changes. The easiest way is to add another field in your map for last used, or next free. Another option is to generate next ID on the fly. Here is an example of shell way, you can, of...

Hi @ssevasta , This is a free community support forum, so posting here does not open an official support case. For formal case tracking, you would need to have an active support subscription. That said, a staff member may still notice your post and take a look. However, you haven’t provided...

Hi @dsintayehu , The first step would be to accompany your report with actual saved and running configuration output from "good" and "bad" notes. I.e. output of: - cat /etc/network/interfaces - ip a - ip route - brctl show - ping x.x.xx Add to it similar output from the VM. Do any VMs work on...