Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1208768
Summary: | kvm [1]: error initializing Hyp mode: -6 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Itaru Kitayama <itaru.kitayama> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | berrange, clalancette, crobinso, ehabkost, extras-orphan, gansalmon, itamar, itaru.kitayama, jonathan, kernel-maint, madhu.chinakonda, markmc, mchehab, mjuszkie, quintela, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-04-08 21:52:12 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
Itaru Kitayama
2015-04-03 06:43:58 UTC
Can you give more details of where you are getting that error? Like trying to start a VM, or from dmesg, etc What kernel version are you running? The message is found in dmesg. The kernel version is 4.0.0-0.rc5.git2.4.1.fc22.aarch64 4.0.0-0.rc5.git4.1.fc22 has the same issue. The TC2 kernel still does not launch kvm either. Reproduced on my mustang. I brought it up on arm list since this issue affected f21 at one point, maybe a patch was dropped: https://lists.fedoraproject.org/pipermail/arm/2015-April/009335.html *** This bug has been marked as a duplicate of bug 1165290 *** |