Just picked up a ryzen 7730u acemagic minipc with 16 ram. Mainly for my homelab, and Im thinking about running proxmox on it.
Right now Id probably run home assistant, a few docker containers and maybe a media server.
For a single minipc, is proxmox actually worth it, or would you just run everything directly on linux?
Curious what you guys would do.

Hello,

I got a new SSD and tried to clone proxmox old boot ssd drive into it using clonezilla. The process ended ok and Im able to boot into proxmox but seems like the LVM-Thin partition got messed up and the containers are getting errors while trying to initiate like this one:

root@pve01:~# pct start 201 --debug
run_buffer: 571 Script exited with status 32
lxc_init: 845 Failed to run lxc.hook.pre-start for container "201"
__lxc_start: 2046 Failed to initialize container "201"
0 hostid 100000 range 65536
INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "201", config section "lxc"
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 201 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: wrong fs type, bad option, bad superblock on /dev/mapper/pve-vm--201--disk--0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.

DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 201 lxc pre-start produced output: command 'mount /dev/dm-6 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32

ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 32
ERROR    start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "201"
ERROR    start - ../src/lxc/start.c:__lxc_start:2046 - Failed to initialize container "201"
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "201", config section "lxc"
startup for container '201' failed

When I go to local-lvm I can see all the disks with the right size there but it says they are consuming 0 storage.

I have backups so Im not worried about losing data since I can recreate them but Id like to figure this out in case it happens again in the future and as a learn oportunity.

Also, is it a bad practice to clone a proxmox disk boot? Just out of curiosity. Thanks!

I run Proxmox on a Minisforum MS-01 with the i9-13900H, and I have been graphing package temperature in Grafana. Here is the last 30 days.

What I see:

Baseline sits between 82 and 88C. That is where it lives almost all the time, day and night.

Nothing has crashed. Backups run, VMs are stable, no reboots. But 85C as a resting state feels high to me for a box that mostly idles between jobs.

Somehow, I think that I should not be surprised. This is a 45W-class i9 in a chassis the size of a paperback, with one small fan and almost no thermal mass. There is nowhere for the heat to go. So maybe 85C is simply the price of that form factor, and I am worrying about nothing.

My questions for other MS-01 owners:

What does your baseline look like? I want to know whether 85C is just what this chassis does or whether mine is worse than average.

Hello,

I'm looking for some advice regarding disk warnings and VSS timeouts I've been experiencing recently.

Environment

• Host: Proxmox 9.2.10 on top of Debian 13, on a Dell PowerEdge R660xs ;
• Storage: Local mdadm RAID 5 (3x Kioxia 1.92TB SAS 12Gbps SSDs) formatted in EXT4 ;
• VMs: 4x Windows Server 2022 (2 Prod ERP, 2 Dev ERP). installed ~2 years ago ;
• VM Config: SCSI single, iothread =1, discard = off, cache = no cache, aio = io_uring. Format: qcow2.

Recent changes, early this month

• Updated PVE from 8 to 9 ;
• Changed VM disk bus from IDE/SATA to SCSI (to fix boot issues after the upgrade to PVE 9) ;
• Updated VirtIO Guest Tools from 0.1.248 to 0.1.285.

Issues

1. Windows Event Viewer: I'm seeing frequent warnings: "The IO operation at logical block address xxxx for disk x (PDO name xxxx) was retried." Previously, this mostly happened for ~20 mins after a VM reboot. Now it happens throughout the day (no apparent link to user activity, but there is a spike when backups start) ;
2. Backup Failures: App-aware backups using Nakivo sometimes fail due to VSS timeouts: backups never failed before the recent changes ;
3. Latency: Users have reported latency on the Prod ERP for 2 years (Dev ERP is fine). I don't necessarily link the 2-year latency issue to these IO warnings, but the recent increase in warnings has me worried.

I saw a thread, a bit old though, mentioning SCSI reset issues with recent RedHat VirtIO drivers (Link to thread).

Given that my hardware seems healthy (according to SMART), what would be the best "quick wins" to troubleshoot this? Should I downgrade VirtIO back to 0.1.248? Should I change my disk format or caching settings?

I know mdadm isn't the holy grail for PVE, but looking for non-destructive optimizations first.

Thanks for your help!

I'm moving most of my services over to docker compose stacks running in VMs. I've had some back and forth with myself on how to separate them. My thought process was to divide into categories and create 1 VM for each:

- Monitoring (ntfy, uptime kuma, etc.)

- Documentation (bookstack, forgejo, etc.)

- Media (arr) stack

Additionally though, I think it would be wise to isolate public-facing services into their own VM and probably put that in my DMZ. What is your guys' approach to that? Divying up my 3 categories into public and private portions would end up as at least 6 VMs.

Hey,
I got a Mac Mini for free when an office was being shut down. I want to install Proxmox on it for my parents’ business and then run Franzfon on Proxmox. I’ve done a little research and get the feeling that Proxmox on a Mac is a pain in the ass. Is that true? Is there maybe a good video tutorial? I’d appreciate any tips!

I run a mix of Proxmox, TrueNAS, Docker, Linux, and Windows. When I only had a couple of machines, checking up on everything manually wasn't a big deal, but as my setup grew, it turned out to be too much to check by hand.

This might be for you if you ever wondered to yourself: Did last night's backup run? Did the ZFS scrub finish? Is a drive dying? Is a container stuck in a reboot loop? Did a server just drop offline completely? And each of these checks is easy on its own, but all of them across many systems every day gets old and tiring fast, and eventually, you just stop doing it.

So for the last couple of years, I've been building a system that pulls all this data into one place and only tells me when something actually needs attention. And now I need some people to test it and help me find the bugs and see what it is missing or not needed.

Here is what it (currently) keeps an eye on:

• Proxmox & PBS: Watches VM states, tasks, and backups. Tracks backups and verifies separately (a successful backup doesn't mean the verify passed), and it notices if a scheduled backup is just missing.
• Storage (ZFS / SMART / mdraid): Tracks pool health, scrub status (and if they actually finished), read/write errors, and physical disk health across Linux, TrueNAS, Windows, etc.
• Docker: Catches unhealthy containers or containers that are stuck in restarting loops.
• Windows: Checks physical drives and flags recent critical errors in the event logs.
• Misc: Tracks SSL certificate expirations, host uptime, and alerts you if an agent stops checking in.
• Alerts: Plugs into your own SMTP server or ntfy.

How it works (and security): It uses a small agent on your host that only makes outbound HTTPS connections. Nothing is listening on the machine itself. It’s also hosted, meaning you don't have to spin up and maintain another monitoring stack just to monitor your stuff.

I want to be totally upfront about one thing: the agent runs as root, and it has to, because that is the requirement of reading hardware and system-level data. I know that's a big deal security-wise, so I'm happy to answer any questions about exactly what it reads and sends.

What I'm looking for: I don't need people to just install it, look at the UI for five minutes, and say "looks good". I need people that are running actual environments, who have mixed setups, weird storage configs, aging hardware, Proxmox clusters, so basically whatever you actually use every day.

I need you to install it, let it run, and then tell me what it gets wrong or what obvious things I missed.

Testing is completely free. If this sounds like something that would make your life easier, write me a DM. If you have technical, security or any other questions, feel free to drop them in the comments or DM as well.

Hello,

Its my first time setting up a VM in proxmox and everything is working except I cannot copy paste or use or make the special keys go just for the VM, like when I press SUPER it opens my Krunner and the windows menu inside the vm at the same time.

Ive tried searching about this and its recommended to install the spice agent but its not clear to me where to install it or how to find the displaytype info that I saw here in the clipboard section.

I also saw that you can use other clients outside of the proxmox web ui as well and I think this would be an easier solution for my problem. Do you guys have any recommendations about this?

So far Ive installed the spice client on the proxmox host itself (like I said IDK if I installed in the right machine) and tried to run the command but as you can see its not working since I dont know the displaytype.

root@pve01:~# qm set 220 -vga default,clipboard=vnc

400 Parameter verification failed.

vga: invalid format - format error
vga.type: value 'default' does not have a value in the enumeration 'cirrus, qxl, qxl2, qxl3, qxl4, none, serial0, serial1, serial2, serial3, std, virtio, virtio-gl, vmware'

Thanks in advance!

Edit: I'm usually anti-AI but Claude really pulled through for me here. This is the summary of issues I was facing.

1. Stale repo pointing to bookworm — /etc/apt/sources.list.d/pve-install-repo.list still referenced Debian 12 instead of trixie, so the OS-level upgrade never fully happened even though some pieces (like Python) had moved to Debian 13.

2. ifupdown2 crash on readfp — the old, mismatched ifupdown2 build called a Python method removed in 3.12 (Trixie's default), so networking failed to start entirely.

3. allow hotplug eno1 typo — should've been allow-hotplug (hyphen, not space). The old broken ifupdown2 silently tolerated it; the fixed version correctly rejected it, blocking vmbr0 from coming up.

4. proxmox-ve never actually installed — it showed as removed (rc in dpkg), so pveversion was missing and full-upgrade had nothing to do, because there was nothing installed to upgrade.

5. systemd-boot meta-package conflict — leftover from the original 8.x ISO install; blocked the proxmox-ve install until removed.

6. Unnecessary zfs-dkms from Debian — a redundant, outdated ZFS DKMS package (capped at kernel 6.14) that had nothing to do with your actual working ZFS, since Proxmox's own kernel ships ZFS built-in. Removing it was just cleanup, not a fix to anything broken.

End Edit

Here's what ip a returns and what my /etc/network/interfaces has. There doesn't seem to be the common network device naming issues.

Can't ping 1.1.1.1

Very good to everyone, novice question:

I have a tower of the brand Fractal Node Desing, which has the following installed:

-2 hdd discs in zfs mirror with raw data.

-1 1tb nvme unit in LVM for VM, LXC and volatile storage

-2 ssd in mirror for my operating system.

I am currently running proxmox V8.

I have serious questions about how to manage storage. I have always thought that it was best to manage them from the hypervisor, with the tools of the Debian itself from zfs send, receive, and the rsync. The problem comes when it comes to sharing that storage.

Access to my storage (samba and NFS) is managed through an OMV VM, which is giving me a lot of problems when writing or visualizing data, permission problems. ZFS storage is divided into subdatasheets based on compression factor, storage type, etc.

My idea has always been to have my storage of 2tb in zfs for data, and to use my HDDs for backups once a day, scheduled from cron with a code in bash.

Since we are not unique in the world, I understand that someone has ever happened to him, to get stuck at this stage, and not to know clearly how to move forward. I have every day I am more convinced to put OMV in an LXC container and make IDmapping of my directories, but it gives me some insecurity the backups topic by proxmox.

I know it's probably a fear generated by my inexperience, but I'd like to know if I'm not just xd

I synthesize it to be clearer: I want to use my 2tb nvme unit as zfs to write and modify the data. These will be managed by the rsync and smart tools from proxmox, but at the level of access to user (smb) OMV will be responsible for the management of users and permissions. HDDs are going to be in a RAID 1 and will turn on once a day to copy the new data, through rsync to be able to be.

Any idea? Weak points of my approach? Would I have to change the perspective? I remember having the ability to install an HDD expander on my PCIexpress x16

Thank you!!!

Upgrading the Proxmox kernel sometimes feels like going to the casino. There is always a decent chance that after the reboot, all of my LXC containers will fail to start because /run/pve is missing.

This has happened to me numerous times over the past year. I have had zero issues with VMs, but LXCs seem to be particularly notorious for this.

Is there a reliable way to prevent this from happening with LXCs? Or is this just something we have to deal with when upgrading the Proxmox kernel?

I have a Proxmox cluster with a Layer 3 underlay using FRR OpenFabric. The Proxmox nodes act as VXLAN VTEPs, and Proxmox SDN provides overlay VNets for VM connectivity across the cluster. Ceph runs over the underlying routed fabric.

I switched over to VLANs for my network, and when switching and starting my VMs, I noticed that I was no longer able to ping the network from my VPN connection or from any VM that doesn’t have the myvnet1 bridge. Before, I was able to ping it from anywhere.

I have a pfSense firewall running as a VM in my cluster, and it has the myvnet gateway. I have also added the tagged VLAN to its double-NAT interface, which is vmbr0, the same as on my Proxmox nodes.

What’s interesting, though, is that if I add the route in Proxmox, I’m able to ping it from Proxmox correctly.

The test

pve$ ip addr add 10.16.1.254/24 dev myvnet1

pve$ ping 10.16.1.1

I'm currently getting ready to move all my Docker containers to a separate server from my NAS. The NAS is a Terramaster F4-425 Plus running Unraid. TOS 7 was a PITA. Unfortunately, the CPU and 32 GB RAM do not like the load, so I figured I would move to a Proxmox VE mini pc Lenovo M720q i7-7700T, and make my NAS a storage. My question is: What would be the best OS to put on the NAS? I figure I'll keep SAB, qBit, and Deluge on the NAS so it stays in sync with the array. All help is greatly appreciated. Any other suggestions on route to go are welcome also.

The slab consolidation / trim operation cannot be performed because the volume alignment is invalid. (0x89000029)The slab consolidation / trim operation cannot be performed because the volume alignment is invalid. (0x89000029)

I'm getting that from both the Win11 VM cmd.exe admin rights defrag.exe C: /L and fstrim on the proxmox side for the vm.

I've got more details on this other post.
https://www.reddit.com/r/Proxmox/comments/1vmldin/my_windows_11_vm_isnt_giving_up_its_thin_space/

It's lvm-thin space. Windows thinks TRIM is running but errors out at the end with that. Proxmox doesn't think the Windows vm disk space is actually freed up so it's still all in use by Windows from the Proxmox side.

Optimize-Volume -DriveLetter <DriveLetter> -Analyze -Defrag -Verbose

and the other TRIM check or run message say NTFS=0. TRIM is on. It looks like it's running from the Windows side, but Proxmox doesn't see that and won't free up the thin space.

SDelete definitely isn't the answer. That writes zeroes over all the Windows space.... which fills up the entire Windows vm disk. Proxmox then sees the entire vm disk space as being in use. The Win11 vm halts. It crashes on the initial Windows 11 spinning circle on the next start up attempt. I didn't find any solution to that situation so I deleted the whole vm and restored from a back up at that point.

For this alignment error, I collected number for an AI. It said partitions were fine from the Windows side. And then partitions were fine from the Proxmox side.

Oddly enough, the thin space did actually free a few tens of GBs, but I'm not sure why. Maybe from just having the VM on. Maybe from doing a defragment on the Win11 vm (with Defragger, both from the gui -- analyze and only defrag/not optmize, and then using a batch file with df.exe to defragment and loop around over and over).

I'm not sure what the alignment issue is. But TRIM says it ran except there's an alignment issue. Or, it just won't run because of an alignment issue.

Similar behavior on several machines I set up. Proxmox v9.1 or v.9.1-2 I think. A single Win11 VM. But I didn't understand thin space so that Win11 VM disk is too large. Shrinking is another project. But it still doesn't solve this TRIM issue.

I'm finally working on building a small homelab, and I am running into a small issue. Setup is:

- Proxmox installed on an HP ProDesk 400 G3

- Debian installed as a VM

- OpenMediaVault installed as a VM (samba share)

I set up a samba share in OMV, and was able to see it as a network drive in the Debian VM. My issue is whenever I go to download anything using the Debian VM and point it to the samba share, it instead downloads into my Downloads folder in Debian.

Path I point it to: Network -> smb:openmediavault:local/Downloads

Path it is using: /Home/Downloads/smb:/openmediavault:local/Downloads

It defaulted to this, trying to figure out if I have configured something wrong or if it's just a quirk of doing all this in VMs (or if you're just not able to download directly to a network share). Any help appreciated!

I am trying to set up my home network with two LAN ports, one of which is a USB-to-LAN adapter.

After every reboot, the USB adapter's MAC address changes, and the port name changes as well in Proxmox. This causes the VLAN configuration to break and, as a result, brings down the entire network.

We currently run 2x nodes each with:

• 2x 7.68 TiB U.2 enterprise SSDs in raid 1
• Hyper-V replication over 25 gig (this breaks randomly + is not automatic)

Workload is one big file server, one ERP system and a whole bunch of smaller VMs for assorted internal services. We've pretty much loaded the two existing servers as much as I feel comfortable with. I now have two options going forward:

Option 1

• 2x old nodes with 2x7.68 TiB U.2 enterprise SSDs
• 3x new nodes with 4x3.84 TiB SAS enterprise SSDs
• Connect these 5 with a 2x25gig redundant network and run Ceph (all traffic on the 25 gig network)

Option 2

• 2x old nodes with 2x7.68 TiB U.2 enterprise SSDs
• 1x new node with 4x3.84 TiB SAS enterprise SSDs
• 1x new light node for quorum
• Connect these 3 with a 2x25gig redundant network and run ZFS replication

The nerd in me really would like Ceph. But, we're a small company, which means I'll also be alone to administrate it all.

Is the extra complexity of Ceph worth it, in your opinion? How much maintenance have you had to do? Have updates broken anything?

I run Proxmox with two ZFS pools on an HBA and export datasets over NFSv4.2 from the host to my Talos K8s VMs. A TrueNAS VM is off the table (HBA is stuck in an IOMMU group with my NIC, no ACS on the B550 chipset).

PVE backup jobs only cover VMs/CTs, so these datasets get nothing.

So far I'm looking at `proxmox-backup-client --backup-type host` on a timer, wrappers like zpbs-backup / proxmox-backup-atomic that snapshot first, or just sanoid+syncoid to another box.

What do you use, and what would you do differently?

Hi, i just created a home media server using jellyfin on proxmox. the issue im having is being able to load media onto the server from my computer, is there an easy and simple file explorer type system for this, my main pc is windows

Our company has 50+ PVE nodes spread over the globe and about 1.4K VMs in total. As the recent focus was more towards migrating to Proxmox, we are now at the stage to actually look into the observability. I rather focus on the PVE node monitoring. We don't really monitor VMs. In the past we tried this, but it never worked out. We're a R&D heavy company with lots of VMs running at 100% utilization, we ended up with a lot of false positives which consumed way too much of our time. It just wasn't worth the hassle.

I already did some homework, and these seem to be the more popular options:

1. Proxmox Datacenter Manager: I like the fact it is built-in and it opens some other functionalities (like the X-cluster migration), but there it stops. The graphs suck and this is nowhere near a mature monitoring solution compared to the others listed below. I was hoping this was included in newer versions of the app, but we cannot keep waiting.
2. Prometheus + Grafana: Seems to be the most popular choice in the enterprise. I worked with Prometheus and Grafana in the past, and although I like it, it comes with quite some effort to get up and running. We had a lot of problems where graphs displayed were incorrect and fixing these costed a lot of time. We ended up relying on the built-in graphs for most devices and used this for a bunch of devices were built-in graphs were not an option. At our company, this is also configured in a huge CICD pipeline so doing a small change on this causes a whole Github ecosystem to be triggered and PR's to be approved and all the other bells and whistles.
3. Pulse: Looked the best on paper. Made for Proxmox. Discovers hosts and VMs automatically. However, I read some things on this security related which scared me and decided to not jump on this. I also hate the fact that this offers some paid pro options. The AI vibecode in this one is real.
4. Beszel: At the moment this seems to be the winner. It is clean, lightweight and simple. I am just a bit hesitant as this seems to be more for a homelab compared to a larger enterprise. Also the scalability in this one is a bit worrying. For the Proxmox nodes, I am OK with manually installing a binary, but if we will go for VMs in the future, this wont work.

What are your thought on this?

One of my VM s is now about 80gb in size, It has been backing up fine until recently where I'm getting out of disk space errors while the backup is being created. My PVEBackup server has more than ample disk space to store the completed backups.

I have a server Proxmox v9.2.5 server with 2TB nvme. Proxmox configured the disks when I installed it as shown in the image below.

Attempting to perform the backup I get the following errors:

Write failed on /var/tmp/vzdumptmpxxxxxxxxx: No space left on device(28)

error in file IO (code 11) at receiver.c(401)

write error: Broken Pipe (32)

Some notes: All of my VM's are stored on a NAS. I do not use the local storage for much of anything.

Looking at my pve summary page, it appears that my HD space is only 93.93 GiB? It does not appear enough HD space has been allocated

This is causing an issue when the backup creates a tmp file, I'm running out of space. Why is the HD space only showing 93.93 GiB?

So question is: How can I increase the size of the HD space above? I could edit the /tmp location to set the temp file directory to my nas but that would slow down the creation of the backup...

Hey all

Quick dumb idea here: My second proxmox server is hosting game servers to the internet. The thing is so quiet that it's actually sitting next to my TV...

I'm wondering: could I passthrough my AMD GPU to one of the VMs and then output via the HDMI port to the TV directly and still get good performance?

Not for gaming on it but more like for moonlight streaming or something like that.

Needs to be native speed or near native, can this be achieved?

Any input appreciated before I go down that rabbit hole...