testdrive claims no VT when I do have it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
TestDrive |
Fix Released
|
Medium
|
Dustin Kirkland | ||
testdrive (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
I happen to have both Virtualbox 3.0.12 and kvm installed, but unloaded the kvm/kvm-intel modules so that VirtualBox doesn't complain. I wanted to try out an ISO and note that testdrive will pick Virtualbox, which is fine. However it complains that I lack VT, when VirtualBox _does_ support VT. Can testdrive be changed to spawn VirtuxlBox with the necessary parameters to use VT.
alan@hactar:~$ testdrive -u http://
INFO: Your CPU supports KVM extensions
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm
KVM acceleration can NOT be used
WARNING: Your CPU's lack of VT will impact the performance of your VMs.
INFO: Using VirtualBox for virtual machine hosting...
Changed in testdrive (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Dustin Kirkland (kirkland) |
Changed in testdrive: | |
status: | Fix Committed → Fix Released |
Changed in testdrive: | |
status: | Fix Released → Fix Committed |
Changed in testdrive (Ubuntu): | |
status: | Fix Released → Fix Committed |
Changed in testdrive: | |
status: | Fix Committed → Fix Released |
Further to this, VirtualBox _does_ actually enable VT by default it seems when used as above, so the warning message is really not needed if using VirtualBox.