I use Gigabyte GA-MA78GM-US2H main-board, and I solved this problem by upgrading BIOS to version F9D (beta). I think the previous version (maybe F9C, but I'm not sure now) has some problem.
You may close this bug. I really thank you, and sorry for bothering you. Have a nice day ~ Regards, Hae-woo Park. 2011/10/22 Michael Tokarev <m...@tls.msk.ru>: > On 22.10.2011 09:42, Hae-woo Park wrote: >> Package: qemu-kvm >> Version: 0.14.1+dfsg-4 >> >> Hello. >> I really like this package, qemu-kvm. >> However, in these days, I cannot use it due to its bug. >> >> When I start kvm, I get the following message. >> >> ------- >> kvm_create_vm: Device or resource busy >> Could not initialize KVM, will disable KVM support >> kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument >> Aborted >> ------- > > This appears to be a bug in qemu-kvm - the last "Aborted" message. > Please retry with 0.15 version which were uploaded into unstable > just yesterday. The bug appears to be minor - it should not > crash in this case but continue running without kvm enabled > (which is, obviously, very slow). > >> The kvm modules seem well loaded. >> ------- >> Module Size Used by >> kvm_amd 46898 0 >> kvm 228179 1 kvm_amd >> >> dmesg: >> [ 3.958082] kvm: Nested Virtualization enabled >> [ 3.958085] kvm: Nested Paging enabled >> ------- >> >> When executing kvm, dmesg presents a simple message: >> [ 225.730117] kvm: enabling virtualization on CPU0 failed > > And this is a bug most likely in your BIOS. Check if virtualization > is enabled in the BIOS. Remember that in order for this change to > take effect (virtualisation in bios enable/disable), you have to > power-cycle the machine in question, simple reboot is not enough. > > If it is properly enabled and the thing still does not work, I'd > suggest you to post to k...@vger.kernel.org mailing list, where > kvm is being discussed/developed - I can't help here myself since > I don't know this area well enough and I don't want to act as a > broken phone between you and developers. > > >> And my /proc/cpuinfo is shown as follows: >> >> ------- >> processor: 0 >> vendor_id: AuthenticAMD >> cpu family: 16 >> model: 2 >> model name: AMD Athlon(tm) 7750 Dual-Core Processor > [] >> I think I've got this error since I upgraded the linux kernel to version 3.x, >> but I am not sure. :< > > It is very unlikely that the problem is kernel-specific. It is > possible, yes, but unlikely. But I guess it's trivial to verify - > just install an older (2.6.32?) kernel and see if you can reproduce > the issue. > >> There is one who suffers from a similar problem in Ubuntu Forum; >> http://ubuntuforums.org/showthread.php?t=1773187 > > Well, there's almost no information in that thread, so nothing to > say too. > >> How can I handle this bug ? >> Please help me. > > So verify if the problem is specific to some kernel version or is > general on your machine. If different kernel shows different > behavour, the next step will be to try to find the change which > is causing this -- git bisect will help here. If another kernel > shows the same issue, the problem is in hardware most likely. > In either case, it is kernel<=>hardware problem, and should be > addressed in kvm@vger mailinglist with all the details you can > provide. > > Thanks, > > /mjt > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
