{"id":38405,"date":"2009-08-04T11:22:27","date_gmt":"2009-08-04T11:22:27","guid":{"rendered":"https:\/\/www.vmengine.net\/2009\/08\/04\/xenserver-pool-how-to-force-add-a-host\/"},"modified":"2025-05-23T17:07:17","modified_gmt":"2025-05-23T17:07:17","slug":"xenserver-pool-how-to-force-add-a-host","status":"publish","type":"post","link":"https:\/\/temp-new.vmenginelab.com\/en\/2009\/08\/04\/xenserver-pool-how-to-force-add-a-host\/","title":{"rendered":"XenServer Pool: How to Force Add a Host"},"content":{"rendered":"

The addition of a new host server installed with the free XenServer Enterprise 5.5 hypervisor, even if it can be trivial using the XenCenter graphical interface<\/p>\n

\"\"\"\"\"\"\"\"\"Xencenter\"<\/p>\n

It can easily generate errors even if the host machines are practically the same, of the same brand and model, this is because to allow a painless XenMotion migration, the compatibility between the processors and the installed software must be as homogeneous as possible.<\/p>\n

The generic errors that the graphical interface (XenCenter) generally proposes are<\/p>\n

The hosts in this pool are not homogeneous.reason. Software Version Differs<\/em><\/strong><\/p>\n

The hosts in this pool are not homogeneous.reason. cpu differ<\/em><\/strong><\/p>\n

In the case of the software it could be that on one of the two hosts the extra Linux pack has not been installed, instead in the second case, it is the case to go and check the versions of the CPUs of the two hosts, looking at the file \/proc\/cpuinfo, we could find some difference in the model or flags or generally just trivial differences in the MHz cpu, Below is an example of the output<\/p>\n

Processor : 0
\nvendor_id : AuthenticAMD
\nCPU Family : 15
\nModel : 75
\nmodel name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
\nStepping : 2
\nCPU MHz : 2204.612
\ncache size : 512 KB
\nfdiv_bug : No
\nhlt_bug : No
\nf00f_bug : no
\ncoma_bug : No
\nfpu : yes
\nfpu_exception : yes
\ncpuid level : 1
\nwp : yes
\nFlags : FPU de tsc MSR PAE CX8 apic mtrr cmov pat clflush mmx fxsr sse sse2$
\nBogomips : 4410.18<\/p>\n

In case we find ourselves with obvious differences, it is not recommended to add the new host in the pool, but if we really want to insist, we need to maneuver from the shell and no longer from the GUI.<\/p>\n

Let’s connect in SSH or in console to the new host server and type the following command<\/p>\n

xe pool-join master-address=MASTERIP master-username=root master-password=PASSWORD force=true<\/em><\/strong><\/p>\n

A few moments of synchronization of the master database to the new host and we added a new resource to our pool\"Xenpool\"<\/p>\n","protected":false},"excerpt":{"rendered":"

The addition of a new host server installed with the free XenServer Enterprise 5.5 hypervisor, even if it can be trivial using the XenCenter graphical interface It can easily generate errors even if the host machines are practically the same, of the same brand and model, this is because to allow a painless XenMotion migration, […]<\/p>\n","protected":false},"author":2,"featured_media":29061,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[97],"tags":[247,1012,1013,251,4986,1014,228,259,1015,545,1016,546,431,1017,1018],"class_list":["post-38405","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-en","tag-citrix-en","tag-cpuinfo-en","tag-gui-en","tag-hypervisor-en","tag-management-2-2","tag-ssh-en","tag-technical-en","tag-virtualization-en","tag-xe-pool-join-en","tag-xen-en","tag-xen-pool-en","tag-xencenter-en","tag-xenserver-en","tag-xenserver-enterprise-en","tag-xenserver-pool-en"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t