I found another problem which is sort of related to this thread. I hit a time-out waiting for the disk to be unlocked after creation:
https://github.com/libguestfs/libguestfs/commit/8081f54105bd990233f166170890192c1fd7d1f3#diff-5ca47c29ae13efa3959b8b28cf4dbd31R112 line 112 The disk size in this case is 40 GB and we currently wait 5 minutes. On the ovirt-node there's an ‘fallocate’ process (still) running. It's taken 23 minutes so far. Because we didn't reach a satisfactory conclusion of the whole sparse/format business, I am currently setting sparse = False (format is always raw in my testing): https://github.com/libguestfs/libguestfs/commit/8081f54105bd990233f166170890192c1fd7d1f3#diff-5ca47c29ae13efa3959b8b28cf4dbd31R92 line 92 I guess this is the cause of this problem in some sense. Is there something we can do? I'm still unclear how to fix the sparse/format mess, it seems unsolvable from the client side because we don't have sufficient information to make a decision. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
