Today I forgot to check how much RAM my PVE host was using before I added additional ram to a VM. Problem is that this host also passes through it's GPU to a VM for hardware transcoding, thus no output on the display from the host OS past grub. I could ping the host but it was just dead; no ssh. Also all VM's are set to auto-boot. I would get about 3 seconds in the web interface before the host would crash.

This post is basically to raise awareness in case anyone else runs into this problem. There's an extremely easy work around to prevent guests from auto starting temporarily.

When grub posts, press "e" to edit the boot options for the kernel you're using. Append "systemd.mask=pve-guests" to the "linux" line. Press F10 (I believe) to boot using your modified grub config.

That's it. Your VM's will not auto boot. You will then be able to fix your mistake and go about your day. The grub modification is not permanent, so just reboot after you've made your changes and you should be back up and running.

Good luck and make sure you check your RAM before you make a change.

OK, here we go. I installed Proxmox on an NVMe SSD via Ventoy. The install seemed to go well. Rebooted and finally got to the welcome page w/ Web GUI address as 10.0.0.216:8006. Went to my Win 11 machine to try to go to the GUI to try to configure Proxmox, but totally timed out and nothing! I can ping the DHCP-assigned address just fine. So I know it's alive. However, when I go to the router to view connected devices, the router says 10.0.0.126 is offline. Totally confused by now and ready to give up, but Reddit to the rescue, I hope...

Hey Gang!

PVE 9.2.3

Intel Arc B60 / B70 / B50 GPU Passthrough (working just fine with windows 11 guest!)

For some reason, I am unable to install Ubuntu 26.04 with the Intel Arc card in pass-through, it fails at some point during OS init, even during the installer/liveCD. This occurs on Ubuntu 26.04 Server and Desktop.

The server installer gets to the point of:

"Finished systemd-journal-catalog-update.service - rebuild journal catalog" - and then the entire VM locks up.

The Desktop OS installer silently fails during the OS loading spinner, also locking up. (Presumably the same cause?)

Bizarrely, this issue does not happen on Ubuntu 24.04, and install/runtime happens without any problems, along with win11 running my GPUs quite happily.

Anyone got any ideas?

I have a pc x99 with 128 gig of ram. I have punch of .vmx files form vmare how do I import this in promox

So, I got tired of having to manually get rid of the no subscription nag pop up every time I upgraded Proxmox. It became tedious. Eventually I wrote an APT hook that listens for package updates. Whenever apt runs, it triggers a sed command to find and replace the line of JS that triggers the nag pop-up.

First, open shell from the dashboard.

Create the apt hook:

nano /etc/apt/apt.conf.d/99-pve-nag-remover

Paste the following into the new configuration file:

DPkg::Post-Invoke { "sed -i.bak \"s/res.data.status.toLowerCase() !== 'active'/false/g\" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js"; };

Save the file and exit nano.

Restart the web service:

systemctl restart pveproxy.service

Now every time you run update/upgrade, the no-subscription nag will automatically be disabled.

I'm sure that this will have been asked before, but I'm not 100% I'm using the right wording so I couldn't find anything form a google search.

I have proxmox v8.xx running on a mini PC
Home assistant,
A Debian install mostly running docker
and an LXC container for Pihole

I logged in to the dash for the 1st time in a while and saw the banner that 8.xx is going out of support. I know for the documentation back when v9 released that the update path is to either flatten the machine and install 9 and restore the VMs from backup or to migrate to another box.

I have a couple of spare SSDs kicking around. I don't have any spare PCs of the same spec so I'm wondering if I could do the install and base config of proxmox on a spare SSD in another machine, then swap the hard drive to the original PC, different CPU, motherboard more ram etc then restore the VMs form backup to minimise downtime and general grief from the rest of the house over the lack of wifi & light switches

Hi everyone,

I am planning to reinstall one of my Proxmox nodes and switch from LVM/LVM-thin to ZFS.

The server currently uses a MegaRAID 9341-4i controller. Proxmox sees the storage like this:

NAME   SIZE   MODEL    SERIAL
sda    7.3T   MR9341   00ad5e9e0ea511a62c10

The disk model is shown as MR9341 makes me think Proxmox is currently seeing a MegaRAID virtual disk rather than the physical disks directly.

My questions are:

• Does the caching of the MegaRAID have any benefit for ZFS?
• Is the MegaRAID 9341-4i suitable for ZFS when configured in JBOD mode?
• Does this controller provide proper disk passthrough, including SMART data and individual disk serial numbers?
• Would it be better to replace it with a proper HBA in IT mode?

Any advice from people using this controller with Proxmox and ZFS would be appreciated.

Proxmox installed on 1TB drive, allocated 256GB, the rest I wish to use for whatever (700GB+), not extend!!, aka create another partition for use, which is not visible in system :)

I forgot how to do this, so can anyone help?, short of taking drive out and running through Parted, which pains me.

Cheers ma deers! :D

I'm migrating a 400-VM Proxmox cluster from a flat network with IP aliases and multiple subnets to a planned VLAN-based network.

My plan is to write a script that checks which subnet each VM belongs to and then has Proxmox assign the correct VLAN tag accordingly. It will probably cover around 200 VMs. I'll need the QEMU Guest Agent for that, but it still feels a bit messy. Are there any better ideas?

Some personal notes:

For VMs with multiple NICs, I'll need to assign multiple VLANs to the VM, one for each NIC.

I havent really built an inventory with ip adresses for each vm should I prioritise that first and really spend time on it.

Good evening!

I just got my Dell Poweredge R640, HBA330, and Boss S1 card in for my first small business Proxmox adventure! I ordered a Dell TPM 2.0 module in case a Windows 11 VM, etc needs it. Was this a wrong move? I'm seeing various reports from various dates saying that it's useless, to it's needed for Windows VMs, etc. Can anybody chime in and fill me in!

Good morning, I have a server built with:

CPU: i5-10600
GPU: RX 5700 XT
MOBO: ASUS TUF B460-PLUS

I'm encountering an issue: when I turn on the PC, the BIOS white GPU LED remains lit (which indicates a missing/undetected GPU), but the operating system boots up fine without any problems. Additionally, when I try to shut down the server, it stays powered on with a black screen (with no access to either the shell or the GUI).

Claude says that this issue might be caused by the monitor being connected to the GPU via DisplayPort, preventing the GPU from properly initializing the monitor connection.

I tried turning on the monitor first and then the PC. On the monitor, I can see the boot screen and the Proxmox shell, but the BIOS LED still stays on, and I face the exact same shutdown issue.

Does anyone know how to fix this?

solution:

I managed to understand that the problem is because if you turn off the server with the bulk shutdown, probably vm or ct not disassembling the disk correctly and therefore proxmox remains in a waiting loop endlessly waiting for those disks to disassemble correctly

So you have to turn off all the vm and ct first and when they are all offline turn off the server

The gpu is not connected to this problem, but it probably started giving me the error led and at the same time also this error

I'm in the process of p2v a windows box. The Windows partition is ~118GB with 90GB used.

I have disk2vhd the machine, plugged the USB into proxmox and made a copy and converted it to qcow2.

I've made an empty VM to then import the disk, but on import it shows a line

Rounding up size to ful physical extent <238.48 GiB

Why is the disk size 85.8 GiB yet "virtual size" is 238 GiB? It occupies over half of the space on the datastore where I intend to hold it. I want to keep it small so I can clone for testing purposes.

Minisforum MS-A2
1x 1Tb OS drive
2x 2Tb Samsung 9100 Pro (all m.2 slots are set to gen 4.0)

FIO test directly to the drive works well:

~# fio --name=raw-test --filename=/dev/nvme0n1 --size=10G --rw=randrw --rwmixread=70 --bs=4k --ioengine=libaio --iodepth=16 --direct=1 --numjobs=4 --runtime=60 --time_based
raw-test: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=16
...
fio-3.39
Starting 4 processes
Jobs: 4 (f=4): [m(4)][25.0%][r=3307MiB/s,w=1418MiB/s][r=847k,w=363k IOPS][eta 00m:45s]

However once I either create a lvm group, create a lvm-thin or create a zfs mirror (using proxmox gui), the performance drops significantly

:~# fio --name=raw-test --filename=/fast/test.img --size=10G --rw=randrw --rwmixrea
d=70 --bs=4k --ioengine=libaio --iodepth=16 --direct=1 --numjobs=4 --runtime=60 --time_based
raw-test: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=16
...
fio-3.39
Starting 4 processes
raw-test: Laying out IO file (1 file / 10240MiB)
Jobs: 4 (f=4): [m(4)][16.7%][r=504MiB/s,w=216MiB/s][r=129k,w=55.3k IOPS][eta 00m:50s]

I can't figure out why this is for the life of me

Hello all, im somewhat at my whits end, im trying to get my proxmox home lab set up and finally have some good equipment (minisform MS-01) and im just hitting road block after road block. i can walk away from either install for an hour and it will be stuck at the same place, so i assume its stuck or crashed

from what i have gathered for more efficient PCI pass-though i believe i should be using q35 as the machine type, and to use OVMF as the bios. since i have a Arc Pro B50 for my Plex/Jellyfin, i would imagine this would help with trans-coding.

i have tried installing Ubuntu Desktop 26.04 and Ubuntu server 26.04, both install medias are known good, i have installed both with the SeaBIOS and i440fx machine type.

i accept the defaults for the drive as virtIO SCSI, there is 10 cores and 16gb of ram for the VM.

i swear i have never had issues like this before but ive also had older hardware that didnt support some things.

Hi,

I have a Proxmox instance on a baremetal from a provider. I have installed pfsense with wireguard, but I can't access my LXCs : I created NAT rules on pfSense to redirect some port to my LXCs, but I get a "SSL_ERROR_RX_RECORD_TOO_LONG" error (however the access to pfSense webadmin from wireguard works great).

The issue seems to be linked to SSL certificates. I have ACME certificates on the PVE and pfsense, but not on my LXCs (I don't get how to install them).

What do I need to do to get rid of this error ?

I tried to install HAProxy on pfSense, but didn't manage to make it work.

Thanks.

Just put together a small Proxmox system, will probably be running a bunch of lightweight containers, nothing really performance sensitive.

Initially, just to test it out, I set it up with a 120GB SSD, essentially half the SSD went to system and half went to storage. All of the real storage is on a Synology NAS so the only Proxmox storage is for containers and environment, not data.

I just picked up a 256GB NVME drive as well.

I'm fine with blowing away the config and starting over, nothing is really built yet.

Does it make more sense to start over with the NVME as the primary, using the SSD as the overflow or just keep what I have on the SSD and add the NVME as pure storage for containers?

EDIT: just managed to blow up the system trying to install the NVME, so scratch all of this.

Hi everyone, I set up a Proxmox server using a Chuwi mini PC with 32GB of RAM, an AMD Ryzen 8745HS, and two Crucial P310 1TB NVMe SSDs in a ZFS raid (mirror) and PVE version is 9.2.4.

Unfortunately, the server is no longer accessible from the GUI at random; accessing the IP on port 8006 times out. The same thing happens when trying to access it with SSH; it attempts to connect but fails and doesn't throw any errors, as if the server were completely blocked.

The nice thing is that the internally deployed containers running some services like PiHole, Immich, TailScale, etc. remain active and accessible from the web.

Searching online and examining some logs, I thought it was a power-saving issue, so much so that I changed a parameter on the SSDs to disable power saving on the disks. I thought I'd fixed it; it worked fine for about 12 hours, then suddenly the GUI was no longer accessible again. Reading other forums online, some people are talking about a kernel bug in the latest version of Proxmox.

Have any of you ever encountered a similar problem? If so, how did you resolve it? Thanks.

Hi
I've wanted to setup a Ugreen NAS with TrueNAS installed for my proxmox environment. The idea behind it would be, that all of the data from the vms and lxcs would be stored on the NAS and not localy on the machine.
I run primarily game server like Crafty Controller and AMP on the proxmox machine. I would like to save the gamefiles on the NAS, so that the proxmox machine only needs to save the OS files.
What I also would like to do, is setup the NAS storage in a way, that I dont need to add it to every vm manually.
Does anyone know if this is posible or not?

Sorry for my not so great phrasing, english is not my first language.

I have a small proxmox server with a couple of drives, a 256 with OS on and 512 with a couple of containers volumes.

The 256GB drive has an LVM partition of 32GB.

How can I extend this? Ultimately I can't update my OS as it needs 2GB of space and only has ~900MB free currently. There is a 256GB drive but the partition is only 32GB.

I looked at some guides but got completely lost with physical volumes, volume groups, partitions etc etc.

lsblk:

NAME                          MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                             8:0    0 476.9G  0 disk 
├─sda1                          8:1    0     2G  0 part 
└─sda2                          8:2    0 474.9G  0 part 
nvme0n1                       259:0    0 238.5G  0 disk 
├─nvme0n1p1                   259:1    0  1007K  0 part 
├─nvme0n1p2                   259:2    0     1G  0 part /boot/efi
└─nvme0n1p3                   259:3    0    31G  0 part 
  ├─pve-swap                  252:0    0   3.8G  0 lvm  [SWAP]
  ├─pve-root                  252:1    0  13.6G  0 lvm  /
  ├─pve-data_tmeta            252:2    0     1G  0 lvm  
  │ └─pve-data                252:4    0  11.6G  0 lvm  
  └─pve-data_tdata            252:3    0  11.6G  0 lvm  
    └─pve-data                252:4    0  11.6G  0 lvm  
nvme1n1                       259:4    0 476.9G  0 disk 
├─multistore-vm--101--disk--0 252:5    0    20G  0 lvm  
└─multistore-vm--100--disk--0 252:6    0     8G  0 lvm

pvs

PV             VG         Fmt  Attr PSize    PFree   
  /dev/nvme0n1p3 pve        lvm2 a--   <31.00g    8.00m
  /dev/nvme1n1   multistore lvm2 a--  <476.94g <448.94g

vgs

  VG         #PV #LV #SN Attr   VSize    VFree   
  multistore   1   2   0 wz--n- <476.94g <448.94g
  pve          1   3   0 wz--n-  <31.00g    8.00m

lvs

LV            VG         Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  vm-100-disk-0 multistore -wi-ao----   8.00g                                                    
  vm-101-disk-0 multistore -wi-ao----  20.00g                                                    
  data          pve        twi-a-tz-- <11.62g             0.00   1.58                            
  root          pve        -wi-ao----  13.62g                                                    
  swap          pve        -wi-ao----   3.75g 

Which cloud do you use for your homelab with proxmox owncloud, next cloud, oxicloud or opencloud?

I tried to use nextcloud but I don't know how to make it work ,that I use my ssd as system storage and my hdd(zfs) for data.

My idea is to use oxicloud and make a second lxc which I would use as s3 storage to integrate into oxicloud

Edith: Made a Nextcloud VM and got it to Work

My hardware setup is :

Dell PowerEdge T360

Intel CPU with VT-d enabled

NVIDIA A2 (PCI ID 10de:25b6)

Proxmox VE

Ubuntu 24.04 VM (OVMF + Q35)

I already enabled IOMMU using intel_iommu=on and iommu=pt, and the gpu is isolated and bound to vfio-pci. Running lspci shows 01:00.0 3D controller NVIDIA Corporation GA107GL [A2 / A16] kernel driver in use:vfio-pci

The gpu is also in it's own IOMMU group (9). No nouveau or nvidia modules are loaded on the host.

When I add hostpci0: 01:00.0,pcie=1 to the VM, starting it with qm start 101 hangs and then the host server automatically reboots. If I remove the GPU passthrough entry, the VM starts normally. The issue seems specific to GPU passthrough. I already checked, and saw FLR support is present, the gpu is being detected correctly by proxmox, vfio is binding correctly, I configured OVMF and Q35, and I tried setting cpu: host and cpu: host,hidden=1. I also tried reducing the VM Ram, and following a few nvidia passthrough guides from the proxmox forums. I should also mention that nvtop says "No GPU to monitor", the card shows LnkSta: Speed 16GT/s, width x4 (downgraded) and there is no HDMI or audio function to pass through and this card only has 01:00.0.

In my VM Config I have:

bios: ovmf
machine: q35
cpu: host,hidden=1
memory: 16348
scsi0: local-lvm:vm-101-disk-0
efidisk0: local-lvm:vm-101-disk-1
scsihw: virtio-scsi-single

Has anyone successfully passed through an NVIDIA A2 on Proxmox? Is there something specific about the A2 (SR-IOV, reset behavior, Dell firmware, etc.) that I'm missing?

Any ideas on what logs or diagnostics I should check next would be appreciated.

Necessary disclaimer that I haven't used Proxmox before and don't know enough yet to know how big the learning curve will be.

I am starting to encounter more and more issues with Truenas Scale that make me want to have more control over my homelab while keeping things modular and easily maintainable. After a little bit of deliberation, I decided that migrating to Proxmox would likely allow me to more easily do the things I want and also becore a great opportunity to incorporate high availability into my setup.

Here is what I want to acheive with that new setup:
- Have multiple VMs running my PFsense install, Pihole, VM for docker, HAOS, sandboxing...
- Have high availability set up for every component I deem "necessary" and automatically fire it up on a secondary node once it's primary node goes offline.
- Keep full backups of everything without simply "syncing" my main and backup pools to prevent data loss

Here is the current hardware I intend to use with the new cluster:
- Router:
Dell R220, E3-1286v3, 4GB RAM
Would mostly only run PFsense/Pihole in normal operation
- Server 1:
Dell R520, dual E5-2450, 64GB RAM
Hosts the primary storage pool
Would run the docker VM in normal operation
- Server 2:
Custom built, Ryzen 5 3400G, 32GB RAM
Hosts the backup storage pool
Would run nice-to-have VMs, sandboxes...

I realize that such a hardware mismatch could cause complications as to high availability, and I am open to replacing one of the nodes with something else if that will measurably improve reliability, simplicity, performance, etc. I would however like to avoid buying too many new drives as I already had to buy two 16TB drives earlier this year wich left a pretty big mark on the homelab budget.

I wanted to have all three nodes have an "apps" drive that would be synced across all three of them (from what I understand, this should be running in a CEPH cluster), all the VMs and containers would operate from that pool from their host machines.

The main "Mass" storage pool would still be hosted on the R520, with the other backup pool serving as a replication target. My concern is, in the event of a node failure for this specific node, could there be a way for the cluster to keep operating from the backup and store a diff somewhere that could eventually be sent to the main storage node once it becomes available again? So far, everything has been on a single dataset of that main ZFS pool, could I split things into multiple datasets and have a portion of the pool be replicated across the other nodes in real time and place the important data there? I want to avoind placing all my media on the apps pool.

My goal with high availability is to be able to fully shut down one machine for cleaning, maintenance, upgrades and whatnot without impacting the operation of my network. I want to be able to click shut down on any node and my router, jellyfin and everything to keep working (I often decide its time to do some maintenance when specifically streaming with jellyfin so that'd be a nice touch). Having the services stay up and running in the event of a failure with minimal downtime would just be icing on the cake.

Am I seeing too big? Would such a goal require a real cluster of 3 similarly spec'ed machines and buying waaay more drives?

Thanks everyone!