similar to: virt-builder fail with "bridge ‘virbr0’ not found" (fixed by LIBGUESTFS_BACKEND=direct ?!)

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

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 > > > ...

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

The current diagnostic is terrible. This one tells the user how to diagnose and fix the problem. --- src/launch-libvirt.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c index 1c0bfac..d4c4c47 100644 --- a/src/launch-libvirt.c +++ b/src/launch-libvirt.c @@ -181,6 +181,7 @@ static int is_blk (const

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

Possibly for post 1.40. Rich.

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

v3: - Various changes to dhclient/dhcpcd as discussed on the mailing list.

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

v2: - Make virbr0 configurable. - Fix the tests.

[Best to ask these questions on the libguestfs mailing list. You don't have to subscribe] On Wed, Aug 31, 2016 at 03:18:32PM +0100, cmc wrote: > Hi, > > I have two questions about virt-v2v that I hope someone could help with. > > 1. I have a host that I use to export VMs from VMWare to oVirt, as the RHEL > 7 version of virt-v2v does not support W2012. Please try this

On 30.03.16 14:28, Nir Soffer wrote: > On Wed, Mar 30, 2016 at 1:36 PM, Michal Skrivanek > <michal.skrivanek@redhat.com> wrote: > > > >> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones@redhat.com> wrote: > >> > >> On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote: > >>> Hi, > >>> > >>> We

"qemu-img convert" detects zeroes in allocated areas and punch holes in the destination image. This may save space on the destination image, but slows down conversion when using outputs such as rhv-upload, which have very large overhead per requests. Using the -S flag, we can treat small areas filled with zeroes as data, limiting the number of requests, and speeding the operation. Here

Hi Rich, Thanks, I'll see if oVirt supports 7.3 yet. > What's the actual error? > -------------8<------------ virt-v2v: 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

> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote: >> Hi, >> >> We encounter a problem in VDSM project that virt-v2v become zombie task while >> importing vm from vmware. >> When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware

I have a Fedora 24 system I can already get this working for most OVA files, just the BSD and atomic ones weren't recognized. Assuming my version of virt-v2v is just old, I installed rawhide on a different system and tried with virt-v2v-1.37.8-1.fc27.x86_64 and now its having another problem. Is there a known version of virt-v2v I should be using? Here is the output from the rawhide attempt

Seems that archive.libguestfs.org has issues: $ virt-builder --list curl: (7) Failed to connect to archive.libguestfs.org port 80: Network is unreachable virt-builder: error: external command ‘'curl' -q --config '/tmp/virt-builder.zfIvaP/guestfscurl5afb25.conf'’ exited with error 7 If reporting bugs, run virt-builder with debugging enabled and include the complete output:

On Tue, Nov 18, 2014 at 11:37:31AM +0530, Niranjan wrote: > libvirt: XML-RPC error : Cannot recv data: Connection reset by peer > virt-builder: error: libguestfs error: could not connect to libvirt (URI = > qemu:///session): Cannot recv data: Connection reset by peer [code=38 > domain=7] This is a libvirt bug. Possibly: https://bugzilla.redhat.com/show_bug.cgi?id=1164773 or: