similar to: Can I specify qcow2 preallocation method with virt-builder?

On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > When creating qcow2 images using virt-builder, is there a way to specify > > the qcow2 preallocation, as possible with qemu-img create -o > > preallocation=metada , for example? > > No .. but .. it does default to preallocation=metadata

On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > > When creating qcow2 images using virt-builder, is there a way to

On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > When creating qcow2 images using virt-builder, is there a way to specify > the qcow2 preallocation, as possible with qemu-img create -o > preallocation=metada , for example? No .. but .. it does default to preallocation=metadata provided that the output format is qcow2:

On Tue, May 17, 2016 at 6:01 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > > On Tue, May 17, 2016 at

On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > When creating qcow2 images using virt-builder, is there a way to > specify > > > the qcow2 preallocation, as possible with qemu-img create -o

On Sun, Dec 24, 2017 at 3:49 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Dec 24, 2017 at 02:15:44PM +0200, Yaniv Kaul wrote: > > I'm copying a file into a VM using virt-copy-in - which is great, but the > > file is wrongly labeled. > > How can I fix that? > > Hi Yaniv, > > The easiest thing is to run this after doing the virt-copy-in:

On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. > > The debug messages: > > libguestfs: trace: set_verbose true > > libguestfs: trace: set_verbose = 0 > > libguestfs: create: flags = 0, handle =

I'm copying a file into a VM using virt-copy-in - which is great, but the file is wrongly labeled. How can I fix that? TIA, Y.

As the minimum block size to discard in qcow2 is 64K, any point in fstrimming smaller contiguous blocks? TIA, Y.

On Thu, Nov 23, 2017 at 4:05 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, Nov 23, 2017 at 03:00:45PM +0200, Yaniv Kaul wrote: > > On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > > > Since I upgrading to FC27, I

On Thu, Nov 23, 2017 at 02:05:32PM +0000, Richard W.M. Jones wrote: > On Thu, Nov 23, 2017 at 03:00:45PM +0200, Yaniv Kaul wrote: > > On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > > > Since I upgrading to FC27, I *sometimes* fail to

v3: Change the flag from --vdsm-compat-11 to --vdsm-compat=1.1 Also the --machine-readable output has changed. I have also added a test. Rich.

On Feb 6, 2018 11:06 AM, "Luca 'remix_tj' Lorenzetto" < lorenzetto.luca@gmail.com> wrote: On Mon, Feb 5, 2018 at 11:13 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > http://libguestfs.org/virt-v2v.1.html#vmware-vcenter-resources > > You should be able to run multiple conversions in parallel > to improve throughput. > > The only long-term

Any idea what 'virt-customize' script I should use to convert from virtio-blk (vda, vdb...) to virtio-scsi (sda, sdb...) ? I've tried naively to convince libvirt to use virtio-scsi and still present it to the guest as 'vd*' - that didn't work ( <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/>

On Wednesday, 7 December 2016 10:02:49 CET Richard W.M. Jones wrote: > Support for RHEV with RHEL 6 nodes required us to output the old style > qcow2 compat=0.10 images. Since RHEV 3.6 GA, RHEL 6 has not been > supported as a RHEV node type. Since RHV 4.1, compat=1.1 is > supported. (Support for compat=1.1 is uncertain in RHV 4.0 even on > RHEL 7 nodes.) > > There are

Assuming the VM is not running, and we have a base (raw, sparse) with a snapshot (qcow2) on top of it. Is there any issue with running virt-sparsify on the base image? I assume deleted blocks in the base can be sparsified, since they are either still deleted on the snap (which is fine) or were written in the snap (which is fine either and does not change or matter for the base image). Can I assume

Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. The debug messages: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x7f4600005dd0, program = python2 libguestfs: trace: set_program "lago" libguestfs: trace: set_program = 0 libguestfs: trace: add_drive_ro

[Let's discuss this upstream] On Wed, Nov 04, 2015 at 12:18:48PM +0200, Yaniv Kaul wrote: > I'm missing something here - what will happen to the tree structure? > Will we lose it? So essentially it performs a merge? In copying mode: virt-sparsify disk1 disk2 creates an overlay on top of disk1, writes zeroes to the overlay in the parts of disk1 which are not used (disk1 is not

$ qemu-img create -f qcow2 -b /tmp/centos-6.img overlay.qcow2 $ virt-sparsify --in-place overlay.qcow2 virt-sparsify: error: disk image 'overlay.qcow2' appears to have a backing file. You should use copying mode sparsification for this file (see the virt-sparsify(1) manual). Thanks: Yaniv Kaul --- sparsify/in_place.ml | 5 +++++ 1 file changed, 5 insertions(+) diff --git

On Tue, Feb 06, 2018 at 11:11:37AM +0100, Luca 'remix_tj' Lorenzetto wrote: > Il 6 feb 2018 10:52 AM, "Yaniv Kaul" <ykaul@redhat.com> ha scritto: > > > I assume its network interfaces are also a bottleneck as well. Certainly if > they are 1g. > Y. > > > That's not the case, vcenter uses 10g and also all the involved hosts. > > We