search for: l1387

...why does virt-v2v need a bridge. That's because it calls guestfs_set_network (g, 1): http://libguestfs.org/guestfs.3.html#guestfs_set_network and that causes the libvirt driver to add a network interface to the guest: https://github.com/libguestfs/libguestfs/blob/master/src/launch-libvirt.c#L1387-L1398 So you can get around this using LIBGUESTFS_BACKEND=direct which uses an entirely different form of networking (SLIRP / qemu user net). But why does virt-v2v call set_network? One reason is that old virt-v2v called it. Old virt-v2v tried to download and install kernels, but new virt-v2v d...

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

...?p=libvirt.git;a=blob;f=src/lxc/lxc_cgroup.c;h=39d955cd8cc2e34b6157e126fbb455d8f71e0647;hb=e8684eb541f01df9b45e87e0a8ce446c7bc90a17#l334 [2] http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/lxc/lxc_controller.c;h=5ca960f13e53501315b28f9086eaa389475b8feb;hb=e8684eb541f01df9b45e87e0a8ce446c7bc90a17#l1387 On Thu, Apr 17, 2014 at 11:26 AM, Filip Maj <fil@saucelabs.com> wrote: > Ah, nevermind, think my last post may not have been entirely correct. > We've spent some more time correlating the log output from our failed LXC > startup via libvirt [1] with libvirt code from the 1.2.2...

Further followups! We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2 code to try to figure out what libvirt is doing under the hood. Even though we have the log level set to 1 (info) in our libvirtd.conf, we are not seeing the VIR_DEBUG() [1] statements being printed out. There are tons of other presumably-debug lines of output showing up in our log. We are sort of