On Tue, 2013-07-23 at 23:11 +0200, Massimiliano Adamo wrote: > All, > > this is a bug with KVM, impacting (at least) all mainstream kernels that > I tried so far: 3.2, 3.3, 3.4, 3.5, 3.8, 3.10 and 3.11 > > This is the link of the downstream bug: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092 > > - Firt of all I mention that this bug has been raised also for Fedora > 18. > Here is the link: https://bugzilla.redhat.com/show_bug.cgi?id=978608 > > - I am running Ubuntu Raring (with the kernel 3.8.0-27-generic), but > I've also tried the mainstream kernel (without Ubuntu patches). > > - It happens with the following CPU: AMD E-350D > > - The kvm-ok executable says that the system is capable of running KVM, > but it also says the it's disabled in the BIOS. > > - This is the out put of kvm-ok: > # kvm-ok > INFO: /dev/kvm does not exist > HINT: sudo modprobe kvm_amd > INFO: Your CPU supports KVM extensions > INFO: KVM (svm) is disabled by your BIOS > HINT: Enter your BIOS setup and enable Virtualization Technology (VT), > and then hard poweroff/poweron your system > KVM acceleration can NOT be used > > - This is what modprobe kvm-amd says: > # modprobe kvm-amd > ERROR: could not insert 'kvm_amd': Operation not supported > root@yasna:~# dmesg |tail -n1 > [ 2542.263745] kvm: disabled by bios > > - AMD-V extension on Virtualbox works correctly. > Therefore the extension works properly but it's not recognized by KVM. What evidence do you have that Virtualbox is actually making use of AMD-V? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
