VirtualBox

Opened 16 years ago

Last modified 16 years ago

#2053 closed defect

kvm check fails — at Version 3

Reported by: Christoph Thielecke Owned by:
Component: other Version: VirtualBox 2.0.0
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by Frank Mehnert)

I have problems to start an vm because vbox 2.0.0 tells me there is kvm enabled but thats not true. Its definitly an module:

develop:/home/crissi# modinfo kvm
filename:       /lib/modules/2.6.25-2-686/kernel/arch/x86/kvm/kvm.ko
license:        GPL
author:         Qumranet
depends:
vermagic:       2.6.25-2-686 SMP mod_unload 686

and its not loaded:

develop:/home/crissi# lsmod | grep kvm
develop:/home/crissi#

Happens on Debian Lenny running 2.6.25-2-686 distribution kernel.

Additional info: I had installed 1.6.4 which was running fine. Then I upgraded to 1.6.6 and it runs fine too. Then I upgraded to 2.0.0 (using the VirtualBox-1.6.6-Linux_x86.run binary) and it claims about kvm. I went back to 1.6.6 (fixed the xml too) and it also claims about kvm. I dont had rebooted from working vbox 1.6.4.

Change History (3)

comment:1 by Sander van Leeuwen, 16 years ago

priority: criticalmajor

VBox.log?

Somebody is using VT-x or AMD-V, so that's why the warning is there. On Linux we just assume it's KVM. It doesn't give fake warnings.

comment:2 by Sander van Leeuwen, 16 years ago

Make sure there are no duplicate vbox drivers around too. Maybe the upgrade went wrong or something.

comment:3 by Frank Mehnert, 16 years ago

Description: modified (diff)

AFAIR you wrote somewhere that indeed kvm was involved, correct?

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use