WZ-IT supports Proxmox setup and Managed Proxmox. VM configuration, networking, backup and ongoing maintenance are agreed within the respective scope.
A VM receives virtual hardware and its own guest operating system. This workflow follows installation of the Proxmox host. Ubuntu or Windows is installed inside the VM rather than on the running hypervisor (VM fundamentals).
As of October 2026. Workflow for the Proxmox web interface. Size resources for the operating system and application; this article makes no general performance promise.
Contents
- 1. Prepare ISO and storage
- 2. Select virtual hardware
- 3. Install Ubuntu or Linux
- 4. Install Windows
- 5. Accept networking and operations
- Diagnose errors
- Sources
1. Prepare ISO and storage
Obtain installation media from the operating system vendor, verify the checksum and upload it to storage supporting ISO content. Choose storage supporting Images for virtual disks. ISO storage and VM storage can differ (storage model). Check capacity and the intended backup path before creation.
For Ubuntu, the vendor covers download and installation. Windows media and usage rights come through the appropriate Microsoft distribution channel. Creating a VM does not grant a Windows licence; Windows Server licensing is a separate topic.
2. Select virtual hardware
Open Create VM in the web interface. Set node, an unused VM ID, name and ISO. Then coordinate system, disk, CPU, RAM and networking. The VM documentation explains the individual settings.
| Decision | Clarify before confirming |
|---|---|
| Firmware | Guest-supported BIOS or UEFI boot; matching EFI disk for OVMF |
| System disk | Capacity, target storage and guest-supported controller |
| CPU and RAM | Guest and application requirements, plus host reserves |
| Network interface | Bridge, VLAN, address assignment and firewall |
| Installation | Correct ISO, boot order and console access |
The EFI disk holds UEFI variables and does not replace a system disk. VirtIO devices need matching guest drivers. Settings from a specialised guide are not universal; Talos in particular has its own VM requirements.
3. Install Ubuntu or Linux
Start the VM and open its console. Select the new virtual disk as the guest installer's target. Configure language, users, networking and packages according to requirements. The Ubuntu installation workflow explains the steps inside the guest.
After installation, boot from the virtual system drive; eject the ISO or correct boot order. Update the guest and configure required administrative access. If using the QEMU guest agent, install or enable it in the guest and enable the option in Proxmox (guest agent).
For many similar Linux VMs, an appropriate cloud image with cloud-init can replace manual installation. This initialises guests; auto-installing the Proxmox host is a different operation.
4. Install Windows
For VirtIO devices, provide the VirtIO driver ISO alongside the Windows ISO. If setup does not see the virtual SCSI disk, use “Load driver” to select the matching storage driver. After installation, add missing network and other device drivers inside the guest. The guest agent is an additional service rather than a driver replacement.
For Windows 11, follow Microsoft's system requirements: these include a compatible CPU, UEFI with Secure Boot capability, TPM 2.0, at least 4 GB RAM and 64 GB storage. Provide appropriate OVMF/EFI and TPM 2.0 devices in Proxmox. A TPM device alone does not satisfy all requirements. Do not replace requirements with bypass procedures.
5. Accept networking and operations
Checklist for your own acceptance:
- Compare guest address, gateway and DNS against the intended network.
- Allow access only from the intended networks.
- Check reboot and orderly shutdown.
- Document updates and administrative accounts.
- Include the VM in a backup job and verify recovery separately.
Proxmox manages backups through jobs and a defined backup destination (backup and restore). A snapshot on the same storage is not a sufficient backup strategy. This list describes outcomes to check rather than findings measured here.
Diagnose errors
| Symptom | Next check |
|---|---|
| No boot media | ISO assignment, firmware and boot order |
| Windows sees no disk | Match VirtIO driver and selected controller |
| No networking | Bridge, VLAN, guest driver, address and firewall |
| Agent unreachable | Guest service and Proxmox option |
| Storage missing from selection | Content type, availability and permissions |
For deployment, continue to Proxmox setup. For maintaining an existing environment, Managed Proxmox is the target offering.
