NewExtra server protection with Measured Boot & UKI images.View Measured Boot
BlogDocumentationFAQNo Third-Party CookiesContact Us
  • Pricing
Log inSign up
Cloud VPSVDSMemory-Optimized VDSStorage-Optimized VDSWindows VPSBitcoin VPSDDoS ProtectionPrivate Networking (VPC)Floating IPsAdditional Server SupportMicrosoft LicensesDatacenterNetworkDocumentationFAQNo Third-Party CookiesConfidential ComputingSelf-Hosted VPNBlogAboutBrand GuidelinesAffiliatesContact UsLegal & Compliance

Products

  • Pricing
  • Cloud VPS
  • VDS
  • RAM-Optimized VDS
  • Storage-Optimized VDS
  • Windows VPS
  • Bitcoin VPS
  • DDoS Protection
  • Private Networking (VPC)
  • Floating IPs
  • Microsoft Licenses
  • Additional Server Support

Explore

  • Documentation
  • Developers API Docs
  • FAQ
  • Datacenter
  • Network
  • Looking Glass
  • Confidential Computing
  • Cookie Policy
  • Self-Hosted VPN

Company

  • Blog
  • Contact Us
  • About Us
  • Brand Guidelines
  • Affiliates

Legal & Compliance

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement
  • Acceptable Use Policy
  • Microsoft Software Terms of Use
  • Refund Policy
  • Report Abuse

Products

  • Cloud VPS
  • VDS
  • RAM-Optimized VDS
  • Storage-Optimized VDS
  • Windows VPS
  • Bitcoin VPS
  • DDoS Protection
  • Private Networking (VPC)
  • Floating IPs
  • Microsoft Licenses
  • Additional Server Support
Pricing

Explore

  • Documentation
  • Developers API Docs
  • FAQ
  • Datacenter
  • Network
  • Looking Glass
  • Confidential Computing
  • Cookie Policy
  • Self-Hosted VPN

Company

  • Blog
  • Contact Us
  • About Us
  • Brand Guidelines
  • Affiliates

Legal & Compliance

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement
  • Acceptable Use Policy
  • Microsoft Software Terms of Use
  • Refund Policy
  • Report Abuse

© VPS.BG Ltd. 2026 · All rights reserved!

Made with passion in Bulgaria · VAT ID: BG203144520

Contents

  • Most Common QGA Problems
  • How to fix QGA Problems on Debian, Ubuntu
  • How to fix QGA Problems on RHEL, AlmaLinux, Rocky Linux & Fedora
  • How to Fix QGA Problems on Windows Server

Subscribe to Our Newsletter

Join 5000+ subscribers and receive helpful content, deals and more! We promise no spam - 100% great content. Unsubscribe anytime.

Share Article

#QGA
  1. Documentation
  2. /
  3. #QGA
  4. /
  5. QEMU Guest Agent (QGA) Troubleshooting Guide

QEMU Guest Agent (QGA) Troubleshooting Guide

Published: 02 February 2026 • 5 min read

#Tutorial#QGA

The QEMU Guest Agent (QGA) is a small daemon (service) that runs inside your VPS and enables direct communication between the virtualization platform/host hypervisor and the guest operating system on your virtual machine.

QGA is required for several important management features such as changing your server’s hostname, changing your root (administrator) password, managing SSH keys, executing basic guest commands from outside your virtual machine and many others.

This guide will help you troubleshoot some of the most common QGA problems and will help you get thing up and running.

Most Common QGA Problems

When trying to perform actions that require QGA, you might get an error that QGA cannot be reached. This is because QGA was most likely not properly installed or isn’t running inside of your virtual machine.

The most common reason for this is if the QEMU Guest Agent is missing, stopped, disabled or if the server was restored from an image or a backup that did not include it. On Windows VPS instances, QGA may also be unavailable if the VirtIO drivers are not installed.

How to fix QGA Problems on Debian, Ubuntu

Being a popular choice for an OS, let’s start by focusing on problems that are usually found on Ubuntu/Debian virtual machines. Remember to log in to your VPS via SSH or console access in order to run any of the following commands.

Try Starting QGA

If by some reason, QGA has been stopped or it is disabled, you can simply run this command to try and start the agent:

systemctl start qemu-guest-agent

If you don’t get any output, then you should try to see if QGA is installed on your virtual machine.

Check if QGA is Installed

The most common cause for a QGA unreachable error is that the agent hasn’t been installed on the virtual machine. This could happen during installation or it might be missing if you have previously removed it.

First, run the following command:

dpkg -l | grep qemu-guest-agent

If QGA is installed, you should see an output similar to the one from the screenshot below:

output command

While your output might resemble this, that doesn’t mean you have QEMU guest agent up and working. For example:

Notice how this output begins with “rc”. That means that QGA was previously installed but has been removed and only its configuration files remain on your system.

output command

How to Install QGA

If there is no output from the command above, you need to install QGA by running the following command:

apt-get install qemu-guest-agent

Wait for the installation to complete successfully. After that you should start the daemon:

systemctl start qemu-guest-agent

Then enable the service to autostart (permanently) with:

systemctl enable qemu-guest-agent

Finally, You can check whether the installation was successful by running:

systemctl status qemu-guest-agent

Your CLI output should resemble the one below and the service should show Active: active (running).

active output

How to fix QGA Problems on RHEL, AlmaLinux, Rocky Linux & Fedora

Similarly to Ubuntu and Debian, you need to log into your virtual machine to ensure that you can run the following commands.

Try Starting QGA

Again, the first thing that you need to try is to attempt to start QGA using this command:
systemctl start qemu-guest-agent

If you get a positive output, then QGA was basically stopped or disabled. If you don’t get any output, then you can proceed to checking whether QGA is installed on your virtual machine.

How to check if QGA is installed

Firstly, run this command:

rpm -qa | grep qemu-guest-agent

If QGA is installed, the package name will be listed.

command output

How to Install QGA

If the package is not present, install it using:

dnf install -y qemu-guest-agent

Allow the installation to complete then proceed with:

systemctl start qemu-guest-agent

Finally, you can check the status of the service with:

systemctl status qemu-guest-agent

Your CLI output should resemble the one below and the service should show Active: active (running).

active output

How to Fix QGA Problems on Windows Server

On Windows VPS instances, QGA is included as part of the VirtIO drivers package and runs as a Windows service.

How to check if the QGA service is running

  1. Open the Start Menu
  2. Type services
  3. Press Enter

In the Services window, locate QEMU Guest Agent. It should be tucked in right around the red highlighter in the screenshot below.

check qemu is running

Check the Status column. If the service is Running, QGA is working correctly but if the service is Stopped, it must be started manually. If that is the case, then QEMU guest agent should be started manually.

To activate the agent, simply right-click on the the QEMU Guest Agent service and click Start.

start qemu

Once started, the status should change to Running.

How to Install QGA

If the QEMU Guest Agent service is not present, the VirtIO drivers/Virtio-win-guest-tools may not have been properly installed. If that’s the case, then you will need to download an official VirtIO driver ISO and manually install it. You can utilize the following link from the FedoraPeople group.

After downloading the ISO file with your preferred version, you can now mount it to your VPS by right-clicking on your file.

mount qemu

After the process has finished the ISO will appear as a new CD/DVD drive in This PC.

mounted qemu

Finally you need to install VirtIO Guest Tools (that includes the QEMU Guest Agent). Simply open the mounted VirtIO CD/DVD drive and run virtio-win-guest-tools.exe.

run qemu

After the installation is completed you can verify if qemu-guest-agent has been installed by navigating back to the Services window. If it still doesn’t appear make sure you right-click somewhere inside the list of services and click Refresh as shown below.

refresh qemu

That’s it! We hope that you have managed to get QGA up and running for your virtual machine. If these solutions have still not fixed your problem, you can always reach out to our dedicated support team.

Subscribe to Our Newsletter

Join 5000+ subscribers and receive helpful content, deals and more! We promise no spam - 100% great content. Unsubscribe anytime.

Share Article

Related Content

02 February 2020

How to encrypt your cloud server and decrypt it remotely with Dropbear SSH

In this tutorial, you are going to learn how to fully encrypt your KVM-based cloud VPS server as well as how to decrypt it using Dropbear SSH.

#Tutorial#Security#Custom ISO
05 June 2026

How to Rebuild the OVMF Firmware Used for VPSBG Measured Boot

Learn how to rebuild the OVMF firmware that we use for our transparent, AMD SEV-SNP powered Measured Boot feature for our cloud servers.

#SEV#Measured Boot#Tutorial
01 August 2021

What is an SSH key and how to generate one

Learn how to use SSH keys to establish a secure remote connection to your server as well as how to generate an SSH key pair for Linux, Mac and Windows.

#Tutorial#Security
03 February 2020

How to change your SSH port

In this tutorial, you are going to learn how to change your default SSH port (22) in order to improve your server’s overall security.

#Tutorial#Security

Unrivaled Performance & Security

Deploy a powerful and reliable Cloud VPS today to ensure your privacy. SEV-SNP included for maximum protection.

Configure VPSContact Us