Public bug reported:

KVM nesting support consumes too much memory
 
When running KVM with nesting support (kvm.nested=1 on the kernel command line) 
the shadow page table code will produce too many entries in the shadow code.

There is an upstream fix that will prevent the majority of the problem:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a06afe8383080c630a7a528b8382fc6bb4925b61


The fix is needed for 20.04 and 22.04.

** Affects: linux (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: New


** Tags: architecture-s39064 bugnameltc-198271 severity-high 
targetmilestone-inin2004

** Tags added: architecture-s39064 bugnameltc-198271 severity-high
targetmilestone-inin2004

** Changed in: ubuntu
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1974017

Title:
  [UBUNTU 20.04] KVM nesting support leaks too much memory, might result
  in stalls during cleanup

Status in linux package in Ubuntu:
  New

Bug description:
  KVM nesting support consumes too much memory
   
  When running KVM with nesting support (kvm.nested=1 on the kernel command 
line) the shadow page table code will produce too many entries in the shadow 
code.

  There is an upstream fix that will prevent the majority of the
  problem:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a06afe8383080c630a7a528b8382fc6bb4925b61

  
  The fix is needed for 20.04 and 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974017/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to