Deep down debugging the root cause
-----------------------------------
 
Issue
-------
Storage configuration error during Anaconda install while building Fedora Atomic CloudImage locally on armhfp

Error mesage from Anaconda log:
Volume group given physical extent size of "4 MiB", but must be one of: 1024 B"

Code Flow in different projects:
---------------------------------
* anaconda/pyanaconda/kickstart.py: LVMVolumeGroupDevice.get_supported_pe_sizes()
* blivet/devices/lvm.py: return [Size(pe_size) for pe_size in blockdev.lvm.get_supported_pe_sizes()]
* libblockeddev/src/plugins/lvm.c: guint64 *bd_lvm_get_supported_pe_sizes () <----   Python to C ( C Python Binding)
* BlockDev-2.0.typelib gets generated during libblockdev building which contains information on exported function which can be called in other language
* Can be read by converting to gir representation using g-ir-generate command from gobject-introspection
    <function name="lvm_get_supported_pe_sizes" c:identifier="bd_lvm_get_supported_pe_sizes" throws="1">
      <return-value transfer-ownership="full">
        <array zero-terminated="1">
          <type name="guint64"/>
    </function>
* pygobject3/gi/pygi-invoke.c makes call to this function using ffi_call()
* Saves data to be returned to Python in pygiobject3/gi/pygi-array.c: 
   static PyObject * _pygi_marshal_to_py_array()
* One of the possible cause looks to be use of arch dependent data type usage, example:
   unsigned long -  4 byte on 32 bit and 8 byte on 64 bit arches