All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 211109] New: Hard kernel freeze due to large cpu allocation.
Date: Sun, 10 Jan 2021 09:45:51 +0000	[thread overview]
Message-ID: <bug-211109-28872@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 211109
           Summary: Hard kernel freeze due to large cpu allocation.
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.9.9-95-tkg-MuQSS-llvm
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: vytautas.mickus.exc@gmail.com
        Regression: No

Allocating a large amount of vcpu (30,31) on a system with 32 threads (16 core
ryzen 3950x) causes hard freeze of the whole system. While 16-17 vcpu
allocation is fine.

This was seen while using minikube
```
minikube start --cni=calico --container-runtime=cri-o --cpus=$(($(nproc) - 1))
--driver=kvm2 -n 3
```

Last journal entry is:
```
Jan 10 10:14:51 rig libvirtd[2269]: operation failed: domain 'minikube' already
exists with uuid 4aacd29f-bd5f-418d-b267-42b79f75fbab
```
At which point minikube sees that the domain already exists and launches it.
Hard freeze is immediate.

OS:
Linux rig 5.9.9-95-tkg-MuQSS-llvm #1 TKG SMP PREEMPT Sun, 22 Nov 2020 07:41:26
+0000 x86_64 GNU/Linux

os-release:
```
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
```

-- 
You may reply to this email to add a comment.

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

             reply	other threads:[~2021-01-10  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10  9:45 bugzilla-daemon [this message]
2021-01-10  9:48 ` [Bug 211109] Hard kernel freeze due to large cpu allocation bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-211109-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.