similar to: [PATCH] launch: libvirt: Better error when bridge / virbr0 doesn't exist (RHBZ#1262127).

We've been carrying this exact patch in RHEL 7 for several years. It reverts the change made in 2014 where we switched to using the virbr0 bridge for libguestfs networking instead of SLIRP. We thought SLIRP was going to become unsupported in qemu, but recently there have been more encouraging signs since it looks like SLIRP will be spun off as a separate project, running as a modular process

Let's actually compile and test the patch this time, rather than trusting the RHEL 7.6 patch to apply directly to head ... Rich.

If the user doesn't specify a format (ie. they want autodetection) then we must do the file format detection ourselves since libvirt disabled this and now doesn't work at all on qcow2 overlays that have no backing_fmt field set. --- src/launch-libvirt.c | 90 ++++++++++++++++++++++++++++++++-------------------- 1 file changed, 56 insertions(+), 34 deletions(-) diff --git

Possibly for post 1.40. Rich.

I'm trying to build fedora-27 image for testing uploads: $ virt-builder fedora-27 -o /var/tmp/fedora-27.img ... [ 25.2] Opening the new disk virt-builder: error: libguestfs error: bridge ‘virbr0’ not found. Try running: brctl show to get a list of bridges on the host, and then selecting the bridge you wish the appliance network to connect to using: export

Hi, I noticed that brctl (or more accurately, libbridge) is using the wrong path when doing various lookups in sysfs: e.g. /sys/class/net/brXXX/stp_state when it should use /sys/class/net/brXXX/bridge/stp_state. This doesn't cause any problems on most systems as it falls back to the ioctl when the sysfs attempt fails; however the ioctl method is apparently deprecated. I believe the

On Wed, Oct 10, 2018 at 10:18 AM Pino Toscano <ptoscano@redhat.com> wrote: > On Tuesday, 9 October 2018 20:16:04 CEST Nir Soffer wrote: > > I'm trying to build fedora-27 image for testing uploads: > > > > $ virt-builder fedora-27 -o /var/tmp/fedora-27.img > > ... > > [ 25.2] Opening the new disk > > virt-builder: error: libguestfs error: bridge

On Wed, Oct 10, 2018 at 2:49 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > On Wed, Oct 10, 2018 at 02:27:44PM +0300, Nir Soffer wrote: > > On Wed, Oct 10, 2018 at 10:18 AM Pino Toscano <ptoscano@redhat.com> > wrote: > > > > > On Tuesday, 9 October 2018 20:16:04 CEST Nir Soffer wrote: > > > > I'm trying to build fedora-27 image for

Implement the GUESTFS_ADD_DRIVE_OPTS_SECRET argument of guestfs_add_drive_opts. For libvirt we have to save the secret in libvirtd first, get a UUID, and then pass the UUID back through the domain XML. --- src/launch-libvirt.c | 227 ++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 224 insertions(+), 3 deletions(-) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c

https://bugzilla.redhat.com/show_bug.cgi?id=912499 (especially comments 7 & 10) This patch set is the final fix so that we can access disks in use by other guests when SELinux and sVirt are enabled. Previously such disks were inaccessible because sVirt labels the disks with a random SELinux label to prevent other instances of qemu from being able to read them. So naturally the libguestfs

On Tuesday, 9 October 2018 20:16:04 CEST Nir Soffer wrote: > I'm trying to build fedora-27 image for testing uploads: > > $ virt-builder fedora-27 -o /var/tmp/fedora-27.img > ... > [ 25.2] Opening the new disk > virt-builder: error: libguestfs error: bridge ‘virbr0’ not found. Try > running: > > brctl show > > to get a list of bridges on the host, and

On Wed, Oct 10, 2018 at 02:27:44PM +0300, Nir Soffer wrote: > On Wed, Oct 10, 2018 at 10:18 AM Pino Toscano <ptoscano@redhat.com> wrote: > > > On Tuesday, 9 October 2018 20:16:04 CEST Nir Soffer wrote: > > > I'm trying to build fedora-27 image for testing uploads: > > > > > > $ virt-builder fedora-27 -o /var/tmp/fedora-27.img > > > ...

static function selinux_warning() isn't used if HAVE_LIBSELINUX isn't defined, which results in a warning. --- src/launch-libvirt.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c index 4588602..10a4d2c 100644 --- a/src/launch-libvirt.c +++ b/src/launch-libvirt.c @@ -138,7 +138,10 @@ static int make_drive_priv (guestfs_h *g, struct

Sorry, I didn't see this email yesterday. On Sun, Dec 11, 2016 at 11:25:12AM +0200, Shahar Havivi wrote: > Hey, > > I am getting this error after using virt-v2v-copy-to-local and trying to > run: > $ virt-v2v -i libvirtxml rhel7.xml -o local -os /var/tmp -of raw > > I try to set: > export LIBGUESTFS_BACKEND_SETTINGS=virbr0=ovirtmgmt The syntax is wrong, it should

Hey, I am getting this error after using virt-v2v-copy-to-local and trying to run: $ virt-v2v -i libvirtxml rhel7.xml -o local -os /var/tmp -of raw I try to set: export LIBGUESTFS_BACKEND_SETTINGS=virbr0=ovirtmgmt with no success and the file /etc/qemu/bridge.conf contains: allow virbr0 it only worked after creating the bridge, is there other way to import without creating the bridge? Thank

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA