At the moment libvirt users have no way to know what CPU models are known by libvirt; for example, virt-manager is accessing directly the file /usr/share/libvirt/cpu_map.xml to get this information. This can lead to cases (e.g. remote server) where the information known by the user accessing directly the file is different from what libvirt knows.