search for: guestfs_set_network

Thanks Pino for quick response. Actually I use the libguestfs APIs in C++ program. Following your idea, I think I should try guestfs_set_network for this. Please correct me if I have any misunderstanding. Thanks, Allen 2016-07-12 16:38 GMT+08:00 Pino Toscano <ptoscano@redhat.com>: > Hi, > > On Tuesday, 12 July 2016 16:30:17 CEST Baochuan Wu wrote: > > I mounted virtual disks of CentOS 6.4 using libguestfs. After moun...

On Tue, Jul 12, 2016 at 04:48:06PM +0800, Baochuan Wu wrote: > Thanks Pino for quick response. > Actually I use the libguestfs APIs in C++ program. Following your idea, I > think I should try guestfs_set_network for this. Yes this is correct. Calling: guestfs_set_network (g, 1); should enable the network inside the appliance. For further tips on using yum, have a look at how virt-customize works. In particular you must use "yum -y install ..." to avoid any unwanted interactivity. https:/...

...idge-helper. > 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? The larger question is 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 use...

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

An experimental series that adds support for rsync. Rich.

Hi All, I mounted virtual disks of CentOS 6.4 using libguestfs. After mounting, I tried to install some software using yum command. The yum command failed because of DNS failure, I think I correctly configured DNS(/etc/resolv.conf in the CentOS virtual disk). I wonder is it possible to access network inside libguestfs? Thanks, Allen

[Let's keep the replies on the mailing list please] On Wed, Jul 13, 2016 at 11:04:13AM +0800, Baochuan Wu wrote: > Thanks Richard. > I tried guestfs_set_network, and I think I can successfully use yum -y to > install software. It is a little slow. Most of the time is taken running yum and downloading packages ... > My program operates CentOS 6.4 VM virtual disks on CentOS 7, I installed > libguestfs into the CentOS 6.4. After installing, I reboo...

...d your guide and it works for me. Thanks, Allen 2016-07-13 17:04 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > [Let's keep the replies on the mailing list please] > > On Wed, Jul 13, 2016 at 11:04:13AM +0800, Baochuan Wu wrote: > > Thanks Richard. > > I tried guestfs_set_network, and I think I can successfully use yum -y to > > install software. It is a little slow. > > Most of the time is taken running yum and downloading packages ... > > > My program operates CentOS 6.4 VM virtual disks on CentOS 7, I installed > > libguestfs into the CentOS 6....

...upstream, but not in Fedora/RHEL/CentOS. It might also have been selected if you set the LIBGUESTFS_BACKEND=direct environment variable or called ‘guestfs_set_backend (g, "direct")’. Networking is enabled automatically by some tools (eg. virt-builder), or is enabled if your code called ‘guestfs_set_network (g, 1)’ (which is not the default). Note that the libvirt backend is _not_ affected, for two reasons: (1) It doesn't use SLIRP for networking (2) libvirt will use SELinux to confine the qemu process, so even if the appliance gains full control over qemu it is limited in what it can do. The so...

...s/recipes.html -------------- next part -------------- >From 56f426a0be9b0c2e6551ae7a841d236c5909b488 Mon Sep 17 00:00:00 2001 From: Richard Jones <rjones at redhat.com> Date: Tue, 24 Aug 2010 11:53:40 +0100 Subject: [PATCH] New APIs: set-network and get-network to enable network support. guestfs_set_network (g, true) enables network support in the appliance. --- src/generator.ml | 19 +++++++++++++++++++ src/guestfs-internal.h | 1 + src/guestfs.c | 13 +++++++++++++ src/guestfs.pod | 5 +++++ src/launch.c | 8 ++++++++ 5 files changed, 46 insertions(+), 0...

I didn't see what are the main differences in http://libguestfs.org/guestfs.3.html#backend Specifically, I'm interested in what is faster (direct sounds faster to me), and if there are any major restrictions (networking?) Here's an example command we are running (sorry, Python'ish, but you'll get it): ['virt-sysprep', '--connect', 'qemu:///system',

Possibly for post 1.40. Rich.

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

...otplugging of drives, ie. you can call guestfs_add_drive_opts after launching the handle - there are some differences in how networking is done, although they are rather obscure (and networking is not enabled by default anyway, so it would not affect you unless the main program called guestfs_set_network (g, 1) before guestfs_launch) - libvirt is the supported method to run qemu in RHEL - libvirt is way more complex and fails much more frequently :-( It's unfortunately because of the last point that if libvirt fails to start the qemu appliance, we print an error message telling you to try...

...ecisely match the kernel being used. -=head3 network_bridge - -The libvirt backend supports: - - export LIBGUESTFS_BACKEND_SETTINGS=network_bridge=virbrX - -This allows you to override the bridge that is connected to when the -network is enabled. The default is C<virbr0>. See also -L</guestfs_set_network>. - =head2 ATTACHING TO RUNNING DAEMONS I<Note (1):> This is B<highly experimental> and has a tendency to eat diff --git a/lib/launch-direct.c b/lib/launch-direct.c index 1e51d2a45..aa42f4ade 100644 --- a/lib/launch-direct.c +++ b/lib/launch-direct.c @@ -49,17 +49,6 @@ #include...

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.

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

...t; in v2v man page https://bugzilla.redhat.com/1527334 Various -it vddk -io vddk* options should be documented, removed or fixed https://bugzilla.redhat.com/1148012 Reverted: RFE: Allow qemu-bridge-helper to be used to implement guestfs_set_network -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject...

...n guestfs_impl_launch () from /lib64/libguestfs.so.0 #10 0x00007fac58a5eba5 in guestfs_launch () from /lib64/libguestfs.so.0 #11 0x00000000004117ca in main () Log: 2016-Aug-29 15:02:07 main:1385 Entering main() 2016-Aug-29 15:02:07 main:1393 guestfs_create succeeded 2016-Aug-29 15:02:07 main:1398 guestfs_set_network ok 2016-Aug-29 15:02:07 main:1406 Trying to add drive /dev/xvdc libguestfs: trace: add_drive "/dev/xvdc" "format:raw" libguestfs: trace: add_drive = 0 2016-Aug-29 15:02:07 main:1413 guestfs_add_drive_opts succeeded for drive: /dev/xvdc libguestfs: trace: launch libguestfs: trace...