adisbladis changed the topic of #nixops to: NixOps related talk | logs: | NixOps 2.0 planning call 2021-02-05 15:00 UTC
meh` has quit [Ping timeout: 240 seconds]
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixops
aleph- is now known as Batou
avaq has joined #nixops
cole-h has quit [Ping timeout: 245 seconds]
dmj` has quit [Read error: Connection reset by peer]
davidtwco has joined #nixops
dmj` has joined #nixops
avaq has quit [Ping timeout: 265 seconds]
andycandy has joined #nixops
<andycandy> I've got a question about virtualization. I'm planning my host and guests to run nixos, I just need a low footprint way to split resources between guests. it's all headless server AMD. Should I use vitrualbox as is described in nixops manual?
<andycandy> are there simpler or better performance solutions?
<CRTified[m]> Not necessarily nixops, but I think classical nixos containers (which uses systemd-nspawn) might be more efficient due to shared kernel and no virtualized hardware andycandy
<andycandy> thnx
avaq has joined #nixops
<andycandy> I was only able to find CPUShares and MemoryLimit for . is there a way to do that for containers?
<andycandy> CRTified[m] maybe?
<CRTified[m]> as far as I can tell it should be possible with systemd.resource-control:
meh` has joined #nixops
cole-h has joined #nixops
avaq has quit [Ping timeout: 260 seconds]
andycandy has quit [Ping timeout: 240 seconds]
andycandy has joined #nixops
andycandy has quit [Quit: Connection closed]
avaq has joined #nixops
avaq has quit [Ping timeout: 260 seconds]
meh` has quit [Ping timeout: 260 seconds]
cwnovusordoseclo is now known as cwfefifofum[m]
<Batou> Should almost definitely be someway to do it if that doesn't work. Given it's just cgroups v2(?) underneath