I haven't played with host-model, but manual says (
http://docs.cloudstack.apache.org/en/4.11.1.0/installguide/hypervisor/kvm.html
)
"
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
Hi All,
By popular demand, I've created a 4.11.2.0 release (RC4), with the following
artefacts up for testing and a vote:
Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.2.0-RC20181030T1040
Commit:
Hi Andrija,
thank you for your quick answer.
I already checked out the custom CPU-Model of our CPU generation as plan b.
This would also work for us.
The question for me was just why is qemu64 working with
guest.cpu.mode=host-model and not working with guest.cpu.mode=custom.
BR
Alexander
Hi Alex,
based on CPU_map.xml, qemu64 CPU model requires (presents to Guest) the SVM
flag, which is the AMD things as you know (not sure why though...)
Here is the info:
root@ix1-c7-4:~# cat /usr/share/libvirt/cpu_map.xml| grep qemu64 -A36
Hi all,
maybe someone can help me with my KVM related questions.
At the moment we want to add cpu flags to the standard qemu64 CPU-Model in a
testcluster.
For this we tried the following configuration:
guest.cpu.mode=custom
guest.cpu.model=qemu64
guest.cpu.features=sse4.2 sse4.1
But ended up
