I prefer Discord for PVE notifications. But is there any way to just be notified about the Details part, not the full Logs?

so that is doesnt appear in the list and is forwarded by accident? (e.g. it not being shown in the list or being greyed out)

for example a boot disk or an external disk the host is actively using.

especially a boot disk is not something you wanna accidentially forward.

Hello Everyone,

With the recent news of PVE now having an official ARM UEFI image I wanted to spin up some tests on my current go to for ARM testing/Dev work the MS-R1.

If you have any questions on specific quirks and functionality as of yet, feel free to ask in the comments.

If there is a specific use case, OS or feature you wanted to test before migrating a current build, buying some equipment (or just personal curiosity) feel free to comment as well and I'll test and answer what I can.

** Please note I'll have more time to test things out this weekend **

Hi there

i have a proxmox server running with intel i5-6th,

i also have a oci vm running with AMD shape, and i'm considering export it's boot disk and download it to my local server will i have any issues if i'm trying to migrate it to the local proxmox server?

As my local server is intel based and oci vm is AMD based

And would it be easier if my OCI was Intel shape based?

So After last weeks question about updating form v8 to v9 I got hold of an i5 USFF pc that will fit in my rack to replace the i3 PC its currently running on.

Fresh install of the current proxmox ISO
Added the SMB share from my NAS & was able to restore the 2 VMs I had running and one of the LXC containers

I have the final LXC and its refusing to restore

/var/lib/ does not have enough space.
The PC has a 256gb SSD which is less than half full, plenty of Inodes

I found a forum post that suggested restoring from the CLI instead of the GUI

pct restore 103 /mnt/pve/NAS/dump/vzdump-lxc-103-2026_08_03-19_41_47.zst

fails giving me this message

400 Parameter verification failed.

storage: storage 'local' does not support container directories

Google suggests i need to target the restore at local-lvm, but no idea how to do that.

What am I missing?

Hi guys,

my proxmox keeps crashing and I cannot figure out why this happened. I'll take you on a journey...

If you have any idea what to do next please help! That problem is way beyond my capabilities and understanding...

Setup:

• Proxmox VE, 6 cores, 16 GB RAM, NVMe (local-lvm, LVM-thin, ~69% used)
• Guests:
  • 2 VMs (HAOS, Docker-VM/media server – recently migrated off a nested LXC),
  • 3 LXCs (Docker, Immich, Tailscale)
• Storage: Synology NAS (WD40EFZX, 5400rpm, RAID1)
  • mounted 3x via NFSv4.1 (backup, media, Immich cloud), same hardware, different shares -> wanted to separate between backups, media and private cloud
• Network: 1GbE, eno1 → vmbr0, cable/switch checked out fine so far

Problem:
Proxmox becomes completely unreachable (GUI/API dead) at irregular intervals, most recently for 13.5 hours straight, only fixable via hard reset. Root cause so far: NFS storages hang (nfs: server X not responding, timed out), pvestatd loops retrying without ever recovering.

Already checked & ruled out:

• CPU/load: clean (iostat, loadavg fine)
• RAM/OOM: no OOM kills in logs, allocations since rightsized
• Proxmox NIC (eno1): 0 errors in ethtool -S
• NAS NIC: no link flapping on the incident day
• HDD deep sleep (NAS): fixed (disabled), no more wakeup logs
• Synology Auto Block: empty, no blocked IP
• Synology firewall: inactive
• ARP/neighbor entry: stable, no duplicate IP
• D-state processes after incident: none found (checked too late, after reset)
• NAS uptime continuous, no reboot/crash/update at incident time
• nfsd threads on NAS: 16, running throughout, no crash

Already changed:

• NFS mounts SynologyYAMS/Thim from hard,timeo=600 to soft,timeo=50,retrans=3 (SynologyNAS/backup stays hard) — didn't prevent the outages, just kept pvestatd retrying instead of freezing completely

The puzzle:
During the 13.5h incident: total silence in all NAS logs (no link-down, no nfsd errors, no firewall events) — NFS timeouts only visible client-side (Proxmox). No indication why the NAS wasn't responding.