On 12/2/19 10:03 AM, Daniel P. Berrangé wrote: > The intent here is to allow the virt drivers to be run directly embedded > in an arbitrary process without interfering with libvirtd. To achieve > this they need to store all their configuration & state in a separate > directory tree from the main system or session libvirtd instances. > > This can be useful for doing testing of the virt drivers in "make check" > without interfering with the user's own libvirtd instances. > > It can also be used for applications using KVM/QEMU as a piece of > infrastructure to build an service, rather than for general purpose > OS hosting. A long standing example is libguestfs, which would prefer > if its temporary VMs did show up in the main libvirtd VM list, because > this confuses apps such as OpenStack Nova. A more recent example would > be Kata which is using KVM as a technology to build containers. > > Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> Reviewed-by: Cole Robinson <crobinso@xxxxxxxxxx> - Cole -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
