Xcp-ng 8.2 no more recognized with Cloudstack since last update
Hello @olivierlambert ,
I saw the problem was due to my yum update on my xcp-ng 8.2 cluster has changed the subversion of xcp-ng
It changed from 8.2.0 to 8.2.1
So the Cloudstack management server is updating his entries for my hosts saying it is version 8.2.1
The hypervisor capabilities in Cloudstack 4.16 says only xenserver 8.2.0 is recognized
I added hypervisor capabilities in Cloudstack like this :
#add hypervsisor xcp 8.2.1 to acs 4.16
INSERT IGNORE INTO
hypervisor_version, max_guests_limit, max_data_volumes_limit,
max_hosts_per_cluster, storage_motion_supported) values (UUID(), 'XenServer',
'8.2.1', 1000, 253, 64, 1);
+-- Copy XenServer 8.2.0 hypervisor guest OS mappings to XenServer 8.2.1
+INSERT IGNORE INTO
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined)
SELECT UUID(),'Xenserver', '8.2.1', guest_os_name, guest_os_id,
utc_timestamp(), 0 FROM
hypervisor_type='Xenserver' AND hypervisor_version='8.2.0';
This is now working for me
Could you confirm me from your side that between xcp-ng 8.2.0 and xcp-ng 8.2.1 there is no changes with :
- Live storage migration stuff
- Live migration (just instance no storage moving
Thanks a lot for your help @olivierlambert
No change, it's a patch version, as the semantic number says
AlexanderK last edited by AlexanderK
@kurushi9000 you have added this into database cloud i suppose?
will report to cloudstack team.
@AlexanderK Yes i added these sql into the Cloudstack cloud database
I also saw that Debian 11 vm already present on xcp-ng 8.2.0 were working no more
I added so these two lines in order to map Debian 11 from xcp-ng 8.2.1 with "Debian GNU/Linux 11" of Cloudstack :
is_user_defined) VALUES (8227, 'Xenserver', 'Debian Bullseye 11', 337, '8.2.1', '35b0f2f7-ca33-11ec-85d0-96264736f9a1', '2022-05-03 12:08:36', NULL, 0);
is_user_defined) VALUES (8231, 'Xenserver', 'Debian Bullseye 11', 338, '8.2.1', '35b0f3b0-ca33-11ec-85d0-96264736f9a1', '2022-05-03 12:11:26', NULL, 0);
I tested a set of features after modyfing so the Cloudstack databases entries :
test export vm OK
test import vm OK
test migration XenMotion live OK
test migration XenStorageMotion live OK
test snapshot OK
test snapshot vm OK (was bugging before patching guest os mapping)
test revert snapshot OK
test revert snapshot vm OK
This has been tested on Centos, Debian 10 and Debian 11 vms
AlexanderK last edited by
So happy for what happened at github
This is exactly why we love Open Source
Thanks guys for your intervention in github
@stormi , it could be possible to have major security issues causing disruptives upgrade of some components in future.
I would like to benefit nevertheless of updates without taking risk of changing to a specific version causing incompatibilities with CS per example.
This time, I used a yum update after seeing your warn issue about memory loss (ixgbe)
Is there a way to have something like XS82xxx.update hotfix file to execute as it was with Citrix Xenserver ?
This permit to update to a specific version of Hypervisor (very useful in production)
Have a Nice Week-end
@olivierlambert me too
@kurushi9000 I wasn't aware cloudstack would take the minor version number into account and suddently stop working.
It's not planned to provide updates cherry-picking like Citrix does. It's a logistical nightmare, would require specific yum repositories for each updates. So instead we provide a large testing period (several weeks) before bigger updates to let you test them and report if anything goes wrong. It would be good to have cloustack users take part in the testing, and even contribute changes to cloudstack before the release so that they are made compatible in time.
Note that XCP-ng 8.2.1 was not made incompatible in any way with cloudstack. It's cloudstack that considered it was a version it doesn't know, but it was technically fully compatible. Not major change on our side.
If any major change must happen in the future, we'll warn in the release notes. It won't happen if we can avoid it, by the way. However, if cloudstack solely depends on the XAPI API, then there's no reason a future update to XCP-ng 8.2 LTS would break compatibility. We don't change the API in maintenance updates. What does cloudstack depend on in XCP-ng exactly?
We'll also try to anticipate compatibility issues, but we don't manage external projects. That's why, in the context of the open source development process that is XCP-ng's, I strongly advise users of anything that plugs into XCP-ng to take part in pre-release testing.
AlexanderK last edited by
i am happy that found another user who uses xcp-ng with cloudstack @kurushi9000
@stormi i am using cloudstack and xcp-ng as hypervisor for almost 2 years.
lately i have tried terraform with cloudstack and the results were really amazing.
Possible to build many labs in different networks for testing in minutes.
by the way @kurushi9000 have you tried cs 126.96.36.199 rc2?
I will try it, hope today, at my virtual testbed.