However, there seems to be an issue with test 2c. Test 2c is running the script with VT Extensions disabled in the bios. Here is the output for that case:
$ ./kvm-ok.new
INFO: Your CPU supports KVM extensions
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm
KVM acceleration can NOT be used
The script checks for /dev/kvm before checking dmesg for the bios message. This causes verdict to be called with an arg of 1 and the script exits. The user does not get the suggestion to enable KVM in the bios.
Maybe swap execution order of the /dev/kvm check and the dmesg check?
I tested the script at:
* http:// rookery. canonical. com/~kirkland/ kvm-ok
However, there seems to be an issue with test 2c. Test 2c is running the script with VT Extensions disabled in the bios. Here is the output for that case:
$ ./kvm-ok.new
INFO: Your CPU supports KVM extensions
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm
KVM acceleration can NOT be used
The script checks for /dev/kvm before checking dmesg for the bios message. This causes verdict to be called with an arg of 1 and the script exits. The user does not get the suggestion to enable KVM in the bios.
Maybe swap execution order of the /dev/kvm check and the dmesg check?