Re: domU memory exceeded =?=> spontaneous reboots

[Mike <debian@xxxxxxxxxxxxxxxxxxxxx>]

Elliott Mitchell wrote:
> It is
> reasonable to think people here might have surface familiarity with
> Kubernetes, but you're going to need to fill in many pieces for us.

Yes, I know.

> do you have any pieces of Kubernetes in domain 0?

No.

> Did you in fact look at the output of `xl info`

Yes.

> Are you instead guessing based on what you think your
> computer's setup is?

"313" is a guess based on what I recall changing, since I don't have that
configuration anymore.

> > dom0_mem=4G;max:4G dom0_max_vcpus=4 dom0_vcpus_pin 
> > xpti=dom0=false,domu=true no-real-mode edd=off
> 
> Okay, but 4GB for domain 0 strikes me as an odd value.  If this computer
> is primarily a server then 1GB should be plenty.

OK.  But that's scaled back from the default, all 64GB of the memory and
ballooning.  I can afford it for now.  I can also easily add 64GB to the
machine.

> Is
> this computer primarily your desktop and you're using Xen to generate VMs
> to experiment with Kubernetes?

It's a personal server, no GUI.  I'm migrating my services to Kubernetes.

> I'm starting to suspect this computer has a total of 8GB of memory?

32GB x 2 DDR5-5600.  I'll link you the full specs offline.

> the moment you have a VM machine, it will start eating your network.

I don't expect much in that regard.  I'll probably have a few dozen
Kubernetes pods (VMs), and Calico (a Kubernetes network plugin) handles
all the inter-node (inter-domU) traffic within the domU.  But there will
be communicaton between every pod and the control node (the other domU),
and that would pass through the xenbr0.


FYI, I've been using Xen for, idk, 15-20 years?  It's mostly been set-it-
and-forget-it.