Hi Everyone,
I'm excited to share a deep dive into one of the notable new feature in PVE9: the enhanced snapshot functionality designed for legacy SANs. This feature represents a meaningful step forward in expanding PVE's compatibility with...
Can you share your "/etc/pve/storage.cfg" ?
Also, what is serving your iSCSI?
Finally, what version of PVE are you running: pveversion -v
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @powersupport ,
Would you clarify your setup for me? You moved from local SSD to NFS hosted in a VM on ESX backed by spinning rust? At the very least, I’d suggest starting your fio testing inside the ESX VM.
Your VM configuration file shows a...
Hi @Amila, welcome to the forum.
To receive an official response from Proxmox GmbH, you should contact them directly via shop.proxmox.com.
That said, your proposed architecture looks fine. Proxmox GmbH will likely support it as far as PVE is...
It should start.
Likely will be ok, as much as it can be on 7yo pc
no, you should not run into issues. But if you were to use some other ARCH than host, you could. The 7yo PC will not support CPU commands introduced in younger generations.
Use...
Hi @daus2936 , yes, of course.
Please see this article for some guidance:
https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/
Best regards,
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Oh, the other easy workaround - use an IP in your PBS config.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
In Linux systems there is a specific order in which DNS resolution is done:
cat /etc/nsswitch.conf|grep hosts
hosts: files dns
Each "service" is a caching device of a sort. The files (/etc/hosts) can cache your most used entry, the DNS...
no, ZFS is not a cluster filesystem and is not suitable for multi-writer applications.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @Raja Sekhar , welcome to the forum.
The best way to achieve your goal, based only on the information you supplied, is to use NFS over raw block SAN.
Things become somewhat complicated if you are unable to use NFS.
The standard use-case for...
Hi @Henry Wong , welcome to the forum.
The first thing to try would be to roll back your Openwrt change.
You've changed a portion of your network infrastructure and the remaining part appears to have been cut off. There is much more information...
If you presented the two MSA LUNs to all nodes, you have the basics of shared storage in place.
However, you used wrong LVM type - LVM-thin is not compatible with multi-writer scheme that is needed by "shared storage".
Once you have wiped your...
Hi @ashah , welcome to the forum.
The port specification is separated from the host name by column, not by slash.
Https://ip:8006
Cheers.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @dCipher ,
No, there are special instructions. Update your repositories, i.e. disable "test" and enable Trixie no-sub, then follow standard procedure...
Hi @nautilus7 ,
Since the disk is stored as raw block device on top of LVM slice, you should already see this disk when you list LVM slices: lvs
However, the name of the parent group (vgs) must not overlap with existing names on the new hosts...
You said you upgraded PVE - were you trying for PVE9, or did you just do a PVE8 refresh? Or went from 7 to 8?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Thanks @aaron ! Yes, the resources is always first place to start to get a handle on current state.
My understanding is that OP is looking for data on which VMs were moved by HA event.
Blockbridge : Ultra low latency all-NVME shared storage for...
A number of issues with similar symptoms that were reported recently end up being incomplete/failed upgrades. Please take a look at a few recent threads for advice on how to force-reinstall the packages.
Other than that, outputs of the following...
VMDK is a proprietary format. The open-source community has made efforts to enable migration from VMDK, but there’s no incentive to make it perform as efficiently in non-ESXi environments, it’s likely not possible to match native ESXi...
Hi @joshiyamamoto , welcome to the forum.
Sounds like you are looking for historical information, which is more suitable to be in "log", "task" or similar end point. I am not sure if these have what you want - check and let us know...