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 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 :
INSERT INTO guest_os_hypervisor (id, hypervisor_type, guest_os_name, guest_os_id, hypervisor_version, uuid, created, removed, 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);
INSERT INTO guest_os_hypervisor (id, hypervisor_type, guest_os_name, guest_os_id, hypervisor_version, uuid, created, removed, 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);
Regards, Benoit
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 cloud.hypervisor_capabilities(uuid, hypervisor_type,
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 cloud.guest_os_hypervisor (uuid,hypervisor_type,
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 cloud.guest_os_hypervisor WHERE
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 :
Thanks a lot for your help @olivierlambert
Best Regards
Hello guys,
Since last update on xcp-ng via yum update, Cloudstack management platform does not recognize hypervisor capabilities
With a xcp-ng 8.2 build date 2020-11-05 it i ok
With a xcp-ng 8.2 build date 2022-02-11 this does not work anymore
Live storage migration is no more available due that capabilities of xcp-ng could not be retrieved anymore
Regards, Benoit
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
Benoit
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 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 :
INSERT INTO guest_os_hypervisor (id, hypervisor_type, guest_os_name, guest_os_id, hypervisor_version, uuid, created, removed, 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);
INSERT INTO guest_os_hypervisor (id, hypervisor_type, guest_os_name, guest_os_id, hypervisor_version, uuid, created, removed, 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);
Regards, Benoit
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 cloud.hypervisor_capabilities(uuid, hypervisor_type,
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 cloud.guest_os_hypervisor (uuid,hypervisor_type,
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 cloud.guest_os_hypervisor WHERE
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 :
Thanks a lot for your help @olivierlambert
Best Regards
It seems yum update made xcp-ng 8.2.1 ? is this normal ?
Hello guys,
Since last update on xcp-ng via yum update, Cloudstack management platform does not recognize hypervisor capabilities
With a xcp-ng 8.2 build date 2020-11-05 it i ok
With a xcp-ng 8.2 build date 2022-02-11 this does not work anymore
Live storage migration is no more available due that capabilities of xcp-ng could not be retrieved anymore
Regards, Benoit
Hello Guys,
We are trying to scale up (DMC Feature) the computing on our guest Vm on Xcp-Ng 8.2
It is working with Centos and CoreOS Os but not with Debian 10 and Debian 7
Any ideas ?
Regards, Benoit
Hello guys,
with CS when shutting down a VM, the XCP DB is emptied of the entry concerning the relations with ressources (disk, name, metrics of vm).
These informations are stored in CS Database in place of keeping it on Xcp host
But normally values which are not changing are the uuid of disk of the vm
Also if XOA realise a backup of a disk, it could be possible to play again the vm
@AlexanderK have you succedded to test with XOA ?
@olivierlambert is it possible to test the backup feature with XOA before buying the licence ?
Regards, Benoit
@olivierlambert said in Manage XCP-NG with XOA and Cloudstack:
We have customers doing this!
Nice !! So it is possible without any conflicts ?
I used to move somes vms disk with xencenter (or xcp-ng center) and i had to change in Cloudstack DB, the uuid of disk
Can i achieve a backup protecting me agaist a disk array failure with XOA Starter version ?