%BOOK_ENTITIES; ]>

To manage KVM instances on the host &PRODUCT; uses a Agent. This Agent communicates with the Management server and controls all the instances on the host. First we start by installing the agent: In RHEL or CentOS: $ yum install cloudstack-agent In Ubuntu: $ apt-get install cloudstack-agent The host is now ready to be added to a cluster. This is covered in a later section, see . It is recommended that you continue to read the documentation before adding the host!

In additional,the &PRODUCT; Agent allows host administrator to control the guest CPU model which is exposed to KVM instances. By default, the CPU model of KVM instance is likely QEMU Virtual CPU version x.x.x with least CPU features exposed. There are a couple of reasons to specify the CPU model: To maximise performance of instances by exposing new host CPU features to the KVM instances; To ensure a consistent default CPU across all machines,removing reliance of variable QEMU defaults; For the most part it will be sufficient for the host administrator to specify the guest CPU config in the per-host configuration file (/etc/cloudstack/agent/agent.properties). This will be achieved by introducing two new configuration parameters: guest.cpu.mode=custom|host-model|host-passthrough guest.cpu.model=from /usr/share/libvirt/cpu_map.xml(only valid when guest.cpu.mode=custom) There are three choices to fulfill the cpu model changes: custom: you can explicitly specify one of the supported named model in /usr/share/libvirt/cpu_map.xml host-model: libvirt will identify the CPU model in /usr/share/libvirt/cpu_map.xml which most closely matches the host, and then request additional CPU flags to complete the match. This should give close to maximum functionality/performance, which maintaining good reliability/compatibility if the guest is migrated to another host with slightly different host CPUs. host-passthrough: libvirt will tell KVM to passthrough the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU. Here are some examples: custom guest.cpu.mode=custom guest.cpu.model=SandyBridge host-model guest.cpu.mode=host-model host-passthrough guest.cpu.mode=host-passthrough host-passthrough may lead to migration failure,if you have this problem,you should use host-model or custom