bbgeek17's latest activity
-
bbgeek17 replied to the thread KVM installation issues.The 5th keyword should be your storage name, ie local-lvm, not a filename. The error you see confirms that. You can list your available storage pools via : pvesm status Cheers Blockbridge : Ultra low latency all-NVME shared storage for... -
bbgeek17 replied to the thread cloud-init dhcp does not set domain or search in /etc/resolv.conf.Its possible that this setting is being overwritten by DHCP, have you checked whether you can set this in DHCP? Here is an example we use in one of the cases, it shows how to extract/view what is being sent via DHCP and then use that for manual...
-
bbgeek17 replied to the thread KVM installation issues.Hi @Shazam77 , welcome to the forum. You need to specify the full path: qm importdisk VMID /path/to/iso/iso.name STORAGE --format raw Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
bbgeek17 replied to the thread [PROXMOX CLUSTER] Shared disk for VM.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
-
bbgeek17 replied to the thread Can I install molly-guard on a pve node?.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...
-
bbgeek17 replied to the thread Proxmox and IBM Flashsystem 7300.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...
-
bbgeek17 replied to the thread Using qcow2 for 20TB disks on iSCSI SAN (NVMe, 25G, multipath) — any risk of corruption or performance issues?.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...
-
bbgeek17 posted the thread [TUTORIAL] Understanding QCOW2 Risks with QEMU cache=none in Proxmox in Proxmox VE: Installation and configuration.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...
-
bbgeek17 replied to the thread Migrating from XCP-NG to Proxmox with Shared Storage and High Availability.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...
-
bbgeek17 replied to the thread Migrating from XCP-NG to Proxmox with Shared Storage and High Availability.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...
-
bbgeek17 replied to the thread Proxmox installation on Proliant BL460.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...
-
bbgeek17 replied to the thread Proxmox Directory Documentation - Out of date?.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...
-
bbgeek17 replied to the thread Proxmox installation on Proliant BL460.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...
-
bbgeek17 replied to the thread Proxmox installation on Proliant BL460.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
-
bbgeek17 replied to the thread Server Suggestions.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...
-
bbgeek17 replied to the thread Server Suggestions.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...
-
bbgeek17 replied to the thread Optimize maintenance process ?.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
-
bbgeek17 replied to the thread About Proxmox VE & PBS features.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
-
bbgeek17 replied to the thread local-lvm issue adding node to cluster.@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...
-
bbgeek17 replied to the thread VMs are not responding during backups.@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...