similar to: virt-builder resize error

On Tue, Nov 21, 2017 at 3:55 AM, Pino Toscano <ptoscano@redhat.com> wrote: > Hi, > > On Monday, 20 November 2017 22:57:04 CET David Kaylor wrote: > > I was trying out virt-builder and noticed that in some directories I > > receive an error when the image is resized. > > > > For example, if I run the following command from my home directory it > works >

On Tuesday, 21 November 2017 15:36:02 CET David Kaylor wrote: > On Tue, Nov 21, 2017 at 3:55 AM, Pino Toscano <ptoscano@redhat.com> wrote: > > > Hi, > > > > On Monday, 20 November 2017 22:57:04 CET David Kaylor wrote: > > > I was trying out virt-builder and noticed that in some directories I > > > receive an error when the image is resized. >

steps to reproduce: ./run guestfish -N disk:1536M <<EOF part-init /dev/sda mbr part-add /dev/sda p 1 1048577 part-add /dev/sda p 1048578 2097154 part-add /dev/sda p 2097155 -1 mkfs ext2 /dev/sda1 mkfs ext2 /dev/sda2 mkfs ext2 /dev/sda3 EOF qemu-img create -f raw test2.img 1520M ./run virt-resize --format raw --output-format raw --resize /dev/sda1=-2M --resize /dev/sda2=-8M --shrink

Instead of creating Guestfs handles and manually apply common options (e.g. debug and trace), use the open_guestfs in Common_utils. This also applies the common options to handles which didn't set them before, so we can inspect also their messages if needed. --- builder/builder.ml | 8 ++------ customize/customize_main.ml | 4 +--- dib/dib.ml | 4 +---

This still isn't working at the moment. See: http://marc.info/?t=139457409300003&r=1&w=2 This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. Rich.

Hello everyone! After I ran virt-resize (v1.31.28) on my disk with win2012R2 (partition table [GPT]: VFAT (100M), unknown (128M), NTFS (64G)) My VM fails to boot: black screen informing that Windows failed to start... Status: 0xc000000e Info: an unexpected error has occured. After some investigations, I realized that Windows remembers the GUID of disk it is installed to. If I execute

I've tried several times to resize one of my ocfs volumes[see emcpowere1 below] I'm on the latest [prod] version of ocfs/ocfs-tools as of 3pm EST on 18JUL04. Per instructions... Take down db, unmount all ocfs drives, use ' tuneocfs -F -S 100G /dev/emcpowere1 ' Supposedly this should work, but I get get.... The size specified, 100G, is larger than the device size, 59G. Aborting.

On 04/30/2015 06:51 PM, Chen, Hanxiao wrote: > Hi, Rich > >> -----Original Message----- >> From: Richard W.M. Jones [mailto:rjones@redhat.com] >> Sent: Wednesday, April 29, 2015 7:04 PM >> To: Chen, Hanxiao/陈 晗霄 >> Cc: libguestfs@redhat.com >> Subject: Re: [Libguestfs] [PATCH 00/10] virt-resize: add support for resizing MBR >> logical partitions

On 12/10/2015 02:55 PM, Pino Toscano wrote: > On Thursday 10 December 2015 13:55:26 Maxim Perevedentsev wrote: >> Hello everyone! >> >> After I ran virt-resize (v1.31.28) on my disk with win2012R2 >> (partition table [GPT]: VFAT (100M), unknown (128M), NTFS (64G)) >> My VM fails to boot: black screen informing that >> >> Windows failed to start...

Hi, On Monday, 20 November 2017 22:57:04 CET David Kaylor wrote: > I was trying out virt-builder and noticed that in some directories I > receive an error when the image is resized. > > For example, if I run the following command from my home directory it works > fine: > > virt-builder rhel-7.4 --size 10G --output test.img > > If I run the same command from /tmp or

Hey there everyone! Trying to use virt-builder to download & resize the standard fedora-23 image from libguestfs.org ... ??[rsawhill at jiop 11:50 ~] {0} $ rpm -q libguestfs-tools > libguestfs-tools-1.32.7-1.fc23.noarch > ??[rsawhill at jiop 11:50 ~] {0} $ virt-builder --list | grep fedora-23 > fedora-23 x86_64 Fedora? 23 Server > fedora-23 i686

Store the machine-readable flag globally, just like done for verbose/debug/etc, and enhance create_standard_options to provide --machine-readable automatically. --- common/mlstdutils/std_utils.ml | 4 ++++ common/mlstdutils/std_utils.mli | 7 +++++-- common/mltools/tools_utils.ml | 7 ++++++- common/mltools/tools_utils.mli | 5 ++++- 4 files changed, 19 insertions(+), 4 deletions(-) diff

Hi, the situation: Label: ''RootFS''  uuid: c87975a0-a575-405e-9890-d3f7f25bbd96     Total devices 2 FS bytes used 284.98GB     devid    2 size 311.82GB used 286.51GB path /dev/sdb3     devid    1 size 897.76GB used 286.51GB path /dev/sda3 RootFS created when sda3 was 897.76GB and sdb3 311.82GB. I have now freed other space on sdb. So I deleted sdb3 and recreated it occupying all

This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. This is now working, after fixing the rather stupid bug in fstrim. I've pushed the ones which were ACKed previously + the fstrim fix. Rich.

The first patch is just some simple refactoring. See the second patch for a description of the new virt-sparsify --tmp option. I tested this using a loopback device as my temporary block device, and it seems to work fine for me. Federico .. this needs a BZ :-) Rich.

I didn't test this one fully yet, but I'm building Fedora 26 ppc64/le test images now. However it seems like it could be a good idea. I wonder if anyone depends on the images we supply being MBR-based? Rich.

Hello, is CoreOS supported by libguestfs? I was trying to run several commands some were successful others ended up with an error: for example virt-df was OK but when I tried to do virt-resize I got the following error message: root@ny2proxd03:/var/lib/vz/images/100# virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized Examining vm-100-disk-1.qcow2 ... 100%

Some simple refactoring of virt-resize. I originally had the idea that we could turn virt-resize into a library (cf. virt-customize) and use it from virt-builder, but I now don't think that would make any meaningful difference. In particular we'd still have to open the handle the same number of times. These two patches are left over from my work on that. Rich.

Use the common function for ensuring a path is absolute; it should not change the behaviour at all. --- sparsify/cmdline.ml | 6 +----- v2v/input_disk.ml | 4 +--- v2v/input_ova.ml | 4 +--- 3 files changed, 3 insertions(+), 11 deletions(-) diff --git a/sparsify/cmdline.ml b/sparsify/cmdline.ml index 3eb0d5b..523d612 100644 --- a/sparsify/cmdline.ml +++ b/sparsify/cmdline.ml @@ -142,11

On Fri, Oct 10, 2014 at 04:03:26PM +0800, Zhi Yong Wu wrote: > On Fri, Oct 10, 2014 at 3:39 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Fri, Oct 10, 2014 at 11:40:03AM +0800, Zhi Yong Wu wrote: > >> HI, Richard > >> > >> Is there any plan to make daemon to directly run on the hypervisor, > >> not starting a guest? e.g. directly export