Search results

This is correct, the user and their permissions apply to all nodes in the cluster. System-Wide refers to "Linux PAM" which is not PVE specific. Its a generic Linux concept. The "system" in this particular wording is the server/node. Each system, correct. The username and permissions are...

You should only need a virtual IOMMU in the guest if you have software/drivers running in the guest that expect to be able to program an IOMMU. It is my understanding that you only need a vIOMMU if you are attempting nested virtualization (i.e., running another virtual machine inside your...

@alhex , Just because Ansible calls an operation “ping” doesn’t mean it’s actually doing an ICMP ping. For a web server, “ping” in Ansible might mean making a curl connection to port 80/443. In your case, it’s “pinging” the SSH port by attempting an SSH connection. That connection is being...

Thanks for posting this. IPMI is a small independent OS, essentially a completely different network node. It must be treated the same way as other computers on your network - independent network settings. Some vendors allow physical "port sharing" between IPMI and server OS, but they still must...

Hi @coolnodje, There’s no such thing as “clone” in iSCSI, nor is there snapshot, compression, zero optimization, etc. iSCSI is a well-established (25+ years) protocol that encapsulates SCSI commands over TCP/IP. It’s a standards-based, vendor-independent way to move block data. With any...

The best way to key key based authentication working is to use "ssh-copy-id", if you have it on your client. If you don't, then carefully take the context of your id_rsa.pub from windows host, and place its context as single line , adding it to the end of "authorized_keys" on the PVE. Make...

@damiengm , You may find this article helpful: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/ Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @SInisterPisces, vIOMMU does not generally improve the raw performance of SR-IOV GPU virtual functions; SR-IOV itself is designed to bypass much of the hypervisor overhead by giving VMs direct access to hardware, and vIOMMU is primarily focused on improving security, memory isolation, and...

Hi @SInisterPisces, The first thing to understand is what an IOMMU is: An IOMMU is hardware that manages how devices access memory. It translates device I/O virtual addresses into physical RAM addresses and enforces isolation so that devices can only access the memory regions assigned to them...

Hi @powersupport, We’re having trouble communicating in a way that allows us to assist you. The information shared so far isn’t sufficient for diagnosing the issue. At this point, I recommend opening a support ticket through your Proxmox support contract, where you can get dedicated one-on-one...

Something changed. Yes, work on troubleshooting your firewall rules. The last one is DROP. Change it to Accept, does it consistently work now? Change back to DROP, enable log - does it log your gui/ssh attempts when broken? Which rule in your list do you think should be responsible for...

What you are describing is very bizarre and unusual. This typically means that its something in your environment. Given your statements above, it is likely a switch misbehavior. Some sort of weird PnP issue? Aggressive ARP expiration? Strange AI host banning? If the network connectivity works...

Thank you for the update, you can now mark the thread as Solved by editing the original post and selecting Solved from drop down near the subject. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @Niraat , this is a good example why one should be careful with assigning VMs as HA resources, i.e. not having local disks. Is the VM currently stopped? qm status 109 Does the original host have the referenced disks? (pvesm list local-lvm) If the VM is stopped and the disks are present on...

Hello @bravo0916 , You should try some basic troubleshooting: nc -vz 192.168.25.75 445 smbclient -L //192.168.25.75 -U test Try manual mount, ie: mount -t cifs //192.168.25.75/proxmox_backup /mnt/test -o username=test,password=xxxx,vers=3.0 Try with different protocols, etc Blockbridge ...

Alright, NFS, migration, ESXi, network - all of that is extraneous and not related to your problem. It really boils down to this: you have a RAID-backed LVM group, and you’re not happy with its performance inside the VM. It didn’t get worse - it simply was never satisfactory to begin with...

You can try "vgscan --mknodes" Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @wifi75 , This does not seem to be PVE specific and there are a few discussions online about the warning: https://askubuntu.com/questions/1299499/warning-pv-dev-sda3-in-vg-ubuntu-vg-is-using-an-old-pv-header-modify-the-vg-t https://access.redhat.com/solutions/5906681...

Hi @dan.ger , Are you able to SSH/CURL directly from PVE host into itself at the time when the issue manifests? What about between PVE hosts? I.e.: ssh root@localhost ; ssh root@LAN_IP ; ssh root@pve-02; curl -k https://localhost:8006 ; etc The subject of your post states that webui and SSH...

Yes, your physical disk (sda) is failing. It could be a bad cable, a faulty motherboard slot, or even a power issue, but most likely it’s simply a dying disk. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox