Recent content by bbgeek17

Hi @zync, welcome to the forum. A good test to try is install vanilla Debian - do you have a similar challenge? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @heytmi , welcome to the forum. Your question is more related to PVE part of the forum than PDM I recommend opening a thread there. Do include as much relevant technical information as possible. For example: lsblk fdisk -l pvs vgs lvs pvesm status cat /etc/pve/storage.cfg Blockbridge ...

Hi @Nathan Stratton and all, You need clear guidance here: do not do that unless you have a very compelling reason to. a) Your hardware is discontinued and past the end of service, which significantly increases the likelihood of component failure. b) As the number of virtual machines grows...

The PVE endorsed methods are described here: https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/proxmox-ve-import-wizard-for-vmware https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE...

Hi @imsuyog, welcome to the forum. With any migration path, you will need to invest some time and effort into testing how appropriate it is for your data. The migration will most likely involve data transfer, probably over an API, and may require data conversion. You might be able to reuse...

Did you check the CI log after boot? Have you monitored the console output during the boot? (qm start xxx && qm monitor xxx). You presented you sanitized CI config but did not present the actual VM config. Keep in mind that according to ...

Did you only have VMs active on node1 when you restarted the nodes last time? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

May be your ISP is running openwrt on PI... Dust out tcpdump and start capturing and comparing traces :) Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

This is a good read: https://forum.proxmox.com/threads/temporary-failure-in-name-resolution-help-needed.164020/ I think the summary is: DNS resolution failure that affected only PVE and only when used with internal router. Caused by new version of openwrt, running on Pi , affecting Debian...

Are there VLANs involved? Have you tested MTU max size between the internal hosts on the switch? Does your switch implement some sort of "smart" filtering? The best approach is to keep reducing the number of variables and complexity of the test. Install vanilla Debian instead of PVE - do things...

Yes, you are absolutely correct. I was just pointing out that there is more than one downside. I realize OP may have been exaggerating with 99 PB; that said, the higher the over-provisioning ratio, the greater the chance that someone might take this literally. This may not be an issue in a home...

The other downside is that if you do accidentally run out of space it will be somewhat catastrophic for your data. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @davidedaps , welcome to the forum. Your request is not PVE specific but rather regarding general Linux system administration. There are many existing guides and discussions covering this questions. For example: https://www.redhat.com/en/blog/resize-lvm-simple...

All I can tell you is that in our lab we are running, or were at one point running, successfully: ESXi in PVE, PVE in ESXi, PVE and ESXi in Openstack, Openstack in ESXi. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Every situation is unique, sure. You can, may be, unmap the LUN from the target on the SAN side If your steps work, go with them. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox