Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=978608.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-06-26T22:57:22+00:00 George wrote: Description of problem: Despite exposed flags and SVM enabled in the BIOS - module won't load. Works flawlessly in Virtualbox. vendor_id : AuthenticAMD cpu family : 20 model : 2 model name : AMD E-350D APU with Radeon(tm) HD Graphics stepping : 0 microcode : 0x500010d Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter Hardware: AMD APU E350, M/B Gigabyte E350N Win8, F3 BIOS Version-Release number of selected component (if applicable): Kernels 3.6.10-4.fc18.x86_64 (release), 3.9.6-200.fc18.x86_64 (latest) How reproducible: For my HW - always Steps to Reproduce: 1. Enable SVM in BIOS 2. Install Fedora 18 3. modprobe kvm_amd Actual results: [root@localhost ~]# modprobe kvm_amd modprobe: ERROR: could not insert 'kvm_amd': Operation not supported [root@localhost ~]# dmesg|tail -n1 [ 1611.001914] kvm: disabled by bios Additional info: AMD-V available in Virtualbox Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/0 ------------------------------------------------------------------------ On 2013-07-14T11:10:25+00:00 Massimiliano wrote: I confirm that this issue arises even with kernels 3.8.0-27 and 3.10 (tryied on Ubuntu): dmesg shows the message "kvm: disabled by bios" I don't know if Red Hat has the 'kvm-ok' executable, BTW in Ubuntu it says that the machine is capable of running KVM, but KVM is disable. This is the output: # 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/1 ------------------------------------------------------------------------ On 2013-07-15T10:19:47+00:00 Kashyap wrote: On Fedora based systems, you can run $ virt-host-validate QEMU: Checking for hardware virtualization : PASS QEMU: Checking for device /dev/kvm : PASS QEMU: Checking for device /dev/vhost-net : PASS QEMU: Checking for device /dev/net/tun : PASS LXC: Checking for Linux >= 2.6.26 : PASS (NOTE: 'libvirt-client' package provide the above tool.) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/19 ------------------------------------------------------------------------ On 2013-07-24T13:54:48+00:00 George wrote: FYI: we've got pretty heavy email traffic regarding this issue, will update as soon as will confirm the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/27 ------------------------------------------------------------------------ On 2013-10-18T21:13:46+00:00 Justin wrote: *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/38 ------------------------------------------------------------------------ On 2013-11-27T16:03:27+00:00 Justin wrote: *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/39 ------------------------------------------------------------------------ On 2016-12-05T15:57:24+00:00 George wrote: No HW available for testing - cannot reproduce Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/comments/40 ** Changed in: linux (Fedora) Status: Unknown => Expired ** Changed in: linux (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1201092 Title: Cannot load kvm_amd module - (says disabled by bios) Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Expired Bug description: - Firt of all I would like to mention that this bug as been also raised 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 NOTE that I've also tried the new kernel 3.10 from Ubuntu Saucy. - 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 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: lightdm 2472 F.... pulseaudio /dev/snd/controlC0: lightdm 2472 F.... pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=3addb1e2-6fd3-4581-b4e3-287fc638926d InstallationDate: Installed on 2013-07-02 (12 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: fglrx Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=UUID=a820e9a0-4b2c-4ab6-adfd-f638f44d867f ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware 1.106 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: raring package-from-proposed third-party-packages Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: dmi.bios.date: 01/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E350N WIN8 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
