wget https://drive.google.com/open?id=1F5NydYXACEdhmkyQdF1llfdBWEUjD4rp

QNX4 file system support (read only) - CONFIG_QNX4FS_FS
QNX6 file system support (read only) - CONFIG_QNX6FS_FS

$ file inpu_model_743_B.img 
inpu_model_743_B.img: QEMU QCOW Image (v2), 33554432 bytes

$ man qemu-img
...
       usage: qemu-img command [command options]
...
       convert [-c] [-p] [-q] [-n] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-s snapshot_id_or_name] [-l snapshot_param] [-S sparse_size] filename
...
       filename
            is a disk image filename

       fmt is the disk image format. It is guessed automatically in most cases. See below for a description of the supported disk formats.
...
       convert [-c] [-p] [-n] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-s snapshot_id_or_name] [-l snapshot_param] [-S sparse_size] filename [filename2
       [...]] output_filename
           Convert the disk image filename or a snapshot snapshot_param(snapshot_id_or_name is deprecated) to disk image output_filename using format output_fmt.
           It can be optionally compressed ("-c" option) or use any format specific options like encryption ("-o" option).

           Only the formats "qcow" and "qcow2" support compression. The compression is read-only. It means that if a compressed sector is rewritten, then it is
           rewritten as uncompressed data.

           Image conversion is also useful to get smaller image when using a growable format such as "qcow" or "cow": the empty sectors are detected and suppressed
           from the destination image.

           sparse_size indicates the consecutive number of bytes (defaults to 4k) that must contain only zeros for qemu-img to create a sparse image during
           conversion. If sparse_size is 0, the source will not be scanned for unallocated or zero sectors, and the destination image will always be fully
           allocated.

           You can use the backing_file option to force the output image to be created as a copy on write image of the specified base image; the backing_file
           should have the same content as the input's base image, however the path, image format, etc may differ.

           If the "-n" option is specified, the target volume creation will be skipped. This is useful for formats such as "rbd" if the target volume has already
           been created with site specific options that cannot be supplied through qemu-img.
...

export LIBGUESTFS_DEBUG=1
export LIBGUESTFS_TRACE=1
sudo -E virt-copy-in ...

$ qemu-img info inpu_model_743_B.img 
image: inpu_model_743_B.img
file format: qcow2
virtual size: 32M (33554432 bytes)
disk size: 128M
cluster_size: 65536
Snapshot list:
ID        TAG                 VM SIZE                DATE       VM CLOCK
5         prevvw                  23M 2014-10-09 13:43:34   00:02:20.697
4         prevvm                  22M 2017-07-07 12:41:35   00:00:43.582
3         lastvm                  23M 2017-07-07 12:48:25   00:00:32.592
Format specific information:
    compat: 0.10

$ qemu-img convert -f qcow2 -O raw inpu_model_743_B.img inpu_model_743_B.raw

$ qemu-img info inpu_model_743_B.raw
image: inpu_model_743_B.raw
file format: raw
virtual size: 32M (33554432 bytes)
disk size: 31M

$ sudo fdisk -l inpu_model_743_B.raw 

Disk inpu_model_743_B.raw: 33 MB, 33554432 bytes
16 heads, 63 sectors/track, 65 cylinders, total 65536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

               Device Boot      Start         End      Blocks   Id  System
inpu_model_743_B.raw1   *          63       65519       32728+  4f  QNX4.x 3rd part

$ sudo mkdir -pv /mnt/test
$ sudo mount inpu_model_743_B.raw /mnt/test -o loop,ro,offset=32256 -t qnx4
$ cd /mnt/test