Displaying 20 results from an estimated 3000 matches similar to: "[PATCH] v2v: -o vdsm should assume data domain at -os path"
2015 Jan 26
2
Re: [PATCH] v2v: -o vdsm should assume data domain at -os path
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
>
2015 Jan 20
2
Re: [PATCH] v2v: -o vdsm should assume data domain at -os path
On 20.01.15 14:48, Richard W.M. Jones wrote:
> On Tue, Jan 20, 2015 at 04:25:20PM +0200, Shahar Havivi wrote:
> > > > + let pos = (String.length os) - 36 in
> > > > + let mp = String.sub os 0 (pos-1) in
> > > > + let uuid = String.sub os pos 36 in
> > >
> > > What is the significance of 36 here?
> > the length of uuid.
>
2015 Jan 20
3
Re: [PATCH] v2v: -o vdsm should assume data domain at -os path
On 20.01.15 12:59, Richard W.M. Jones wrote:
> On Tue, Jan 20, 2015 at 02:53:43PM +0200, Shahar Havivi wrote:
>
> > >From 87f448fc8b3243ad5d01acb65efb0c710d811a93 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
> >
2014 Dec 23
2
[PATCH] v2v: adding --vdsm-ovf-output option
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 +++++++---------
v2v/output_vdsm.mli | 1 +
v2v/test-v2v-o-vdsm-options.sh |
2014 Dec 23
2
[PATCH] v2v: adding --vdsm-ovf-output option
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 +++++++---------
v2v/output_vdsm.mli | 1 +
v2v/test-v2v-o-vdsm-options.sh |
2014 Dec 23
3
[PATCH] v2v: adding --vdsm-ovf-output option
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 +++++++---------
v2v/output_vdsm.mli | 1 +
v2v/test-v2v-o-vdsm-options.sh |
2015 Jan 20
0
Re: [PATCH] v2v: -o vdsm should assume data domain at -os path
On Tue, Jan 20, 2015 at 02:53:43PM +0200, Shahar Havivi wrote:
> >From 87f448fc8b3243ad5d01acb65efb0c710d811a93 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 rhev can and usually
2016 Mar 30
2
Re: [ovirt-devel] virt-v2v become zombie via python cpopen on error
On 30.03.16 14:28, Nir Soffer wrote:
> On Wed, Mar 30, 2016 at 1:36 PM, Michal Skrivanek
> <michal.skrivanek@redhat.com> wrote:
> >
> >> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones@redhat.com> wrote:
> >>
> >> On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote:
> >>> Hi,
> >>>
> >>> We
2015 Jan 26
0
Re: [PATCH] v2v: -o vdsm should assume data domain at -os path
On 26.01.15 09:11, Richard W.M. Jones wrote:
> 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
> >
>
2014 Sep 15
2
external call to v2v (vdsm integration)
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.
2014 Sep 17
3
Re: virt-v2v -ic question
On 16.09.14 15:09, Richard W.M. Jones wrote:
> On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote:
> > I am using upstream qemu while using this local variables:
> > export PATH=/home/shahar/git/qemu:$PATH
> > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64
> >
> > Is that sufficient?
>
> Yup, upstream qemu should
2016 Dec 07
2
[PATCH v3] v2v: -o vdsm: Add --vdsm-compat flag.
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.
2014 Sep 21
2
Re: virt-v2v -ic question
On 17.09.14 10:02, Richard W.M. Jones wrote:
> On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote:
> > On 16.09.14 15:09, Richard W.M. Jones wrote:
> > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote:
> > > > I am using upstream qemu while using this local variables:
> > > > export PATH=/home/shahar/git/qemu:$PATH
> > >
2015 Jan 26
1
[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-uuid>/<data-domain-uuid>
Bug-Url: https://bugzilla.redhat.com/1176591
Signed-off-by: Shahar Havivi <shaharh@redhat.com>
---
v2v/output_vdsm.ml
2014 Sep 16
2
Re: virt-v2v -ic question
On 16.09.14 14:21, Richard W.M. Jones wrote:
> On Tue, Sep 16, 2014 at 04:04:02PM +0300, Shahar Havivi wrote:
> > Hi,
> >
> > I am trying to convert from esx server to local directory a VM names CSB,
> > Its build from source 77b371b18b6a7ad37105a595931514f542a04396
> >
> > When running:
> > LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic
2016 Sep 06
2
[PATCH] virt-v2v: Support for ova exported from AWS
1. AWS the name tag is not mandatory - using default as a name
2. AWD doesn't prefix 'ovf:' as prefix to disk path
There is an open bug for oVirt:
https://bugzilla.redhat.com/show_bug.cgi?id=1371843
Signed-off-by: Shahar Havivi <shaharh@redhat.com>
---
v2v/input_ova.ml | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/v2v/input_ova.ml
2016 Sep 08
1
[PATCH] virt-v2v: Support for ova exported from AWS [v2]
1. AWS the name tag is not mandatory - using default as a name
2. AWD doesn't prefix 'ovf:' as prefix to disk path
There is an open bug for oVirt:
https://bugzilla.redhat.com/show_bug.cgi?id=1371843
Signed-off-by: Shahar Havivi <shaharh@redhat.com>
---
v2v/input_ova.ml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/v2v/input_ova.ml
2016 Mar 30
2
Re: virt-v2v become zombie via python cpopen on error
> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones@redhat.com> wrote:
>
> On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote:
>> Hi,
>>
>> We encounter a problem in VDSM project that virt-v2v become zombie task while
>> importing vm from vmware.
>> When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware
2016 Mar 30
2
virt-v2v become zombie via python cpopen on error
Hi,
We encounter a problem in VDSM project that virt-v2v become zombie task while
importing vm from vmware.
When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware
the process hang in read() method,
I am pretty sure that its not virt-v2v problem because when I run it from the
shell virt-v2v exit with an error, still maybe someone have an idea....
I wrote a small
2016 Nov 30
2
virDomainBlockInfo for local volume
Hi,
I am using virStorageVolGetInfo to get the volume size virStorageVol.download to download a
normal file for VDSM project.
I want to add support for block devices as well, I was able to see the size
via virDomainBlockInfo and download via virDomain.blockPeek which is works
fine for both file and block device.
1. Can I depend on virDomainBlockInfo for non block devices?
2. Does the