Special handle --cpus for krun

[karuboniru]

Feature request description

krun, if no additional parameters are specified, assigns 16 vCPUs, while can usually be too much for a single threaded container and adds extra overhead.

--cpuset-cpus= could limit the cores assigned, but it also binds the workload to specific cores and requires extra permission.

--cpus just limits the time assigned but the krun instance will still use 16 vcpus.

Suggest potential solution

Maybe the code change is related to krun, what I want is when --cpus=2 is specified, the kvm instance will only have 2 cpus.

Have you considered any alternatives?

--cpuset-cpus=, at the cost of permission required + binding to specific cores.

Additional context

This might be the job for krun, if so, feel free to move this issue.

[baude]

@jakecorrenti ptal

[jakecorrenti]

Hi @karuboniru, this is most likely an issue with how krun handles arguments from the container engine. Let me look into it a little more in the coming days to confirm. If my initial hunch is correct, I'll move it over to the crun repository and assign it to myself from there.