Hello Peter,
Peter Boy [2022-03-15 8:29 +0100]:
> Am 15.03.2022 um 06:25 schrieb Martin Pitt
<mpitt(a)redhat.com>:
>
> I sent
https://github.com/cockpit-project/cockpit-machines/pull/622 to trim
> cockpit-machine's RPM dependencies. Today is release day, so this should make
> it into the F35/36/Rawhide package updates today.
off by one.. release day is *tomorrow*, sorry 😅
This is really great news (and incredibly fast). Thank you very much
for your effort.
No worries! I'm glad to clean this up, this has annoyed me for a long time also
in our infra (where I reduced the libvirt deps yesterday already).
I have not been able to find documentation on the machines module. Do
you have a link for me?
I'm afraid there currently isn't any user-facing docs for cockpit-machines
specifically. The generic libvirt documentation explains the concepts, what you
can do, etc. -- there is no c-machines specific functionality.
Or can you give me 1-2 sentences what the „session“ option in the
„Create VM“ worksheet does (available if not logged in as root)? Thanks a lot!
It's explained here:
https://wiki.libvirt.org/page/FAQ#What_is_the_difference_between_qemu:.2F...
I recommend it as such: Use "system" for production deployments, and
"session"
for testing/development/experimention as long as you can.
"session" does not support any custom/advanced networking, but works pretty
much everwhere (including containers) and without any privileges. "system"
requires a *lot* of privileges, but is independent from any user being logged
in.
Martin