Bobcares

Why Proxmox Says “QEMU Guest Agent is Not Running”

Learn why Proxmox Says “QEMU Guest Agent is Not Running”. Our Proxmox Support team is here to help you with your questions and concerns.

Why Proxmox Says “QEMU Guest Agent is Not Running”

If you’ve run into the “QEMU Guest Agent is not running” message in Proxmox VE, you are in luck!

Why Proxmox Says "QEMU Guest Agent is Not Running"

Our experts are here to help you out. This error means the communication channel between your virtual machine and the Proxmox server is disrupted.

The QEMU Guest Agent helps Proxmox to effectively monitor and manage our VM. It offers several features like:

  • Performance Monitoring:
    Track memory, CPU, disk usage, and network traffic within the VM.

  • Shutdown/Reboot:
    Start shutdowns or reboots of the VM from the Proxmox interface.

  • File System Synchronization:
    Easily transfer files between the virtual machine and Proxmox host.

  • Time Synchronization:
    Make sure the VM’s clock is in sync with the Proxmox host.

Reasons behind the “QEMU Guest Agent is Not Running”

  • Not Installed or Enabled:

    The QEMU Guest Agent might not be installed or enabled within the guest VM.

  • Not Running:

    Even if installed, the Guest Agent service might not be running due to various reasons.

  • Driver Issues:

    Missing or outdated drivers for the Guest Agent within the VM can cause communication problems.

Troubleshooting Tips

  1. First, go to the VM and log in to the guest operating system. The installation commands depend on the guest OS. For example:
    • For Debian/Ubuntu:
      sudo apt update
      sudo apt install qemu-guest-agent
    • For CentOS/RHEL:
      sudo yum update
      sudo yum install qemu-guest-agent
  2. Next, enable and start the Guest Agent service:
    • For Systemd (most modern Linux distros):
      sudo systemctl enable qemu-guest-agent
      sudo systemctl start qemu-guest-agent
    • For SysVinit (older Linux distros):
      sudo chkconfig qemu-guest-agent on
      sudo service qemu-guest-agent start
  3. Next, check if the Guest Agent service is running:
    • For Systemd:
      sudo systemctl status qemu-guest-agent
    • For SysVinit:
      sudo service qemu-guest-agent status
  4. In some cases, a simple reboot can fix temporary glitches that prevent the Guest Agent from starting correctly.
    sudo reboot
  5. Sometimes, firewall rules within the guest VM might block communication with the Proxmox host. So, make sure the Guest Agent service is allowed to communicate on the appropriate ports (typically port 22 for SSH).
    sudo iptables -A INPUT -p tcp --dport 22 -j ACCEPT

Let us know in the comments if you need further help with this error.

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

Conclusion

In brief, our Support Experts demonstrated how to fix the “QEMU Guest Agent is Not Running” error in Proxmox

0 Comments

Submit a Comment

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

server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

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