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.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
DistroRelease: Ubuntu 18.04
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
Tags: bionic uec-images
Uname: Linux 4.19.160-0419160-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Nov 27 21:50 seq
crw-rw---- 1 root audio 116, 33 Nov 27 21:50 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21
RelatedPackageVersions:
linux-restricted-modules-5.0.0-63-generic N/A
linux-backports-modules-5.0.0-63-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 5.0.0-63-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: False
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.0
dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0:
dmi.product.family: Virtual Machine
dmi.product.name: OpenStack Nova
dmi.product.version: 20.1.1
dmi.sys.vendor: OpenStack Foundation
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.