On Tue, Nov 20, 2018 at 11:17 AM Christian Ehrhardt
<christian.ehrha...@canonical.com> wrote:
>
> There are certain cases e.g. containers where the sysfs path might
> exists, but might fail. Unfortunately the exact restrictions are only
> known to libvirt when trying to write to it so we need to try it.
>
> But in case it fails there is no need to fully abort, in those cases try
> to fall back to the older ioctl interface which can still work.
>
> That makes setting up a bridge in unprivileged LXD containers work.
>
> Fixes: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1802906
>
> Signed-off-by: Christian Ehrhardt <christian.ehrha...@canonical.com>

FYI: in the meantime I got the email of the bug-reporter.
Eventually I'll add:
  Reported-by: Brian Candler <b.cand...@pobox.com>
But that alone was not worth a v2 submission.

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to