[Bug 203543] New: Starting with kernel 5.1.0-rc6, kvm_intel can no longer be loaded in nested kvm/guests - bugzilla-daemon

From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203543] New: Starting with kernel 5.1.0-rc6,  kvm_intel can no longer be loaded in nested kvm/guests
Date: Tue, 07 May 2019 20:45:45 +0000	[thread overview]
Message-ID: <bug-203543-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=203543

            Bug ID: 203543
           Summary: Starting with kernel 5.1.0-rc6,  kvm_intel can no
                    longer be loaded in nested kvm/guests
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.1.0-rc6
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: hilld@binarystorm.net
        Regression: No

1. Please describe the problem:
Starting with kernel 5.1.0-rc6,  kvm_intel can no longer be loaded in nested
kvm/guests

[root@undercloud-0-rhosp10 ~]# modprobe kvm_intel
modprobe: ERROR: could not insert 'kvm_intel': Input/output error

2. What is the Version-Release number of the kernel:
5.1.0-rc7

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes it seems to have appearded between 5.1.0-rc4 (it worked) and 5.1.0-rc6 (it
no longer worked)

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes, update to 5.1.0-rc6 and try to modprobe kvm_intel inside a guest where the
VMX capabilities has been exposted

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.