On Fri, Jun 28, 2024 at 01:08:43PM +0200, Gianluca Cecchi wrote: > On Fri, Jun 28, 2024 at 11:52 AM Michal Prívozník <mprivozn@xxxxxxxxxx> > wrote: > > > > > > > I'm not sure why you want to replicate what libvirt does, but anyway. > > > > [snip] > > > > > Happy hacking! > > Michal > > > > Thanks for your reply, Michal. > It is not for hacking, but mainly for curiosity. > I never really reasoned about it before, but until yesterday I wrongly > assumed that all the details for the VM, set from within virt-manager (or > similar) or with "virsh edit", were driven then through and translated into > command line parameters. Alot of stuff does translate to QEMU command line parameters. The resource management side though is mostly implemented by libvirt with help from QEMU. All QEMU really does is tell libvirt what PIDs each of its threads have, so libvirt can then issue suitable syscalls / make cgroups changes for these PIDs. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
