Comment 4 for bug 183663

> It's perfectly reasonable for kvm not not get properly configured (and
> thus be marked as installed) if you don't have the proper hardware
> extensions. You will not be able to use kvm.

For me, the only thing I can do is uninstall, and with the new release it works now, thanks for fixing that.

I'm going to make a suggestion for you to consider and see whether it is possible or desirable:

The problem is that some of us HAVE support for svm extensions on out systems, but bios disables it so support is there but can't be used.

When the installation script tries to load the modules, it fails and configurations fails, leaving an unconfigured package without a hint of what the problem is.

The installation script may be modified so it checks for virtualization support and do:
  1.-If there is no support (egrep ‘^flags.*(vmx|svm)’ /proc/cpuinfo), a message tell the user that the package can't work on that machine and stops the installation without trying to load the module.
  2.-If there is support, tries to load the module and if it fails, show a message telling the user to check the bios for options to enable virtualization.

Not all bioses have that option, and in some cases a bios upgrade is needed, but I think that this can help some users