This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1905993

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
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/1905993

Title:
  Actual kernel don't want to make more than 64 cpus available

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is kinda complicated but i try my best to explain it as much as i
  can.

  First of all i found out that in bionic beaver cloud image i was able to have 
248 cpus without any issues.
  Then i've taken a look into focal, but there i was only able to get up up to 
64 cpus.

  
  Then i've tryed to figure out what was wrong. Debian, wasnt able to handle 
this with a 4.19 kernel.
  Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only 
with 64 cpus.

  So i think the problem maybe exist since 4.19.

  My setup. Openstack Hypervisor with ubuntu 18.04
  KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18.
  Every 5.* version seems to be affected as well.

  Debian buster has this issue and fedora (Both in latest versions with
  kernel above 4.18)

  
  Already started debugging with TJ- at irc.

  Paste links with debugging informations
  /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/
  and 
  virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/

  
  CPU on the Hypervisor (works fine):
  https://pastebin.ubuntu.com/p/KRNMSThT92/

  Hope this helps to dig down the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+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