Introduction
Got an old laptop sitting in a drawer? That's actually a decent little Proxmox VE box, and installing it isn't much different from installing on a desktop or server — with two catches that trip up almost everyone the first time. The lid closes and the whole thing suspends itself mid-transfer. The built-in Wi-Fi card just doesn't show up as a usable network option once you get to the networking step. Neither one is a bug. Both have simple fixes once you know where to look.
This guide walks through installing Proxmox VE 9.2 on laptop hardware specifically, then fixing the two things that are genuinely different about laptops versus a desktop or rack server: networking without a row of Ethernet ports, and keeping the machine running once you close the lid.
What You Will Learn
- Whether your laptop's hardware can actually run Proxmox VE
- How to build the installer USB and get through setup on laptop hardware
- Why the built-in Wi-Fi card won't work as your VM network, and what to use instead
- How to stop the laptop from suspending when you close the lid
- The errors people run into most often on laptop installs, and how to fix them
What Is This Feature?
Proxmox VE is a free, open-source virtualization platform. It installs directly on bare metal — meaning it becomes the operating system on the machine, rather than running inside Windows or macOS — and lets you create virtual machines and Linux containers, manage them through a web browser, and get most of what an expensive enterprise hypervisor offers, at no cost.
None of that changes because the hardware happens to be a laptop. The CPU, RAM, and storage inside a five-year-old business laptop work exactly the same way they would inside a rackmount server; Proxmox doesn't know or care what chassis it's sitting in. What does change is the peripheral hardware that's specific to laptops: a Wi-Fi card instead of, or alongside, a wired network port, a lid switch tied into power management, and usually just one Ethernet jack instead of two or four.
Why Would You Use It?
Buying a dedicated server for a home lab costs real money, and a lot of people already own a laptop that's too slow for daily use but still has a perfectly good CPU and a decent amount of RAM. Turning it into a Proxmox host is close to free, and it's quiet enough to sit on a shelf without anyone noticing.
It's also a genuinely good way to learn. You get real hardware instead of nested virtualization inside another hypervisor, you can practice backups, snapshots, and networking without touching anything that matters, and if you break it, a reinstall takes about twenty minutes.
I wouldn't recommend it for anything you actually depend on, though. Laptop batteries degrade, laptop storage is usually a single small SSD with zero redundancy, and a spilled cup of coffee takes out your entire cluster of one. Treat it as a lab, not infrastructure.
Prerequisites
Before you start, make sure you have the following:
- A laptop with a 64-bit CPU that supports hardware virtualization (Intel VT-x or AMD-V) — check this in the BIOS/UEFI settings, since it's sometimes switched off by default on business laptops with corporate imaging profiles
- At least 4GB of RAM just to get through the installer, though 16GB or more is a realistic target if you plan to run more than one or two VMs at a time
- A spare USB drive, 8GB or larger, dedicated to the installer — it gets wiped during the process
- A wired Ethernet connection if at all possible: a USB dock, a USB-to-Ethernet dongle, or a spare cable straight to your router
- A second computer to download the ISO and write it to the USB drive
- Physical access to the laptop, since you'll need to get into its BIOS/UEFI menu at least once
You don't need a laptop with a discrete GPU or a fast CPU for this. An old Core i5 with a SATA SSD handles a handful of lightweight VMs and containers without much complaint.
Step-by-Step Tutorial
Step 1: Confirm virtualization is enabled in the BIOS
Reboot the laptop and get into its BIOS/UEFI setup screen — usually by tapping F2, F10, Delete, or Esc right after powering on, depending on the manufacturer. Look for a setting called Intel VT-x, Intel Virtualization Technology, or AMD-V, and make sure it's enabled. A surprising number of laptops, especially business models, ship with this switched off out of the box.
While you're in there, disable Secure Boot if it's turned on. Proxmox VE can work alongside Secure Boot on recent releases, but disabling it removes one more variable if the installer refuses to boot from your USB drive.
Step 2: Create the installer USB
Download the latest Proxmox VE ISO from the official downloads page. As of this writing that's Proxmox VE 9.2, built on Debian 13 ("Trixie") and shipping Linux kernel 6.14.8-2 by default. On your second computer, write the ISO to your USB drive using Rufus on Windows or balenaEtcher on Windows, macOS, or Linux. Don't just drag-and-drop the ISO file onto the drive; it needs to be written as a bootable image, which both tools handle for you automatically.
Step 3: Boot the installer and set up the disk
Plug the USB drive into the laptop, power it on, and use the BIOS boot menu (often triggered with F12) to boot from the USB drive instead of the internal disk. Select Install Proxmox VE when the boot menu appears.
Walk through the installer: accept the license, choose your target disk, and set your country, time zone, and keyboard layout. Most laptops only have one internal SSD, so the installer defaults to using the whole thing with either an ext4 or a ZFS filesystem. Unless you specifically want ZFS's snapshots and self-healing checksums, ext4 is the simpler and lower-overhead choice on a single-disk laptop — ZFS wants extra RAM for caching and generally prefers multiple disks to show off what it does well.
Set a strong root password, an email address for system alerts, and a hostname for the machine. The installer also asks for network details on this screen. If a wired connection is already plugged in, it usually detects the interface and lets you assign a static IP right there. If nothing's plugged in yet, just get through this screen for now; networking gets fixed properly in Step 4.
Step 4: Get networking working without relying on Wi-Fi
This is the part that catches almost every laptop install. Proxmox VE builds its networking around a Linux bridge, usually named vmbr0 — think of it as a small virtual switch inside the host that lets your VMs share its physical network connection. That works cleanly with a wired NIC. It generally does not work with a Wi-Fi card.
The reason comes down to how Wi-Fi itself works, not a Proxmox limitation. Wireless access points only accept traffic from devices that authenticated with them directly. Once you bridge a Wi-Fi interface, every VM's traffic leaves with a different source MAC address, and the access point just drops it on the floor. A wired Ethernet port doesn't run into this because switches don't police MAC addresses the way access points do.
You've got three realistic options here, roughly in order of how much I'd recommend them:
| Option | How it works | Worth it? |
|---|---|---|
| Wired Ethernet | Plug directly into your router or switch, bridge that NIC as vmbr0 | Yes — do this if there's any way to |
| USB-to-Ethernet adapter | A cheap USB dongle gives a single-NIC laptop a second wired port to bridge | Yes — the easiest fix if you only have one built-in port |
| Wi-Fi with NAT | Host stays connected over Wi-Fi; VMs get a private subnet routed through it instead of bridged | Only if wired is genuinely impossible |
For a wired NIC or a USB adapter, edit /etc/network/interfaces, or use the web interface under Datacenter → your node → System → Network, and make sure the physical interface is set as a bridge port for vmbr0, with vmbr0 itself holding the IP address. That's identical to how you'd configure a desktop machine; nothing about it is laptop-specific once a wired connection exists.
The Wi-Fi-only NAT route is more involved, and honestly not something I'd bother with on a first setup. It means building a separate bridge with no physical port attached, then configuring IP forwarding and NAT rules so that bridge can reach the internet through the Wi-Fi interface. It works, but you end up hand-maintaining a small router configuration, and it fails in ways that are hard to diagnose if you're new to Linux networking. A cheap USB Ethernet adapter saves you that entire headache.
Step 5: Stop the laptop from suspending when the lid closes
By default, closing a laptop's lid tells systemd to suspend the machine, which is exactly the opposite of what you want from a server meant to run unattended. Fix it by editing the logind configuration file:
nano /etc/systemd/logind.confFind these three lines, commented out with a # by default, and set them like this:
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
HandleLidSwitchExternalPower=ignoreSave the file, then restart the logind service so the change takes effect right away, without a reboot:
systemctl restart systemd-logindClose the lid now and the laptop keeps running — fans keep spinning, VMs stay up. Worth double-checking that the machine doesn't overheat with the lid shut, since some designs rely on the small airflow gap an open lid provides. If it's tucked into a cabinet or closet, prop the lid open an inch or point a small fan at the vents.
Step 6: Access the web interface and finish setup
From another computer on the same network, open a browser and go to https://your-laptop-ip:8006. You'll hit a certificate warning the first time; that's expected, since Proxmox VE generates a self-signed certificate during install. Accept it and log in as root with the password you set earlier.
From here on, everything is identical to any other Proxmox VE install. You create VMs, add storage, and configure the rest of your environment through the same interface you'd use on a rack server, and none of it knows or cares that it's running on a laptop.
Commands Explained
| Command | What it does |
|---|---|
nano /etc/systemd/logind.conf | Opens the systemd-logind configuration file, which controls what happens on lid close, power button presses, and similar physical events |
systemctl restart systemd-logind | Restarts the logind service so lid-switch changes apply immediately, without a reboot |
ip a | Lists network interfaces and their current addresses — useful for confirming which interface is your wired NIC versus your Wi-Fi card |
ip link show type bridge | Shows any Linux bridges currently configured on the host, including vmbr0 |
pveversion | Prints the installed Proxmox VE version, useful for confirming your install matches what you downloaded |
apt install lm-sensors | Installs temperature-monitoring tools, handy for checking whether running with the lid closed is causing the laptop to overheat |
Common Errors
"No network interfaces found" during install. This almost always means the installer can't see a wired NIC and won't offer the Wi-Fi card as a usable option in the setup screen. Plug in a USB Ethernet adapter or a wired connection before booting the installer, not after the fact.
The laptop suspends and drops every VM the moment you close it. Step 5 got skipped, or one of the lines was mistyped. Double-check /etc/systemd/logind.conf — the # needs to be removed from the start of each line, and something like Handlelidswitch with the wrong capitalization gets silently ignored.
Web interface loads but VMs have no internet access. Almost always a bridging problem. Check that the physical NIC is actually listed as a bridge port for vmbr0 under Datacenter → Node → System → Network, and confirm the NIC shows as up with ip a.
Installer boots but freezes on a black screen. This is usually a graphics driver conflict on older Intel or hybrid-GPU laptops. Reboot, press e at the installer's boot menu to edit the boot line, and add nomodeset before booting again.
Troubleshooting
If networking still isn't working after Step 4, start by confirming the physical link is actually up. Run ip a and check that your Ethernet interface shows a state UP flag. If it's correctly enslaved to vmbr0, the physical interface itself should show no IP address — vmbr0 is the one that should be holding it.
If the laptop still suspends despite the logind.conf changes, check whether anything else on the system is managing power. Proxmox VE's default install doesn't include a desktop environment, but if you added extra packages, something like gnome-power-manager or upower can intercept the lid event before logind ever sees it. Removing unnecessary desktop packages usually clears this up.
For overheating with the lid closed, install monitoring tools with apt install lm-sensors, run sensors-detect to configure them, and then check temperatures with sensors under load. If they're climbing past 85 to 90°C at idle, prop the lid open slightly or add a small external fan. Laptop thermal designs generally assume some airflow through that hinge gap.
Best Practices
Back up before you start experimenting. A laptop's single SSD has no redundancy at all, so setting up a backup job to an external USB drive or a network share is worth doing on day one, not after you've already lost something.
Plug in AC power and turn off battery-related power saving. Laptops love to throttle the CPU on battery to stretch runtime, which is the last thing you want on a host that's supposed to be running VMs around the clock. Set the power profile to performance in the BIOS if it offers one, or run the laptop without its battery entirely if it's old enough that the battery's already degraded.
Skip Wi-Fi for anything that actually matters. Even with the NAT workaround running smoothly, it's a layer of complexity and a single point of failure that a ten-dollar USB adapter avoids completely.
Don't expect laptops clustered together to behave like server-grade hardware. They're great for learning, testing configurations, and running a handful of low-stakes services. They're not a substitute for real server hardware once uptime actually matters.
Frequently Asked Questions
Can Proxmox VE use my laptop's Wi-Fi card as the main network connection?
Not through a normal bridge. You can route VM traffic through Wi-Fi using NAT, but a wired connection, whether built-in or via USB, is far simpler and more reliable.
Will closing the lid damage the laptop if I leave it running like this?
No, as long as it can get rid of heat. Most laptops handle running lid-closed fine for years, though it's worth checking temperatures under load during the first few days.
Can I dual-boot Proxmox VE and Windows on the same laptop?
Not in any practical sense. Proxmox VE installs directly on the hardware and takes over whichever disk you point it at. If you want both, use a second internal or external drive, or run Proxmox inside a VM under Windows for testing, though you'll lose the bare-metal performance benefit.
How much RAM do I actually need?
The installer boots with as little as 4GB, but that's really only enough for the host itself plus maybe one small VM. 16GB is a comfortable starting point if you want to run a handful of lightweight VMs and LXC containers at once.
Does the laptop's built-in keyboard and screen still work after installing Proxmox VE?
Yes, but you generally won't touch them again. Proxmox VE runs as a headless server managed entirely through the web interface from another machine, so the laptop just needs to sit there and run.
Conclusion
An old laptop makes a genuinely useful, nearly-free Proxmox VE host once you get past the two hardware quirks that catch first-timers: Wi-Fi that refuses to bridge, and a lid switch that wants to suspend everything the moment it closes. Sort out networking with a wired connection or a cheap USB adapter, tell systemd-logind to ignore the lid, and from that point on it behaves exactly like any other Proxmox VE install. It won't replace real server hardware for anything you depend on, but for learning, testing, and running a few homelab services, it's hard to argue with the price.