Bug 1456273
Summary: | kvm disabled by bios on AMD Ryzen 7 1700 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Vlug <jan.public> |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | berrange, crobinso, jan.public, pbonzini, qguo, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-05-31 10:55:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jan Vlug
2017-05-28 15:16:41 UTC
Some additional version info: dnf list installed | grep virt libgovirt.x86_64 0.3.4-1.fc25 @anaconda libvirt-client.x86_64 2.2.1-1.fc25 @updates libvirt-daemon.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-config-network.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-interface.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-network.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-nodedev.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-nwfilter.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-qemu.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-secret.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-driver-storage.x86_64 2.2.1-1.fc25 @updates libvirt-daemon-kvm.x86_64 2.2.1-1.fc25 @updates libvirt-gconfig.x86_64 1.0.0-1.fc25 @updates libvirt-glib.x86_64 1.0.0-1.fc25 @updates libvirt-gobject.x86_64 1.0.0-1.fc25 @updates libvirt-libs.x86_64 2.2.1-1.fc25 @updates libvirt-python.x86_64 2.2.0-1.fc25 @fedora virt-install.noarch 1.4.1-2.fc25 @updates virt-manager.noarch 1.4.1-2.fc25 @updates virt-manager-common.noarch 1.4.1-2.fc25 @updates virt-viewer.x86_64 5.0-1.fc25 @updates dnf list installed | grep kvm libvirt-daemon-kvm.x86_64 2.2.1-1.fc25 @updates qemu-kvm.x86_64 2:2.7.1-6.fc25 @updates If I execute: # modprobe kvm-amd I get: modprobe: ERROR: could not insert 'kvm_amd': Operation not supported And in the log: kvm: disabled by bios I looked in the BIOS, but could not find an option to enable or disable virtualization extensions, of course there is the risk that I overlooked the setting in the BIOS. Here the details of the problematic AMD-Vi Event: [ 0.839574] AMD-Vi: Event logged [ [ 0.839576] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffffffdf8000000 flags=0x0a00] Sorry, this is a BIOS issue. The "disabled by bios" message only comes up if the BIOS has set a specific bit in the processor's MSR_VM_CR model specific register. It has nothing to do with bug 1445834. However, before closing this bug, please report the output of running this as root: modprobe msr dd if=/dev/cpu/0/msr iflag=skip_bytes skip=$((0xc0010114)) bs=8 count=1 1+0 records in 1+0 records out 8 bytes copied, 3.8182e-05 s, 210 kB/s Note that there is a special character in front of the output, that is not visible anymore here in Bugzilla. It is the U+0018 CANCEL control character: https://unicode-table.com/en/0018/ I got some feedback on the MSI forum: https://forum-en.msi.com/index.php?topic=287179 The virtualization was indeed not enabled in the BIOS. After enabling it (see details in the MSI forum) KVM works fine, and I get these results: # dmesg | grep -i kvm [ 15.843001] kvm: Nested Virtualization enabled [ 15.843008] kvm: Nested Paging enabled # lsmod | grep amd edac_mce_amd 28672 0 kvm_amd 2179072 0 kvm 593920 1 kvm_amd The CANCEL character does not show up anymore in: # dd if=/dev/cpu/0/msr iflag=skip_bytes skip=$((0xc0010114)) bs=8 count=1 1+0 records in 1+0 records out There is still this AMD-Vi Event logged: [ 0.845332] AMD-Vi: Event logged [ [ 0.845334] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffffffdf8000000 flags=0x0a00] I will close this bug, because KVM is working fine now. Thanks, 0x18 is SVMDIS+LOCK. Because it's locked, KVM could not fix up the value of the MSR. |