search for: kworkflow

...lp us. Follows: 1) Import our QEMU images with virsh Currently, we import the QEMU VMs with virt-install. Is it possible to automatically discover the distro variant of a QEMU image in order to use it in the “--os-variant” option? Here is how we register a VM: https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-70617d452b008bc71362804d54032f24R113 2) The requirement of sudo to create a network When we register our VM, we want to keep the ssh working well. However, every time we register a VM we create a new network bridge as a result it requires sudo. Is it possible to avoid this? Or...

...did it last week. I'm doing the following steps: 1. I mount the disk image using libguestfs 2. Print the value MOUNT_PATH_DISK/etc/*-release 3. Take the distro and version Do you know a straightforward path? > > Here is how we register a VM: > > https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-70617d452b008bc71362804d54032f24R113 > > > > 2) The requirement of sudo to create a network > > > > When we register our VM, we want to keep the ssh working well. However, > > every time we register a VM we create a new network bridge as a result &...

...ossible to automatically discover the distro variant of a QEMU >image in order to use it in the “--os-variant” option? > You might be able to get that info using libguestfs (virt-v2v should be able to do that for you). >Here is how we register a VM: >https://github.com/rodrigosiqueira/kworkflow/pull/23/files#diff-70617d452b008bc71362804d54032f24R113 > >2) The requirement of sudo to create a network > >When we register our VM, we want to keep the ssh working well. However, >every time we register a VM we create a new network bridge as a result >it requires sudo. Is it pos...