qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
<hyperfekt> qyliss: That's where I had gotten too. Nice to hear you got minijail to work after all.
<hyperfekt> s/(too)/to \1/
<hyperfekt> tutu
andi- has quit [Remote host closed the connection]
andi- has joined #spectrum
tilpner has joined #spectrum
<MichaelRaskin> qyliss: are plain NixOS VM rootfs good enough to boot with CrosVM?
<qyliss> probably, but there's not a lot to gain from them for single application VMs
<qyliss> there's no reason for these to be NixOS VMs
<MichaelRaskin> There is a lot to gain from saying «Our CeosVM packaging is good enough for NixOS VMs»!
<qyliss> those gains are for somebody else, then :)
<MichaelRaskin> Gimme the branch link and I could try, I guess
<MichaelRaskin> Actually, qemu-vs-CrosVM boot time comparison for the same NixOS image could be interesting, too
<qyliss> The branch is hyperfekt's: https://github.com/NixOS/nixpkgs/pull/52352
<qyliss> you'll have to wait for them to push the latest code though
<MichaelRaskin> In general, once your CrosVM-with-generated-boot-image fails, finding out whether it's crosvm or the image will be very useful
<MichaelRaskin> (and if it works from the first try, you are clearly hiding a lot in a supposedly openly developed project)
<qyliss> what?
<MichaelRaskin> Well, a rootfs debugger requires debugging, crosvm packaging might still require debugging, so on the first try you _are_ supposed to need to debug something
<MichaelRaskin> (And finding which side has a problem usually benefits from replace-one-half tests)
<hyperfekt> awake now, pushing
<hyperfekt> pushed...
pie_ has quit [Ping timeout: 268 seconds]
pie_ has joined #spectrum
tilpner has quit [Quit: tilpner]