Hi @admin55,
Congratulations on making the move. Either option is fine, frankly. Both protocols have been around for decades. It depends on your requirements, management familiarity, etc. Why not try both? Just create two storage pools and see...
Hi @bratac ,
Since your post contains references to "Allow Snapshots as Volume-Chain" and your disk references /dev, it suggests that you are using a SAN of some sort.
The ASVC feature requires use of LVM, so you must have an LVM volume left...
"wipefs -a" one of the devices in the group, if you still cant access mpath device. Remove the iSCSI storage pools, remove any nodes/sessions with iscsiadm, reboot the node, optionally remove/re-init the LUNs on SAN side.
run "vgcreate" with...
Yes, the PVE server can run as a VM in another hypervisor (PVE, ESXi, HyperV, etc). It does not even need to be a PVE server. It can be a Debian VM, and has very low specs. The QDevice is described here...
Hi @ManuS , welcome to the forum.
The supported/recommended configuration is to have equal number of nodes in each site with additional node in a third site.
With your proposed configuration, if SiteA(4node) fails, the SiteB(3node) will not have...
Hi @baalkor,
I understand the recommendation in the Red Hat documentation, but the right choice really depends on two factors: what you're optimizing for (latency, IOPS, or bandwidth) and how fast your iSCSI SAN actually is.
In general, with...
Thank you for the update @adrian-1030
You can mark this thread as SOLVED by editing the first post and selecting appropriate option from the dropdown near the subject
Cheers.
Blockbridge : Ultra low latency all-NVME shared storage for...
No worries,
You can mark this thread as SOLVED by editing the first post and selecting appropriate option from the dropdown near the subject
Cheers.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Thank you for the update @odhiambo.
You can mark this thread as SOLVED by editing the first post and selecting appropriate option from the dropdown near the subject
Cheers.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
The limitation is somewhat similar to the one described in this thread https://forum.proxmox.com/threads/proxmox-8-how-migrate-vm-without-shared-storage.179176/page-2#post-832785. That one was just recently addressed.
Here, the code checks...
This is a PVE clone restriction. Here is an example of cloning a Template VM located on shared storage and hosted on pve-2.
Clone to PVE-2 local storage:
root@pve-2:~# qm clone 9001 10001 --full --name bbtest1 --storage optane-lvm
create full...
Hi @hoot,
You’ve already received a lot of good feedback. The important points mentioned are:
- You can use ME4 with PVE. If you have spare ports, servers, and capacity, you can run PVE in parallel with ESXi during the migration window.
- PVE...
Are you able to check the logs of your S3 providing software? It will likely have additional information on what failed.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @adrian-1030, welcome to the forum.
What you’re running is a fairly complex nested virtualization and networking setup, and it’s unlikely this is a Proxmox VE issue. If I understand correctly, your topology is:
Fedora (Wi-Fi) > VMware...
Hi @vluxh ,
PDM runs on top of a Debian Linux. The general Debian Linux VM recommendations apply to PDM build.
We've done some performance analyses and our finding may be helpful to you...
Note that a patch has been proposed to improve this behaviour:
https://bugzilla.proxmox.com/show_bug.cgi?id=3229#c7
It has not been accepted yet, but one could manually apply it to a system if there is an urgent need.
Cheers
Blockbridge ...
You should be looking at, following and checking the instructions on page 355
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
You are welcome.
The error you were receiving was somewhat generic. The tool was upset about the label/signature, not a partition:
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Give "wipefs -a /dev/mapper/3690b11c0000238a20000030e5098c67b" a try.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Have you yet retried: pvcreate /dev/disk/by-id/dm-uuid-mpath-3690b11c0000238a20000030e5098c67b ?
Have you rebooted the server since detecting the error?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...