Hi Everyone,
This email is about CQM (a new feature implemented in Intel Xeon processors) enabling in XenAPI. And we have to ask you for help.
CQM (Cache QoS Monitoring) allows an Operating System, Hypervisor or similar system management agent to determine the usage of cache by applications running on
the platform. The hardware is not publicly available yet, but Red Hat and others should have some of these platforms for testing. For details on the implementation, please refer to the Intel Software Development Manual, Volume 3, Chapter 17.14: Cache Quality
of Service Monitoring
Now we have to enable this new feature in XenAPI, in order to Openstack can use it with Xen environment. As you know, for Openstack, XenAPI is the best way to use
Xen Hypervisor, and libvirt.xen could not be supported smoothly by Openstack.
In order to add CQM support in XenAPI, we maybe modify some public structures or functions, including host info, vm info, etc., to add cache usage related information.
It means we will have to patch the latest code from XenAPI repo. But unfortunately, we tried some ways to setup XenAPI development environment, and it is not ready yet. There are a lot of package dependence issues or build issues, so that I can’t not build
XenAPI code successfully.
- According to README, I used opam to build XenAPI code. But some packages, including vhd, xenstore, etc., could not be built successfully. And with CentOS, opam
must use GLIBC 2.14, which is not provided by CentOS 6.5.
- I once asked Zheng Li for help. Thanks for Zheng’s help.:) Zheng told me that we could build xenserver-core probject (https://github.com/xenserver/xenserver-core),
with which we should be able to build most xenserver components (including xapi) on a vanilla CentOS.
We tried this way, and xenserver-core could be built smoothly on CentOS6.5 or Ubuntu1304. But after that, XenAPI could not be built successfully, and said some
packages could not be found (stdext, xml-light2, uuid, etc..)
So, could anyone tell me how to setup XenAPI development environment, or how to add new feature into XenAPI? Or could any citrix guys help us enable this new feature
in XenAPI? J
Thanks,
Qiaowei
