Il 2022-06-13 09:47 Peter Krempa ha scritto:
If you want it to be more optimized you can e.g. write a script using
python bindings for libvirt and simply keep the connection open ...
... which additionally allows you to register 'domain lifecycle events'
[1] which give you a trigger when a new V
On Sun, Jun 12, 2022 at 00:16:20 +0200, Gionatan Danti wrote:
> Il 2022-06-11 19:32 Laine Stump ha scritto:
[...]
> > I guess you'll need to do a "virsh dumpxml --inactive" for each guest
> > and parse it out of there.
>
> It matches my results. However, virsh dumpxml is an expensive operation -
Il 2022-06-11 19:32 Laine Stump ha scritto:
libvirt's defaults are defaults, and can't be changed with config.
libvirt also will never changed the hardcoded default, because that
could break existing installations.
Thanks for the direct confirmation that default can not be changed with
config.
On 6/11/22 8:54 AM, Gionatan Danti wrote:
Hi all,
I just realized that libvirt default for directly attached interface is
vepa mode.
I discovered it now because virt-manager automatically enables bridge
mode, while cockpit-machines get the default vepa mode. This is
unfortunate because, bein
Hi all,
I just realized that libvirt default for directly attached interface is
vepa mode.
I discovered it now because virt-manager automatically enables bridge
mode, while cockpit-machines get the default vepa mode. This is
unfortunate because, being vepa switches very rare, it means that us
