On Sun, Sep 16, 2018 at 07:30:09PM +0300, Nir Soffer wrote:
I used to disable the limit enforcing "sparse" in libguestfs upstream source, but lately the simple check at the python plugin level was moved to to the ocaml code, and I did not have time to understand it yet.
If you want to remove the limit, try to look here: https://github.com/libguestfs/libguestfs/blob/51a9c874d3f0a9c4780f2cd3ee7072...
On RHEL, there is no such limit, and you can import vms to any kind of storage.
Richard, can we remove the limit on sparse format? I don't see how this limit helps anyone.
We already remove it downstream in all RHEL and LP builds. Here is the commit which does that:
https://github.com/libguestfs/libguestfs/commit/aa5608a922bd35db28f555e53aea...
Am 17.09.2018 um 09:53 schrieb Richard W.M. Jones: thanks for pointing to the commit. I was lazy and recompiled virt-v2v from the rhel-branch now and it worked fine. Regards Bernhard
We could remove it upstream, but AIUI it causes conversions to break with no easy way for users to understand what -oa modes are supported by what backends. To fix it properly we need a way for oVirt / imageio / whatever to describe what modes are possible for the current backend.
oVirt support several combinations:
file: - raw sparse - raw preallocated - qcow2 sparse (unsupported in v2v)
block: - raw preallocated - qcow2 sparse (unsupported in v2v)
It seems that oVirt SDK is does not have a good way to select the format yet, so virt-v2v cannot select the format for the user. This means the user need to select the format.
Right.
There are two open bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1600547 https://bugzilla.redhat.com/show_bug.cgi?id=1574734
Rich.