https://bugzilla.kernel.org/show_bug.cgi?id=209079 --- Comment #6 from Sean Christopherson (sean.j.christopherson@xxxxxxxxx) --- Nope, the failure path is common so we can't even glean anything from the offsets in the stack trace. In your data dump, both nodes show 10gb+ of free memory so there's plenty of space for the measly 4kb that KVM is trying to allocate. My best guess is that the combination of nodemask/cpuset stuff resulted in a set of constraints that were impossible to satisfy. At this point, I'd say just chalk it up to a bad configuration unless you want to pursue this further. If there's a kernel bug lurking then odds are someone will run into again. -- You are receiving this mail because: You are watching the assignee of the bug.
