Re: CPU oversubscription =?=> spontaneous reboots

[Mike <debian@xxxxxxxxxxxxxxxxxxxxx>]

Paul Leiber wrote:
> Could it be possible that it's not the activity on the DomU that is
> triggering the reboot, but rather network activity between two DomUs?

Sure, that's possible.  The domUs are a k8s control and worker node,
respectively, so they need to communicate with each other when I issue the
`kubectl delete` that trigger it.

But I resolved the issue (for now) by increasing the control node's
admittedly tight memory.  So that doesn't point to a network issue in my
mind.

> If the
> cause were activity by itself on one DomU (or both DomUs), then it should be
> possible to trigger the reboot by causing activity on the DomU itself (or on
> both DomUs), without network activity.

Because it's a k8s action, there's no way to do this action on one domU
alone.  The command communicates to the control node, then the control node
will tell the worker node what to do.

> What CPU architecture is your system based on?

amd64
Intel Core i9-14900T