I don't believe this is a libvirt bug, because I can run VMS fine under libvirt. However, I can reproduce this (in utopic) with virt-manager.
When I manually insert cpu type 'qemu64', it complains about cpu flag svm not being applicable - this is on an intel laptop.
Somehow virt-manager is not getting the right cpu capabilities - this still could boil down to a libvirt bug (i.e. virsh capabilities giving wrong results).
I don't believe this is a libvirt bug, because I can run VMS fine under libvirt. However, I can reproduce this (in utopic) with virt-manager.
When I manually insert cpu type 'qemu64', it complains about cpu flag svm not being applicable - this is on an intel laptop.
Somehow virt-manager is not getting the right cpu capabilities - this still could boil down to a libvirt bug (i.e. virsh capabilities giving wrong results).