r/Proxmox

hi friends,

I am in need to sell my Dell PowerEdge r720. It is used as my Proxmox server, which has a VM running my jellyfin server. Is there a way to backup my jellyfin VM and transfer it to another linux, and have it basically install the VM instance of Debian that has my Jellyfin server, with all the same configurations? please let me know if there is a better subreddit i can post to get this answered!

Is anyone else having trouble getting the VE 9.1 iso to download? I'm new to proxmox but wanted to experiment with an old laptop. I tried both the torrent (stalled, no seeds) and the direct download with a manager (timed out due to too many errors).

Is there an alternative somewhere? I don't think it's my computer; everything else internet-wise is fine.

I’m running a Proxmox node and have all of my media on a 3tb WD passport that I keep plugged in but it will randomly disconnect and not show up in lsblk. The drive is being passed through to several lxc’s. A reboot doesn’t fix the reconnect - the only thing that does is unplugging it and plugging it in. The drive doesn’t seem to power down either because its indicator light will stay when it’s plugged in whether the node is detecting it or not

Long term, the plan is to invest in a NAS or DAS, but is there anything I can do to solve this in the meantime? Thank you!

Hello there,

is it possible to create a drive (maybe across multiple physical hard drives) in CephFS and share it with multiple VMs so they can read it and write to it at the same time? I think this is normally done using NFS or SMB, but is it also possible with Ceph and CephFS? I've tried out multiple solutions from the forum without any success.

Thanks in advance.

How do you guys handle this many kernel updates in such a short time? We've had like five kernel updates in the past few weeks alone, and of course each one needs a reboot. I get that they're probably fixing urgent security vulns but the maintenance fatigue is real. Is everyone actually biting the bullet and rebooting every single time? or are you delaying them?

As the title says, is there any known issues running Proxmox on  Lenovo ThinkCentre M720Q with 16 GB of RAM?

I noticed that a place where I almost always buy my IT stuff they are selling this machine used on 299 euros (256 GB disk + 16 GB RAM) and I was thinking that maybe I should upgrade my Raspberry Pi servers (Pi 3B + Pi 5) to this one.

Before I order it I am more keen about if this machine can run Proxmox. Note that I have never used Proxmox, so that's why I ask this question and it might be stupid question. Anyway, if somebody knows why that would be a bad machine for Proxmox (eg. known hardware compatibility issues or so) then please tell me so I don't waste my time and money 😄

What are the security basics a noobie can put in place, beyond "strong pwd and 2fa"?
For now im mostly running everything as root, with unprivileged LXC, as well as PVE as root. I have a feeling it might not be great, but i dont really what to do as a routine to spin up LXCs / VMs.

As a sidenote I use Tailscale the most I can to access LXCs / VMs using its ssh feature, which, if I understand correctly, is a nice hardenning.

What is your workflow for creating LXCs / VMs at the security level?

I'm relatively new to Proxmox. I'm using unattended-upgrades for Debian security updates.

It seems like there are Debian/Proxmox package updates available several times a week, if not almost daily. I'm more used to Home Assistant and OPNsense which update much less frequently and have clearer release notes. And an easier rollback path.

I would really like to automate as much as I can, while still remaining "safe". Are there any Proxmox origin updates that I can include? And any Debian updates other than security?

Good morning.

Just came back where i left yesterday... Edge open, Proxmox tab with running shell window open. Was wondering why my notebook fan was higher then it used to be, checked Taskmanager and saw my Proxmox tab was using 12GB of RAM. 12GB of so expensive DDR 5 Ram.

Whyyyyyyyyyyyy :D Closed tab, reopened, and got back to work.

yet i still wonder why this happend.

Just about to push the button on buying a new GPU but 'm reading various bug tickets about people struggling to pass through Blackwell-gen GPUs to a guest VM.

AI gives me a whole range of rubbish about whether this works or not!

Has anyone actually managed this?

Mobo: Asus B760-A w/ i5 14500 CPU

Nvidia 5070 (Asus Prime)

Proxmox 9.1 w/ 6.17 kernel.

Guest VM is windows 11.

I've got a load plan involving hookscripts and D3Cold when the VM is OFF. It seems this is not doable at all given the Blackwells internal power management, but then even the passthrough capability was called into question!

I have a VM for all my *arr applications but this weekend the VM which hosts all the docker images has suddenly started shutting down without any errors being logged in Proxmox and I am unsure why or where to check for the issue. It happens reliably, about 5 minutes after starting the VM. There are no tasks in the Proxmox log indicating it was told to shut down not any errors. This VM has been working for several months without any changes. I tried restoring an old backup of the VM but its still having the same issue, so I dont think its happening from the VM side but Im not 100% sure. I tried watching dmesg when the issue happened but all I saw was below

[   15.930629] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[   15.930634] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
^[[A[   99.909565] workqueue: pm_runtime_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[  110.418099] workqueue: output_poll_execute hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[  192.145611] workqueue: pm_runtime_work hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
[  202.621305] workqueue: output_poll_execute hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
[  375.328624] workqueue: pm_runtime_work hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
[  385.422856] workqueue: output_poll_execute hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
[  742.686663] workqueue: pm_runtime_work hogged CPU for >10000us 32 times, consider switching to WQ_UNBOUND
[  753.052906] workqueue: output_poll_execute hogged CPU for >10000us 32 times, consider switching to WQ_UNBOUND

Any help finding why VMs shut down would be appreciated, whether its within a VM or on the host. I am on Proxmox 9.1.5 and the VM is Ubuntu 24.04.4 LTS (GNU/Linux 6.8.0-110-generic x86_64).

I've got a really old Radeon HD 6570 in my newly built server (retired gaming rig), I just need the GPU so it will boot, it's not doing any real work (if I could fully power it off after boot, that would be cool too). However It always seem so be at max fan spin, and afaik (though this is outside my expertise) it's showing up as power_state D0. Looking up GPU and proxmox in the same search always return 'passthrough' result which isn't helpful. Anyone got any ideas?

root@proxmox:~# lspci -k | grep -EA3 'VGA|3D|Display' 
  22:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550 / R5 230]
  Subsystem: Diamond Multimedia Systems Device 6570
  Kernel driver in use: radeon
  Kernel modules: radeon, amdgpu

root@proxmox:~# dmesg | grep radeon
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-7.0.2-4-pve root=/dev/mapper/pve-root ro quiet radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-7.0.2-4-pve root=/dev/mapper/pve-root ro quiet radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1
[    4.671017] [drm] radeon kernel modesetting enabled.
[    5.011705] radeon 0000:22:00.0: vgaarb: deactivate vga console
[    5.012192] radeon 0000:22:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[    5.012197] radeon 0000:22:00.0: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF
[    5.012302] [drm] radeon: 2048M of VRAM memory ready
[    5.012305] [drm] radeon: 1024M of GTT memory ready.
[    5.020315] [drm] radeon: dpm initialized
[    5.022197] radeon 0000:22:00.0: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[    5.036570] radeon 0000:22:00.0: [drm] PCIE GART of 1024M enabled (table at 0x0000000000162000).
[    5.036700] radeon 0000:22:00.0: WB enabled
[    5.036703] radeon 0000:22:00.0: fence driver on ring 0 uses gpu addr 0x0000000080000c00
[    5.036707] radeon 0000:22:00.0: fence driver on ring 3 uses gpu addr 0x0000000080000c0c
[    5.037456] radeon 0000:22:00.0: fence driver on ring 5 uses gpu addr 0x0000000000072118
[    5.037788] radeon 0000:22:00.0: radeon: using MSI.
[    5.037834] [drm] radeon: irq initialized.
[    5.231519] radeon 0000:22:00.0: [drm] ring test on 5 succeeded in 2 usecs
[    5.231533] radeon 0000:22:00.0: [drm] UVD initialized successfully.
[    5.887234] radeon 0000:22:00.0: [drm] ib test on ring 5 succeeded
[    5.888085] radeon 0000:22:00.0: [drm] Radeon Display Connectors
[    5.888088] radeon 0000:22:00.0: [drm] Connector 0:
[    5.888091] radeon 0000:22:00.0: [drm]   HDMI-A-1
[    5.888094] radeon 0000:22:00.0: [drm]   HPD3
[    5.888096] radeon 0000:22:00.0: [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c
[    5.888100] radeon 0000:22:00.0: [drm]   Encoders:
[    5.888103] radeon 0000:22:00.0: [drm]     DFP1: INTERNAL_UNIPHY2
[    5.888106] radeon 0000:22:00.0: [drm] Connector 1:
[    5.888108] radeon 0000:22:00.0: [drm]   DVI-I-1
[    5.888111] radeon 0000:22:00.0: [drm]   HPD1
[    5.888113] radeon 0000:22:00.0: [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
[    5.888117] radeon 0000:22:00.0: [drm]   Encoders:
[    5.888119] radeon 0000:22:00.0: [drm]     DFP2: INTERNAL_UNIPHY
[    5.888122] radeon 0000:22:00.0: [drm] Connector 2:
[    5.888124] radeon 0000:22:00.0: [drm]   VGA-1
[    5.888126] radeon 0000:22:00.0: [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
[    5.888130] radeon 0000:22:00.0: [drm]   Encoders:
[    5.888132] radeon 0000:22:00.0: [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    6.080052] [drm] Initialized radeon 2.51.0 for 0000:22:00.0 on minor 0
[    6.169725] fbcon: radeondrmfb (fb0) is primary device
[    6.307568] radeon 0000:22:00.0: [drm] fb0: radeondrmfb frame buffer device
[    7.706815] snd_hda_intel 0000:22:00.1: bound 0000:22:00.0 (ops radeon_audio_component_bind_ops [radeon])

Hello, I was hoping that in 2026 there would be some kind of fix for this by now but I'm still not seeing one. Hopefully I'm just missing something.

Context: I have 4x PVE 9.1 nodes in a cluster. Each has local storage as local-lvm.

​After live migrating a VM from one host to another. The disk becomes "thick" that is, if it's a 200GB disk, but only 10GB are used. The size of the virtual drive on the host disk expands to 200GB (No longer being "thin").

This can be resolved by enabling "discard" on the VM disk and performing an fstrim in the guest. However there are two issues with that.

1. If the VM has discard enabled, the live migration process absolutely thrashes the destination host. Causing high io load and freezing disk access for the most part for the other VMs on the destination host. If you disable discard on the disk, and do the same migration. This doesn't occur.

2. Enabling/Disabling discard requires a power down of the guest VM to apply. So the process becomes Migrate>Power Down VM>Enable Discard>Boot VM>Do fstrim>Power Down VM>Disable Discard>Boot VM. Which is a pretty painful process end-to-end. And has to be done after each host migration.

Besides some kind of shared storage (Ceph, a SAN..etc.) is there really no other option?

New to Proxmox. I just inherited a mess at a client from an old IT company. The setup is a SAN with 2 hosts in a cluster. They have HA set up and the QDevice on host #2 alongside production VMs. I don’t understand how this even makes sense. I thought it need to be on a 3rd device. Is there some sort of magic here I could be missing?…