Bobcares

Proxmox Cluster Error: This host already contains virtual guests

by | Jul 17, 2024

Learn how to fix Proxmox Cluster Error: This host already contains virtual guests. Our Proxmox Support team is here to help you with your questions and concerns.

Proxmox Cluster Error: This host already contains virtual guests

Proxmox Cluster Error: This host already contains virtual guestsIf you have been having trouble with the following error message, our Experts have your back.

This host already contains virtual guests

This error usually occurs in Proxmox when we try to join a node to a cluster, but the node still has virtual machines or containers configured on it, even if they are not running presently.

Today, we are going to take a look at the common causes behind this error and how to troubleshoot it.

Common Causes

  • Leftover VM/CT Configuration Files:

    Even if we remove the VMs or CTs from the node’s configuration, the configuration files may still exist on the node’s file system. When we try to join the node to the cluster, these leftover configuration files lead to the “This host already contains virtual guests” error.

  • Powered-off VMs/CTs:

    Even if virtual machines or containers are powered off on the node, the cluster will still prevent it from joining. This is because the cluster detects them in the node’s configuration, even if they are not running.

  • Corrupted Configuration:

    Sometimes, the “This host already contains virtual guests” error can occur due to corrupted node configuration files. This corruption may be due to hardware malfunctions, software glitches, or incorrect configuration adjustments.

    When these files are compromised, the cluster can’t accurately detect the node’s status, leading to the error.

  • Network Connectivity Issues:

    Network issues can also trigger the “This host already contains virtual guests” error when joining a Proxmox cluster. If the node’s network configuration is incorrect or it cannot communicate properly with the cluster, this error might appear.

Troubleshooting Tips

  1. To begin with, make sure all VMs and CTs on the node are powered down before we try to join the cluster. This helps remove the cluster’s detection of these virtual resources, thereby allowing the node to join the cluster.
  2. Next, manually delete the configuration files for the VMs and CTs from the node’s directory:

    /etc/pve/nodes/<node_name>/qemu-server/ directory

    This makes sure that the cluster cannot detect any virtual guests on the node.

  3. In case we want to preserve the configuration files, back them up before deleting them, so we can restore them later if needed.
  4. Also, check the node’s network settings, like IP address, gateway, and DNS, to make sure they are correctly configured. Furthermore, check if the node has a stable network connection to the other nodes in the cluster.
  5. If the above steps do not fix the error, we may have to recreate the entire cluster. This involves removing the node from the cluster, deleting the cluster, and then recreating the cluster with the node.

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

Conclusion

In brief, our Support Experts demonstrated how to fix Proxmox Cluster Error: This host already contains virtual guests.

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