Bobcares

Troubleshooting Proxmox: No QEMU Guest Agent Configured

by | Jun 18, 2024

Learn how to fix the “No QEMU Guest Agent Configured” Proxmox error. Our Proxmox Support team is here to help you with your questions and concerns.

Troubleshooting Proxmox: No QEMU Guest Agent Configured

Troubleshooting Proxmox: No QEMU Guest Agent ConfiguredIn Proxmox VE, the “No QEMU Guest Agent configured” message indicates that the communication channel between Proxmox and our VM is not set up.

The QEMU Guest Agent is a key software component installed within the VM. It helps with seamless interaction with the Proxmox host. This setup allows Proxmox to:

  • Monitor VM Performance:

    Track CPU, memory, disk usage, and network traffic of the VM.

  • Synchronize Time:

    Ensure the VM’s clock is in sync with the Proxmox host.

  • Manage VM Power State:

    Initiate shutdowns or reboots of the VM from the Proxmox interface.

  • Synchronize Files:

    Easily transfer files between the VM and Proxmox host.

According to our experts, there are two main reasons behind the error message:

  • The VM configuration within Proxmox does not enable the QEMU Guest Agent functionality.
  • Even if enabled on Proxmox, the QEMU Guest Agent software itself may not be installed or activated within the guest VM’s operating system.

How to Fix the “No QEMU Guest Agent Configured” Message

  1. First, enable QEMU Guest Agent on Proxmox during VM creation or configuration. So, go to the VM configuration menu in Proxmox VE.
  2. Then, go to the Options tab and find the checkbox for “Qemu Agent.”
  3. Make sure this this checkbox is enabled for this specific VM.
  4. However, if we are creating a new VM, enable the checkbox during the VM creation process.
  5. Then, click “Save” to apply the changes.
  6. Next, we need to install and enable the QEMU Guest Agent within the guest operating system. Here are the steps for common Linux distributions:
    • Debian/Ubuntu:

      sudo apt update
      sudo apt install qemu-guest-agent

    • CentOS/RHEL:

      sudo yum update
      sudo yum install qemu-guest-agent

  7. Once installed, enable and start the Guest Agent service:
    • Systemd (Most Modern Linux Distros):

      sudo systemctl enable qemu-guest-agent
      sudo systemctl start qemu-guest-agent

    • SysVinit (Older Linux Distros):

      sudo chkconfig qemu-guest-agent on
      sudo service qemu-guest-agent start

  8. In some cases, a VM reboot can resolve any issues that prevent the Guest Agent from starting correctly.

The above steps will help us fix the “No QEMU Guest Agent configured” message in Proxmox VE.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to fix the “No QEMU Guest Agent configured” error.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF