- Open
Virt-Manageron your Linux host. - Click the icon to create a new virtual machine.
- Choose Local install media and select your downloaded ISO file.
- Allocate RAM and CPU cores. Give it at least 4096 MB of RAM and 4 CPUs if your host can handle it.
- Create a disk image for the virtual machine.
- Check the box that says Customize configuration before install and click Finish.
- In the hardware details window, make sure you have the following components:
- Display Spice
- Video
Virtio - Channel spice (
com.redhat.spice.0) - Controller
VirtIO Serial
- Click Play to start the virtual machine.
- Follow the standard installation steps for whatever operating system you chose.
- Once the installation is done, reboot the virtual machine.
- Install the guest agent inside the virtual machine (see per-OS instructions below).
Arch Linux:
sudo pacman -S spice-vdagentUbuntu/Debian:
sudo apt install spice-vdagentFedora:
sudo dnf install spice-vdagentDownload and install the Windows SPICE Guest Tools executable: https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe
Warning: Running macOS inside KVM on a Linux host is highly complex, legally restricted to Apple hardware per Apple's EULA, and outside standard Virt-Manager scope. It requires the OpenCore bootloader and specific QEMU CPU flags. SPICE clipboard is not available.
Use the OSX-KVM project for a complete setup guide. Key requirements:
- OVMF firmware with Secure Boot disabled
- OpenCore as the boot EFI image
- QEMU CPU set to
host-passthroughwith CPUID masking for Apple model detection- Clipboard sharing is not supported; use VNC mode as a workaround
Enable the SPICE agent daemon inside the guest after installing spice-vdagent:
sudo systemctl enable --now spice-vdagentdClipboard will work automatically between guest and host after the service starts.
Use this only when the systemd service does not bridge clipboard under KDE Plasma running on Wayland. The service alone cannot reach the Wayland clipboard — it must be forced through the X11/Plasma bridge.
-
Stay on the Wayland session. Do not switch to X11.
-
Inside the guest, open System Settings.
-
Navigate to Security & Privacy → Application Permissions → Legacy X11 App Support.
-
Find the clipboard access setting and change it to allow access without asking.
-
Click Apply.
-
Kill any stuck processes from previous attempts:
killall -9 spice-vdagent
-
Force the agent to run on the X11 backend so it reads from the Plasma clipboard bridge:
GDK_BACKEND=x11 spice-vdagent -x & -
Copying from the guest to the host will now work.
-
Install the VirtIO-FS daemon on your Linux host:
Debian/Ubuntu:
sudo apt update && sudo apt install virtiofsdArch Linux:
sudo pacman -S virtiofsd
Fedora:
sudo dnf install virtiofsd
-
Create the shared folder on your Linux host:
mkdir -p ~/Documents/VM-Share -
Open permissions so the hypervisor can read the directory:
chmod +x ~ chmod +x ~/Documents chmod 777 ~/Documents/VM-Share
-
Shut down the virtual machine completely.
-
In
Virt-Manager, open the virtual machine details and go to Memory. -
Check the box for Enable shared memory and apply.
-
Click Add Hardware and select Filesystem.
-
Set Driver to
virtiofs. -
Set Source path to
~/Documents/VM-Share(use the full path, e.g./home/<username>/Documents/VM-Share). -
Set Target path to
VM-Share. -
Click Finish and boot the virtual machine.
-
Create the matching mount point inside the virtual machine:
mkdir -p ~/Documents/VM-Share -
Mount the folder using the target tag:
sudo mount -t virtiofs VM-Share ~/Documents/VM-Share -
To make the mount permanent, add this line to
/etc/fstabinside the virtual machine.$HOMEputs in the full path of your home folder. Run it once, because every run adds one more line:echo "VM-Share $HOME/Documents/VM-Share virtiofs defaults 0 0" | sudo tee -a /etc/fstab
Check it. This must print the one line:
grep -n 'VM-Share' /etc/fstab -
Apply the fstab change:
sudo systemctl daemon-reload sudo mount -a