search for: vdsm

This option is needed by vdsm for writing the ovf to a specific directory. The default is current directory. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1176598 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/cmdline.ml | 5 +++++ v2v/output_vdsm.ml | 16 +++++++---------...

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.

This option is needed by vdsm for writing the ovf to a specific directory. The default is current directory. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1176598 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/cmdline.ml | 5 +++++ v2v/output_vdsm.ml | 16 +++++++---------...

This option is needed by vdsm for writing the ovf to a specific directory. The default is current directory. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1176598 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/cmdline.ml | 5 +++++ v2v/output_vdsm.ml | 16 +++++++---------...

...port for compat=1.1 is uncertain in RHV 4.0 even on RHEL 7 nodes.) There are significant downsides to using qcow2 compat=0.10 instead of the modern default (compat=1.1). Therefore this patch does two things: For -o rhev, it drops support for compat=0.10 completely. You must use RHV 4.1. For -o vdsm, it adds an interim flag (--vdsm-compat=0.10 or --vdsm-compat=1.1) which controls the compat level of the qcow2 output file. VDSM should use --vdsm-compat=1.1 when it is known that modern qemu is available. We can make this the default later when all RHV instances have moved to 4.1. It also adds...

Currently we have a bunch of ad hoc options like --vddk* and --vdsm* (and proposed to add --rhv*) to handle extra parameters for input and output modes/transports. This complicates the command line parsing and also the clarity of the command line (becauseit's not very obvious which options apply to which side of the conversion). Replace these with a general m...

I still have not found time to fully review the series, but I found out that this patch breaks VDDK. See below. On Thu, 22 Mar 2018 15:24:23 +0000 "Richard W.M. Jones" <rjones@redhat.com> wrote: > Currently we have a bunch of ad hoc options like --vddk* and --vdsm* > (and proposed to add --rhv*) to handle extra parameters for input and > output modes/transports. This complicates the command line parsing > and also the clarity of the command line (becauseit's not very obvious > which options apply to which side of the conversion). > >...

This option is needed by vdsm for writing the ovf to a specific directory. The default is current directory. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1176598 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/cmdline.ml | 5 +++++ v2v/output_vdsm.ml | 16 +++++++---------...

This option is needed by vdsm for writing the ovf to a specific directory. The default is current directory. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1176598 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/cmdline.ml | 5 +++++ v2v/output_vdsm.ml | 16 +++++++---------...

Add option for -o vdsm that enables output of the modified OVF. oVirt engine should already be able to consume the OVF, but let's not take any chances and enable it only by command line argument. It can be made default later when it receives proper testing. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com&g...

...; RHEL 7 nodes.) > > There are significant downsides to using qcow2 compat=0.10 instead of > the modern default (compat=1.1). > > Therefore this patch does two things: > > For -o rhev, it drops support for compat=0.10 completely. You must > use RHV 4.1. > > For -o vdsm, it adds an interim flag (--vdsm-compat=0.10 or > --vdsm-compat=1.1) which controls the compat level of the qcow2 output > file. VDSM should use --vdsm-compat=1.1 when it is known that modern > qemu is available. We can make this the default later when all RHV > instances have moved t...

...t for compat=1.1 is uncertain in RHV 4.0 even on RHEL 7 nodes. There are significant downsides to using qcow2 compat=0.10 instead of the modern default (compat=1.1). Therefore this patch does two things: For -o rhev, it drops support for compat=0.10 completely. You now must use RHV 4.1. For -o vdsm, it adds an interim flag (--vdsm-compat-11) which turns off the previous behaviour. We can drop this flag later when all RHV instances have moved to 4.1. It also adds: vdsm-compat-11-option to the `virt-v2v --machine-readable' output to indicate that this flag can be used. Thanks: Yaniv...

Hi, I have several question regarding error handling when we call v2v from vdsm: 1. do you have return code values table? 2. how can vdsm determine if operations success/fail assuming vdsm crushed or the service restarted. 3. what is the best strategy to cancel blocked I/O calls? Thanks, Shahar.

This patch isn't quite complete (see ‘assert false’). Currently we have a bunch of ad hoc options like --vddk* and --vdsm* (and proposed to add --rhv*) to handle extra parameters for input and output modes/transports. This complicates the command line parsing and also the clarity of the command line (becauseit's not very obvious which options apply to which side of the conversion). Replace these with a gener...

On Tue, Jan 20, 2015 at 05:19:54PM +0200, Shahar Havivi wrote: > >From ff9261b201283f7bff16dc41721480e2e0a9f80f Mon Sep 17 00:00:00 2001 > From: Shahar Havivi <shaharh@redhat.com> > Date: Tue, 20 Jan 2015 14:41:23 +0200 > Subject: [PATCH] v2v: -o vdsm should assume data domain at -os path > > Unlike -o rhev which have only one data domin, -o vdsm can and usually > does have multiple data domain. > The path to vdsm is pre mounted so no need to assume nfs path with -os > Example: > -o vdsm -os /rhev/data-center/<data-center-u...

...gnificant downsides to using qcow2 compat=0.10 instead of > > the modern default (compat=1.1). > > > > Therefore this patch does two things: > > > > For -o rhev, it drops support for compat=0.10 completely. You must > > use RHV 4.1. > > > > For -o vdsm, it adds an interim flag (--vdsm-compat=0.10 or > > --vdsm-compat=1.1) which controls the compat level of the qcow2 output > > file. VDSM should use --vdsm-compat=1.1 when it is known that modern > > qemu is available. We can make this the default later when all RHV > > in...

v6 was here: https://www.redhat.com/archives/libguestfs/2018-March/msg00126.html This makes a number of significant changes: - Input and output options now use a uniform set of -io and -oo parameters. - For -o rhv-upload, we use ‘-oo rhv-cafile=/tmp/ca.pem’ etc. The ‘--rhv*’ options have been dropped. - Rearranges the documentation. - As before includes (untested) support for zero,

Unlike -o rhev which have only one data domin, -o vdsm can and usually does have multiple data domain. The path to vdsm is pre mounted so no need to assume nfs path with -os Example: -o vdsm -os /rhev/data-center/<data-center-uuid>/<data-domain-uuid> Bug-Url: https://bugzilla.redhat.com/1176591 Signed-off-by: Shahar Havivi <shaharh@redh...

...d (raw) > (100.00/100%) > [34357,0] Creating output metadata > [34357,0] Finishing off 9 hours ..? > And here the import folder /data/big_export/IMPORTS/0a6404e0-2857-45e4-9322-c1ada5ae13fb/images/a22862e8-f1ef-4530-ba55-6fda7850428c/ : > > total 556453768 > -rw-rw-rw- 1 vdsm kvm 214762060800 7 oct. 21:29 0c4abdff-af25-49df-87a4-917298c85688 > -rw-r--r-- 1 vdsm kvm 297 7 oct. 12:29 0c4abdff-af25-49df-87a4-917298c85688.meta > -rw-rw-rw- 1 vdsm kvm 21484431360 7 oct. 17:52 14dc0673-d4e0-43fc-84ef-3d4f3318f79e > -rw-r--r-- 1 vdsm kvm 296...