similar to: Re: [PATCH] add enable_appliance flag to specify the appliance build

On Fri, Apr 28, 2017 at 05:03:58PM +0300, Pavel Butsykin wrote: > On 27.04.2017 18:28, Richard W.M. Jones wrote: > > > >On Thu, Apr 27, 2017 at 03:55:10PM +0300, Pavel Butsykin wrote: > >>The flag determines the behavior of working with the appliance, and specifically > >>the choice to use the build supermin appliance or the fixed appliance. If the >

On Thu, Apr 27, 2017 at 03:55:10PM +0300, Pavel Butsykin wrote: > The flag determines the behavior of working with the appliance, and specifically > the choice to use the build supermin appliance or the fixed appliance. If the > flag is false then the libguestfs will only use the fixed appliance, otherwise > the build supermin appliance. > > This patch is aimed at solving the

On Fri, Apr 28, 2017 at 05:04:15PM +0300, Pavel Butsykin wrote: > At least two control files (packages and base.tar.gz) are necessary for the > supermin appliance. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > lib/appliance.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/lib/appliance.c b/lib/appliance.c >

On Thu, Apr 27, 2017 at 03:54:44PM +0300, Pavel Butsykin wrote: [...] > >(2) If the fixed appliance was located somewhere else, you could do: > > > > LIBGUESTFS_PATH=/path/to/somewhere/else:/usr/lib64/guestfs > > export LIBGUESTFS_PATH > > > >and then it would look for the fixed appliance in > >/path/to/somewhere/else and use it. If the fixed

On Tue, Jun 20, 2017 at 06:34:28PM +0300, Pavel Butsykin wrote: > On 20.06.2017 17:47, Richard W.M. Jones wrote: > >On Tue, Jun 20, 2017 at 05:04:53PM +0300, Pavel Butsykin wrote: > >>I noticed that raw is intentionally used as image format for appliance > >>image. So I would like to ask, is there any reason to use raw as image > >>format for appliance? >

On Thu, May 04, 2017 at 02:20:28PM +0300, Pavel Butsykin wrote: > This patch changes appliance search using paths with multiple directories. Now > all appliance checks will be done separately for each directory. For example > if the path LIBGUESTFS_PATH=/a:/b:/c, then all applainces are searched first in > /a, then in /b and then in /c. It allows to flexibly configure the libguestfs

Could you run the command below on the same arm host and attach the output? It'll give us a lot more information about what went wrong: /usr/bin/supermin --build -v -v -v --copy-kernel -f ext2 --host-cpu armv7hl /usr/lib/guestfs/supermin.d -o /tmp/appliance.d Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and

On Tue, Sep 15, 2015 at 04:31:46PM +0300, Maxim Perevedentsev wrote: > Hello everyone! > > I am working on resizing qcow2 images using virt-resize+liguestfs. If you're shrinking, I believe a better way to do this is to sparsify the image. > E.g. I when shrinking a partition, I have to resize filesystem using > resize2fs-size. The problem is that I cannot find out minimal >

On Tue, Sep 15, 2015 at 05:17:16PM +0300, Maxim Perevedentsev wrote: > On 09/15/2015 04:57 PM, Richard W.M. Jones wrote: > >>2) More general, how to execute commands from appliance but make > >>them run over image (which may not have anything but filesystem) - I > >>saw something like that in source. > >Not sure I understand the question? > > As I

A lot of people ask where they can get virt-p2v & virt-v2v for RHEL or CentOS. All the answers are here: http://libguestfs.org/virt-v2v/ Rich. -- 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.

On Tue, Nov 03, 2015 at 03:03:21PM +0530, Chengappa Changz wrote: > Hello Rich, > Greetings! > > It was great connecting with you and, I would like to thank you for your > time and being patient on answering all our queries. > > However, referring to the link -> > http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works we have a > ambiguity -> i.e. under the

On Tue, Nov 15, 2016 at 10:23:26AM +0000, Richard W.M. Jones wrote: > (1) Try upgrading to a newer version of supermin. RHEL 7.3 has > supermin 5.1.16, also available here: > > https://people.redhat.com/~rjones/libguestfs-RHEL-7.3-preview/ > > If the bug is still present in the newer version, then: > > (2) Run supermin with lots of debugging enabled: > >

On Wed, Feb 01, 2017 at 03:53:52PM +0100, Pino Toscano wrote: > On Wednesday, 1 February 2017 13:40:17 CET Richard W.M. Jones wrote: > > In commit 08f82f2e3d6975b72340dd59f438862e152a15ef we increased the > > memory size to 800MB (on x86) so that the semodule command would work. > > > > However it has been discovered that another SELinux command takes > > large

On Wed, Jun 05, 2019 at 04:13:37PM +0000, kedorlaomer wrote: > According to the manpage, > > > Virt-p2v converts a physical machine to run virtualized on KVM, > > managed by libvirt, OpenStack, oVirt, Red Hat Virtualisation > > (RHV), or one of the other targets supported by virt-v2v(1). > > In fact, `openstack` is one of the targets of `virt-v2v`. According > to

On Wed, Sep 25, 2019 at 03:16:18PM +0200, Pino Toscano wrote: > Mention what is the password of the root user on the disk images created > by virt-p2v-make-disk, virt-p2v-make-kickstart, and virt-p2v-make-kiwi, > so users know how to login in the live p2v system. > --- > virt-p2v-make-disk.pod | 2 ++ > virt-p2v-make-kickstart.pod | 2 ++ > virt-p2v-make-kiwi.pod |

On Wed, Nov 19, 2014 at 02:41:49PM +0100, Nicolas Ecarnot wrote: > When trying to p2v an Oracle Linux 7.0 VM, it ran very verbosely > then failed saying it was not a kind of OS it knows how to convert. We could probably support OEL with a bit of effort, but it's not supported now. The virt-v2v manual (which you should read, as well as the virt-p2v manual) provides a list of all OSes

On Fri, Jan 24, 2014 at 11:55:26AM +0100, Olaf Hering wrote: > On Fri, Jan 24, Richard W.M. Jones wrote: > > > However I don't understand why disabling IPv6 should be necessary. If > > sites resolve to AAAA+A records, then presumably it's going to choose > > the A (IPv4) route since no IPv6 route exists. If a site resolves to > > only an AAAA record, then

On Sat, Feb 08, 2020 at 01:25:28AM +0200, Mykola Ivanets wrote: > From: Nikolay Ivanets <stenavin@gmail.com> > > I faced with situation where libguestfs cannot recognize partitions on a > disk image which was partitioned on a system with "4K native" sector > size support. Do you have a small test case for this? > In order to fix the issue we need to allow users

On Mon, Feb 10, 2020 at 02:28:08PM +0200, Nikolay Ivanets wrote: > пн, 10 лют. 2020 о 13:43 Richard W.M. Jones <rjones@redhat.com> пише: > > > > On Sat, Feb 08, 2020 at 01:25:28AM +0200, Mykola Ivanets wrote: > > > From: Nikolay Ivanets <stenavin@gmail.com> > > > > > > I faced with situation where libguestfs cannot recognize partitions on a

I had some more ideas overnight: (1) Check that libparted0 is installed on the *host*. (2) Try to find out what libraries the parted binary requires on the host and appliance. On the host: ldd /usr/bin/parted On the appliance: virt-rescue --scratch ><rescue> ldd /usr/bin/parted (3) Remove the appliance and recreate it: rm -rf /var/tmp/.guestfs-* libguestfs-test-tool (4)