How to Install AlmaLinux 10 Step by Step (Proxmox, VMware, VirtualBox, Hyper-V)
A complete installation guide for AlmaLinux 10: install it on a physical server, or build a virtual machine in Proxmox VE, VMware, VirtualBox or Hyper-V, with the exact settings that avoid the common boot and CPU errors.
sudo dnf update -y. In a virtual machine, set the CPU type to host so the standard build can boot.One Guide for Every Platform
AlmaLinux 10 is a free, RHEL-compatible server operating system. The installer is the same everywhere, but each hypervisor needs a few specific settings. This guide shows the right ones for Proxmox VE, VMware, VirtualBox and Hyper-V.
Same Installer Everywhere
The Anaconda steps are identical on every platform.
Platform-Specific Settings
CPU type, UEFI and Secure Boot settings avoid most failures.
Finish with Guest Tools
Install the guest agent for better performance and management.
Requirements and ISO Choice
| Resource | Recommended for a lab or small server |
|---|---|
| CPU | 2 or more vCPUs, with x86-64-v3 features for the standard build |
| Memory | At least 2 GB. Use 4 GB or more for a graphical install |
| Disk | 20 GB or more (about 10 GB for a minimal system) |
| Firmware | UEFI recommended |
| Network | A bridged or NAT connection with internet access |
Which ISO should you use? The DVD ISO installs everything offline, the Minimal ISO installs a small base system, and the Boot ISO installs over the network. All official files, checksums and the x86_64_v2 images are listed on our AlmaLinux 10.2 download page. Verify the checksum before you install.
Which platform should you use? Proxmox VE is free and efficient for a home lab, VMware is common in enterprises, VirtualBox is the easiest on a personal PC, and Hyper-V is built into Windows Pro and Windows Server. See our Proxmox VE 9.1.1 download if you want to start with a free hypervisor.
Prepare the Installation Media
For a physical server
Write the ISO to a USB drive of 8 GB or more. This erases the drive. On Windows, use Rufus in DD Image mode or balenaEtcher. On Linux, use:
sudo dd if=AlmaLinux-10.2-x86_64-dvd.iso of=/dev/sdX bs=4M status=progress oflag=syncReplace /dev/sdX with your USB device. Check it with lsblk first, because writing to the wrong disk destroys data. Then boot the server from the USB drive and continue at Run the AlmaLinux 10 Installer.
For a virtual machine
You do not need a USB drive. Attach the ISO to the VM as described in the section for your platform.
Install AlmaLinux 10 on Proxmox VE
Upload the ISO
In the Proxmox web interface, open your node, select the local storage, go to ISO Images and click Upload (or Download from URL).
Create the VM
Click Create VM and use these settings:
| Tab | Setting |
|---|---|
| General | Name: almalinux10 |
| OS | Select the AlmaLinux ISO. Guest type: Linux |
| System | Machine: q35. BIOS: OVMF (UEFI) with an EFI disk. SCSI controller: VirtIO SCSI single. Tick Qemu Agent |
| Disks | 20 to 32 GB on a SCSI (VirtIO) disk |
| CPU | 2 or more cores. Type: host (or x86-64-v3) |
| Memory | 4096 MB |
| Network | Bridge vmbr0, model VirtIO |
Start the VM and install
Click Start, open the Console and continue with the installer steps. After the first reboot, remove the ISO under Hardware → CD/DVD Drive.
Install the QEMU guest agent
sudo dnf install -y qemu-guest-agent
sudo systemctl enable --now qemu-guest-agentThis lets Proxmox show the VM’s IP address and shut it down cleanly.
Install AlmaLinux 10 on VMware
These steps work for VMware Workstation, Fusion and for ESXi with the vSphere client.
Create the VM
Choose Create a New Virtual Machine and pick the AlmaLinux ISO. For the guest OS, select Linux and a recent Red Hat Enterprise Linux 64-bit version (choose the newest one offered). On ESXi, first upload the ISO to a datastore, then attach it to the CD/DVD drive and tick Connect at power on.
Set the hardware
Give the VM 2 vCPUs, 4 GB of RAM and a 20 to 40 GB disk. Choose UEFI firmware if available. Keep the VM hardware version current, and avoid CPU compatibility masks (such as EVC on a cluster set to an old CPU baseline), because they can hide x86-64-v3 features.
Install, then add VMware Tools
Run the installer, then install the open-source tools:
sudo dnf install -y open-vm-tools
sudo systemctl enable --now vmtoolsdInstall AlmaLinux 10 on VirtualBox
Create the VM
Click New, enter a name, select the ISO, set Type to Linux and Version to Red Hat (64-bit). Tick Skip Unattended Installation so that you control the installer.
Set the hardware
Use 4096 MB of RAM, 2 or more CPUs and a 25 GB VDI disk. Open Settings and set the display adapter to VMSVGA with 128 MB of video memory. For networking, use NAT for internet access, or Bridged Adapter if you want the VM to get an address on your LAN.
Install, then add Guest Additions
Run the installer, update and reboot, then install the build tools and the matching kernel headers:
sudo dnf update -y
sudo reboot
sudo dnf install -y gcc make perl bzip2 tar elfutils-libelf-devel kernel-devel-$(uname -r) kernel-headersChoose Devices → Insert Guest Additions CD image, then run the installer from the mounted disc:
sudo sh /run/media/$USER/VBox_GAs_*/VBoxLinuxAdditions.runInstall AlmaLinux 10 on Hyper-V
Create a Generation 2 VM
In Hyper-V Manager choose New → Virtual Machine, select Generation 2, assign 4096 MB of memory, connect a virtual switch, create a 30 GB virtual disk and select the ISO for installation.
Change the Secure Boot template
This is the step that most people miss. Open the VM’s Settings → Security, keep Secure Boot enabled and set the template to Microsoft UEFI Certificate Authority. Otherwise the VM will not boot the Linux installer.
Or create it with PowerShell
New-VM -Name "AlmaLinux10" -Generation 2 -MemoryStartupBytes 4GB -NewVHDPath "C:\VMs\AlmaLinux10.vhdx" -NewVHDSizeBytes 30GB -SwitchName "Default Switch"
Set-VMProcessor -VMName "AlmaLinux10" -Count 2
Add-VMDvdDrive -VMName "AlmaLinux10" -Path "C:\ISO\AlmaLinux-10.2-x86_64-dvd.iso"
Set-VMFirmware -VMName "AlmaLinux10" -SecureBootTemplate MicrosoftUEFICertificateAuthority -FirstBootDevice (Get-VMDvdDrive -VMName "AlmaLinux10")
Start-VM -Name "AlmaLinux10"The Default Switch exists on Windows 10 and 11. On Windows Server, use the name of your own virtual switch.
Install, then add the Hyper-V services
Run the installer, then install the Hyper-V integration daemons:
sudo dnf install -y hyperv-daemons
sudo systemctl enable --now hypervfcopyd hypervkvpd hypervvssdIf a service name is not found on your version, run systemctl list-unit-files | grep -i hyperv to see the exact names.
Run the AlmaLinux 10 Installer
These steps are the same on every platform. Use the keyboard or mouse in the console window.
Boot menu
Select Install AlmaLinux 10.2. You can also choose the option that tests the media first.
Language
Choose your language and keyboard layout and click Continue.
Installation Summary
Work through the items on the summary screen:
| Item | What to choose |
|---|---|
| Time & Date | Select your time zone and turn on network time |
| Software Selection | Minimal Install for a lean server, Server for common tools, or Server with GUI for a desktop |
| Installation Destination | Select the disk and keep Automatic partitioning for a first install |
| Network & Host Name | Turn the network on and set a hostname such as alma10.lab.local |
| Root Password / User Creation | Create a strong password, and create an administrator user (tick Make this user administrator) |
Begin the installation
Click Begin Installation, wait for it to finish and click Reboot System. Remove the ISO or USB drive so that the system boots from the disk.
Post-Installation Setup
Update and confirm the version
sudo dnf update -y
cat /etc/os-release
uname -rThe output should show AlmaLinux 10.2.
Enable extra repositories
sudo dnf config-manager --set-enabled crb
sudo dnf install -y epel-releaseSet a static IP address (optional)
Find the connection name with nmcli con show. The device name depends on the platform:
| Platform | Typical interface name |
|---|---|
| Proxmox (VirtIO) | ens18 |
| VMware (vmxnet3) | ens192 |
| VirtualBox | enp0s3 |
| Hyper-V | eth0 |
sudo nmcli con mod "ens18" ipv4.addresses 192.168.1.50/24 ipv4.gateway 192.168.1.1 ipv4.dns 1.1.1.1 ipv4.method manual
sudo nmcli con up "ens18"Check the firewall and SSH
sudo firewall-cmd --state
sudo systemctl status sshdThen secure remote access. Follow our guides to set up SSH key-based authentication and to use a different SSH port. On AlmaLinux, remember to allow the new port in firewalld and SELinux.
Take a snapshot or backup
Once the base system is ready, take a snapshot in your hypervisor so you can roll back. For regular backups of servers and VMs, see our Veeam Backup & Replication download.
Troubleshooting
“CPU does not support x86-64-v3”
Set the VM CPU type to host or x86-64-v3, remove CPU compatibility masks, or use the x86_64_v2 images.
Hyper-V VM will not boot the ISO
Change the Secure Boot template to Microsoft UEFI Certificate Authority, or turn Secure Boot off.
No bootable device after install
Remove the ISO from the virtual drive and check that the first boot device is the hard disk and that the firmware mode matches.
No network in the VM
Check that the NIC is connected to the right bridge or switch, and that nmcli device status shows it as connected.
Black screen or a slow desktop
In VirtualBox, use VMSVGA. Choose Minimal or Server instead of Server with GUI for a lighter system.
Installer fails on the destination disk
Make sure the virtual disk is large enough and use Automatic partitioning if you are not sure how to partition.
For more information, see the AlmaLinux wiki and the AlmaLinux 10.2 release announcement.
Frequently Asked Questions
How do I install AlmaLinux 10?
Download the ISO, write it to a USB drive or attach it to a virtual machine, boot from it, then follow the installer: choose your language, destination disk, software selection, network and user accounts, and begin the installation.
Which AlmaLinux 10 ISO should I use?
Use the DVD ISO for a full offline install, the Minimal ISO for a small base system, or the Boot ISO for a network install. Our AlmaLinux 10.2 download page lists all official files.
Why does AlmaLinux 10 fail to boot in my virtual machine?
The standard x86_64 build needs a CPU with x86-64-v3 features. Set the VM CPU type to host (or x86-64-v3), turn off CPU compatibility masking, or use the x86_64_v2 images on older hardware.
Which VM settings are best for AlmaLinux 10?
Use UEFI firmware, at least 2 vCPUs, 4 GB of RAM, a 20 GB or larger disk and a paravirtualized network and storage controller where the platform offers one.
Why does AlmaLinux not boot on a Hyper-V Generation 2 VM?
Hyper-V enables Secure Boot with the Microsoft Windows template by default. Change the Secure Boot template to Microsoft UEFI Certificate Authority, or disable Secure Boot.
Do I need guest tools in the virtual machine?
They are optional but recommended: qemu-guest-agent for Proxmox, open-vm-tools for VMware, VirtualBox Guest Additions for VirtualBox and hyperv-daemons for Hyper-V.
Is AlmaLinux 10 free?
Yes. AlmaLinux is free and open source, and no license key is needed.
Conclusion
Installing AlmaLinux 10 is the same simple installer on any platform. What changes is the virtual machine setup: use the host CPU type on Proxmox, avoid CPU masks on VMware, choose VMSVGA on VirtualBox and change the Secure Boot template on Hyper-V. After the install, update the system, install the guest tools, secure SSH and take a snapshot.
sudo dnf update -y → Install guest tools → Enable CRB and EPEL → Secure SSH → Take a snapshot.Keep Learning with VMoreCloud
Find more Linux, virtualization, networking and Windows Server tutorials.
Sources & Further Reading
Technical note: menu names, package names and defaults differ between hypervisor versions and AlmaLinux releases. Test on a non-production VM first, and keep backups of any data before you install on a physical server.
