Bug 1378362 - nVMX: Could not insert 'kvm_intel': Input/output error
Summary: nVMX: Could not insert 'kvm_intel': Input/output error
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 09:16 UTC by Gleb Schukin
Modified: 2017-09-04 12:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:13:49 UTC
Type: Bug


Attachments (Terms of Use)

Description Gleb Schukin 2016-09-22 09:16:15 UTC
Description of problem:

I'm running F25 with 4.8.0-0.rc7.git0.1.fc25.x86_64 kernel as L1 under Mirantis OpenStack 7.0 with nested wirtualization enabled in it as L0. 

#modprobe kvm_intel results is:
modprobe: ERROR: could not insert 'kvm_intel': Input/output error

I have another L1 with F24 with 4.7.3-200.fc24.x86_64 and I'm able to run other guests as L2

Both VM F24 and F25 show same output for
# rdmsr -0 0x483
007f6fff00036dff 

Version-Release number of selected component (if applicable):

kernel-4.8.0-0.rc7.git0.1.fc25

How reproducible:
Always with 4.8.0-rc7

Steps to Reproduce:
1. Start L0 Ubuntu 14.04 with 3.13 kernel
2. Start L1 Fedora 25 Alpha + dnf update
3. modprobe kvm_intel

Actual results:
I'm unable to start L2 guest under F25 as L1

Expected results:
I'm able to start L2 guest under F25 as L1

Additional info:
# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 63
model name	: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
stepping	: 2
microcode	: 0x1
cpu MHz		: 2599.996
cache size	: 25600 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl eagerfpu pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm vnmi ept fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
bugs		:
bogomips	: 5199.99
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:

Comment 1 Laura Abbott 2017-01-17 01:22:56 UTC
*********** 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 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 2 Gleb Schukin 2017-02-20 13:06:00 UTC
The issue still exist on 4.9.9-200.fc25.x86_64

Comment 3 Gleb Schukin 2017-02-22 15:42:05 UTC
It also exist on 4.10.0-1.fc26.x86_64 from rawhide

Comment 4 Justin M. Forbes 2017-04-11 14:53:29 UTC
*********** 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 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 5 Justin M. Forbes 2017-04-28 17:13:49 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 6 wp 2017-09-04 12:18:55 UTC
Issue is still present in 4.12.9-300.fc26.x86_64


Note You need to log in before you can comment on or make changes to this bug.