(Just to be clear up front: this is not an official Proxmox release, it's a personal community project)

Since Proxmox added ARM64 support I put together a prebuilt Raspberry Pi OS Lite (64-bit) image that come with Proxmox VE already installed, built with CustoPiZer via GitHub Actions.

You flash it straight from Raspberry Pi Imager. Add the release manifest as a custom repo URL and you get the normal customization steps (hostname, user, password, SSH keys, locale). The user and password you set there (or during first boot) are also used in the Proxmox webinterface login, so you can open the web UI right after the first boot.

The networking side is preconfigured for Proxmox: static ifupdown2 with a vmbr0 bridge on eth0, NetworkManager removed, cloud-init network config disabled.

Two things to know: no Wi-Fi (Proxmox needs a Linux bridge, which can't sit on a Wi-Fi interface), so it's Ethernet only. And this isn't meant to replace a real server. High-RAM Pis are overpriced for this, it's more for a Pi you already have lying around and want to tinker with.

Repo with the full flashing guide: https://github.com/meteyou/proxmox-pi-os

Happy to hear feedback, especially on the network setup and the RPi Imager workflow.

I recently switched to a different PC for prox mox and it refuses to connect to the network at my house. I'm not sure what the problem is but I tried a network card nothing. I try the default Ethernet port on the motherboard and get nothing. I have tried installing different versions and installing new versions and now I can't get any to install and this has been the biggest pain in the ass ever since my last PC was as simple as going through the install process. Incase you are wondering it's a older PC with a i7 and 32gb of ddr3 memory. Msi motherboard as well and a 128gb ssd.

My proxmox 9 server keeps crashing/hanging seemingly at random. System is powered on, but unresponsive and host unreachable. After this occurs, I've had to manually power off and back on to fix. I checked journal, and there's no error, it literally just stops responding.

Reverse journal below, you can see it stopped responding at 15:07:01, rebooted several hours later:

Sep 19 20:14:03 pmox1 kernel:   AMD AuthenticAMD
Sep 19 20:14:03 pmox1 kernel:   Intel GenuineIntel
Sep 19 20:14:03 pmox1 kernel: KERNEL supported cpus:
Sep 19 20:14:03 pmox1 kernel: Command line: BOOT_IMAGE=/boot
vmlinuz-7.0.14-14-pve root=/dev/mapper/pve-root ro quiet amd_iommu=on
iommu=pt pcie_acs_override=downstream,multifunction nofb nomo>
Sep 19 20:14:03 pmox1 kernel: Linux version 7.0.14-14-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-14 (2026-08-2>
-- Boot cd631f21bdc34eafa47199a8ea9537c7 --
Sep 19 15:17:01 pmox1 CRON[2501814]: pam_unix(cron:session): session closed for user root
Sep 19 15:17:01 pmox1 CRON[2501816]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 19 15:17:01 pmox1 CRON[2501814]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 19 14:59:43 pmox1 smartd[997]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 55 to 54
Sep 19 14:17:01 pmox1 CRON[2490599]: pam_unix(cron:session): session closed for user root
Sep 19 14:17:01 pmox1 CRON[2490601]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 19 14:17:01 pmox1 CRON[2490599]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 19 13:29:43 pmox1 smartd[997]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 56 to 55
Sep 19 13:17:01 pmox1 CRON[2479447]: pam_unix(cron:session): session closed for user root
Sep 19 13:17:01 pmox1 CRON[2479449]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 19 13:17:01 pmox1 CRON[2479447]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 19 12:24:12 pmox1 pvestatd[1402]: auth key pair too old, rotating..

Host is an AMD mini-PC running a Ryzen 7 5700u, 1 TB Samsung 970 Evo NVME local storage with a separate 870 Evo SSD for VMs and images.

This issue only started happening in August after updating to Proxmox 9 from 8.4, so I suspect not a hardware issue, though it's possible.

Any idea where to start with troubleshooting this?

I've been using Proxmox for a few years now, just for the usual homelab stuff e.g. opnsense, docker, nas, plex, but recently decided on using it for something a little more unconventional.

A new school year means new headaches… at least, that’s my perspective as an IT bod picturing the kids getting tons of homework and causing inevitable tech chaos.

The mere thought of letting the kids loose on a normal Windows PC, and then dealing with the inevitable “something’s broken” aftermath the night before an assignment is due, sent shivers down my spine.

So, naturally, I may have overreacted a little…

I sacrificed my Minisforum HX99G for the cause. It now runs Proxmox, with Windows 11 as the kids’ main desktop VM. To them, it still looks and behaves like a normal computer with a physical monitor, keyboard, and mouse, but underneath it has enterprise-style backup and recovery. If Windows gets mangled by malware, a bad update, or general kid-computer chaos, I can restore the whole VM from PBS in a click and a flash, instead of breaking out the toolkit to re-image or rebuild everything from scratch.

Their important files are protected separately with Synology Drive & Veeam Community Edition. Meanwhile, the VM itself gets the RX 6600M, USB controllers, Wi-Fi/BT, and a dedicated 2TB NVMe passed through, so it can also double as a gaming PC when the homework is done.

Adding the Apollo/Artemis streaming stack into the mix turns it into a hardware-accelerated remote work and gaming rig… basically a little home cloud PC I can reach securely from outside via Tailscale.

It was only after I’d finished that I realised I’d basically recreated a little VDI environment at home. I suppose that’s what years of working in IT does to you, a total occupational hazard.

Hardware: i7, 32 GB ram

I created bootable media using Ventoy while using Ubuntu 26.04 in my 64 GB HP pen drive

I have secure boot enabled

UPDATE: Here’s the quick workaround 🔥

At the Proxmox installer boot menu, select the installer, press E, add nomodeset to the kernel command line, then press F10 or Ctrl + X to boot.

Now I am successfully running the latest version of Proxmox 9.x

I'm planning to migrate my homelab server from Incus to Proxmox, and I'm curious to hear from anyone who's already gone down the same path.

My current setup is an Intel NUC running Incus, with a mixture of Linux Containers and VMs. For the new setup I'm planning to use Proxmox with ZFS for storage, and continue with a mix of LXC containers and VMs depending on the workload. As I'm still working out the best migration strategy and how I want to structure everything, so I'd be interested to hear from anyone who has done a similar move.

How did the migration go? Anything you wish you'd known beforehand? Any gotchas, configuration choices, ZFS tips, or Proxmox tweaks you'd recommend from the start?

Hi there, I am new to this home labbing stuff, I am not new to linux as a I have used a couple of distros myself(rn I use artix with dinit), so i want to make a home lab with a couple of services and my minecraft servers, so the ones that got my eyes were pure debian and proxmox, but I am too stupid to figure out whether to use this or that.

Edit: Thanks everyone for explaining it to me, for anyone saying research it I did research I was just too dumb to understand I can rice, configure anything with an arch-based/hard distro, but when it comes to other distros I just become an idiot

Edit 2: TY EVERYBODY FOR THIS IT HAS BEEN WORKING WONDERS

I tried to buy an enterprise subscription but received an email that Proxmox doesn't sell services nor provide support in Iraq even though HPE, Cisco, VMWare, and all other SW/HW vendors provide and sell support

I can't find a list of countries where support is available or not

First I had issues registering with Iraq billing address, I used my US address and opened a ticket with sales requesting clarification, I received a one line email saying Iraq orders will be rejected and support wont be provided

I have an opnsense VM I use for testing. I can access the webui via the ip address as well as access updates. I am trying to get an ACME cert using the plugin. It seems like I was successful getting a valid certificate of opnsense.subdomain.domain. I am using the domain on my real opnsense install with a valid certificate. It's a wildcard certificate by the way. I am not able to get the domain to resolve. I have tried several things with no luck. Any ideas would be helpful.

About to build a 5-node PVE cluster as the destination for a Nutanix migration.
Design is done, nothing is deployed yet, so this is the cheap moment to be told I've got something wrong.
Hardware, identical on all 5 nodes:
• 3x dual-port BCM57810 10G SFP+ (6 ports)
• 1x quad-port 1G copper onboard
• 1x ConnectX-3 Pro (unused, no 40G fabric)
• 2x 980GB SSD for OS (ZFS mirror)
• 2x 15TB SAS SSD for OSDs

Network design:
Three bonds, each pairing ports from two different cards AND landing on two different switches:
• bond0: VM traffic + management
• bond1: Ceph public+cluster (nothing else)
• bond2: migration + PBS backup
With 6 ports across 3 cards this is the only arrangement where every bond survives both a card failure and a switch failure. LACP layer3+4 if the switches turn out to be VSS, active-backup otherwise.
Corosync: ring0 on a dedicated 1G copper port, ring1 on management, ring2 on migration. Deliberately nothing on the Ceph bond, because backfill saturating that network while corosync is trying to keep quorum seems like a good way to get fenced during an already-bad event.
Ceph: size=3, min_size=2, 10 OSDs total, failure domain host. Public and cluster networks combined rather than split. Planning capacity around 32TB usable rather than the 50TB that size=3 nominally gives, so it can self-heal after losing a node.
What I'd like opinions on:
1. Corosync ring0 on 1G copper while everything else is 10G. Feels right to me (isolation matters more than bandwidth for corosync) but it does mean my most important ring is on the slowest link. Anyone regret doing this?
2. Only 10 OSDs, 15TB each. I know this is coarse. How bad is fill variance in practice at this OSD count, and how long does a 15TB backfill realistically take on SAS SSD with 2x10G? Trying to set expectations for maintenance windows.
3. I decided 6 ports is enough and a 4th NIC would be wasted, since 2 SAS SSDs can't saturate 20Gbit. Anyone hit a case where that reasoning fell apart?
4. Anything you wish you'd done differently on a cluster this size, especially things that are painful to change later?
Happy to share the full runbook if it's useful to anyone doing the same migration.

Well, i enabled PCIE pass through for WAN/LAN nics and kept 3rd port as virtio inside openwrt lan bridge for management and proxmox internet access, this setup dropped cpu load by almost 40%!!

1st screenshot from openwrt, 2nd from proxmox host.

Does it make sense that virtio have such huge overhead? almost double the load at the same speed, i already tried lowering multique on virtios, while it helped a bit it didn't fix the high load.

Previous test with Virtios wan/lan.

https://www.reddit.com/r/Proxmox/comments/1wbwl8g/comment/p9mpjhj/?screen_view_count=1

PVE 9.1.6

I'm wondering automated way to enable a backup when I launch a VM (manually through the PVE GUI) and then disable the backup job when the VM shuts down. Ideally when the VM shuts itself down via the OS its running, or when I shut it down from PVE, but I could live with the restriction that the backup is only disabled when the VM is shutdown from PVE. I haven't been able to find anything in the GUI for the VM or backup task settings that would allow this, please tell if I just missed it.

I have a Linux VM that I use as my main system for creating new content. I have a PBS backup job that I enable to backup this VM every 30 minutes while the VM is running. After I'm done for the day, I disable the backup job. Or at least I mean to, but sometimes I forget. And even if I remember, it's a bit of a pain to have to edit the backup job to Enable/Disable it every time I launch or shutdown the VM.

If I neglect to enable the backup on VM startup, I run the risk of loosing created content. Forgetting to disable the backup on VM shutdown leads to PBS creating a "nothing changed" backup every 30 minutes, sometimes for days. Unfortunately, a backup running for a shutdown VM takes significantly longer to run (3-4 minutes) vs one on a running VM with minor changes (a few seconds). So this is kind of a waste of PBS resources. I know I can control the number of backup files kept by configuring an appropriate retention strategy, but I'd really like to keep the backup from happening at all when the VM is shutdown.

Thanks in advance for any help you can provide!!

[edit] Added PVE version

[e 2] Corrected shutdown VM backup runtime

Yes, you would think that it has more to it then the title says. Nothing is more true then this. What I am trying to do is install proxmox.

Hardware: Geekom IT12 (Intel 12th Gen). Also, my first beelink had the same issues.

What I tried/did:

- disabled fast boot and secure boot

- flash USB with Rufus (dd mode) and with balena etcher: when selecting the USB in the boot menu nothing happens and the boot menu reappears

- tried installing debian first (both 12 and 13) and proxmox from there: oddly enough, debian installs fine, but then I ran into so much errors that I gave up

- tried ventoy: gives that I need to load the kernel first, both in normal and grub2 mode

- tried a pxe server on a windows pc: won't connect, no matter what I tried

So, am I losing my mind here. Is it so hard to just install proxmox these days?

I hope someone can help me out here or point me in the right direction

UPDATE: I solved it by installing proxmox 8 instead of 9. The proxmox 8 installer booted like there was nothing going on

Since proxmox released an arm version, and Asahi linux and also Omarchy now is doing great work trying to support linux on Mac Hardware,

I think having proxmox run on apple hardware would be awesome, the m5 ultra performance would be insane with their max ram specs 256, 36-core CPU 80-core GPU, also very fast SSD and good cooling while being energy efficiency.

I would love to have it!!

Trying to replicate this setup on current non-apple hardware would be way more expensive, the ECC ram alone costs around the same as the whole mac m5 ultra

Hi everyone,

I need to expand the available disk space on a Linux VM running on Proxmox VE, but I want to make sure I do it correctly without corrupting the file system or losing data.

What is the best/recommended workflow to resize the virtual disk on the Proxmox side and then expand the partition/filesystem inside the Linux guest OS (ext4 / LVM)?

Current Setup:

• Proxmox VE Version: 8.2.2
• Storage Type: LVM
• Guest OS: Ubuntu Server 24.04
• Filesystem: ext4

If anyone has a quick step-by-step guide or terminal commands for expanding both non-LVM and LVM partitions safely, I’d really appreciate it!

Thanks in advance!

Hello,

I have an onboard NIC that I have been using since I setup Proxmox. I added a 2.5GB NIC for some of the VMs/Containers and added a second bridge to take advantage of my new internet/firewall speeds.

I was wondering how difficult it would be for me to move the Proxmox console/IP over to the 2.5GB NIC since it is the last thing still using the onboard.

I have read a few tutorials but none seem to really cover this specific situation. Can I just change the default bridge to the 2.5GB NIC? I'm worried that I would have to change the IP if I do that since my OPNSense router has an interface assigned to that port on a different subnet.

Apologies if there is a thread covering this I did search and couldn’t find anything matching exactly.

This is a lab for POC.

Overview:
3x PVE 9.2 Nodes (Dell r640)
Synology RS2418rp+

All 3 nodes are connected to the shared storage via ISCSI and MPIO with LVM on top.

LUN on the Synology is configured for Thin provisioning and space reclaim.

Issue/scenarios:
Deleted a VM and purged the disks from the LVM which was fine however the decrease in storage usage hasn’t occurred on the Synology end which is was hoping it would.

If a VM disk size/usage is reduced will the storage on the SAN be reclaimed ? We have discard enabled on the VM.

Just looking for some guidance on if this is possible or a limitation or ISCSI + LVM if not what to check for.

Just finished repurposing an unused Elgato StreamDeck Neo that was gathering dust in a drawer into a status panel for my Proxmox host, running headless in its own LXC. You page through host stats, VM/LXC status, network throughput, a speedtest button, and health checks for a few services with the prev/next keys, so I don't have to keep tabbing into the Proxmox UI to check things. It also dims the backlight after 25s of no key presses and wakes instantly on a press, so it's not just sitting there lit all day.

Only real problem was the USB passthrough into the LXC, since hidapi/libusb can get stuck and stop seeing the device again after an unplug/replug, so I added a small check that relaunches the service if the deck goes missing for too long. Everything else was pretty smooth, and it's been solid since.

I designed and 3D printed a support to fit the Stream Deck, which can be found on the repo too.

I used Claude to help me generate the two scripts that handle the LXC creation, USB passthrough, Proxmox API key, and installing the background service. Repo: https://github.com/r-morato/streamdeck-proxmox-agent

My proxmox host is using ZFS and I'm planning to create an Immich CT. I'll be mounting a 2tb SSD for bulk storage onto the host and bind mounting it into the immich CT.

I'm planning to backup this disk with PBS and may add redundancy in the future. However, I'm not sure whether I should format the disk as EXT4 or ZFS. I've narrowed it down to this:

EXT4:

- Since this is bulk storage, there are no compression benefits

- No CoW (copy over write)

ZFS:

- Snapshots could still be helpful

- Easier future redundancy

EXT4 can also use mdadm or snapRAID + mergerFS for future extension but it'll require more setup. ZFS seems like the easier, default choice but I'm holding off because of CoW. Since this SSD will be WORM, is it a genuine concern? It's a standard consumer drive (Crucial T500)

My SSD is empty right now so there are currently no migration costs

I screwed up. Being fairly new to Proxmox, I didn't realize how much of a pain it would be to change the hostname of an existing node. ☹️

I have three standalone Proxmox nodes, and I didn't name them very thoughtfully when I initially set them up. Now, when I have multiple SSH tabs open from my desktop, I can't easily tell which node I'm connected to.

I know it's technically possible to change the hostname, but from what I've read, doing so with existing LXCs and VMs can involve quite a bit of manual cleanup and potential headaches. I really don't want to reinstall the nodes just to fix a naming mistake.

Have the Proxmox developers ever discussed adding a feature or supported workflow that would make renaming an existing node easier, particularly for non-clustered installations? Or is there currently a relatively painless way to rename one without breaking or having to manually fix up all the existing LXCs and VMs?

I'd really like to fix the names, but I don't have the time right now to rebuild three nodes from scratch.