+++ This bug was initially created as a clone of Bug #799708 +++ The CPU type is used by engine for compatibility - eg. Nehalem family, westmere, etc. A common issue from users is to understand what CPU they have and it's capabilities - eg. VT/SVM and NX being disabled are problem for us. We should provide CPU name (eg. "Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz") CPU Type (eg. Intel Westmere) Virtualization Extensions enabled (true|false) If XD(NX) is set for Intel machines or "Enhanced Virus Protection" for AMD machines Socket Count : eg 2 Socket Cores per Socket: eg 4 Hyperthreading enabled : Yes / no (only for AMD) --- Additional comment from dyasny on 2012-04-03 10:48:31 EDT --- libvirt's CPU flag notation: http://berrange.com/posts/2010/02/15/guest-cpu-model-configuration-in-libvirt-with-qemukvm/ --- Additional comment from dyasny on 2012-04-03 11:04:18 EDT --- CPU model description xml: /usr/share/libvirt/cpu_map.xml --- Additional comment from berrange on 2012-04-03 11:44:52 EDT --- > A common issue from users is to understand what CPU they have and it's > capabilities - eg. VT/SVM and NX being disabled are problem for us. Libvirt 0.9.10+ now provides a standalone command expressly for validating the scenario fo VT/SVM being off in the BIOS. eg you can run # virt-host-validate qemu QEMU: Checking for hardware virtualization : PASS QEMU: Checking for device /dev/kvm : PASS QEMU: Checking for device /dev/vhost-net : PASS QEMU: Checking for device /dev/net/tun : PASS we don't check NX currently, but that could be added. The virt-host-validate command is intended to be used by users / admins to sanity check their hardware prior to running libvirt/KVM --- Additional comment from acathrow on 2012-04-03 11:54:03 EDT --- (In reply to comment #4) > > A common issue from users is to understand what CPU they have and it's > > capabilities - eg. VT/SVM and NX being disabled are problem for us. > > Libvirt 0.9.10+ now provides a standalone command expressly for validating the > scenario fo VT/SVM being off in the BIOS. eg you can run > > # virt-host-validate qemu > QEMU: Checking for hardware virtualization : > PASS > QEMU: Checking for device /dev/kvm : > PASS > QEMU: Checking for device /dev/vhost-net : > PASS > QEMU: Checking for device /dev/net/tun : > PASS > > > we don't check NX currently, but that could be added. The virt-host-validate > command is intended to be used by users / admins to sanity check their hardware > prior to running libvirt/KVM Dan what's your thoughts on adding the virsh capabilities cpu vendor|model output there as well ? Alternatively we just parse that ourselves. --- Additional comment from berrange on 2012-04-03 12:05:40 EDT --- We could add a check that the host CPU model, is resolvable to one of the CPU models in cpu_map.xml - that would catch the NX problem nicely.
I wonder if this information should be presented on an additional - e.g. a debug or an informations/hosts page, as the status screen is already quite full. Thoughts?
It would be a sub-screen similar to ssh host key. An option on the main screen that is chosen and spawns a popup with the requested information
http://gerrit.ovirt.org/#/c/7653/