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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--- Comment #8 from Liran Alon (liran.alon@xxxxxxxxxx) ---
+Paolo

What are your thoughts on this?
What is the reason that KVM relies on CPU_BASED_RDPMC_EXITING to be exposed
from underlying CPU? How is it critical for it’s functionality?
If it’s because we want to make sure that we hide host PMCs, we should
condition this to be a min requirement of kvm_intel only in case underlying CPU
exposes PMU to begin with.
Do you agree? If yes, I can create the patch to fix this.

-Liran

> On 8 May 2019, at 16:51, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:
> 
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.kernel.org_show-5Fbug.cgi-3Fid-3D203543&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=Jk6Q8nNzkQ6LJ6g42qARkg6ryIDGQr-yKXPNGZbpTx0&m=7TirfLMNxYI-3Ygxm3kjDUB49Jwmk8bqD7671wy0hi8&s=Z_L1UqH19zon0ohDrCMU91ixA-Wn_vO7d-fO8s2G3PI&e=
> 
> --- Comment #5 from David Hill (hilld@xxxxxxxxxxxxxxx) ---
> I can confirm that reverting that commit solves the problem:
> 
> e51bfdb68725 ("KVM: nVMX: Expose RDPMC-exiting only when guest supports PMU”)
> 
> -- 
> You are receiving this mail because:
> You are watching the assignee of the bug.

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



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux