search for: outdisk

...mp; machine_readable then ( printf "virt-sparsify\n"; printf "linux-swap\n"; printf "zero\n"; @@ -126,23 +127,19 @@ read the man page virt-sparsify(1). exit 0 ); - (* Verify we got exactly 1 or 2 disks, depending on the mode. *) - let indisk, outdisk = - match in_place, List.rev !disks with - | false, [indisk; outdisk] -> indisk, outdisk - | true, [disk] -> disk, "" - | _ -> - error "usage is: %s [--options] indisk outdisk OR %s --in-place disk" - prog prog in + let indisk, mode = + if no...

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.

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.

It mimics a bit in OCaml the logic used in commit a95214b1985e694946e3426120a6fdc13a3f081f (for the main library) and commit 588af1953e5f7ab74009b9175cc5d3efb8bb651a (in disk-create), so in OCaml tools direct calls to qemu/qemu-img with filenames provided by the user can properly handle filenames with e.g. ':'. --- mllib/common_utils.ml | 13 +++++++++++++ mllib/common_utils.mli | 8

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.

...y/sparsify.ml @@ -30,15 +30,16 @@ module G = Guestfs let () = Random.self_init () let rec main () = - let indisk, format, ignores, machine_readable, zeroes, mode = - parse_cmdline () in + let cmdline = parse_cmdline () in - (match mode with + (match cmdline.mode with | Mode_copying (outdisk, check_tmpdir, compress, convert, option, tmp) -> - Copying.run indisk outdisk check_tmpdir compress convert - format ignores machine_readable option tmp zeroes + Copying.run cmdline.indisk outdisk check_tmpdir compress convert + cmdline.format cmdline.ignores cmdline.m...

...however run into a bit of a problem > > Basically I have a 5.4T qcow2 virtual disk, which I made too small (bugger) > > So I had read that you can expand these with your virt-resize tools. > > So I tried this sort of thing > > virt-resize --expand /dev/sda1 virtual.qcow2 outdisk.qcow2 > > however it gives me the rather intersting Fatal error: exception Guestfs.Error("febootstrap-supermin-helper exited with error status 1, see debug messages above") > > Which I took to be non-optimal > > I believe however this could mean that my cachedir is to...

...d_drive "/dev/null"; g#launch (); if g#feature_available [| "ntfsprogs"; "ntfs3g" |] then diff --git a/sparsify/copying.ml b/sparsify/copying.ml index ef196f6..bef0664 100644 --- a/sparsify/copying.ml +++ b/sparsify/copying.ml @@ -60,7 +60,7 @@ let run indisk outdisk check_tmpdir compress convert | Some fmt -> fmt (* user specified input format, use that *) | None -> (* Don't know, so we must autodetect. *) - match (new G.guestfs ())#disk_format indisk with + match (open_guestfs ())#disk_format indisk with...

...00644 --- a/sparsify/copying.ml +++ b/sparsify/copying.ml @@ -311,7 +311,7 @@ You can ignore this warning or change it to a hard failure using the (match option with | None -> "" | Some option -> " -o " ^ quote option) - (quote overlaydisk) (quote outdisk) in + (quote overlaydisk) (quote (qemu_input_filename outdisk)) in if verbose then printf "%s\n%!" cmd; if Sys.command cmd <> 0 then -- 1.9.3

...ay disk. *) - let indisk = - if not (Filename.is_relative indisk) then - indisk - else - Sys.getcwd () // indisk in + let indisk = absolute_path indisk in (* Check the output is not a char special (RHBZ#1056290). *) if is_char_device outdisk then diff --git a/v2v/input_disk.ml b/v2v/input_disk.ml index d56c476..3926602 100644 --- a/v2v/input_disk.ml +++ b/v2v/input_disk.ml @@ -63,9 +63,7 @@ class input_disk input_format disk = object error (f_"-i disk: invalid input filename (%s)") disk; (* Get the absolute path...

...ng at the verbose output, it appears that a randomly-generated name in /var/tmp is used for the indisk. Example: virt-resize --verbose --format raw --output-format raw --expand /dev/sda3 --unknown-filesystems error /var/tmp/vbaf3053.img test.img For directories where it fails, both the indisk and outdisk are the same: virt-resize --verbose --format raw --output-format raw --expand /dev/sda3 --unknown-filesystems error test.img test.img -David

...ring list; mode : mode_t; } diff --git a/sparsify/copying.ml b/sparsify/copying.ml index 8c8924241..a4bfcaa2a 100644 --- a/sparsify/copying.ml +++ b/sparsify/copying.ml @@ -37,7 +37,7 @@ type tmp_place = | Directory of string | Block_device of string | Prebuilt_file of string let run indisk outdisk check_tmpdir compress convert - format ignores machine_readable option tmp_param zeroes = + format ignores option tmp_param zeroes = (* Once we have got past argument parsing and start to create * temporary files (including the potentially massive overlay file), we @@ -179,7 +179,7 @...

...ppears that a randomly-generated name in > /var/tmp is used for the indisk. Example: > > virt-resize --verbose --format raw --output-format raw --expand /dev/sda3 > --unknown-filesystems error /var/tmp/vbaf3053.img test.img > > For directories where it fails, both the indisk and outdisk are the same: > > virt-resize --verbose --format raw --output-format raw --expand /dev/sda3 > --unknown-filesystems error test.img test.img Hmm... can you please paste the output of `findmnt --df`? In addition to that, do /tmp or /vms (mentioned above by you) have any special mount poin...

...gt;> We are trying not to start a appliance guest when issuing a libguestfs > >> command, such as virt-resize. > > > > There may be some confusion here. Virt-resize doesn't run the guest. > When i issue virt-resize, i exactly saw one guest is started, indisk > and outdisk are attached to this guest.... > > Do you mean that in the latest upstream, virt-resize doesn't run the guest? OK so you mean the libguestfs appliance. > > TBH I'm not exactly sure what your concerns are. > > We are afraid that if a guest is started when vrit-xxx comman...

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, 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 /vms (my default libvirt pool), I see the following in my verbose output: virt-resize '--verbose'

...output disk. -The output disk is the one created in the previous step. +virt-resize takes two mandatory parameters, the input disk and the +output disk (both can be e.g. a device, a file, or a URI to a remote +disk). The output disk is the one created in the previous step. # virt-resize indisk outdisk -- 2.7.4

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

...output disk. -The output disk is the one created in the previous step. +virt-resize takes two mandatory parameters, the input disk and the +output disk (both can be e.g. a device, a file, or a URI to a remote +disk). The output disk is the one created in the previous step. # virt-resize indisk outdisk -- 2.9.3

Version 1 of the patch, for discussion, but not to be applied. It does work, but needs a lot more testing. This removes all the psychopathic gettextify cruft, and replaces it with a 99 line Makefile.am. A large win, I think. The third patch implements gettext support in the OCaml tools. The fourth patch is just for illustration. It shows the consequent changes to libguestfs.pot and the po