I wouldn’t have thought of Proxmox being something to advertise in public space. I think it’s really funny though. Probably >90% of people seeing the Ad have no Idea or usecase for it 😅.

Edit: Apparently the “VMWare Explore on Tour” Event is on the other side of the Street right now.
Cheeky! 😁

Breaking News! ;-)

https://github.com/virtio-win/kvm-guest-drivers-windows/pull/1653

https://github.com/virtio-win/kvm-guest-drivers-windows/commit/f5e50c8bed233d96140536701934d55d09a59e8b

Version 0.1.302 is the currently broken one who needs workaround in qemu config for the VM-guest to function properly, so keep an eye on this URL for when update is released (as in newer than 0.1.302):

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/

Workaround:

args: -set device.scsi0.discard_granularity=16K

discard_granularity size should match whatever zvol volblocksize you are using (by default 16k in Proxmox 9.x).

Hey,

we are considering to retire a batch of V100 for B60 Pro Dual GPUs as we got a great quote on them. Does anybody have any significant experience with the following aspects of Intel GPUs on proxmox:

• Slicing
• Windows Driver Stability
• AI stability

We don't have to provide real time services and can make all workloads asynchonous, stability and price are much more important to us than performance; As in if we can have two of three of cheap, fast or good, we are ok with cheap and good, doesn't have to be fast.

Any experience with any of the intel arc pro is appreciated.

first let me tell you i have tried and give it a try on Proxmox it is very easy via helper script. but there are some cons and pros too

I'm noob in Computer Sciences so i cant configure on my own by general knowledge if given specific instructions to follow yes i can do that.

the reason i want Proxmox is iam running 4-5 servers on of minipc which are Immich, Adguard Home, Homeassistant, Frigate and some upcoming years i will add some more.

first my most important questions

1: It is better to configure Immich on Docker VM/LXC on Proxmox?
2: what if a just simple setup a Debian base image and install immich on it via docker?
3: how to Recover backed-up data from immich already running on docker ubuntu to this setup? and is the new proxmiox immich is future proof of updates?
4: i have multiple servers running i want to share same storage to other LXC/VM too is that possible too?
5: is this easy to return to my Ubuntu docker setup if my Proxmox doesn't satisfy my needs?

any expert in Proxmox having configured successfully Immich and all my related questions would like to help me i would be very thankful to him/her.

Ive got my proxmox server on a VLAN sat behind an opensense firewall... do i still have to use the proxmox host firewall and CT/VM firewalls?

So I bought a used hp elitedesk G9 that came pre-installed with Windows 11 Pro. Does it make sense to override the install with proxmox and run windows as a vm? Or should I do the other way around and install proxmox on a vm within the Windows 11 Pro OS?

Will I lose access to the Pro OS? Does that matter? lol

Your recommendations are welcome and greatly appreciated. Thank you in advance

Hi,

i upgraded some old VMs from windows server 2012 to 2025 using in place upgrade.

it went fine up to 2022, then it was throwing some errors, when i tried the upgrade to 2025.

I changed the CPU type from x86-64-v2-AES to host, and now it boots.

It doesnt boot with any other x86 CPUs.

Is it an expected behaviour? What could cause this?

PVE version is 9.2.3, with 40 x Intel(R) Xeon(R) Gold 6209U CPU @ 2.10GHz (1 Socket)

3-node PVE + Ceph 19.2.6, following the aes → aes256k migration. Cluster-owned keys are done (PASS: Every service key uses 'aes256k'). I then staged client.admin with --rotate-all-storage-keys --rotate-admin-key --apply. Refreshing consumers has barely started (about 27 sessions still on the old key).

Separately, mon.pve3 won't start. Its RocksDB store is corrupted: Corruption: block checksum mismatch ... store.db/184870.sst, so it aborts with ceph_abort_msg("failed to write to db"). The other two mons are healthy (63 MB stores) and in quorum. pve3 also has a dead OSD with BlueFS corruption, which looks like the aftermath of a watchdog hard reset on 18 Sep.

The dry run now warns that not every monitor can keep two client keys valid, and that I shouldn't add or downgrade monitors while a key is staged. I ran --abort-staged-key client.admin --apply. Step 1 passed ("restored managed copies of 'client.admin' to its current key"), but rollback verification is incomplete until every monitor answers, so --confirm-abort-clients-refreshed can't run.

What is the supported way to get pve3's mon back? Is pveceph mon destroy pve3 followed by pveceph mon create safe while the key is staged and the abort is half-done? Or must the rotation be fully resolved first, and if so, how, with one mon unable to answer?

pveversion and ceph versions output below:

pve-manager: 9.2.20 (running version: 9.2.20/49318c671b82f31e)
ceph: 19.2.6-pve4
ceph-fuse: 19.2.6-pve4

{
"mon": {
"ceph version 19.2.6 (7198987e0613d69ffb68c62f59cf70ce51a10eb7) squid (stable)": 3
},
"mgr": {
"ceph version 19.2.6 (7198987e0613d69ffb68c62f59cf70ce51a10eb7) squid (stable)": 3
},
"osd": {
"ceph version 19.2.6 (7198987e0613d69ffb68c62f59cf70ce51a10eb7) squid (stable)": 5
},
"overall": {
"ceph version 19.2.6 (7198987e0613d69ffb68c62f59cf70ce51a10eb7) squid (stable)": 11
}
}

Hi everyone, I made a new account for this post. I'm going to go a head and post this on a few other forums where there might be some interest. I'm also not sure if anyone solved this problem before, but if they had then the internet long forgot about it. Anyway, I managed to get GPU (the D500) passthrough working on my MacPro 6,1 (the trashcan model) in Proxmox version 9. I know it's a VERY niche problem to have, but I consolidated it all on my GitHub for it.

And yes, I used to AI on the project, so be mad about if you want... idc... I suck at writing guides and papers, so it is what it is. I hope at the very least it can help someone out there if they run into the same issue. At least it's documented.

https://github.com/demonphage-glitch/macpro6-1-d500-proxmox

Hi,

Tried to configure CPU governor from “powersave” to replace “performance”, then I found the CPU loading keep higher.

Loading returned to normal once rollback to “performance”.

CPU is i5-6500T and only 2 options allowed to change between performance and powersave.

Any other configuration could try?

Thanks

I've a mechanical rotating hard disk, put into a USB cage and connected to a Proxmox node (x86 running PVE version 9). The USB cage is a USB 3.0 one, but no matter I put that USB device into a VM, or use the PVE console, I only got around 40MB/s performance. I tried to put the USB cage to another computer (Mac), and I got around 180MB/s performance. So, my question is:

How to get a USB hard disk to have good performance on a Proxmox PVE 9 node?

My performance test is just a dumb write test like:

date ; dd if=/dev/zero of=/dev/sdb bs=40MB count=200 ; date (sdb is the USB disk)

It took 3 minutes something on Proxmox, natively in console or in a VM by USB passthrough.

Thank you for your help.

Edit: the port was running at USB 2 speed, ie. 480M, confirmed by running 'lsusb -vt' on console. That's a cable/port/connector issue. After multiple plug-and-replug on the port, now 'lsusb -vt' shows 5000M speed, ie. USB 3. Thank you for everyone's help here.

Hi everyone,

I’m looking for advice on Windows Server licensing for a hosting environment I manage. I want to understand the most cost-effective and compliant way to offer Windows Server VMs to multiple customers.

My current infrastructure:

• Hypervisor: Proxmox VE
• Physical server: 2 × Intel Xeon E5-2682 v4 @ 2.50 GHz
• Physical cores: 32 (16 cores per CPU)
• Logical CPUs: 64
• Environment: Multiple Windows Server VMs running on the same physical host
• Hosting model: Different customers rent individual Windows Server VMs from me.

What I want to achieve:

I would prefer to let each customer purchase their own Windows Server license instead of including the licensing cost in my monthly VM pricing.

For example, if I provide a customer with a VM configured with 4 vCPUs and 16 GB RAM, can they purchase a license based on the VM's allocated virtual cores instead of requiring me to license all 32 physical cores of the host?

Can customers legally use their own Windows Server licenses on VMs hosted on my shared Proxmox infrastructure?

Can customers license individual VMs based on virtual cores, and what are the minimum core requirements?

If I operate multiple Proxmox hosts and migrate VMs between them for maintenance or fail-over, how does licensing work?

I'm building a test server (2 NVMe + 4 HDD, no internet access) and I have to use mdadm instead of ZFS for the host. I can't use ZFS because of resource limitations in my organization (it has to be mdadm). I know the Proxmox installer only offers ZFS for software RAID, not mdadm.

Has anyone taken an already installed and running Proxmox VE host (single disk) and converted it to an mdadm RAID1 mirror afterwards? Is that practical, or a bad idea?

Or is the only sane way to install Debian 13 first, build the mdadm RAID1 in the Debian installer, and then install Proxmox VE on top of it (the "Install Proxmox VE on Debian 13 Trixie" method)?

If you run it like this, any gotchas? In particular UEFI boot redundancy (ESP on both disks), GRUB, initramfs, and kernel/package updates.

Thanks!

* Second try publishing after receiving quite a few dm since the project was removed from here. I removed the Curl-bashing section as requested. I encourage you to review the code and give me your feedback here :)

I'm used to the Proxmox web GUI. I like it. My muscle memory is built around it. But every once in a while the shit hits the fan (network's borked, a bridge network config went sideways, the web UI won't load...) and I end up on the local console trying to remember the right qm/pct/pvesh incantations, with the pressure of getting that Plex server back online fast.

So I built proxhawk-tui: a text-based console that looks and navigates like the Proxmox web GUI. Same resource tree, same per-object menus, same panels, just rendered in your terminal with box drawing, braille graphs and (optionally) Nerd Font icons.

This is vibecoded. I built it with Claude Code. I directed it, reviewed it and tested it on a real nodes, using an integration test script that hits every panel and verifies writes through the API. Still, I'd rather be upfront about it.

What it does:

• Same layout and menus as the PVE 9 web UI (Datacenter / Node / VM / CT views, tasks & cluster log panel)
• Read and write: Add/Edit/Remove dialogs are generated from the API schema, so you get the same options and defaults as the GUI
• Covers most of the GUI: storage, backups, HA, permissions, SDN, firewall, network (with apply/revert), disks/ZFS/LVM, Ceph, snapshots, clone, migrate, cloud-init...
• Consoles: qm terminal, SSH into Linux VMs without a serial port (finds the IP through the guest agent / neighbour table), pct enter, node shell
• Community Scripts integration: browse and launch the awesome community-scripts.org helper scripts right from the menu (plugin, enable it in F4 > Plugins)
• Batch start/stop/backup, keyboard + mouse, 10 themes, CLI mode (pvetty guests list -o table)
• Tiny footprint: pure bash + the Perl/pvesh already on the node. No daemon, nothing to install besides itself

Install (on a PVE 7/8/9 node, read install.sh ):

Repo: https://github.com/Mrdindon/proxhawk-tui

Credit where it's due: I took some inspiration from other projects, especially pvetui by devnullvoid, which is great and worth checking out. (Mine was actually called pvetui at first, I renamed it to avoid confusion.)

What's next: right now it runs locally on a node only. I'm working on a remote version so you can manage multiple hosts/clusters from one place.

I'd really love feedback: what breaks, what's missing, what panels you'd actually use when things go wrong, whether the keybindings make sense. Issues and PRs welcome. Be gentle, but honest 🙂

Hallo,
gibt es die Möglichkeit auf einem geklonten Server in Proxmox, der kein Internet hat Copy & Paste zu machen? Es ist in der Konsole und Ubuntu.

Hi all, I have just acquired a N100 NUC with dual Intel I226 V on which I installed PVE and it's just been running an Openwrt instance so far.

Now it has a link flaps on nic1 every 20 min:

Oct 13 02:06:16 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Down
Oct 13 02:06:19 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
Oct 13 02:26:24 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Down
Oct 13 02:26:27 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
Oct 13 02:46:33 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Down
Oct 13 02:46:36 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
Oct 13 03:06:37 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Down
Oct 13 03:06:40 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
Oct 13 03:26:42 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Down
Oct 13 03:26:45 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
Oct 13 04:07:09 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Down
Oct 13 04:07:13 pve kernel: igc 0000:02:00.0 nic1: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX

The Link will come back up immediately and on the client side (an UniFi AP), there even isn't any Link Down log and the AP thought everything is normal. Don't have any serious outage but if I keep ping the router I get one timeout around the time of link down.

Have been trying to fix this for the last couple days and have tried:

1. Disable ASPM, EEE, C-State

2. Turn off Hardware offloading: TSO/GSO/GRO

3. Update NVM firmware to latest (2.32)

4. Change cables

But none of these worked and the problem persists. The only thing worked is to force nic1 to run in 1000Mbps mode but it is not what I wanted (I have a 2G broadband).

I am literally out of any ideas how this is happening and how to fix it. Please help me

PVE-UPS is a small appliance (LXC or Docker container) that watches one or more UPS devices, via SNMP or an existing NUT server, and shuts Proxmox VE and Proxmox Backup Server hosts down through the API when the power fails. It is configured entirely in a web UI, with no agent or scripts on the nodes.

Two releases have come out since the last summary (4.2 and 4.3). Most of what follows started as a GitHub issue, so thanks to everyone who reported something.

History tab (4.3)

Remaining runtime, load and charge of every UPS over time, from one hour up to 90 days or a freely chosen period. Outages, triggered shutdowns and warning/critical events from the event log are drawn into the chart, and the runtime threshold appears as a dashed line, so after an outage you can see how close it actually got. You can drag to zoom, open an outage table (duration, lowest runtime and charge, whether it triggered) and export the raw values as CSV.

The data stays local in its own SQLite file, 90 days by default, roughly a few MB per UPS per quarter. It is written in the background and cannot delay a shutdown. On a new install it is on; after an update it is off until you enable it under Settings → System.

Cluster-wide guest stop without Ceph (4.3)

The parallel guest stop used to exist only as part of the Ceph procedure. It is now a switch of its own: before the first node goes down, every VM and container in the cluster is asked to shut down at once, instead of each node working through its guests in reverse startup order. That helps where the sequential version takes longer than the battery lasts. Off by default, and like the rest of the cluster support still marked Beta.

CyberPower network cards (4.3)

CyberPower cards are now read through their own MIB, including cards without any RFC 1628 support. "Automatic" detects it the same way as APC PowerNet.

Docker image for Raspberry Pi (4.3)

The image is now published for arm64 and arm/v7 in addition to amd64, so the UPS monitoring can run on a small, low-power device rather than on one of the machines it shuts down. (Thanks to @ somejavadev for PR)

Smaller changes (4.2 / 4.3)

• Extra headers per webhook, for targets like Nextcloud Talk that need more than one.
• Disabled webhooks can be saved without a URL.
• The login page works with password manager autofill again.
• Successful self-tests can be kept out of the event log; failures are always reported.
• install.sh has a --template-storage option and a --help listing every option.

From earlier releases: Proxmox Backup Server as a shutdown target, several webhooks with Slack, Discord, ntfy, Teams and custom formats, and Proxmox VE cluster support (Beta) with HA disarm (requires PVE 9.2+) and an optional Ceph-aware shutdown order.

No configuration changes are needed. Updates install as before: release upload in the web UI, docker compose pull for the container, or via community-scripts.

• Repo: https://github.com/ffind-dev/pve-ups
• Changelog: https://github.com/ffind-dev/pve-ups/blob/main/CHANGELOG.md
• community-scripts: https://community-scripts.org/scripts/pve-ups

Feedback is welcome, particularly from clusters.

45Drives is hosting a free Intro to Proxmox VE webinar on Wednesday, October 14, at 3:00 PM ADT.

Learn how Proxmox VE delivers enterprise-grade virtualization, simplifies migration from legacy hypervisors, and helps organizations build resilient virtual machine infrastructure without vendor lock-in.

Our team has designed and deployed Proxmox VE servers and clusters for enterprises and federal agencies. We’ll share practical insights and deployment strategies to help organizations take control of their virtual infrastructure.

📅 Wednesday, October 14, 2026
🕒 3:00 PM ADT
🎟️ Free webinar

Register here: Proxmox Webinar | 45Drives

#Proxmox #Virtualization #OpenSource #45Drives

We’ve been working on a Proxmox VE integration for WHMCS to make VPS provisioning and service management easier for hosting providers.

It supports both KVM and LXC and includes automatic VPS provisioning, OS reinstallation, IPv4/IPv6 management, and VPS controls from the WHMCS client area. It also supports browser-based console access through noVNC, SPICE, and xterm.js.

In version 1.1.0, we added IP management options that allow administrators to assign, unassign, and reserve dedicated IP addresses.

The goal is to handle the usual VPS lifecycle through WHMCS while using Proxmox VE for virtualization.

We developed this module at WHMCS Global Services. If you’re interested in the technical details, the full feature list is available here: https://whmcsglobalservices.com/proxmox-vps-whmcs-module/

Seemingly out of nowhere, I could log in to neither the web gui nor SSH with username and password. I could still access my PVE using an SSH key though.

Repeated authentication failure 401.

Lots of research and hair pulling later, I removed all "!"s in my password and it worked.

I was not expecting the password to be the issue. Is that really a thing?

Disclaimer: I am not an IT professional, just a homelab enthusiast. Criticisms are welcome.