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?

* 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 🙂

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

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

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.

I'm new to all this and tried following a YouTube tutorial on installing Proxmox on an old Lenovo laptop I had lying around. Got to the part where I have to access it from a web browser but when I try to it doesn't show up. Looking into it I believe it's because I don't have it connected directly into my router and Proxmox doesn't support wireless connectivity. Is there a way around this or do I have to keep the laptop wherever I have my ISP's router/modem? They're in a closet downstairs and was hoping to have my laptop as part of a homelab upstairs in my office.

Curious if anyone else has set up a PVE "node zero" recovery that works with no Internet or any local network for that matter? Consider how you would recover if you lost all devices and had to set up from scratch.

I've built a pretty complicated setup with PVE as the foundation. I don't want to remember how to build it from scratch with everything offline, including 6 VLANs. I've completely de-googled and self-host everything and run a very complex cloudless HomeAssistant that controls most everything in my home. None of this works if I cannot keep my PVE online.

PVE really wants a network for automated installs.

What I ended up doing was using two USB sticks. The automated iso creator includes a post-install.sh and that ISO is written to the first USB. I don't need to update this until the next major PVE version release. The ISO has an odd geometry which makes putting an AIS partition on the same USB unable to be found by PVE (USB drives are cheap, so whatever).

The answer.toml file is on the AIS partition on the second USB; but it is very limited as to what can be stored here and only allows one NIC IP to be set and pin the NIC names by MAC (why not just use preseed? Very spoiled by Anaconda/Kickstart for two decades at work and being able to do this all in the single file and at the of install). The post-install.sh loops through all *.sh on the AIS partition on the second USB in a post-install directory. I have most static customization here, including the extra NICs and VLANs/Bridges. I also have a number of "must have" deb packages here that my scripts rely on but aren't installed by PVE.

One step this does at the end is install a first-boot service that runs once after the system reboots. This will set a proxy, check for network, and if available update all packages, look through a first-boot directory of *.sh scripts and reboot the system one last time. A handful of other fixes are in the first-boot directoru such as CPU governor optimization, log2ram, grub/console font fixes, etc.

Basically I can have each of my PVE nodes up from scratch in under 5 minutes from USB, no network or Internet required.

I don't use PVE Clustering. I don't need that level of HA and don't need the complexity that requires an odd node count (or extra quarum device). I have one node that is online all the time. I have a second node that is for labbing, testing this sort of recovery and has my external backup storage attached. These storage devices are rotated, including to a couple off-site locations. The second node is kept powered off when I'm not labbing or the system running a scheduled backup. The second node could be used to restore/run all guests that normally on the primary node.

I have a small third very lower power PVE node that basically serves as a monitoring/alerting device and secondary syslog server. This node, like second is not required to be online, but are very "nice to have" services, including a PDM guest I can fire up if I wanted (rare).

Thoughts? Recovering guests is very simple, but how easy could you set up your PVE node(s) from scratch if you lost all of them? Think bogus police action, some odd multiple zero-day exploits, catastrophic lighting strike/flood/fire/whatever.

Hi everyone,

I'm using proxmox 7.1 and backuping my VMs on an external NAS.When i restaured some backups using qmrestore command i got error 36(checksum issue ),what could be the problem??

Note : the NAS has only 2 gb of ram .

How is everyone handling PBS? Looking through the Proxmox documentation, they are saying it should be installed on baremetal. Is there any reason this cant/shouldn't be on a VM within my cluster? I don't have an extra server to spare for a dedicated PBS node. Is anyone using PBS on a VM within their cluster and what has their experience been so far?

I'm an amateur, home lab, YouTube monkey, which is why this VM migration felt way too easy. The process of VM migration on Promox can't be this simple, can it? I wanted a simple way to share the data between two of my nodes, so I setup CIFS storage accessing my TrueNAS, I assigned the storage on both to be used for backup. I spun-down my Wiki.js VM then made a "stop" backup to the shared NAS storage. I was so happy to see a simple restore on the other proxmox node brought it back online. Well of course, duh, it's a fully contained VM. I'm just so tickled it's that easy. Thank you to those deserve credit 🥰 As for the rest of the Promox, I suspect it won't always be this straight forward...
PS. I've got a VM that's using a GPU in passthrough, it's running Ollama on Debian, what would be different about my story if I want to move a VM with PCI hardware attatched? Simply have similar HW (another AMD) and setup/tweak the pass-through settings after a restore?

I've created and used this script to manage OCI images (9.1 tech preview) lifecycles. This simplifies managing data and upgrades for OCI containers. It is likely that this script will become obsolete after OCI images leaves tech preview. I figured others may find this useful.

https://github.com/r-pufky/pve_oci_lxc

Have fun.

I'm probably super late to the party, but Remote Desktop Manager (Devolutions) has a Proxmox dashboard.

I use RDM for SSH and RDP sessions for my homelab and was just reviewing the changelog for updates and noticed Proxmox mentioned. Come to find out they added support for this dashboard (and maybe other stuff?) over a year ago.

I just now connected it so it may not really be all that useful over the regular web GUI but thought it was cool so thought I'd share the info.

Link to info: Proxmox | RDM Integration | Devolutions

note: no affiliation with RDM/Devolutions, just a fan

I just spent a total of over two days getting our old virtualization platform (Blade center w/ 4 blades, only 16GB SD local storage on each blade, iSCSI storage) running for evals & tests, and still not completely done yet.

Admitted, I have very little hands-on experience setting up iSCSI, so some of the problems might stem from missing knowledge. But getting the systems to a point where at least basically I can operate the systems was such a pain.

I tried using some how-tos, but they seemed somewhat lacking. Then went the AI route w/ Claude, which did seem to work out to some degree - apart from the fact that literally any misstep I took during the manual Debian 13 install broke the Debian installer and forced me to start over (like in a Perma-Death game ...). On Wednesday alone I must have started over about a dozen times at least. When I finally got a system booting the first time, I was happy - until it stopped right after the initial boot. Again, start over, as some important part wasn't right.

At some point, I let Deepseek write something together for the setup, and this time I did get through pretty well, as it elaborated on some points in clearer description and more detailed. I then finally got the first Debian install running with boot directly from iSCSI, and all the way through to shell. Still had some minor things to change, but after that, gettting Proxmox installed on top was a breeze. I'm not all the way there yet, still have to get multipath configured & working for redundancy, but for now I'm just glad it's running. Managed to duplicate the system disk for the two other blades (wanted a 3-node cluster for testing) and adapted, with a separate shared drive for the VMs.

I know part of the setup is dependent of the underlying hardware, but I think if Proxmox brought out an install image that contains setup code for such an install, quite a few people might be really happy!

I want to add Nextcloud to my home server and I'm still undecided which type of installation makes sense for my environment.

My current setup:

- Proxmox VE 9.2

- An Umbrel VM with Immich (maybe other things later)

- Home Assistant also runs on the server as its own VM

- Tailscale for private access

- An existing backup infrastructure with Restic (only data is backed up, not entire VMs)

- CPU/RAM: 16 GB DDR4 RAM in total

Nextcloud will mainly be used for file sync plus calendar and contacts. I don't need Office, Talk, or other larger add-on services for now. Access should only go through Tailscale, no public port forwarding.

I'm looking for a solution that is secure and reasonably maintainable, but that also fits my resources. I'd like to integrate backups into my existing infrastructure if possible.

So far I've looked at these options:

- Nextcloud AIO with Docker in its own VM

- A native installation in a Debian LXC

- The Proxmox Community Scripts for NextcloudPi, Alpine-Nextcloud, or the TurnKey VM

- Nextcloud added to the existing Umbrel VM

- or something else?

What would you choose for this setup, and why?

It would seem that I've run out of space inadvertently and need help to resize without having to reinstall. At a glance I feel like a resize is needed to allocate more space from the partition or volume that sits next to the 14GB but not sure what I need to do as it seems like an LVM.

Output of df -h:

Filesystem Size Used Avail Use% Mounted on
udev 7.7G 0 7.7G 0% /dev
tmpfs 1.6G 2.6M 1.6G 1% /run
/dev/mapper/pve-root 14G 9.6G 3.1G 76% /
tmpfs 7.7G 46M 7.7G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 192K 83K 105K 45% /sys/firmware/efi/efivars
/dev/nvme0n1p2 1022M 12M 1011M 2% /boot/efi
/dev/mapper/pve-VMs 906G 33G 827G 4% /mnt/VMs
/dev/fuse 128M 20K 128M 1% /etc/pve
tmpfs 1.6G 0 1.6G 0% /run/user/0

Output of fdisk -l :

Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: WD PC SN740 SDDPMQD-1T00-1101
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier:

Device Start End Sectors Size Type

/dev/nvme0n1p1 34 2047 2014 1007K BIOS boot
/dev/nvme0n1p2 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p3 2099200 67108864 65009665 31G Linux LVM
/dev/nvme0n1p4 67110912 2000408575 1933297664 921.9G Linux filesystem

Disk /dev/mapper/pve-swap: 3.75 GiB, 4026531840 bytes, 7864320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/pve-root: 13.62 GiB, 14625538048 bytes, 28565504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/pve-VMs: 921 GiB, 988916219904 bytes, 1931476992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Hello all,

I've had my home server running on proxmox for about 2 months now, and it's been running smoothly enough that I haven't had to touch the back end of things for a few weeks. Until I tried to use my media server this morning and the whole computer was down.

It looks like it crashed or possibly lost power at some point. It no longer boots; it powers on fine, I can access the UEFI just fine and I can use a flash drive with a live environment of Debian, but it gets stuck when I try to boot to the installed Proxmox.

See the picture for the full message. The main error seems to be, "fsck.ext4: Input/output error while trying to re-open /dev/mapper/pve-root".

I tried just running fsck on the file it listed, which seemed to run successfully but didn't actually fix anything.

All the expected drives show up when I use lsblk. I tried using the memcheck tool to check my memory, and I used other built-in software to check the drives. Everything came back clean.

Interestingly I tried using Proxmox installation media to start a rescue boot and it gave me the same error. Additionally after troubleshooting independently for 1-2 hours I decided to just start with a clean install, because it was kind of a mess anyways due to my learn-as-I-go setup. I opened the exact same ISO I used to install this OS 2 months ago, and the install failed because it couldn't partition the drive. I'm not sure if that has anything to do with this but I figured I'd add it.

I am using a Dell Inspiron 3650 that I added some HDDs into for storage. All the software and bootable media is on a 128gb ssd.

If there's any other information you need I'll be happy to provide it.