Open etrunko opened 8 years ago
Indeed, hardcoding is unreasonable.
We allow users to specify the path of qemu binary in shared/cfg/base.cfg now. How about add items for qemu library.
qemu_binary = qemu qemu_img_binary = qemu-img qemu_io_binary = qemu-io
You can open a PR including your patch
This patch is a workaround only, a quick hack to make things work as before. Cleber helped me with this one, and I am pretty sure it is not the right way to do it.
On Wed, Nov 9, 2016 at 12:01 AM, Wei Jiangang notifications@github.com wrote:
You can open a PR including your patch
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/avocado-framework/avocado-vt/issues/644#issuecomment-259316493, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzATzVcInWCdoFr5KpR9QXP4GJjNwqAks5q8SlugaJpZM4Jbn3U .
Eduardo de Barros Lima ◤✠◢ eblima@gmail.com
This happens because of hardcoding
LD_LIBRARY_PATH
in functionget_qemu_binary()
, defined in utils_misc.py. This used to work before release 39, but something changed and now an exception is thrown:I don't know avocado deeply enough to say if it is possible to specify the environment variables of a command via configuration, but definitely, hardcoding it in that function seems wrong. I would like to contribute with the fix for this issue, but I would need some pointers of what and how to do it.
I talked to @clebergnu about this problem and he provided a workaround for this problem.
Here is the job.log file.