Description of problem:

On ppc64, the filesystem blocksize defaults to something much
bigger than x86 (ie. 64k).  The reason is because this is the
normal page size on PowerPC.  virt-make-fs filesystem estimation
relies on knowing the block size of the filesystem it will create,
and it assumes 4k.  However on ppc64 this leads to misestimation
of the eventual filesystem size, and so virt-make-fs fails.

This is easily demonstrated by running the virt-make-fs
test in the upstream sources.

For example:

test-virt-make-fs: parameters: --type=ext3 --format=qcow2 --partition=gpt --size=+1M --debug
test-virt-make-fs: size of test file: 2716 KB
2716+0 records in
2716+0 records out
2781184 bytes (2.8 MB) copied, 0.0239506 s, 116 MB/s
input format = POSIX tar archive (GNU)
estimate = 2785280 bytes (2720 1K blocks, 680 4K blocks)
running: qemu-img create -f qcow2 output.img 5554176

[...]

virt-make-fs: error copying contents into filesystem
An error here usually means that the program did not estimate the
filesystem size correctly.  Please read the BUGS section of the manpage.
tar_in: tar subcommand failed on directory: /: tar: test.file: Cannot write: No 
space left on device
tar: Exiting with failure status due to previous errors at ./virt-make-fs line 5
33.
FAIL: test-virt-make-fs.sh


Version-Release number of selected component (if applicable):

1.19.8