Option 1 is possible (you can download and compile qemu for ppc) so I have provided it to the consumer as a workaround for the time being. Unfortunately, getting this into our build process would be unlikely. So, I need a more permanent solution that will enable storwize-svc on ppc systems without qemu-img installed.
Given that the checks for the image type were removed from the iscsi path, I am assuming you would not want them added back in. Would an alternate solution be for the storwize driver to not use the iscsi code, but instead to implement copy_image_to_volume itself and do the necessary checks there? If so I can put together a patch to implement this.
John,
Option 1 is possible (you can download and compile qemu for ppc) so I have provided it to the consumer as a workaround for the time being. Unfortunately, getting this into our build process would be unlikely. So, I need a more permanent solution that will enable storwize-svc on ppc systems without qemu-img installed.
Given that the checks for the image type were removed from the iscsi path, I am assuming you would not want them added back in. Would an alternate solution be for the storwize driver to not use the iscsi code, but instead to implement copy_image_ to_volume itself and do the necessary checks there? If so I can put together a patch to implement this.